Part III · Sell, Deliver, and Compete — Chapter 21
Productize, systemize, and scale
Scale is not “more.” It is repeatable value delivered with controlled quality, economics, and decreasing dependence on founder heroics.
Do not scale confusion. First find repetition.
Capture the repeated path
After several similar customers, map:
1. qualification; 2. proposal and contracting;
3. data/access collection; 4. onboarding; 5. core delivery steps; 6. quality checks and exception handling; 7. customer communication; 8. invoicing and collection;
9. renewal, expansion, or exit.
For each step, record owner, input, output, standard, tool, time, failure modes, and escalation. A useful process makes judgment visible; it does not reduce people to robots.
The leverage order
Use this sequence:
1. Eliminate work that creates no customer value or necessary control. 2. Simplify unnecessary options and hand-offs.
3. Standardize the reliable path and quality floor. 4. Automate stable, understood repetition. 5. Delegate with outcome, authority, resources, and feedback. 6. Instrument so performance and failure are visible.
Automating a broken process makes mistakes faster. Hiring into chaos transfers confusion and adds payroll.
Know when to productize
Productization becomes attractive when:
- • multiple customers need substantially the same outcome;
- • 70–80% of delivery can follow a common path;
- • variations can be configured rather than reinvented;
- • the standardized scope remains valuable;
- • customers accept the boundaries;
- • the margin and quality improve;
- • support burden does not erase leverage.
Keep exceptions priced and controlled. A “standard” offer that accepts every custom request is only an agency with hidden complexity.
Scale through four engines
| Engine | Question | Proof |
|---|---|---|
| Product / delivery | Does the customer receive the promised result reliably? | Retention, quality, time to value |
| Distribution / sales | Can suitable customers be acquired predictably? | Conversion, acquisition cost, sales cycle |
| Operations | Can work flow without founder memory? | On-time delivery, documented control, lower rework |
| People | Can capable owners make decisions at the right level? | Clear accountability, bench strength, improvement |
Growth is limited by the weakest engine. Adding leads when delivery is broken creates faster churn. Hiring delivery when no repeatable demand exists creates idle cost. Diagnose the constraint each quarter.
The founder’s changing job
Do → Document → Delegate → Manage systems → Build leaders → Allocate capital
Do not cling to being the hero. The company cannot become more capable than the amount of responsibility you are willing to transfer with clarity.
· GE ch. 18; TABLE pp. 37–50; LG pp. 100–109. Mechanisms paraphrased; judgment and examples are labelled.