Productised-services delivery quality at scale

The role transitions at each stage

Founder + 1: founder delivers most; new hire shadows for first 3-5 engagements, then takes on the 80% repeatable work. Founder reviews everything.

Founder + 2-3: founder delivers 20-30% (the harder / strategic engagements); team delivers 70-80%. Founder still reviews everything but selectively (sample 50% of deliverables, focus on first engagement per new client).

Founder + 4-5: founder doesn't deliver, only reviews. A delivery lead emerges from the team — most-experienced contributor takes responsibility for quality, founder does final sign-off on customer-facing materials.

The transition between each stage is the dangerous moment. Founders who don't promote the delivery lead by team-of-4 end up as the bottleneck and the team plateaus.

The QA pattern that actually works

For each engagement, a two-tier review:

• Producer review (the team member who built it): self-checks against playbook + checklist.
• QA review (founder or delivery lead): independent sample-check of finalised deliverable. Catches voice / depth / accuracy issues the producer missed.

QA review takes 20-30% of the engagement's production time. Founders try to skip it; that's how quality drifts.

The QA reviewer's job is not to perfect the deliverable; it's to identify what to fix and route the work back. Don't fix it for the producer — that prevents the producer from learning.

What kills quality at scale

• Hiring fast without playbook discipline. New team members produce work that drifts from brand voice. The playbook gap shows up as customer complaints 4-6 weeks later.
• Skipping QA to ship faster. Speed kills quality kills retention. A 15% delivery-time increase from QA gates produces 30%+ better customer outcomes.
• Letting clients dictate scope mid-engagement. Every "can you also do this?" without a Change Request degrades the productised shape. Hold the line.
• Different team members using different tools. Standardise on one stack for each engagement type. Five team members each in their preferred CMS is unmaintainable.

What to instrument

• Deliverable rejection / revision rate. What % of deliverables come back for changes after QA? Above 25% means your playbook is broken; below 5% means QA isn't catching enough.
• Customer-reported quality issues per engagement. Track per team member. Outliers identify training needs.
• Time-to-delivery vs scoped time. Engagements consistently going long mean scope is too vague or the playbook is missing steps.
• NPS at engagement close. Per team member. The data is noisy but trends are real.

What to do today

1. Audit your current playbook. Is it written down, or in the founder's head? If the latter, your team-of-3 problem is approaching.
2. Pick one productised offer and write the full delivery playbook this month. 8-12 hours of focused work.
3. Add a QA gate. If you don't have one, you're shipping inconsistent work.
4. Identify your future delivery lead from the current team. Start handing them more review responsibility now, before you need them at team-of-4.