Skip to content

Pricing a white-label certification service

By VeriScripts · Reviewed by Jerome T. · · 7 min read

Key takeaways

  • The margin in a resold certification service is not in the filing. It is in intake quality, reuse across files and rework you avoided.
  • A fixed fee is the right shape for the client and only safe for you if the rework loop is explicitly bounded in the contract.
  • Cost per file is a distribution, not an average. Price against the tail — the file that generates several rounds of follow-up — or the tail eats the book.
  • Renewals should be priced and contracted at the point of first sale, because after approval the client's perceived value of the work collapses.

Most agencies price certification work by estimating how long the application takes to complete and adding a markup. That produces a number, and the number is almost always wrong, because the application is the smallest and most predictable part of the job.

The cost you actually carry is the chasing, the reconciliation between what the client told you and what their website says, the follow-up rounds after submission, and the elapsed weeks during which somebody has to hold the file in mind. None of that scales with the length of the form, and all of it varies enormously between clients who look identical at sale.

This is written for operators reselling certification work — agencies, platforms and MSOs putting their own name on it. If you are buying certification for your own business, you want a price, not a pricing model, and this is not the post for that.

The filing is not where the margin sits

Two agencies can do identical filing work and have completely different economics. The difference is upstream.

Consider the same client arriving two ways. In the first, intake is a shared document and a kick-off call, and over the following month you discover the pharmacy agreement is out of date, the licensure list is missing a state, and the site describes a product they no longer sell. Each discovery is an email, a wait and a context switch. In the second, structured intake surfaced all three on day one and the client fixed them in one sitting, because they were asked once.

The filing labour is the same in both. The cost is not close. That gap — not your hourly rate, not your reviewer's speed — is your margin, which is why document collection is the real bottleneck is a pricing argument as much as an operational one.

The same logic applies to reuse. The second file for a client with three brands should cost meaningfully less than the first. If your system cannot reuse what the first one produced, you are pricing every file as a first file and losing the compounding advantage of a portfolio.

Fixed fee is the right shape, with one condition

Clients want a number. They are buying a defined outcome with an uncertain path, and a per-hour arrangement asks them to audit work they are not equipped to assess. Time and materials also reads as a penalty for their own disorganisation: the more trouble the file gives you, the more they pay.

Fixed fee is therefore right, and it is only safe if the rework loop is bounded. Bounding is a contract question, not a pricing one. Name what the fee covers — preparation, submission, and a stated number of rounds of response — and name what sits outside it: a material change in the client's business mid-file, a resubmission driven by facts they did not disclose, any response round beyond the stated number.

Agencies resist this because it feels like hedging in a sales conversation. It is the opposite. An unbounded fixed fee is a promise you will quietly break by deprioritising the file that has stopped being profitable, and the client notices that long before they would have noticed a clause.

Price against the tail, not the average

Certification files do not cluster around a mean. Most are unremarkable. A minority generate several rounds of follow-up, a document nobody can locate, and a client contact who changes jobs halfway through. Price at the average and that minority is funded out of your margin on the routine files — which works while your book is small and your sample is lucky, and stops working at the exact moment you scale.

Two adjustments make this manageable. Set the fixed fee above the median rather than at it, and accept that easy files are unusually profitable — that is the point. Then price a small number of well-defined variables separately: additional brands, additional entities, a catalogue that spans several categories. Those genuinely predict cost, and clients accept them because they can see the difference. Avoid anything they cannot verify; a complexity surcharge assessed after you have looked at their business reads as bait and switch even when the assessment is correct.

The retainer belongs to the part that never ends

The filing has an end. The compliance posture does not, and that is where recurring revenue actually lives.

A client whose certification is granted still changes their catalogue, still redesigns their site, still adds a state, still swaps payment provider. Any of those can put the record out of step with what was submitted. Somebody has to notice. That work is continuous, low-intensity and well suited to a monthly fee, and it is the reason monitoring a certified portfolio for drift is a commercial subject rather than a technical one.

Sell it alongside the filing rather than after it. The moment of maximum perceived value is before approval, while the client is anxious and engaged. After it they have a certificate and a belief that the matter is closed, and a retainer proposed then sounds like an upsell on something they consider finished.

Price the renewal at the first sale

