Founder-First Delegation Rule
Master a new growth process before handing it to the team
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 91%
The Founder-First Delegation Rule says that a founder should personally execute and understand a new growth process before systematizing it or assigning it to a team. When a pipeline, sales motion, or offer is still full of major unknowns, meetings cannot substitute for the decisions and firsthand learning only the founder can provide. The founder works through initial cases, discovers what succeeds, resolves ambiguities, and defines the standards that later become training and documentation. Once the process is understood and produces repeatable outcomes, another person can replace the founder in day-to-day execution. The rule is explicitly stage-dependent: it applies most strongly while scaling a founder-led business from roughly two to five million, not necessarily to a chief executive running a mature $50 million company.
Origin
Jasmine articulated the rule while discussing how she advised a founder to systematize sales and how she personally designed a missing customer pipeline. Extracted from The Jasmine Star Show.
Core principles
- 01A team cannot reliably inherit a process the founder does not yet understand.
- 02Early-stage system building often contains questions only the CEO can answer.
- 03Direct execution exposes the patterns, exceptions, and standards needed for delegation.
- 04Delegation should follow initial mastery rather than replace discovery.
How to run it
- 1
Select the Process
Choose a growth activity that needs to become systematic, such as sales, lead cultivation, or offer delivery. Define the outcome the process must reliably create.
Pro tip Start with one commercially important process rather than attempting to systematize the entire company.
Watch out Do not delegate merely because you are eager to hire someone.
- 2
Resolve Founder-Level Questions
Identify decisions about customers, positioning, offers, and standards that only the founder can currently answer. Use uninterrupted thinking time rather than defaulting to another team meeting.
Pro tip Write down every major question mark before beginning execution.
Watch out A team cannot compensate for strategic ambiguity at the top.
- 3
Execute Real Cases
Perform the work personally and observe where the process succeeds, stalls, or requires judgment. Continue until the important patterns and exceptions are visible.
Pro tip Capture decisions and adjustments while performing the work, not weeks afterward.
Watch out One successful attempt is not enough evidence of a repeatable process.
- 4
Codify the Pattern
Turn firsthand learning into a workflow, standards, examples, and expected outcomes. Make tacit founder judgment explicit enough for someone else to apply.
Pro tip Include examples of unacceptable and excellent output.
Watch out A checklist without decision criteria may document activity without preserving quality.
- 5
Transfer and Review
Assign the process to a suitable team member and observe early executions. Reduce oversight as their output converges with the established standard.
Pro tip Use short feedback loops during the first several repetitions.
Watch out Do not remain the permanent operator once the process is stable and transferable.
In the wild
Jasmine's product ladder had a $59 offer, a $2,000 offer, and a $25,000 offer, leaving major gaps for customers progressing toward seven figures. She used founder-level reflection to define intermediate programs, audiences, delivery models, and the pathway toward a first million before turning execution into a broader team system.
→ The company developed a more coherent customer journey rather than building funnels around an incomplete product suite.
Common mistakes
Delegating Discovery
Assigning an undefined process to a team forces employees to guess at strategy while the founder remains dissatisfied with execution.
Scaling Before Proving
Documenting and staffing a process before real cases validate it can multiply a flawed approach.
Refusing to Let Go
Founder-first does not mean founder-forever. Once the system is understood and a capable owner is performing it well, continued control becomes a bottleneck.
Is it for you?
Best for
It is best for founder-led companies building a new sales, marketing, or delivery system while scaling through the low single-digit millions.
Not ideal for
It is not ideal for mature organizations where specialist leaders already possess deeper domain mastery than the CEO.
From the transcript
“And I'm like, you got to do it first. Like do it first to turn it over to the sales team.”
“If you have not done it and mastered it and know it.”
“And so as we were thinking out a pipeline, there was too many big question marks that only the CEO could answer.”
From the episode
The Power of Blank Space: How I Doubled My Growth by Doing Less