Production cannot start on a fuzzy yes.

A working sample-and-approval gate, laid over how you already run — email, spreadsheets, Drive. Not a factory ERP. Not a free pilot. One slice of your flow, built properly, in weeks.

Fixed

Before we start

Live in

2–4 weeks

Your data

Stays yours

Read this first

Have we built this for a private-label beauty manufacturer before? Not yet. We have built and we still run production systems for manufacturers in other regulated categories — procurement through dispatch, batch records, approvals, audit trails — and those clients are under NDA, so we cannot show you their screens or name them.

What that means for you: we know the machinery, we do not yet know your category’s quirks, and the fixed price is what protects you from us learning on your budget.

01 — Where the money actually goes

Not on the filler line. In the week nobody logged.

Nobody loses a project on the manufacturing. It goes in the coordination — the rounds, the re-asks, the version somebody approved in a reply that is now four threads deep. Five questions that should take a second each:

Which sample did they actually approve?Round three or the tweak they asked for after round three.

Who asked for the change, and when?Their marketing lead, on a call, and your chemist heard it secondhand.

Is the artwork on this run the version legal signed off?Or the one that came back with the ingredient line edited.

Did they accept the price at this quantity?Agreed at 25,000 units, and the order came in at 8,000 at the same number.

Are the components actually here?Everything approved, everything scheduled, and the caps land in a fortnight.

02 — The mechanism

Approval-Gated Handoff

One rule, and everything else on this page is a consequence of it.

A job cannot be marked production-ready until every gate carries a name and a date.

01
Formula and sample approved — which version, by whom
02
Price accepted — at this quantity, not a previous one
03
Artwork locked — the file, not the conversation about the file
04
Packaging available — on the floor, not on a PO
05
Required documents in — whatever your category needs

Note what this is not. It is not a report — reports arrive after the handoff. It is not a reminder — reminders go to someone who is not the person deciding. It is a gate, at the one moment the decision is being made, and it can be overridden by a named human who then owns that call. The point is never to block work. The point is that “we thought it was approved” stops being a sentence anyone can say.

03 — The slice

One plant, one team path, said out loud

Scoped before we start and priced before we start. If it grows mid-build, we quote the growth — we do not absorb it quietly and deliver late.

In

A project board for live client jobs — one plant, one team path
Sample and formula version history, with who approved which version
Artwork and packaging approval trail — versions and named sign-off
The production-readiness gate itself
One read-only path in from what you already keep — export, sheet or Drive
A screen-share walkthrough with the people who will actually use it
Thirty days of care after launch, and we train your office ourselves

Out — said up front

Replacing your ERP, batching or inventory system
Multi-site
EDI and custom integrations
Unlimited brand portals, every SKU
AI that approves a formula, certifies safety, or releases production — humans decide, the system records
Any claim that this makes you compliant. It makes records organised, traceable and inspection-ready, which is a different sentence

04 — How it goes

Four steps, no surprises

Step one

Twenty minutes, questions only

No demo, no deck. We ask how a job actually moves through your place and where it stalls. If nothing stalls, we say so and you have lost twenty minutes.

Step two

You see it working, on invented data

Only if you ask. A fictional manufacturer, fictional brands, the real mechanism. We never put your formulas or artwork into anything before an NDA and a kickoff.

Step three

A fixed quote, for one bleeding workflow

We pick the single flow costing you the most and scope only that. Half up front. The clock starts when your data arrives in the shape we specified, not at signature.

Step four

Live, then trained, then thirty days of care

Training is not a courtesy at the end. It is the part that decides whether any of this survives contact with a busy week, so we do it ourselves.

05 — After it is live

The build stands on its own

Thirty days of care come with every build — that is a support window while your office settles into it, not a promise about outcomes. After that, care is optional and month to month, and it only starts if you are actually using the thing daily.

We do not need you on a retainer for the build to have been worth it. If it runs quietly and you never want to hear from us again, that is a fine outcome and you should not be paying us for it.