The renewal is the most commonly given-away piece of a certification service line, usually to close the initial deal. It is also the piece that most reliably becomes unprofitable work you resent doing.

A renewal on a well-maintained record is genuinely lighter than a first filing, and it should cost the client less. It is not free: somebody still has to confirm that what was true at submission is still true and gather anything that has changed. On a record neglected for a year, a renewal is not lighter at all — it is a first filing with a deadline attached.

The clean structure is to sell the renewal inside an ongoing arrangement that includes the monitoring keeping the record current. The incentives align: you are paid continuously for the work that makes the annual event cheap, and the client gets a renewal that is not a fire drill. Doing that across a book is its own discipline, which managing certification renewals across a portfolio goes into.

What to publish and what to quote

Publishing a price disqualifies the wrong clients before they reach a call, which is worth more than the flexibility you give up. It also anchors the conversation, and the anchor matters because most buyers have no reference point for what this work costs.

Anchor the number you publish to your own delivered cost rather than to whatever else is visible on the market. A competitor's list price tells you nothing about their intake quality, their rework rate or what they include after submission, so setting yours against it hands your margin to a stranger's cost structure. Work out what a file costs you to deliver, decide what the service around it is worth, and publish that.

Quote rather than publish where the variables are real: multi-entity groups, portfolios arriving in a batch, partners sending files through an API. Those are different products, and treating them as one product with a discount attached prices complex work as though it were simple.

You cannot mark up a cost you have never measured

You cannot price a resold service without knowing what delivery costs you, and most agencies do not, because the cost is spread across account managers, chasing and elapsed weeks that never hit a timesheet. Three numbers out of your own book replace the guess.

The median file. Take the last ten or twenty you delivered, count the hours actually spent on each between signature and submission — chasing, re-reads and internal check-ins included, not only drafting — and find the middle one.

The tail file. From the same sample take the worst one and express it as a multiple of the median; the multiple matters more than the hours, because it says how much headroom the fixed fee needs. Then work out how often that file turns up — one in five, one in ten — and carry that share of it on top of the median. What you are left with is the cost of a typical file including its share of the expensive ones.

The reuse multiplier. When an existing client brings a second brand, measure the second file as a fraction of the first. On a well-kept record it should be a small fraction, because the licensure evidence, the corporate documents and most of the policy language are already in your possession. If the second costs what the first did, your storage is a folder rather than a record, and you pay for that in every quote after it.

Underneath the three sits a floor you can compute before you quote: a fixed platform licence plus a known per-case charge, with intake supervision rather than the file itself left on your side. That is what the VeriScripts platform gives you — structured intake, explicit per-file status and reusable client records, priced as a licence plus a per-case fee, so the figure you mark up is measured rather than assumed. If you have one client asking rather than a book of them, our done-for-you service files it and you can decide about the service line later.

Frequently asked

Should we charge a fixed fee or a monthly retainer for certification work?
Fixed fee for the filing itself, retainer for everything around it. Clients want a single number for a defined outcome, and a per-hour arrangement invites them to audit your time on work they cannot assess. The retainer belongs to the ongoing part: monitoring the site for drift, handling catalogue changes, keeping documents current and running the renewal. Selling both at once is cleaner than selling the filing and then trying to introduce a retainer after approval, when perceived urgency is at its lowest.
How do we stop rework destroying a fixed price?
Bound it in the contract and reduce it in the process. Bounding means naming what the fee buys — preparation, submission and a stated number of response rounds — and naming what falls outside: further rounds, or a shift in what the client sells or how they are structured while the file is open. Reducing it means moving discovery forward, so a contradiction costs the client a few minutes at intake instead of a fortnight of elapsed time later. Most fixed-fee losses trace back to a question nobody asked at the start rather than to anything that happened at the filing itself.
How should we price a renewal compared with the initial filing?
Lower than the first filing, but never free, and agreed before the first filing is delivered. A renewal is genuinely less work when the record is current, which is exactly why it should be sold with the monitoring that keeps it current rather than as a standalone event. If you give the renewal away to close the first sale, you have created an annual obligation with no revenue attached to it, and it will be the work that gets deprioritised when your book grows.

Keep reading

Filing one application, or a hundred?

The platform is for teams running certifications for their own clients. If you only need your own business certified, our done-for-you service files it end to end at a published price.