Field Note · People, teams, and operating leverage
Why Founders Should Hand Off Delivery Before Sales
A service is not scalable because the founder has documented it. It becomes scalable when someone else can run the full playbook, another person can check it, and the client still receives work the business is willing to stand behind.
A thinking frame by Andrew Moss
The questions I get
Usually some version of these:
- Should I hire a salesperson so I can stop selling?
- How do I scale delivery when clients believe they are buying me?
- What should be documented before the next growth hire?
What a lot of people seem to think
More sales and a documented process are often treated as proof that an expert practice is ready to scale. A niche is then defined by an industry label, even when every engagement still requires a different operating playbook.
How I look at it
I would hand off delivery before sales and define the segment operationally. The segment is the group for whom the same end-to-end playbook, handoffs, evidence, and quality check work. Repeatable means the founder can do it again. Scalable means someone else can run it, someone else can check it, and the founder does not need to rescue the outcome.
Why the decision matters
The cost is rarely confined to the line item.
If the sequence is wrong
Sales adds demand to a founder-dependent delivery system. More clients increase exceptions, review, and hidden rework until the expert becomes the bottleneck at a larger scale.
If the sequence is right
The company proves one full playbook in a coherent segment, builds run-and-check capacity, and adds demand only after delivery can absorb it.
How reversible is it?
Moderate before hiring and customer commitments; low once reputation, team capacity, and contracts depend on growth the delivery system cannot support.
The short answer
Prove the full playbook before adding demand.
Choose a segment where the same client problem, inputs, sequence, outputs, handoffs, and quality standard recur. Let one person run the work and another check it. Fix the exceptions the founder still has to rescue. Then decide how much sales capacity the system can responsibly absorb.
Two different testsRepeatable by the founder is not yet scalable by the business.
A recipe is repeatable when the chef can make it again. A restaurant is scalable only when the kitchen, service, quality check, and recovery path work through other people during a busy night.
Move fromA documented founder method→Move towardA run-and-check delivery system
The order I would use
Take the right steps in the right order.
- 01
Define the segment by the full playbook
Group clients only when the same problem, source inputs, sequence, outputs, handoffs, exceptions, and proof standard genuinely apply.
- 02
Make the work observable
Document decisions, artifacts, quality criteria, escalation points, and the context the founder normally carries invisibly.
- 03
Let someone else run it
Start with a bounded engagement the delivery team can own without the founder quietly doing the hard parts.
- 04
Let someone else check it
Build a review standard that catches consequential errors and teaches the operator why the work passes or fails.
- 05
Count rescues and exceptions
Every founder rescue is evidence that the playbook, segment, authority, or training is still incomplete.
- 06
Add sales against proven capacity
Grow demand only when delivery quality, owner load, throughput, economics, and recovery paths can support it.
Questions worth answering
Before the next irreversible move:
- For which clients does the same full playbook actually work?
- Can someone else run it without hidden founder labor?
- Can another person check the result against an explicit standard?
- Which exceptions still collapse back to the founder?
- How much new demand can the current system absorb without degrading trust?
What not to do
Do not sell a playbook that still depends on invisible heroics.
Do not call an industry label a segment when the work differs end to end. Do not document only the easy middle and leave diagnosis, exceptions, quality, and client trust with the founder. Do not hire sales into capacity that does not exist.
Keep the perspective
Delivery infrastructure is what compounds.
Sales can fill a pipeline. A proven run-and-check system creates capacity, learning, and confidence that the next client can be served without asking the founder to become two people.
Common follow-up questions
Does the founder stop selling entirely?
Not necessarily. Founder judgment and relationships may remain central to complex sales while routine discovery, qualification, and follow-through become transferable.
Should delivery always be hired first?
No. The sequence depends on capacity, demand, margins, work type, and current team. The point is to avoid accelerating demand into a founder-only delivery system.