Everything I know about business
๐งต [Mega-thread] Everything I know about business:
Lessons and mental models for building businesses and companies.
Mainly a summary of Alex Hormozi's strategy. A repeatable system anyone can use to scale their business.
Warning: it's very long.
If you want the text ready to copy into your AI agent, leave me a comment ๐ฌ
The whole system can be summed up like this:
1๏ธโฃ Choose a goal
2๏ธโฃ Map the business
3๏ธโฃ Find the constraint
4๏ธโฃ Fix the constraint
5๏ธโฃ Scale what works
6๏ธโฃ Standardize it
7๏ธโฃ Delegate it
8๏ธโฃ Find the next constraint
9๏ธโฃ โฆand start again
The hard part isn't learning another tactic. It's correctly identifying what matters now and ignoring everything else.
Part 1: PREPARATION โ
1. What scaling really means
Scaling doesn't simply mean increasing revenue.
A business scales when it can increase the number of customers it serves and the profit it generates without causing a proportional increase in founder involvement (your time), costs, complexity, customer complaints, etc....
A business that doubles revenue but triples its headcount, destroys margins, increases churn, and forces the founder (you) to work twice as much.
It has grown, sure, but it hasn't scaled well.
A good north star is:
๐ค Profitable customers retained per period
This combines four things that revenue alone hides:
๐งฒ You acquire customers.
๐ Customers actually buy.
๐ Customers get enough value to stay.
๐ฐ The company makes money serving them.
Growth can be boiled down to three major levers:
โ Get more customers
โ Make each customer worth more
โ Keep customers for longer
Ultimately, everything else should support one of those three outcomes or reduce the risk of them stopping.
2. Apply the framework to one project at a time
Every business has a constraint.
A portfolio of businesses also has a constraint, which will usually be one of these:
๐ your attention
๐ฐ your available capital
๐ฅ your ability to hire operators
๐ ๏ธ your technical ability
๐ฃ your distribution
โ๏ธ your risk tolerance
Don't try to find and solve the constraint for five projects at the same time.
For each operating cycle, choose:
โ One main project that gets most of your attention
โ One proven project that stays in maintenance mode
โ At most, one small exploratory bet
Within each project, identify just one primary constraint.
You can run several projects. You can't aggressively transform all of them at once without fragmenting your efforts.
Part 2: IDENTIFY THE STAGE OF THE BUSINESS โ
The right constraint depends on the stage the business is at.
There are 10 stages: Discover, Monetize, Acquire, Stabilize, Focus, Productize, Optimize, Organize, Specialize, and Capitalize.
The sequence is what matters:
Learn manually โ prove monetization โ generate demand โ stabilize delivery โ focus โ productize โ optimize โ organize โ specialize โ allocate capital and build lasting enterprise value.
Use this practical interpretation:
1. ๐ Discover - Is there a genuinely painful problem for a specific buyer?
โ Typical mistake: Building a huge product.
2. ๐ฐ Monetize - Will they pay for the outcome?
โ Typical mistake: Branding, automation, hiring.
3. ๐ฃ Acquire - Can we generate qualified opportunities repeatably?
โ Typical mistake: Opening five channels at once.
4. โ๏ธ Stabilize - Question: Can we serve customers consistently?
โ Typical mistake: Buying a lot more traffic.
5. ๐ฏ Focus - Which avatar, offer, and channel should we focus on?
โ Typical mistake: Adding more products.
6. ๐ฆ Productize - Can delivery be carried out with a repeatable system?
โ Typical mistake: Hiring without a process.
7. ๐ Optimize - Can we improve margin, conversion, retention, and capacity?
โ Typical mistake: Constantly reinventing everything.
8. ๐๏ธ Organize - Can functions operate with clear owners?
โ Typical mistake: The founder approving everything.
9. ๐งโ๐ง Specialize - Would more specialized roles outperform generalists?
โ Typical mistake: Creating unnecessary management.
10. ๐ธ Capitalize - Where should the next unit of money and attention go?
โ Typical mistake: Diversifying before mastering the core.
The stage rule:
โ Don't solve a problem from a stage you haven't reached yet.
Part III: DEFINE THE OUTCOME โ
Choose one business goal for the next 90 days
A constraint only exists in relation to a goal.
Bad goals:
โ Improve marketing
โ Improve the product
โ Grow on social media
โ Add AI
Better goals:
โ
Increase monthly profit from โฌ20,000 to โฌ35,000.
โ
Increase retained paying customers from 500 to 750.
โ
Reduce customer acquisition payback from nine months to five.
โ
Reduce monthly churn from 6% to 3%.
The template is:
Increase [business outcome]
from [current baseline]
to [target]
by [date]
without worsening [guardrails].
Example:
Increase profitable customers retained
from 100 to 150 per month
within 90 days
without reducing gross margin below 65%
or increasing first response time beyond four hours.
It's important to separate the outcome from the method!
The goal isn't: "Hire three salespeople."
Hiring is an intervention.
The real goal could be: "Increase completed sales from 40 to 70 per month."
Maybe hiring is the right move.
But maybe the real problem is:
โ Lead quality
โ Sales rep utilization
โ Follow-up
โ Pricing
โ Poor qualification
Never put the proposed solution inside the goal.
Part IV: MAP THE BUSINESS โ
Write out the complete system from left to right
Almost any business can be represented like this:
Market
โ Offer
โ Attention
โ Lead
โ Sales conversation or checkout
โ Payment
โ Onboarding
โ Delivery
โ Customer outcome
โ Retention
โ Expansion
โ Referrals
Different business models use different labels.
๐ผ Services
Lead โ appointment โ show-up โ sale โ payment โ service โ renewal/referral
๐ป SaaS
Visitor โ signup โ activation โ paid conversion โ retention โ expansion
๐ E-commerce
Visitor โ product โ cart โ checkout โ delivery โ repeat purchase
๐ค Marketplace
Supply โ demand โ match โ transaction โ successful fulfillment โ repeat
For each stage, measure:
๐ฅ Input volume
๐ฏ Conversion rate
โฑ๏ธ Cycle time
๐ก๏ธ Safe capacity
๐ฐ Cost
โ
Quality
๐ค Owner
The basic funnel equation
End customers = Initial opportunities ร conversion rate at each stage
Example:
10,000 visitors
ร 5% convert into leads
ร 20% book
ร 70% show up
ร 30% buy
= 21 customers
Improving the percentage that looks lowest isn't automatically the right move.
A stage is only the constraint if improving it increases the system's final output.
There's no point widening the mouth of a pipe if there's a bottleneck further upstream.
Part V: FIND THE CONSTRAINT โ
Start with this test:
"If we doubled our advertising, outreach, content, or other demand-generating activity tomorrow, could we properly serve the additional customers?"
- If doubling demand creates operational chaos, you have a supply/capacity constraint.
- If the business could comfortably serve those additional customers, you have a demand constraint.
A supply constraint usually shows up in:
โ Inventory
โ Equipment
โ Qualified staff
โ Onboarding
โ Fulfillment
โ Customer support
โ Management
โ Working capital
โ Founder availability (your time)
A demand constraint usually shows up in:
โ Market selection
โ Offer strength
โ Awareness
โ Lead generation
โ Lead quality
โ Sales conversion
โ Pricing
โ Follow-up
โ Customer unit economics
The most common constraints can be grouped into four areas:
โ Getting customers
โ Selling
โ Delivering
โ How the company operates
Your time is usually underneath all four.
Now go through the full diagnostic tree:
Question 1: Is there a proven market?
โ Does a specific group experience this problem repeatedly?
โ Is it painful enough that they're already spending money or time trying to solve it?
โ Can the buyer afford a solution?
โ Can you identify and reach the buyer?
โ Do people pay, or do they just say the idea sounds interesting?
If not, the constraint is probably the market or problem selection.
If yes, keep going.
Question 2: Can you sell the offer manually?
โ Can the founder close qualified buyers?
โ Do customers understand the promised outcome?
โ Does the offer seem meaningfully different from the alternatives?
โ Does the price feel acceptable relative to the perceived value?
โ Do buyers trust that the solution will work?
If qualified prospects consistently refuse to buy, the constraint is probably in:
โ Offer
โ Positioning
โ Market
โ Sales conversation
If they buy, keep going.
Question 3: Are there enough qualified opportunities?
โ Are enough of the right people seeing the offer?
โ Are they responding?
โ Are they becoming leads?
โ Is lead quality acceptable?
โ Can volume be increased predictably?
If not, the constraint is acquisition.
If yes, keep going.
Question 4: Do qualified opportunities convert?
Measure:
๐ชก Lead response
โ Qualification
โ Booking
โ Show rate
โ Close rate
โ Payment collection
The constraint could be:
โ Slow response
โ Poor qualification
โ Booking friction
โ Low show rate
โ Weak sales process
โ Lack of follow-up
โ Payment friction
โ Bad offer
If there are opportunities but no sales, the constraint is sales or the offer.
If they buy, keep going.
Question 5: Can the business deliver twice the volume?
โ At what stage would a backlog build up?
โ Where are customers currently waiting?
โ Which employees are constantly overloaded?
โ Where does quality drop as volume increases?
โ What work can only be done by one person?
โ What inventory, capital, equipment, or supplier would run out?
If something breaks, the constraint is in delivery or operational capacity.
If the system can handle more, keep going.
Question 6: Are customers getting the promised outcome?
Measure:
โ Activation
โ Time to first value
โ Completion
โ Customer outcomes
โ Complaints
โ Refunds
โ Support load
โ Repeat usage
If customers buy but don't get the outcome, the constraint is the product or delivery quality.
If they do, keep going.
Question 7: Do customers stay and increase in value?
Measure:
โ Cohort retention
โ Churn
โ Repeat purchases
โ Renewals
โ Expansion
โ Referrals
โ Gross profit per customer over time
If acquisition works but customers leave quickly, the constraint is in:
โ Retention
โ Customer success
โ Recurring value
If they stay, keep going.
Question 8: Are the economics scalable?
Measure:
โ Gross margin
โ CAC
โ Contribution margin
โ Payback period
โ Refunds
โ Working capital needs
โ Realized lifetime gross profit
โ Payment timing
If each customer ends up profitable but consumes too much cash up front, the constraint could be in:
โ Payback period
โ Working capital
If customers are structurally unprofitable, the constraint is in:
โ Business model
โ Pricing
โ Delivery cost
โ Retention
Question 9: Can the company operate without the founder?
Ask:
โ Does every decision require founder approval?
โ Do employees wait for answers?
โ Is important knowledge only in the founder's head?
โ Can someone else sell, hire, set prices, or solve customer problems?
โ Does performance collapse when the founder isn't there?
If so, the constraint is in:
โ Founder dependency
โ Management
โ Operating systems
Confirm that it's actually the constraint
A bad metric isn't necessarily a constraint.
Use four tests:
1๏ธโฃ Counterfactual test
"If this metric improved by 50% tomorrow and everything else stayed the same, how much would the business's final outcome improve?"
If the answer is "practically nothing," it's not the current constraint.
2๏ธโฃ Queue test
"Where is work, demand, inventory, information, or decision-making waiting?"
Persistent queues usually reveal the bottleneck.
3๏ธโฃ Throughput test
"Which stage currently sets the lowest ceiling on the number of profitable customers completed?"
That stage is a strong candidate for the constraint.
4๏ธโฃ What breaks next test
"If we removed this constraint, what would break next?"
A real constraint should reveal the next bottleneck once it's removed.
Checklist to confirm a constraint:
โ Explains why the main goal isn't being reached.
โ Improving it should increase final output.
โ There's enough upstream input to benefit from the improvement.
โ Downstream stages can initially absorb the improvement.
โ The constraint can be measured.
โ It can be tested through a specific intervention.
โ The proposed improvement won't destroy quality, margin, or retention.
Part VI: PLAYBOOKS FOR EACH CONSTRAINT โ
โ Market constraint
Symptoms
โ People like the idea but don't pay.
โ Sales require very long explanations.
โ Prospects don't feel any urgency.
โ Almost every conversation ends with a price objection.
โ Retention is poor because the problem isn't important enough.
โ You can't clearly identify the buyer.
โ Acquisition channels contain few suitable prospects.
Diagnostic tests
๐ฌ Behavioral interviews
โ Ask about what people have already done:
โ When did the problem last happen?
โ What did it cost?
โ What have you tried?
โ What are you currently paying for?
โ Who controls the budget?
โ What happens if you do nothing?
Don't rely on: "Would you buy this?"
People are bad at predicting their hypothetical buying behavior.
๐ฐ Manual presale
Describe a clear outcome, ask for payment, and deliver the outcome manually.
Payment is much stronger evidence than:
โ Praise
โ Surveys
โ Email signups
โ Waitlists
๐๏ธ Concierge pilot
Deliver the service manually before building the scalable product.
This reveals:
โ The real workflow
โ The required inputs
โ Common objections
โ What the customer values
โ Which parts can be automated later
๐ Exit condition
There is repeated paid demand from a recognizable type of buyer for a recognizable outcome.
A good early-stage starting point is five to ten paying customers acquired through founder-led sales, although the level of evidence needed increases with the time and capital required to build the business. (which is what you'd expect, right?)
โ Offer constraint
The offer isn't just the product.
It includes:
โ Customer
โ Promised outcome
โ Mechanism
โ Deliverables
โ Price
โ Payment structure
โ Proof
โ Risk reversal
โ Timing
โ Support
โ Bonuses
โ Positioning
โ Scarcity or urgency
Hormozi's course explicitly includes:
โ Market selection
โ Pricing
โ Value Equation
โ Offer construction
โ Bonuses
โ Guarantees
โ Scarcity
โ Urgency
โ Naming
๐งฎ The Value Equation
Hormozi's value equation is:
Value = (Desired outcome ร Perceived likelihood of success) / (Time delay ร Effort and sacrifice)
You need to:
๐ผ Increase the desired outcome
๐ผ Increase the perceived likelihood of success
๐ฝ Reduce the time needed to achieve the outcome
๐ฝ Reduce the effort required
๐ Offer audit ๐
โญ๏ธ Desired outcome
Ask:
โ What does the customer actually want to achieve?
โ Are you selling the outcome or just describing features?
โ Is the outcome important enough to justify taking action?
๐ Perceived likelihood
Build confidence through:
โ Demonstrations
โ Case studies
โ Testimonials
โ Transparent methodology
โ Guarantees
โ Credentials
โ Proof of past results
โ Clear explanations of why the mechanism works
โณ Time delay
Reduce the time until the customer:
โ Sees progress
โ Receives the first deliverable
โ Gets the first meaningful result
โ Understands that the purchase was worth it
๐ฉธ Effort and sacrifice
Reduce:
โ Setup
โ Learning
โ Data entry
โ Coordination
โ Decision fatigue
โ Required behavior changes
โ Switching friction
โ Ongoing maintenance
๐งพ The reusable template
โ Customer:___________
โ Problem:___________
โ Desired outcome:___________
โ Current alternative:___________
โ Unique mechanism:___________
โ Time to first value:___________
โ Total time to outcome:___________
โ Effort required from the customer:___________
โ Deliverables:___________
โ Proof:___________
โ Risk reversal:___________
โ Price:___________
โ Payment terms:___________
โ Reason to act now:___________
๐งช Offer experiment
Keep the same audience and acquisition method while testing one important offer variable:
โ Outcome
โ Price
โ Packaging
โ Guarantee
โ Payment terms
โ Time to value
โ Proof
โ Deliverable
โ Positioning
Measure both:
"Conversion rate" and "Gross profit per opportunity"
A cheaper offer may convert more prospects but generate less profit.
โ Acquisition constraint
Hormozi's Core Four divide lead generation based on:
1๏ธโฃ Whether the communication is one-to-one or one-to-many.
2๏ธโฃ Whether the audience knows you or not.
The practical result is:
๐ค One-to-one
People who know you โ Warm outreach
People who don't know you โ Cold outreach
๐ฅ One-to-many
People who know you โ Organic content
People who don't know you โ Advertising
This also includes:
โ Referrals
โ Employees
โ Agencies
โ Affiliates
as ways to get other people to generate leads.
Recommended sequence for an unproven business:
๐ฅ Warm outreach โ โ๏ธ Targeted cold outreach โ ๐ฒ Consistent content โ ๐ Referrals and partnerships โ ๐ธ Paid acquisition
It's not mandatory, but it usually lets you learn much more cheaply than starting by spending big on advertising.
๐งโโ๏ธ Rule of 100
The Rule of 100 is a volume discipline:
Do approximately 100 reps of the main activity per day instead of drawing conclusions from tiny samples.
Depending on the business, a primary action could be:
โ A targeted outreach message
โ A call
โ An ad variant
โ A distribution attempt
โ A piece of content
โ A follow-up
โ A sales training rep
Adapt the volume to the channel.
In high-value enterprise sales, 100 generic messages can be much worse than 15 thoroughly researched contacts.
The principle is: "Enough consistent volume, not spam."
๐ฅ Diagnose acquisition by stage
Impressions
โ Attention
โ Click or response
โ Lead
โ Qualified lead
โ Appointment or checkout
๐ Low reach
Likely problem: Insufficient distribution
๐ Reach but little attention
Likely problem: Weak hook or targeting
๐ฌ Attention but no response
Likely problem: Weak message or offer
๐ฏ Responses but bad leads
Likely problem: Targeting or qualification
๐
Good leads but no bookings
Likely problem: Friction or follow-up
โฐ Bookings but no-shows
Likely problem: Commitment and reminders
๐ Acquisition exit condition
You have at least one channel that can produce qualified opportunities with acceptable economics and enough consistency to plan around it.
โ Sales constraint
Map the entire sales process
Lead received
โ First response
โ Qualification
โ Appointment
โ Show-up
โ Discovery
โ Offer presentation
โ Objection handling
โ Decision
โ Payment collection
โ Post-sale reinforcement
Measure conversion and cycle time at each stage.
Distinguish an offer problem from a salesperson problem
A useful test:
โ If the founder or best salesperson can't sell the offer to qualified prospects, suspect the market or offer.
โ If the best salesperson consistently closes but the others don't, suspect training, process, management, or hiring.
โ If prospects say yes but don't pay, suspect the payment process, urgency, decision-making authority, or follow-up.
โ If the close rate is high but profit is low, suspect price or packaging.
The CLOSER structure:
C โ Clarify: clarify why the prospect is there.
L โ Label: label the problem.
O โ Overview: review past experiences and attempted solutions.
S โ Sell: sell the destination or outcome.
E โ Explain: explain and remove concerns and uncertainty.
R โ Reinforce: reinforce the decision after the purchase.
Its purpose is to create a repeatable structure that can be:
โ Measured
โ Reviewed
โ Trained
๐ผ Sales improvement process:
1. Record calls.
2. Review wins and losses.
3. Identify the exact stage where deals die.
4. Define observable behaviors for that stage.
5. Rewrite the script or process.
6. Role-play.
7. Test it with real qualified prospects.
8. Compare performance by salesperson, segment, source, and offer.
9. Turn the winning behaviors into a scorecard.
โ Delivery and capacity constraint
Map delivery as a production line
Payment
โ Onboarding
โ Setup
โ Core delivery
โ Quality control
โ Customer support
โ Completion
โ Renewal
For each stage, record:
๐ฆ Current throughput
Question: How many units per period?
๐ก๏ธ Safe capacity
Question: How many can be completed without losing quality?
โฑ๏ธ Cycle time
Question: How long does one unit take?
๐ Queue
Question: How much work is waiting?
โ Error rate
Question: How often does work have to be redone?
๐ค Owner
Question: Who's accountable for it?
๐ Dependency
Question: What person, supplier, or tool is needed?
The first necessary stage that can't absorb more volume is usually the operational constraint.
Fix delivery in this order:
1. Eliminate
โ Unnecessary approvals
โ Redundant steps
โ Low-value customization
โ Duplicate data entry
โ Meetings that don't change decisions
โ Reports no one uses
2. Protect the bottleneck
Don't let scarce specialists spend time on:
โ Admin
โ Scheduling
โ Data cleanup
โ Routine communication
โ Work someone else can do
3. Standardize
Create:
โ Templates
โ Checklists
โ Defined inputs
โ Quality criteria
โ Decision rules
โ SOPs
4. Batch
Group similar work to reduce switching costs.
5. Automate
Only automate when:
โ The manual process works.
โ The exceptions are understood.
6. Delegate
Transfer repeatable work with:
โ Clear outputs
โ Clear quality standards
7. Hire or add infrastructure
Add:
โ Employees
โ Suppliers
โ Inventory
โ Equipment
โ Software
โ Working capital
Only after confirming that additional capacity really is the constraint.
8. Regulate demand
When capacity is scarce:
โ Raise prices
โ Limit availability
โ Prioritize valuable customers
โ Eliminate low-margin work
โ Create a waitlist
โ Turn one-to-one delivery into one-to-many where it makes sense
๐ Delivery exit condition
The business can take on materially more customers without an unacceptable drop in:
โ Quality
โ Delivery time
โ Customer outcomes
โ Gross margin
โ Employee workload
โ Support response time
โ Refunds or complaints
โ Retention constraint
A company can look like it's limited by acquisition when the real problem is that customers disappear too quickly.
Map the retention system
Purchase
โ Onboarding
โ Activation
โ First value
โ Habit or repeat usage
โ Outcome
โ Renewal
โ Expansion
Diagnose churn based on when it happens
๐ Immediately after purchase
Likely problem: Incorrect expectations, buyer's remorse, poor handoff
๐ช Before activation
Likely problem: Setup friction or unclear onboarding
๐งช After initial usage
Likely problem: Weak product or poor fit
โ
After achieving the outcome
Likely problem: Product solves a finite problem with no continuity
๐ After several months
Likely problem: Declining value, competition, price, or lack of a recurring use case
๐ During renewal
Likely problem: Poor communication of value or procurement friction
๐ Retention metrics
Use cohorts instead of overall averages.
Measure:
โ Activation rate
โ Time to first value
โ Percentage that achieves the promised outcome
โ Retention by acquisition source
โ Retention by segment
โ Gross Revenue Retention
โ Net Revenue Retention where relevant
โ Repeat purchase rate
โ Refund rate
โ Reason for churn
โ Expansion rate
๐ผ Improve retention in this order:
1. Sell to customers with a better fit.
2. Set the right expectations.
3. Improve onboarding.
4. Reduce time to first value.
5. Make progress visible.
6. Make sure customers do the highest-value behavior.
7. Intervene proactively when usage drops.
8. Improve the core outcome.
9. Add continuity only when there really is ongoing value.
10. Create natural expansions once the first outcome is achieved.
โ Economics and cash constraint
Growth is dangerous when the company doesn't understand its economics.
Main formulas:
๐ค Customer Acquisition Cost
CAC = Total acquisition and sales cost รท New paying customers
Calculate both:
1. Paid media CAC
2. Fully loaded CAC, including:
โ Sales salaries
โ Commissions
โ Software
โ Agencies
โ Creative production
๐ค Gross profit per customer
Gross profit = Revenue โ Direct cost to serve the customer
๐ฐ Contribution profit
Contribution profit = Revenue โ Direct delivery costs โ Variable acquisition and sales costs
โณ Payback period
Payback period = CAC รท Monthly gross profit per customer
๐คโณ Realized lifetime gross profit
Realized lifetime gross profit = Gross profit actually collected from a customer cohort
Whenever possible, use real cohort data.
Don't build your whole plan around an optimistic LTV estimate from immature customers.
๐ฅ Economics diagnosis
CAC too high
Investigate:
โ Targeting
โ Conversion
โ Sales productivity
โ Channel costs
โ Offer strength
โ Price
โ Referral rate
Gross margin too low
Investigate:
โ Delivery labor
โ Custom work
โ Supplier costs
โ Refunds
โ Support load
โ Product mix
โ Price
Payback too long
Investigate:
โ Upfront payment
โ Annual plans
โ Deposits
โ Setup/onboarding fees
โ Faster activation
โ Higher price
โ Lower CAC
โ Earlier upsells
โ Lower delivery cost
Customer value too low
Investigate:
โ Retention
โ Repeat purchases
โ Expansion
โ Cross-sell
โ Continuity
โ Customer quality
โ Outcome quality
Money Model architecture
Offer architecture can be split into four types:
1๏ธโฃ Attraction offers: make the initial purchase or interaction easier.
2๏ธโฃ Upsells: let customers buy additional value.
3๏ธโฃ Downsells: offer a smaller option or one structured differently.
4๏ธโฃ Continuity offers: create recurring value and recurring payments.
A generic stack could be:
- Attraction: Low-friction entry or small sample outcome
- Core: Main solution
- Upsell: More speed, scope, convenience, access, or outcome
- Downsell: Smaller scope, payment plan, fewer features, or self-service
- Continuity: Service, maintenance, monitoring, replenishment, or ongoing access
Don't add an upsell just to extract more money. It should solve the customer's next problem or improve their current outcome.
๐ Economics exit condition:
Incremental customers generate attractive contribution profit, the payback period can be financed, and growth doesn't cause a liquidity crisis.
โ Operations, people, and founder constraint
Founder bottleneck test
The founder is probably the constraint when:
โ Every important decision requires their approval.
โ Employees wait instead of acting.
โ Only the founder can close important deals.
โ Customer exceptions always escalate to them.
โ Hiring stops when the founder is busy.
โ The company has no written decision rules.
โ Results get worse immediately when the founder steps away.
๐ฆ Productize before delegating
The preferred sequence is:
The founder does the work well
โ Repeats it
โ Identifies the winning process
โ Documents it
โ Trains someone else
โ Measures their output
โ Transfers authority
Don't document every experimental process.
You'll end up with a huge library of SOPs for things that don't work.
๐ Define roles through outputs
Bad role description:
โ Help with marketing.
Better:
โ Generate 80 qualified sales opportunities per month at a fully loaded cost of less than โฌ100 per opportunity.
Every role needs:
โ Outcome
โ Metric
โ Authority
โ Inputs
โ Process
โ Quality standard
โ Review cadence
Delegation ladder
1. Observe: the employee watches.
2. Execute with instructions: the founder directs every step.
3. Execute with review: the employee acts and the founder checks.
4. Recommend: the employee proposes decisions.
5. Decide within limits: the employee has defined authority.
6. Own the outcome: the employee controls the process and metric.
Delegation isn't complete until decision rights are transferred along with the work.
๐ Management cadence
A manager should be accountable for:
โ A clear output
โ A small set of leading metrics
โ The people and resources needed
โ A weekly operating review
โ Corrective actions when metrics are off
Don't hold someone accountable for an outcome without giving them the authority they need to produce it.
โ Focus and risk constraint
Once the main engine works, reduce the risks that could stop it.
Audit:
โ Founder or key-person dependency
โ Customer concentration
โ Acquisition channel concentration
โ Supplier concentration
โ Platform dependency
โ Regulatory dependency
โ Geographic concentration
โ Dependency on a single product
โ Technology or data dependency
โ Liquidity and refinancing risk
Don't diversify too early.
Diversification has a cost:
โ It fragments attention
โ It reduces volume per channel
โ It slows learning
Reduce concentration only when:
โ The main engine is already working.
โ The concentration creates a material existential risk.
โ The alternative can be developed without hurting the core.
โ There's enough management capacity to support it.
Part VII: CHOOSE THE INTERVENTION โ
Separate the constraint from the proposed solution
Example: "Onboarding capacity is limited to 100 customers per month."
Possible interventions:
- Eliminate unnecessary onboarding steps.
- Create group onboarding.
- Automate account setup.
- Improve training.
- Hire another onboarding specialist.
- Charge for personalized onboarding.
The constraint isn't:
โ We need another employee.
That's just one possible intervention.
๐งฎ Intervention prioritization formula
A useful approximation:
Priority = (Expected impact ร confidence ร speed) / (cash required ร effort ร complexity)
This isn't precise math. Its purpose is to force you to explicitly compare the alternatives.
For each intervention, estimate:
โ Expected change in the final metric
โ Confidence based on evidence
โ Time to get evidence
โ Cash required
โ Founder attention required
โ Reversibility
โ Downside risk
Choose the smallest intervention capable of testing the hypothesis about the constraint.
Part VIII: RUN THE EXPERIMENT โ
Experiment rules
โ Change one important variable at a time.
โ Use enough volume to distinguish signal from noise.
โ Run the test for at least one full business cycle.
โ Define success before seeing the results.
โ Measure both local and final metrics.
โ Include quality and margin guardrails.
โ Don't change the test halfway through because the early results feel uncomfortable.
โ Record unexpected effects.
๐ Interpret the result correctly
1๏ธโฃ The local metric improves and final output improves
The constraint diagnosis was probably right.
Scale the intervention.
2๏ธโฃ The local metric improves but final output doesn't
Possible explanations:
โ It wasn't the real constraint.
โ Another stage immediately became the new constraint.
โ The local metric was a vanity metric.
โ Downstream capacity couldn't absorb the improvement.
โ Customer quality got worse.
3๏ธโฃ Final output improves but a guardrail collapses
You've increased activity, not scalable throughput.
Examples:
โ Sales increase but refunds double.
โ More customers come in but gross margin disappears.
โ Delivery volume increases but outcomes get worse.
โ Leads increase but their quality drops.
4๏ธโฃ Nothing changes and volume was low
The result is inconclusive.
Don't confuse a tiny sample with a failed strategy.
5๏ธโฃ Nothing changes after sufficient volume
Stop the intervention and update your mental model.
Part IX: SCALE WHAT WORKS โ
More, Better, New
A good practical starting point is:
70% โ More
20% โ Better
10% โ New
7๏ธโฃ0๏ธโฃ %: More
Do more of what already works.
Examples:
โ Increase budget on a profitable campaign.
โ Publish more versions of a proven content format.
โ Send more of the outreach that gets responses.
โ Add capacity to a productive sales process.
โ Expand a successful offer to more suitable prospects.
โ Create small variations of a winning ad.
This is usually the lowest-risk allocation.
2๏ธโฃ0๏ธโฃ %: Better
Improve or expand what already works.
Examples:
โ Better targeting
โ Better hook
โ Better proof
โ Higher-converting landing page
โ Faster onboarding
โ Better sales script
โ Better packaging
โ More efficient delivery
โ Adjacent customer segment
It carries moderate risk because significant changes can also break what's already working.
1๏ธโฃ0๏ธโฃ %: New
Try something fundamentally different.
Examples:
โ New acquisition channel
โ New product
โ New segment
โ New pricing model
โ New market
โ New sales motion
โ New delivery mechanism
It's reasonable to expect most new experiments to fail.
The goal isn't immediate efficiency. The goal is to discover the next winner.
๐ช Promotion ladder
NEW: A genuinely different experiment works
โ
BETTER: Improve and validate the mechanism
โ
MORE: Scale repeated, proven variations
โ
STANDARDIZE: Turn the winner into a process
โ
DELEGATE: Assign ownership
๐ When to move from More to Better
Do it when:
โ You can't safely increase volume.
โ Marginal returns are declining.
โ The channel is reaching capacity.
โ Quality is deteriorating.
โ Additional volume is prohibitively expensive.
๐ When to move from Better to New
Do it when:
โ The process is materially optimized.
โ Further improvements yield small returns.
โ The market or channel is saturated.
โ Concentration creates an unacceptable risk.
โ A new opportunity has a higher expected return than continued optimization.
โ Don't move to New just because you're bored.
Part X: STANDARDIZE AND DELEGATE โ
Turn the result into an operating asset.
When an experiment works repeatedly:
โ Document the exact inputs.
โ Document the required behaviors.
โ Define the expected output.
โ Define quality standards.
โ Define common exceptions.
โ Assign an owner.
โ Train using real examples.
โ Review performance.
โ Remove the need for founder approval where possible.
โ Keep testing improvements.
A process isn't finished just because a document exists.
A process is finished when another competent person can repeatedly produce the expected result without the founder having to direct every action.
Part XI: OPERATING CADENCE โ
1๏ธโฃ Daily cadence
Focus on the main actions related to the current constraint.
Examples:
โ Outreach attempts
โ Sales conversations
โ Customer interviews
โ Follow-ups
โ Units delivered
โ Recruiting conversations
โ Experiment variants
โ Churn interventions
Don't confuse activity with output. But measure the activity needed to generate the output.
2๏ธโฃ Weekly constraint review
Have a 30- to 60-minute meeting.
Agenda:
โ What's the 90-day goal?
โ What's the current result versus the goal?
โ What's the current constraint?
โ What evidence supports the diagnosis?
โ Has the constraint metric improved?
โ Has the final metric improved?
โ Have any guardrails gotten worse?
โ What have we learned?
โ What will we continue, stop, or change?
โ Who owns the next action, and by when?
Don't fill the meeting with general status updates.
Status can be written down. Meetings should produce decisions.
3๏ธโฃ Monthly review
Review:
โ Funnel conversion
โ Cohort retention
โ Customer outcomes
โ CAC
โ Gross margin
โ Contribution profit
โ Payback period
โ Delivery capacity
โ Employee productivity
โ Founder dependencies
โ Cash needs
Ask:
โ Is the constraint still the same?
4๏ธโฃ Quarterly review
For each project:
โ Recalculate the economic model.
โ Repeat the 2ร test.
โ Identify the current stage.
โ Identify the current constraint.
โ Decide whether to scale, improve, maintain, pause, or kill.
โ Allocate founder time and capital.
โ Choose one business goal for the next cycle.
Part XII: USE THE SYSTEM ACROSS MULTIPLE PROJECTS โ
Classify each project
๐บ๏ธ Explore
There's a plausible market, but no significant evidence of payment.
Goal: Find out whether the problem and customer are real.
๐ง Prove
Customers have paid, but the business is still delivered manually or inconsistently.
Goal: Prove repeatable demand, delivery, and customer value.
๐ Scale
Demand, delivery, retention, and economics are sufficiently proven.
Goal: Increase volume while protecting economics and quality.
๐ Maintain
The project works, but right now it's not the best incremental use of your attention.
Goal: Maintain performance with as little founder involvement as possible.
โธ๏ธ Pause or Kill
The evidence doesn't justify continued investment.
Possible reasons:
โ No paid demand after the previously defined test volume.
โ Poor retention.
โ Structurally bad economics.
โ No realistic path to distribution.
โ Excessive regulatory or platform risk.
โ No available operator.
โ Another project has materially higher expected value.
โ The original thesis is no longer true.
Don't keep a project alive just because you've already put a lot of work into it.
Portfolio allocation
A reasonable adaptation of More, Better, New would be:
70%:
Proven projects and proven growth engines
20%:
Adjacent improvements and promising projects with evidence
10%:
Completely new experiments
Adapt the allocation to the stage of the portfolio.
โ A very early-stage portfolio may need more exploration.
โ A mature, cash-generating portfolio should normally allocate more resources to proven engines.
๐งฎ Project scorecard
Score each project from 1 to 5.
๐ฅ Pain
Question: How severe and frequent is the problem?
๐ฐ Willingness to pay
Question: Is there evidence in the form of payments?
๐ Retention
Question: Do customers keep using or buying?
๐ Economics
Question: Can each customer generate attractive contribution profit?
๐ฃ Distribution
Question: Is there a credible way to reach customers?
๐ง Founder advantage
Question: Do you have uncommon insight, skills, an audience, or access?
โก Learning speed
Question: How quickly can the core hypothesis be tested?
๐ต Capital efficiency
Question: How much cash is needed before getting evidence?
โ๏ธ Operational load
Question: How difficult is delivery?
๐ Upside
Question: How large could the opportunity reasonably become?
Don't just add up the points.
One fatal weakness can invalidate the whole project:
โ Nobody wants to pay
โ Impossible economics
โ No legal path
โ No distribution
โ You can't deliver the product
๐ฌ Portfolio decision
For each project, choose one:
๐ scale: the engine works and isn't saturated yet
๐ง fix: an identifiable constraint is blocking growth
๐ prove: important hypotheses still need evidence
๐ ๏ธ maintain: the project works but deserves little incremental attention
โธ๏ธ pause: keep the option open while reallocating resources
๐ kill: the thesis has failed or the opportunity cost is too high
Part XIII: UNIVERSAL DECISION RULES โ
Use these rules when you don't know what to do next.
No clear painful problem?
โ Research problems and solve them manually.
People show interest but don't pay?
โ Fix the market, outcome, offer, proof, or price.
You can sell manually but lack opportunities?
โ Fix acquisition.
You have leads but few appointments?
โ Fix response, qualification, follow-up, or scheduling.
You have appointments but few sales?
โ Fix the offer, sales process, targeting, or trust.
You have sales but delivery is collapsing?
โ Fix capacity and operations.
Delivery works but customers aren't getting results?
โ Fix product quality and time to value.
Customers get results but leave?
โ Fix ongoing value, retention, or customer fit.
Customers stay but growth consumes too much cash?
โ Fix CAC, payback, payment timing, or the money model.
Everything works but the founder is overloaded?
โ Standardize, delegate, hire, and transfer authority.
Does the proven mechanism still have spare capacity?
โ Do More.
Does More produce diminishing marginal returns?
โ Do Better.
Are More and Better practically exhausted?
โ Try New.
Does an intervention work repeatedly?
โ Document it and delegate it.
Has the constraint disappeared?
โ Diagnose the business again.
Part XIV: COMMON MISTAKES โ
โ Optimizing something that isn't the constraint
Improving an unconstrained stage rarely changes final output.
Scaling before fixing retention
Pouring more customers into a leaky system creates:
โ More churn
โ More support
โ More reputational damage
โ Buying traffic before proving the offer
Paid advertising can't permanently save an offer that qualified buyers don't want.
โ Hiring to solve ambiguity
A new employee can't execute a process nobody understands.
โ Automating too early
Automation makes a process run faster.
Bad processes included.
โ Launching too many channels
Every new channel has a learning curve.
Fragmenting volume slows learning across all of them.
โ Serving too many avatars
Different avatars require different:
โ Messages
โ Sales
โ Prices
โ Features
โ Delivery
โ Support
โ Changing multiple variables at once
You can improve performance without learning what caused the improvement.
โ Confusing low volume with randomness
Small samples produce very volatile results.
Do enough before drawing conclusions.
โ Measuring revenue without gross profit
High revenue can hide:
โ Bad margins
โ Negative contribution profit
โ Reliance on theoretical lifetime value
Future retention assumptions don't pay today's bills.
โ Discounting prices instead of creating value
Lowering prices can increase conversion while worsening:
โ Cash flow
โ Positioning
โ Delivery quality
โ Customer commitment
โ Not defining guardrails
An experiment can improve the target metric while destroying the business somewhere else.
โ Never diagnosing again
Solving one constraint creates the next.
The complete operating cycle:
1๏ธโฃ Choose a project.
2๏ธโฃ Identify its current stage.
3๏ธโฃ Define one economic goal for the next 90 days.
4๏ธโฃ Map the entire customer and delivery system.
5๏ธโฃ Measure volume, conversion, capacity, quality, and economics.
6๏ธโฃ Run the 2ร demand test.
7๏ธโฃ Identify the one stage limiting final throughput.
8๏ธโฃ Confirm it using:
- Counterfactual test
- Queue test
- Throughput test
9๏ธโฃ Choose the smallest intervention capable of testing the diagnosis.
๐ Define in advance:
- Success
- Failure
- Duration
- Guardrails
1๏ธโฃ1๏ธโฃ Run enough volume to learn.
1๏ธโฃ2๏ธโฃ Evaluate the final business outcome, not just the local metric.
1๏ธโฃ3๏ธโฃ Kill the interventions that fail.
1๏ธโฃ4๏ธโฃ Scale the ones that work using More, Better, New.
1๏ธโฃ5๏ธโฃ Standardize the repeatable winners.
1๏ธโฃ6๏ธโฃ Delegate the process and transfer authority.
1๏ธโฃ7๏ธโฃ Diagnose the business again.
1๏ธโฃ8๏ธโฃ Repeat indefinitely.
The central rule is:
"Work on the one problem currently limiting the entire business. As soon as it stops being the constraint, stop optimizing it and find the next one."