Productised consulting promises the appeal of recurring revenue without the chaos of custom projects. Fixed scope, fixed price, repeatable delivery. The pitch is seductive: package your expertise once, sell it many times, reclaim your calendar.
But most solo operators who try it discover the same problem six months in: the parts they productised are the parts that needed to stay flexible. The parts they left manual are the ones begging for systems. The model doesn’t break because productisation is flawed—it breaks because operators template the wrong layer.
The standard productisation mistake
The typical approach goes like this: take your most popular consulting engagement, strip out the variability, write a scope document, set a flat fee, and launch a landing page. A website audit for $1,500. A content strategy sprint for $3,000. An email migration package for $2,200.
It works for the first three clients. Then client four has a WordPress multisite setup your checklist didn’t account for. Client five wants Slack check-ins instead of email updates. Client six needs the deliverable two weeks early because they’re launching a product.
You say yes because you need the revenue. You carve out exceptions. You adjust timelines. You rewrite sections of the template. Within two months, every engagement is a special case again, and you’re back to running a custom consulting practice with a productised label and a fixed price that no longer covers your time.
What to productise: delivery infrastructure, not scope
The fix is inverting the template. Don’t productise the scope—productise the scaffolding that makes delivery predictable.
Productise your onboarding sequence: the intake form, the kickoff email, the Notion workspace structure, the Loom walkthrough you send on day one. Productise your communication cadence: update emails every Monday and Thursday, decision points flagged 48 hours in advance, async video reviews instead of meetings. Productise your handoff: the same Notion deliverable template, the same export format, the same two-week support window post-delivery.
Let the scope flex. A site audit might include four pages for one client and forty for another. A content strategy might cover SEO for one operator and lead magnets for another. That variance is fine—it’s why clients hire you instead of buying a course. But if every client goes through the same onboarding, gets updates on the same schedule, and receives their deliverable in the same format, you’ve productised the part that actually creates leverage.
This is how agencies scale without turning into workflow chaos. It’s also how solo operators can take on more clients without proportionally increasing coordination overhead.
The second-order benefit: pricing becomes modular
When you productise delivery instead of scope, pricing becomes easier to defend and easier to scale. Instead of a single flat fee, you can price along two axes: scope complexity and delivery speed.
A basic website audit with standard delivery might be $1,200. The same audit with a 48-hour turnaround adds $600. An audit covering multisite, headless CMS, and API integrations adds another $900. The client picks the scope; you control the delivery cost by keeping the process identical across all tiers.
This also solves the “I need it faster” problem. Clients who want to jump the queue pay for it. Clients who are fine with standard timelines get the lower price. You’re not discounting for flexibility—you’re charging for constraints.
It’s the same reason Postmark charges per email sent, not per “email strategy.” The infrastructure is productised; the volume is variable.
When to stick with fully productised scope anyway
There are cases where locking down scope still makes sense. If your service is diagnostic—like a technical SEO audit or a site-speed analysis—the inputs are predictable enough that a checklist works. If your market is early-stage operators who don’t yet have complex infrastructure, variability stays low.
But even then, the operators who run these services successfully are still productising delivery. The audit might be the same 40-point checklist every time, but the Loom walkthrough, the Notion handoff doc, and the two-week Q&A window are what make it repeatable.
If you’re spending more time customising the template than you’d spend scoping a custom project, your productisation is backwards.
The goal isn’t to eliminate variability. It’s to move variability into the part of the engagement where your expertise adds value—and to eliminate it everywhere else.
Want more breakdowns on what works (and what doesn’t) when you’re running a content-driven business solo? Subscribe to One Two Three Send and get one focused article like this in your inbox each week.