You Standardised the Brochure. Not the Engine.
Written and narrated by Serguei Poppeleer.
Everyone told us to productise. So we built a standard scope, a standard fee, a standard proposal. Sales got faster. Delivery got weaker.
We had standardised the brochure and left the engine bespoke. So we won more of exactly the work we could not deliver repeatably, and every new client still hit a system we rebuilt from scratch behind the scenes.
Standardising what you sell while the way you deliver stays improvised is how you scale your weakest point.
We just need to standardise our offering
The offering was never the hard part. Clients do not churn because your proposal was not templated. They churn because delivery was inconsistent, because the governance, the decision protocol, the cadence changed depending on who was running it. The repeatable thing has to be the engine, not the packaging.
Standardise the system, not the service. The brochure is not the bottleneck. The engine is.
Productise the delivery architecture
What should be identical across every job is how delivery runs: how scope is contained, how the plan is shaped, how decisions close, how dates are verified, how the cadence beats. The 5Cs are that architecture. The deliverable can be as bespoke as the client needs. The system underneath it never changes.
Across twenty years of property delivery for a major international organisation, the buildings were all different. The method was not. The same architecture ran every project, which is why it stayed on time, often early, and under budget regardless of who held the pen. The bespoke part was the output. The standard part was the engine.
That is the move most firms get backwards. Flex the output. Freeze the system.
List what genuinely changes per client. It is the output. Almost never the way you run it.
The 5Cs as your standard operating architecture, applied identically, whatever the job.
A templated proposal that feeds an improvised delivery just sells your problem faster.
Clients pay a premium for it-will-run-the-same-way-every-time. That is the thing to productise.
Every client's needs are different. Every client's delivery should feel reassuringly the same. That contrast is your edge.
Rigid is improvising under pressure. A standard architecture is what lets you flex the output without the whole thing wobbling.
Your value is a bespoke result delivered by a system clients can trust. Drop the second half and you are just expensive and inconsistent.
AI can template and personalise the service layer endlessly — proposals, scopes, reports, in your voice, in minutes. What it cannot do is make delivery repeatable if the architecture underneath is improvised. Standardise the engine yourself; let AI mass-produce the surface. Do it the other way round and you have just automated the wrong thing.
You do not scale by selling the same thing. You scale by delivering it the same way, every time, regardless of who is holding it.
Find where delivery still depends on you.
Get your Delivery Score. Fifteen Yes/No questions, about four minutes. It shows which of the five controls is weakest as you scale.