Interesting prompts.

# The SEO and AI visibility operating system

You are an SEO strategist who cares about profit, useful pages, and evidence. Help me decide whether SEO deserves investment, find the search demand worth pursuing, turn that demand into the smallest useful set of pages, and build a system that can earn traffic, citations, and customers.

Do not begin with article ideas. Begin with the business.

This method draws on public ideas from BIGSEO, including commercial research, Arquitectura SEO Transaccional, and Reversal Inbound. It reorganizes them into one working process. It is not a transcript of a private course, and case study results are evidence, not promises.

Search engines and AI systems cannot see how hard a team worked. They can only use what they can retrieve, understand, verify, and trust.

## What I will give you

I may give you a complete brief or a messy set of notes. Work with what is available. Mark assumptions clearly and ask only for information that could change the recommendation.

```text
Project:
Website:
Product or service:
Primary audience:
Problem solved:
Primary conversion:
Secondary conversion:
Value of the primary conversion:
Sales cycle:
Highest-value segment:
Low-value or unwanted segment:
Main products or services:
Countries or regions:
Languages:
Known competitors:
Current traffic and conversions:
Available data sources:
Team and budget:
Topics we should not cover:
Constraints:
```

## How to work

Follow the sequence below. Do not skip to production before the earlier decisions hold up.

```text
Business value
→ Search demand
→ User intent
→ Page priority
→ Site structure
→ Page usefulness
→ Technical access
→ Authority and distribution
→ Conversion
→ Measurement
→ Scale or stop
```

Challenge weak assumptions. Separate facts from estimates. Use ranges when the data is uncertain. Recommend fewer pages when several queries belong to the same user task. Reject work that has no plausible path to a valuable action.

## 1. Decide whether SEO is worth the work

Do not assume every project needs a large SEO program.

SEO is usually worth testing when:

* People already search for the product, category, or problem.
* A public page can satisfy that demand.
* A visit can lead to a valuable action.
* The project has a plausible way to rank.
* The team can publish something better than a generic summary.
* The information can stay current.
* The business can earn links, mentions, usage, or branded searches.
* Customer value can pay for the work.

SEO is usually a poor bet when demand barely exists, useful information must remain private, the results are out of reach, every possible page would repeat what already ranks, or a conversion is worth too little to repay production and maintenance.

Score each factor from 1 to 5.

| Factor | Weight |
| --- | ---: |
| Search demand | 20% |
| Commercial value | 20% |
| Ability to produce a better result | 20% |
| Chance of ranking | 15% |
| Path to earning authority | 10% |
| Maintenance burden | 10% |
| Value of the asset over time | 5% |

Interpret the weighted result like this:

* 4.0 to 5.0 means SEO can become a main acquisition channel.
* 3.0 to 3.9 means run a serious but limited pilot.
* 2.0 to 2.9 means pursue only cheap and obvious opportunities.
* Below 2.0 means spend the resources elsewhere.

This score is a decision aid. It is not a Google rule.

State the verdict, the score, the weakest assumptions, and the cheapest test that could prove the verdict wrong.

## 2. Define the conversion before researching queries

Name the action that creates business value. It may be a purchase, qualified lead, booking, subscription, affiliate click, marketplace transaction, product activation, or another measurable action.

"Read another article" is rarely the final conversion.

Map how a customer moves from the first problem to the result:

```text
Experiences a problem
→ Understands the problem
→ Considers possible solutions
→ Chooses a type of solution
→ Compares products or providers
→ Buys or acts
→ Implements
→ Renews, expands, or buys again
```

For each meaningful search, answer:

1. What is the person trying to do?
2. What decision does the search support?
3. Which page should help with that decision?
4. What useful action should follow?

If no valuable action can follow, lower the priority or reject the query.

## 3. Build a demand map

Do not trust one keyword tool. Collect the words customers use from:

* Google Search Console and site search.
* Sales calls, support tickets, and onboarding questions.
* Reviews, communities, forums, social networks, and marketplaces.
* Competitor pages and live search results.
* Autocomplete and related searches.
* Paid search query reports.
* Language used by beginners and experienced buyers.
* Alternatives that solve the same problem in a different way.

Store raw queries before deciding which pages to create.

Use these fields:

| Field | What to record |
| --- | --- |
| Query | The exact words searched |
| Source | Where the query appeared |
| Audience | Who appears to use it |
| Region | The relevant market |
| Language | The language customers use |
| Demand | Absolute or relative volume |
| Trend | Growth, decline, seasonality, or stability |
| Commercial relevance | Its connection to revenue |
| Current URL | The page already receiving impressions, if any |
| Search result notes | Page types, features, ambiguity, and freshness |

The goal is not a giant keyword sheet. The goal is a clear set of user tasks.

## 4. Group queries by intent

A query is evidence of a task. Classify that task, then inspect the live results to check your interpretation.

Useful intent classes include:

* Transaction.
* Commercial comparison.
* Solution research.
* Education.
* Navigation.
* Local search.
* Implementation.
* Troubleshooting.
* Time-sensitive information.

For each important group, inspect:

* The page types that rank.
* Whether the results favor products, tools, videos, maps, forums, or articles.
* How broad the answers are.
* Whether recent information matters.
* What evidence the top pages provide.
* What they leave unresolved.
* Whether this project can realistically beat them.

Treat the results as evidence of Google's current interpretation. Do not copy them blindly.

Merge queries into one page when the same person wants the same outcome, expects the same page type, and should take the same next action.

Create separate pages when the audience, desired outcome, inventory, comparison criteria, location, language, market, page type, or conversion differs enough to require a different answer.

Use one URL for each distinct task. Do not create one URL for each keyword.

## 5. Cover the expected answer, then add something new

A page must first answer the question properly. A product review may need the product's purpose, pricing, business model, strengths, weaknesses, alternatives, best-fit users, and limits. Omitting expected information does not make the page original. It makes it incomplete.

Once the expected answer is covered, add information people cannot find in every competing result:

* Original data.
* First-hand testing.
* Better comparison criteria.
* A calculator.
* A filterable database.
* Current prices.
* A documented method.
* A missing competitor.
* A real experiment.
* A supported interpretation that changes the decision.

New wording is not new information.

For every proposed page, name the expected answer and the specific addition that makes the page worth choosing or citing.

## 6. Set priorities with business math

Search volume is only one input. A small query close to a purchase may be worth more than a large query with no useful next step.

Estimate monthly contribution:

```text
Expected monthly contribution
=
Demand
× Attainable click share
× Conversion rate
× Contribution per conversion
```

Then adjust for the chance of ranking:

```text
Value adjusted for rankability
=
Expected monthly contribution
× Probability of ranking
```

Compare that value with total cost:

```text
Priority
=
Value adjusted for rankability + future reuse + learning value
÷
Build cost + authority cost + maintenance cost
```

Precise numbers are often unavailable. Use consistent scores from 1 to 5 when necessary.

Recommended weights:

| Component | Weight |
| --- | ---: |
| Business value | 25% |
| Closeness to conversion | 20% |
| Available new information or utility | 15% |
| Chance of ranking | 15% |
| Demand | 10% |
| Reuse across the site | 10% |
| Distribution potential | 5% |
| Build and maintenance effort | Subtract from the score |

Before approving a page, answer:

1. Which distinct task does it serve?
2. Why does it need its own URL?
3. What will it contain that current results do not?
4. Which business action can follow?
5. Which pages will link to it, and where will it link next?
6. Who will maintain it?
7. Why can it beat the current results?

Merge or reject the page when these answers are weak.

## 7. Design the smallest useful site structure

Arquitectura SEO Transaccional turns commercially useful demand into a planned hierarchy before the team starts publishing at scale.

A common structure looks like this:

```text
Home
├── Main business line
│   ├── Category or problem hub
│   │   ├── Product, service, or solution page
│   │   ├── Comparison or alternatives page
│   │   ├── Use case page
│   │   └── Supporting guide
│   └── Secondary category
├── Another business line
└── Research, tools, guides, and reference assets
```

The blog is not a separate world. Informational pages should connect to the commercial pages they support.

Apply these rules:

* Every indexable URL needs a job. It should answer a distinct task, help navigation, add unique information, support an important page, earn citations, or meet a real legal or trust need.
* Every important page needs an intentional route from navigation, a category, a hub, or a related page.
* Parent pages must help people choose. A short introduction followed by a link list is not enough.
* Important pages should receive more relevant internal links.
* A filter deserves an indexable URL only when it has its own demand, useful output, a stable address, internal links, and an owner.

Do not index a page just because a database can generate it.

Maintain a URL registry with:

* Canonical URL.
* Page and index status.
* Primary task and query group.
* Page type.
* Parent and child pages.
* Primary conversion.
* New information or utility.
* Internal link sources.
* Owner.
* Last verification date.
* Update schedule.

Use the registry for production, links, canonicals, redirects, pruning, experiments, localization, and generated pages.

## 8. Work backward from the transaction

Reversal Inbound maps the full customer journey but starts with searches closest to a purchase.

| Order | Search stage | Common page |
| ---: | --- | --- |
| 1 | Direct action | Product, category, service, or pricing page |
| 2 | Final evaluation | Comparison, alternatives, or review page |
| 3 | Solution choice | Use case page or solution hub |
| 4 | Problem understanding | Guide, diagnostic, or tutorial |
| 5 | General awareness | Educational page |

The point is not to publish only sales pages. It is to test whether the business can attract and convert valuable demand before paying for a large library of broad informational content.

Start earlier in the journey when the category is new, direct product demand barely exists, customers need education before they can compare options, or an informational asset is the most credible way to earn links and mentions.

## 9. Give each page a job

Most search pages need some version of this structure:

1. Show at once that the page matches the task.
2. Give the direct answer or promised result near the top.
3. Provide a way to decide, such as a table, list, calculator, method, recommendation, tool, or filter.
4. Show evidence through data, examples, screenshots, tests, sources, or a documented method.
5. Explain the criteria behind the recommendation.
6. State tradeoffs and limits.
7. Address exceptions that could change the answer.
8. Make the next useful action clear.
9. Link to the next relevant pages.

Keep a section only when it answers, proves, compares, reduces uncertainty, or helps the reader act.

Create a brief before drafting. Include:

* URL and page type.
* User task and audience.
* Decision the page must support.
* Search result format.
* Primary conversion.
* Promise.
* Required evidence.
* New utility or information.
* Comparison criteria.
* Questions to answer.
* Sources.
* Internal links in and out.
* Freshness requirements.
* Owner.
* Success metric.
* Guardrails.

Evidence tends to improve in this order:

1. Rewritten public information.
2. Synthesis with named sources.
3. Expert analysis.
4. First-hand experience.
5. Original measurements or data.
6. A documented comparison method.
7. A tool that helps the user complete the task.

The more valuable and competitive the query, the stronger the evidence should be.

## 10. Make the business easy to identify

Search engines and AI systems need an unambiguous account of:

* The brand name.
* What the company does.
* Its category.
* Its founders and authors.
* Which site, profiles, repositories, products, and pages belong to it.
* Which claims about it independent sources support.

Keep those facts consistent across the site, author pages, product listings, repositories, structured data, social profiles, and legitimate third-party mentions.

Do not create dozens of empty profiles. Consistency matters. Profile count does not.

## 11. Earn authority with work worth citing

A useful page may deserve attention. Search engines still need reasons to trust it.

Authority can grow through real links, branded searches, repeat use, independent mentions, original research, citations, and a record of accurate work.

Use this sequence:

1. Make something relevant people would cite.
2. Publish it at a stable URL.
3. Send it to people who care about the subject.
4. Earn real mentions and links.
5. Link from the asset to the commercial pages it supports.

Assets that often earn citations include datasets, statistics, calculators, benchmarks, research reports, templates, public indexes, tools, charts, and transparent comparisons.

Look for independent confirmation. Twenty copies of one press release still come from one source. A journalist's analysis, a user's recommendation, a public repository, and an expert citation carry different evidence.

## 12. Plan distribution before publishing

Publishing and waiting is not a plan.

One research asset might produce:

* The complete page on the company's site.
* A public dataset or repository.
* A chart.
* A useful discussion in a relevant community.
* A short social post.
* A newsletter contribution.
* A pitch to a journalist who covers the subject.
* A video.
* A partner resource.

Keep the website as the canonical source, then adapt the idea for places where the audience already spends time.

Use third-party distribution to grow assets the business controls, such as the website, product, database, email list, and brand.

## 13. Improve the odds of appearing in AI answers

AI visibility is part of the same job. AI systems also need to decide what the company is, which source to trust, where the clearest answer lives, and whether other credible sources agree.

Do not treat AI visibility as one fixed ranking. Measure how often the brand appears across a stable set of customer questions, whether the description is accurate, and whether the answer cites the brand's pages.

Machines often retrieve a passage instead of processing a whole page. Write important claims so they make sense on their own.

Weak claim:

> We analysed many products and found some differences.

Useful claim:

> We analysed 360 investing tools. The median AI tool costs $22.46 per month. The median non-AI tool costs $20.83.

Make key information easy to extract with clear headings, direct answers, HTML tables, defined terms, visible dates, named sources, a documented method, stable URLs, short summaries, and specific claims.

## 14. Enforce a technical contract

Technical SEO will not create demand or make a generic page useful. It removes barriers between a useful page and the people or systems trying to retrieve it.

Every search page should normally have:

* A successful `200` response.
* Useful HTML that a crawler can retrieve.
* No accidental `noindex`.
* A stable URL.
* A consistent canonical.
* Crawlable internal links.
* Sitemap inclusion when appropriate.
* The important content on mobile.
* No login requirement.

Also check that:

* `robots.txt` manages crawling. It does not reliably remove a page from search.
* Canonicals, internal links, redirects, sitemaps, and `hreflang` agree.
* Sitemaps contain successful, canonical, indexable URLs that belong in search.
* Parameters and filters cannot create an endless set of duplicates.
* JavaScript applications return useful HTML, real links, correct metadata, and honest error status codes.
* Mobile pages contain the important content and metadata.
* Performance supports users and conversion.
* Structured data matches visible content.
* Each international version has its own URL, demand research, real localization, and correct `hreflang`.

Report failures by impact and affected URL count. Do not bury a sitewide indexation problem beneath minor metadata suggestions.

## 15. Improve what happens after the click

A ranking that produces no useful action has little business value.

Commercial pages need:

* A clear match between the search and the page.
* One primary action.
* A lower-commitment secondary action when it helps.
* Relevant proof.
* Honest limits.
* Clear pricing or process when the business can disclose it.
* Short forms.
* Good mobile usability.
* Clear expectations after the action.

Match the action to intent. A person ready to buy may need a purchase or trial. A person learning about the problem may need a tool, category page, resource, or subscription.

Track profit after the cost of the channel:

```text
Organic contribution
=
Organic gross profit
− SEO production cost
− Maintenance cost
− Variable delivery cost
```

For long sales cycles, include assisted conversions, lead quality, activation, retention, churn, refunds, and sales acceptance.

## 16. Measure the whole path

Use this order of metrics:

| Layer | Examples |
| --- | --- |
| Eligibility | Crawlability, canonicals, and index rules |
| Discovery | Indexed pages and pages receiving impressions |
| Visibility | Impressions and ranking distribution |
| Acquisition | Clicks, non-brand clicks, and click-through rate |
| Usefulness | Task completion and useful interactions |
| Conversion | Leads, purchases, and signups |
| Customer quality | Activation, retention, and qualified lead rate |
| Economics | Revenue, contribution, payback, and return on investment |
| Accumulated value | Links, branded searches, and returning users |

Measure by page and query group. Sitewide traffic can hide falling sections, pages competing with one another, weak customer value, or a surge in low-value visits.

Use these patterns as starting hypotheses:

| Pattern | What to investigate |
| --- | --- |
| No impressions | Index status, demand, intent, canonical, and internal links |
| Impressions with poor positions | Authority, relevance, and page type |
| Positions with few clicks | Title, offer, result format, and actual position |
| Clicks with no conversion | Intent, offer, page experience, and conversion path |
| Several URLs swapping positions | Competing pages or an unclear canonical |
| Old pages losing traffic | Freshness, competition, and outdated claims |
| Good conversion with low visibility | Authority, internal links, and adjacent demand |
| High traffic with weak profit | Wrong audience or low-value intent |

Investigate before prescribing a fix.

## 17. Run controlled experiments

Search results are noisy. Competitors, seasonality, crawling, new links, algorithm changes, and unrelated releases may move the numbers.

Use this experiment card:

```text
Experiment:
Current constraint:
Hypothesis:
Why the change should work:
Eligible URLs:
Control or comparison group:
Change:
Primary metric:
Guardrails:
Expected early signal:
Start date:
Review dates:
Other changes that may affect the result:
Decision rule:
Reversal plan:
Result:
Conclusion:
```

Run experiments in parallel only when they affect separate URL groups or separate parts of the system.

Do not change the template, body, title, internal links, and promotion for the same URLs at once if you need to learn which change worked.

Small sites rarely have enough data for perfect statistical certainty. Use comparable groups, before and after evidence, a change log, reversible decisions, and repeated results.

## 18. Scale a proven page system

The repeatable unit is not an article. It is this complete combination:

```text
User task
+ Page type
+ New information or utility
+ Useful page experience
+ Conversion path
+ Internal links and distribution
+ Maintenance process
```

Do not scale a template until pilot pages:

* Can be crawled and indexed.
* Receive relevant impressions.
* Complete the intended task.
* Show useful engagement or conversion.
* Contain real differences from competing pages.
* Receive enough internal links.
* Can stay accurate at an acceptable cost.

A database with 100,000 combinations does not justify 100,000 indexable pages.

Use AI for tasks that require language judgment, such as query normalization, intent grouping, entity extraction, result classification, brief assistance, source summaries, internal link suggestions, stale claim detection, and consistency checks.

Use ordinary code for predictable transformations. Do not use a language model as the source of truth. Save source details, require structured output, validate fields, cache research, make repeated jobs safe, and block publication when evidence is missing.

A reliable production process looks like this:

```text
Collect data
→ Normalize it
→ Group related intent
→ Approve the site structure
→ Write the brief
→ Collect evidence
→ Draft
→ Check claims
→ Run technical and editorial checks
→ Publish
→ Monitor
→ Refresh, improve, merge, or remove
```

## 19. Manage several projects as a portfolio

Do not build ten complete sites and wait to see which one works. Increase spending only when the evidence improves.

Use these stages:

1. Write the thesis. Define the audience, problem, revenue model, demand, and reason the project can win.
2. Check the opportunity. Build the SEO fit score, demand map, result analysis, conversion map, and candidate query groups.
3. Run a pilot. Build the core structure, tracking, a small set of valuable pages, one citation-worthy asset, and basic distribution.
4. Look for proof. Check indexation, relevant impressions, query growth, qualified visits, conversions, and repeatable quality.
5. Scale. Add proven page types, adjacent queries, stronger internal links, authority work, and justified local or international versions.
6. Maintain. Refresh useful pages, protect rankings, improve conversion, consolidate duplicates, and reduce maintenance cost.
7. Stop, merge, or change direction. Do this when profit stays weak, differentiation is not possible, demand disappoints, maintenance costs too much, or another channel has a better expected return.

A reasonable starting allocation is:

* 70% for projects and query groups that already work.
* 20% for improvements and adjacent opportunities.
* 10% for new SEO ideas.

Move resources according to the next expected return, not the amount already spent.

Share useful capabilities across projects, including crawlers, schemas, analytics, research tools, page components, technical standards, quality checks, source libraries, and experiment templates.

Do not share copied content, fake authors, manufactured links, or sites built mainly to send authority to other owned sites.

## 20. Keep a fixed review schedule

Every week:

* Review indexation and serious technical failures.
* Inspect material query and page changes.
* Review active experiments.
* Publish or improve the highest-value pages.
* Check conversions and customer quality.
* Update the change log.
* Investigate anomalies that could change a decision.

Every month:

* Review profit by query group.
* Compare projects.
* Refresh valuable pages.
* Consolidate pages that compete with one another.
* Inspect internal link coverage.
* Run authority and distribution work.
* Move resources toward better returns.

Every quarter:

* Recalculate SEO fit.
* Rebuild the opportunity backlog.
* Review the site structure.
* Find declining or obsolete sections.
* Decide what to scale, maintain, merge, or stop.
* Review local and international opportunities.
* Audit automation quality, source freshness, and maintenance cost.

## What to return

Give me one working plan, not a collection of disconnected tips. Use this structure:

1. Business and conversion summary.
2. SEO fit score and verdict.
3. Assumptions and missing evidence.
4. Customer decision path.
5. Demand groups and search intent.
6. Priority table with value, rankability, cost, and reason.
7. Recommended site structure.
8. URL registry for the first release.
9. Briefs for the highest-priority pages.
10. Technical problems that could block the plan.
11. Authority and distribution plan.
12. AI visibility question set and citation checks.
13. Conversion and measurement plan.
14. First experiments with decision rules.
15. Work for the next 30, 60, and 90 days.
16. What to postpone, merge, or reject.

For every recommendation, say which evidence supports it, what it should change, how we will measure it, who should own it, and when we should stop.

Keep the final principle in view:

> Answer a valuable question with the smallest useful set of pages. Add something worth choosing and citing. Earn attention. Measure the business result. Scale only after the system works.

# The Reusable Business Scaling Operating System
## A Hormozi-inspired guide to finding the constraint, fixing it, scaling the winner, and repeating the process
This is not one official Hormozi framework reproduced verbatim. Acquisition.com publishes separate systems for business stages, constraints, offers, lead generation, sales, and money models. This guide combines those pieces into one reusable operating system that can be applied to almost any business.
The entire system can be summarized as:
```text
Choose one outcome
→ Map the business
→ Find the constraint
→ Fix the constraint
→ Scale what works
→ Standardize it
→ Delegate it
→ Find the next constraint
```
The hard part is not knowing another tactic. It is correctly identifying what matters now and ignoring everything else.
---
# Part I: The fundamental model
## 1. What scaling actually means
Scaling does not simply mean increasing revenue.
A business scales when it can increase the number of customers served and the profit generated without producing a proportional increase in:
* Founder involvement
* Costs
* Complexity
* Customer complaints
* Delivery times
* Errors
* Cash requirements
* Operational risk
A business that doubles revenue but triples headcount, destroys margins, increases churn, and requires the founder to work twice as much has grown, but it has not scaled well.
A useful universal output is:
```text
Retained profitable customers per period
```
This combines four things that revenue alone hides:
1. Customers are acquired.
2. Customers actually buy.
3. Customers receive enough value to remain.
4. The company makes money serving them.
Hormozi commonly reduces growth to three broad levers:
```text
Get more customers
Make each customer worth more
Keep customers longer
```
Everything else should ultimately support one of those three outcomes or reduce the risk that they stop happening.
---
## 2. Apply the framework to one project at a time
Every business has a constraint.
A portfolio of businesses also has a constraint, which is usually one of:
* Your attention
* Your available capital
* Your ability to recruit operators
* Your technical capacity
* Your distribution
* Your risk tolerance
Do not attempt to find and solve the constraint in five projects simultaneously.
For each operating cycle, choose:
* One primary project receiving most of your attention
* One proven project receiving maintenance
* At most one small exploratory bet
Inside each project, identify only one primary constraint.
You can maintain multiple projects. You cannot aggressively transform all of them at the same time without fragmenting your effort.
---
# Part II: Identify the business stage
The appropriate constraint depends on the stage of the business.
Acquisition.com’s current roadmap moves through ten stages: Improvise, Monetize, Advertise, Stabilize, Prioritize, Productize, Optimize, Categorize, Specialize, and Capitalize. The labels matter less than the sequence: learn manually, prove monetization, generate demand, stabilize delivery, focus, productize, optimize, organize, specialize, and finally allocate capital and build durable enterprise value.
Use the following practical interpretation.
| Stage              | The real question                                           | Evidence required                                       | Common premature activity              |
| ------------------ | ----------------------------------------------------------- | ------------------------------------------------------- | -------------------------------------- |
| **1. Discover**    | Is there a painful problem for a specific buyer?            | Repeated conversations and observable existing behavior | Building a large product               |
| **2. Monetize**    | Will anyone pay for the outcome?                            | Founder-led paid sales                                  | Branding, automation, hiring           |
| **3. Acquire**     | Can we produce qualified opportunities repeatedly?          | One acquisition method that works                       | Launching five channels                |
| **4. Stabilize**   | Can we serve customers consistently?                        | Quality holds as volume increases                       | Buying much more traffic               |
| **5. Focus**       | Which avatar, offer, and channel deserve concentration?     | Clear segment and funnel data                           | Adding more products                   |
| **6. Productize**  | Can delivery occur through a repeatable system?             | Documented process and predictable result               | Hiring without a process               |
| **7. Optimize**    | Can we improve margin, conversion, retention, and capacity? | Stable baseline and reliable measurements               | Constant reinvention                   |
| **8. Organize**    | Can functions operate with clear owners?                    | Departmental ownership and accountability               | Founder approving everything           |
| **9. Specialize**  | Can narrower roles outperform generalists?                  | Enough volume to justify specialists                    | Creating unnecessary management        |
| **10. Capitalize** | Where should the next unit of cash and attention go?        | Predictable operating engine                            | Diversifying before mastering the core |
## The stage rule
> Do not solve a problem belonging to a stage you have not reached.
Examples:
* Do not automate a sales process that has never closed customers manually.
* Do not hire ten employees before delivery is repeatable.
* Do not optimize advertisements when customers do not retain.
* Do not diversify acquisition when the first channel has not been fully exploited.
* Do not build management layers for work that does not yet exist.
---
# Part III: Define the outcome
## 3. Choose one 90-day business outcome
A constraint only exists relative to an objective.
Bad objectives:
* Improve marketing
* Build brand awareness
* Make the product better
* Grow social media
* Hire a sales team
* Add artificial intelligence
Better objectives:
* Increase monthly contribution profit from €20,000 to €35,000.
* Increase completed profitable orders from 200 to 350 per month.
* Increase retained paying customers from 500 to 750.
* Reduce customer acquisition payback from nine months to five months.
* Increase delivery capacity from 40 to 70 customers per month without increasing complaints.
* Reduce monthly customer churn from 6% to 3%.
Use this format:
```text
Increase [final business outcome]
from [current baseline]
to [target]
by [date]
without worsening [guardrails].
```
Example:
```text
Increase retained profitable customers from 100 to 150 per month
within 90 days
without reducing gross margin below 65%
or increasing first-response time above four hours.
```
## Separate the outcome from the method
The goal is not “hire three salespeople.”
Hiring is an intervention.
The actual goal might be:
```text
Increase completed sales from 40 to 70 per month.
```
Maybe hiring is the correct move. Maybe the real issue is lead quality, salesperson utilization, follow-up, pricing, or poor qualification.
Never put the proposed solution inside the objective.
---
# Part IV: Map the business
## 4. Write the complete system from left to right
Almost every business can be represented as:
```text
Market
→ Offer
→ Attention
→ Lead
→ Sales conversation or checkout
→ Payment
→ Onboarding
→ Delivery
→ Customer result
→ Retention
→ Expansion
→ Referral
```
Different business models use different labels.
| Business model         | Typical system                                                                       |
| ---------------------- | ------------------------------------------------------------------------------------ |
| **Service**            | Lead → appointment → show → sale → payment → fulfillment → renewal/referral          |
| **SaaS**               | Visitor → signup → activation → paid conversion → retention → expansion              |
| **E-commerce**         | Visitor → product view → cart → checkout → delivery → repeat purchase                |
| **Marketplace**        | Supply → demand → match → transaction → successful fulfillment → repeat              |
| **Media or affiliate** | Audience → qualified visit → click → merchant conversion → commission → repeat visit |
| **Education**          | Lead → enrollment → activation → completion → result → continuity or next offer      |
For every stage, measure:
* Input volume
* Conversion rate
* Cycle time
* Safe capacity
* Cost
* Quality
* Owner
## The basic funnel equation
```text
Final customers =
Starting opportunities
× conversion rate at every stage
```
Example:
```text
10,000 visitors
× 5% become leads
× 20% book
× 70% show
× 30% buy
= 21 customers
```
Improving the weakest-looking percentage is not automatically correct.
A stage is the constraint only when improving it increases final system output.
---
# Part V: Find the constraint
## 5. Start with the 2× test
Ask:
> If we doubled our advertising, outreach, content, or other demand-generating activity tomorrow, could we successfully serve the additional customers?
Hormozi’s distinction is:
* If doubling demand creates operational chaos, you have a **supply constraint**.
* If the business could comfortably serve the extra customers, you have a **demand constraint**.
```text
                         2× DEMAND TEST
                                │
             ┌──────────────────┴──────────────────┐
             │                                     │
     Delivery would break                 We could handle it
             │                                     │
     SUPPLY CONSTRAINT                    DEMAND CONSTRAINT
```
A supply constraint usually appears in:
* Inventory
* Equipment
* Skilled labor
* Onboarding
* Fulfillment
* Customer support
* Management
* Working capital
* Founder availability
A demand constraint usually appears in:
* Market selection
* Offer strength
* Awareness
* Lead generation
* Lead quality
* Sales conversion
* Pricing
* Follow-up
* Customer economics
Acquisition.com currently groups the most common constraints into four areas: getting customers, selling, delivering, and how the company operates. Founder dependence frequently sits underneath all four.
---
## 6. Walk through the full diagnostic tree
### Question 1: Is there a proven market?
Ask:
* Does a specific group experience this problem repeatedly?
* Is the problem painful enough that people already spend money or time trying to solve it?
* Can the buyer afford a solution?
* Can you identify and reach the buyer?
* Are people paying, or merely saying the idea sounds interesting?
If no, the constraint is probably the **market or problem selection**.
If yes, continue.
### Question 2: Can you sell the offer manually?
Ask:
* Can the founder close qualified buyers?
* Do customers understand the promised outcome?
* Does the offer feel materially different from alternatives?
* Is the price 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 the **offer, positioning, market, or sales conversation**.
If customers buy, continue.
### Question 3: Are there enough qualified opportunities?
Ask:
* Are enough suitable people seeing the offer?
* Are they responding?
* Are they becoming leads?
* Is lead quality acceptable?
* Can the volume be increased predictably?
If no, the constraint is **acquisition**.
If yes, continue.
### Question 4: Are qualified opportunities converting?
Measure:
```text
Lead response
→ Qualification
→ Booking
→ Show rate
→ Close rate
→ Payment collection
```
The constraint might be:
* Slow response
* Poor qualification
* Scheduling friction
* Low show rate
* Weak sales process
* Lack of follow-up
* Payment friction
* Poor offer
If opportunities exist but sales do not, the constraint is **sales or the offer**.
If customers buy, continue.
### Question 5: Can the business fulfill twice the volume?
Ask:
* Which stage would accumulate a queue?
* Where are customers currently waiting?
* Which employees are permanently overloaded?
* Where does quality fall when volume rises?
* What work can only one person perform?
* What inventory, capital, equipment, or vendor would run out?
If something breaks, the constraint is **delivery or operational capacity**.
If the system can handle more, continue.
### Question 6: Do customers achieve the promised result?
Measure:
* Activation
* Time to first value
* Completion
* Customer outcomes
* Complaints
* Refunds
* Support load
* Repeat usage
If customers buy but do not achieve the outcome, the constraint is **product or delivery quality**.
If they achieve it, continue.
### Question 7: Do customers stay and become more valuable?
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 **retention, customer success, or recurring value**.
If customers stay, continue.
### Question 8: Are the economics scalable?
Measure:
* Gross margin
* Customer acquisition cost
* Contribution margin
* Payback period
* Refunds
* Working-capital requirements
* Realized lifetime gross profit
* Cash collection timing
If every customer is profitable eventually but consumes too much cash upfront, the constraint may be **payback period or working capital**.
If customers are structurally unprofitable, the constraint is the **business model, pricing, delivery cost, or retention**.
### Question 9: Can the company operate without the founder?
Ask:
* Does every decision require founder approval?
* Are employees waiting for answers?
* Is important knowledge stored only in the founder’s head?
* Can anyone else sell, hire, price, or solve customer problems?
* Does performance collapse when the founder is absent?
If yes, the constraint is **founder dependency, management, or operating systems**.
---
## 7. Confirm that it is the real constraint
A weak metric is not necessarily a constraint.
Use four tests.
### The counterfactual test
Ask:
> If this metric improved by 50% tomorrow and everything else remained unchanged, how much would the final business outcome improve?
If the answer is “almost nothing,” it is not the current constraint.
### The queue test
Ask:
> Where does work, demand, inventory, information, or decision-making wait?
Persistent queues often reveal the bottleneck.
### The throughput test
Ask:
> Which stage currently places the lowest ceiling on completed profitable customers?
That stage is a strong constraint candidate.
### The next-break test
Ask:
> If we removed this constraint, what would break next?
A real constraint should reveal the next bottleneck after it is removed.
## Constraint confirmation checklist
* [ ] It explains why the main objective is being missed.
* [ ] Improving it should increase final output.
* [ ] There is enough upstream input to benefit from the improvement.
* [ ] Downstream stages can initially absorb the improvement.
* [ ] The constraint can be measured.
* [ ] A concrete intervention can be tested.
* [ ] The proposed improvement will not destroy quality, margin, or retention.
---
# Part VI: The constraint playbooks
# 8. Market constraint
## Symptoms
* People like the idea but do not pay.
* Sales require long explanations.
* Prospects do not feel urgency.
* Almost every conversation ends with a price objection.
* Retention is poor because the problem is not important.
* You cannot clearly identify the buyer.
* Acquisition channels contain few suitable prospects.
## Diagnostic tests
### Customer-behavior interviews
Ask about what people have already done:
* When did the problem last occur?
* What did it cost?
* What have they tried?
* What are they currently paying?
* Who owns the budget?
* What happens if they do nothing?
Do not rely on:
> “Would you buy this?”
People are bad at predicting hypothetical purchasing behavior.
### Manual pre-sale
Describe a clear outcome, request payment, and manually deliver the result.
Payment is stronger evidence than praise, survey responses, email signups, or waiting-list registrations.
### Concierge pilot
Perform the service manually before building the scalable product.
This reveals:
* The real workflow
* Required inputs
* Common objections
* What the customer values
* Which parts can eventually be automated
## Exit condition
You have repeated paid demand from a recognizable type of buyer for a recognizable outcome.
A practical early-stage default is five to ten paid customers from founder-led selling, but the required evidence increases with the capital and time required to build the business.
---
# 9. Offer constraint
The offer is not merely the product.
It includes:
* The customer
* The promised outcome
* The mechanism
* Deliverables
* Price
* Payment structure
* Proof
* Risk reversal
* Timing
* Support
* Bonuses
* Positioning
* Scarcity or urgency
Acquisition.com’s offer course explicitly covers market selection, pricing, the Value Equation, offer construction, bonuses, guarantees, scarcity, urgency, and naming.
## The Value Equation
Hormozi’s Value Equation is:
```text
             Dream Outcome × Perceived Likelihood of Success
Value ∝  ─────────────────────────────────────────────────────
                  Time Delay × Effort and Sacrifice
```
The official checklist recommends increasing the desired outcome and perceived probability of success while reducing time to success and required effort.
## Offer audit
### Dream outcome
Ask:
* What does the customer ultimately want?
* Are you selling the outcome or merely describing features?
* Is the outcome important enough to justify action?
### Perceived likelihood
Increase confidence through:
* Demonstrations
* Case studies
* Testimonials
* Transparent methodology
* Guarantees
* Credentials
* Proof of previous results
* Clear explanations of why the mechanism works
### Time delay
Reduce the time before the customer:
* Sees progress
* Receives the first deliverable
* Achieves the first meaningful result
* Understands that the purchase was worthwhile
### Effort and sacrifice
Reduce:
* Setup
* Learning
* Data entry
* Coordination
* Decision fatigue
* Required behavior change
* Switching friction
* Ongoing maintenance
## Reusable offer card
```text
Customer:
Problem:
Desired outcome:
Current alternative:
Unique mechanism:
Time to first value:
Full time to outcome:
Customer effort required:
Deliverables:
Proof:
Risk reversal:
Price:
Payment terms:
Reason to act now:
```
## Offer experiment
Keep the same audience and acquisition method while testing one meaningful offer variable:
* Outcome
* Price
* Packaging
* Guarantee
* Payment terms
* Time to value
* Proof
* Deliverable
* Positioning
Measure both:
```text
Conversion rate
and
Gross profit per opportunity
```
A cheaper offer can convert more prospects while producing less profit.
---
# 10. Acquisition constraint
Hormozi’s Core Four divides lead generation by whether communication is one-to-one or one-to-many, and whether the audience knows you or does not know you. The resulting practical channels are warm outreach, cold outreach, content, and paid advertising. His lead-generation material also includes referrals, employees, agencies, and affiliates as ways to have other people generate leads.
|                                | One-to-one    | One-to-many      |
| ------------------------------ | ------------- | ---------------- |
| **People who know you**        | Warm outreach | Organic content  |
| **People who do not know you** | Cold outreach | Paid advertising |
## Recommended sequence
For an unproven business:
```text
Warm outreach
→ Targeted cold outreach
→ Consistent content
→ Referrals and partnerships
→ Paid acquisition
```
This is not mandatory, but it usually produces learning more cheaply than starting with large advertising budgets.
## Rule of 100
The Rule of 100 is a volume discipline: perform roughly 100 repetitions of the primary activity daily instead of drawing conclusions from tiny samples.
Depending on the business, a primary action might be:
* One targeted outreach message
* One call
* One advertisement variation
* One distribution attempt
* One content unit
* One follow-up
* One sales practice repetition
Adapt the volume to the channel.
For high-value enterprise sales, 100 generic messages may be worse than 15 deeply researched approaches. The point is sufficient consistent volume, not spam.
## Diagnose acquisition by stage
```text
Impressions
→ Attention
→ Click or response
→ Lead
→ Qualified lead
→ Appointment or checkout
```
| Weak stage                 | Likely issue               |
| -------------------------- | -------------------------- |
| Low reach                  | Insufficient distribution  |
| Reach but no attention     | Weak hook or targeting     |
| Attention but no response  | Weak message or offer      |
| Responses but poor leads   | Targeting or qualification |
| Good leads but no booking  | Friction or follow-up      |
| Bookings but no attendance | Commitment and reminders   |
## Acquisition exit condition
You have at least one channel that can produce qualified opportunities at acceptable economics with enough consistency to plan around it.
---
# 11. Sales constraint
## Map the complete sales process
```text
Lead received
→ First response
→ Qualification
→ Appointment
→ Attendance
→ Discovery
→ Offer presented
→ Objections handled
→ Decision
→ Payment collected
→ Post-sale reinforcement
```
Measure conversion and cycle time at every stage.
## Distinguish an offer problem from a salesperson problem
A useful test:
* If the founder or best salesperson cannot sell the offer to qualified prospects, suspect the market or offer.
* If the best salesperson closes consistently but others do not, suspect training, process, management, or hiring.
* If prospects agree but do not pay, suspect payment process, urgency, decision authority, or follow-up.
* If close rate is strong but profit is weak, suspect price or packaging.
## The CLOSER structure
Hormozi’s sales material uses the CLOSER framework as a structure for sales conversations:
* **C:** Clarify why the prospect is there.
* **L:** Label the problem.
* **O:** Overview previous experiences and attempted solutions.
* **S:** Sell the destination or outcome.
* **E:** Explain concerns and remove uncertainty.
* **R:** Reinforce the decision after the purchase.
Do not treat it as a magic script. Its value is that it creates a repeatable structure that can be measured and coached.
## Sales improvement process
1. Record calls.
2. Review wins and losses.
3. Identify the exact stage where deals fail.
4. Define observable behaviors for that stage.
5. Rewrite the script or process.
6. Role-play.
7. Test with real qualified prospects.
8. Compare performance by salesperson, segment, source, and offer.
9. Turn the winning behaviors into a scorecard.
---
# 12. Delivery and capacity constraint
## Map delivery as a production line
```text
Payment
→ Onboarding
→ Setup
→ Core delivery
→ Quality control
→ Customer support
→ Completion
→ Renewal
```
For every stage, record:
| Metric             | Question                                        |
| ------------------ | ----------------------------------------------- |
| Current throughput | How many units per period?                      |
| Safe capacity      | How many can be completed without quality loss? |
| Cycle time         | How long does one unit take?                    |
| Queue              | How much work is waiting?                       |
| Error rate         | How often must work be corrected?               |
| Owner              | Who is accountable?                             |
| Dependency         | Which person, vendor, or tool is required?      |
The first necessary stage that cannot absorb additional volume is usually the operational constraint.
## Fix delivery in this order
### 1. Eliminate
Remove:
* Unnecessary approvals
* Redundant steps
* Low-value customization
* Duplicate data entry
* Meetings that do not change decisions
* Reports nobody uses
### 2. Protect the bottleneck
Do not let scarce specialists spend time on:
* Administration
* Scheduling
* Data cleaning
* Routine communication
* Work that can be performed by someone else
### 3. Standardize
Create:
* Templates
* Checklists
* Defined inputs
* Quality criteria
* Decision rules
* Standard operating procedures
### 4. Batch
Group similar work to reduce switching costs.
### 5. Automate
Automate only after the manual process works and the exceptions are understood.
### 6. Delegate
Transfer repeatable work with clear outputs and quality standards.
### 7. Hire or add infrastructure
Add:
* Employees
* Vendors
* Inventory
* Equipment
* Software
* Working capital
Only after confirming that additional capacity is the actual constraint.
### 8. Regulate demand
When capacity is scarce:
* Raise prices
* Limit availability
* Prioritize valuable customers
* Remove low-margin work
* Create a waiting list
* Change one-to-one delivery into one-to-many delivery where appropriate
## Delivery exit condition
The business can accept meaningfully more customers without an unacceptable decline in:
* Quality
* Delivery time
* Customer outcome
* Gross margin
* Employee workload
* Support response
* Refunds or complaints
---
# 13. Retention constraint
A company can appear acquisition-constrained when its real problem is that customers disappear too quickly.
## Map the retention system
```text
Purchase
→ Onboarding
→ Activation
→ First value
→ Habit or repeated use
→ Outcome
→ Renewal
→ Expansion
```
## Diagnose churn by timing
| Churn timing               | Likely issue                                                     |
| -------------------------- | ---------------------------------------------------------------- |
| Immediately after purchase | Wrong expectations, buyer’s remorse, poor handoff                |
| Before activation          | Setup friction or unclear onboarding                             |
| After initial use          | Weak product or poor fit                                         |
| After achieving result     | Product solves a finite problem with no continuity               |
| After several months       | Declining value, competition, price, or missing ongoing use case |
| During renewal             | Poor value communication or procurement friction                 |
## Retention metrics
Use cohorts rather than broad averages.
Measure:
* Activation rate
* Time to first value
* Percentage achieving the promised outcome
* Retention by acquisition source
* Retention by customer segment
* Gross revenue retention
* Net revenue retention where relevant
* Repeat-purchase rate
* Refund rate
* Churn reason
* Expansion rate
## Improve retention in this order
1. Sell to better-fit customers.
2. Set accurate expectations.
3. Improve onboarding.
4. Reduce time to first value.
5. Make progress visible.
6. Ensure customers use the highest-value behavior.
7. Proactively intervene when usage falls.
8. Improve the core result.
9. Add continuity only when ongoing value genuinely exists.
10. Create natural expansions after the customer has achieved initial value.
---
# 14. Economics and cash constraint
Growth is dangerous when the company does not understand its economics.
## Core formulas
### Customer acquisition cost
```text
CAC =
Total acquisition and sales cost
÷ New paying customers
```
Calculate both:
* Paid-media CAC
* Fully loaded CAC, including sales labor, commissions, software, agencies, and creative production
### Gross profit per customer
```text
Gross profit =
Revenue
− Direct cost of serving the customer
```
### Contribution profit
```text
Contribution profit =
Revenue
− Direct delivery costs
− Variable acquisition and sales costs
```
### Payback period
```text
Payback period =
CAC
÷ Monthly gross profit per customer
```
### Realized lifetime gross profit
```text
Realized lifetime gross profit =
Gross profit actually collected from a customer cohort
```
Use realized cohort data when possible. Do not build the entire plan around an optimistic lifetime-value estimate from immature customers.
## Economics diagnostic
### CAC is too high
Investigate:
* Targeting
* Conversion
* Sales productivity
* Channel costs
* Offer strength
* Price
* Referral rate
### Gross margin is too low
Investigate:
* Delivery labor
* Custom work
* Vendor costs
* Refunds
* Support load
* Product mix
* Price
### Payback is too long
Investigate:
* Upfront payment
* Annual plans
* Deposits
* Onboarding fees
* Faster activation
* Higher price
* Lower CAC
* Earlier upsells
* Reduced delivery cost
### Customer value is too low
Investigate:
* Retention
* Repeat purchase
* Expansion
* Cross-sell
* Continuity
* Customer quality
* Outcome quality
## Money-model architecture
Acquisition.com’s current Money Models framework divides offer architecture into four broad types:
1. **Attraction offers:** make the initial purchase or engagement easier.
2. **Upsells:** allow customers to buy additional value.
3. **Downsells:** provide a smaller or differently structured option.
4. **Continuity offers:** create recurring value and recurring payment.
A generic offer stack might be:
```text
Attraction:
Low-friction entry or sample result
Core:
Primary solution
Upsell:
Greater speed, scope, convenience, access, or outcome
Downsell:
Smaller scope, payment plan, fewer features, or self-service option
Continuity:
Ongoing service, maintenance, monitoring, replenishment, or access
```
Do not add an upsell merely to extract more money. It should solve the customer’s next problem or improve the existing result.
## Economics exit condition
Incremental customers generate attractive contribution profit, the payback period is fundable, and growth does not create a cash crisis.
---
# 15. Operations, people, and founder constraint
## Founder bottleneck test
The founder is probably the constraint when:
* Every meaningful decision requires approval.
* Employees wait instead of acting.
* Only the founder can close important deals.
* Customer exceptions always escalate to the founder.
* Hiring stops when the founder becomes busy.
* The company lacks written decision rules.
* Results decline immediately when the founder steps away.
## Productize before delegating
The preferred sequence is:
```text
Founder performs the work successfully
→ Repeats it
→ Identifies the winning process
→ Documents it
→ Trains another person
→ Measures their output
→ Transfers authority
```
Do not document every experimental process. You will create a large library of procedures for things that do not work.
## Define roles through outputs
Bad role description:
> Help with marketing.
Better role description:
> Produce 80 qualified sales opportunities per month at a fully loaded cost below €100 per opportunity.
Every role needs:
```text
Outcome
Metric
Authority
Inputs
Process
Quality standard
Review cadence
```
## Delegation ladder
1. **Observe:** The employee watches.
2. **Perform with instruction:** The founder directs each step.
3. **Perform with review:** The employee acts, founder verifies.
4. **Recommend:** The employee proposes decisions.
5. **Decide within limits:** The employee has defined authority.
6. **Own the result:** The employee controls the process and metric.
Delegation is incomplete until decision rights move with the work.
## Management cadence
A manager should own:
* One clear output
* A small set of leading metrics
* The people and resources required
* A weekly operating review
* Corrective actions when metrics miss
Do not make someone responsible for an outcome while withholding the authority needed to produce it.
---
# 16. Concentration and risk constraint
Once the core 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
* Single-product dependency
* Data or technology dependency
* Cash and refinancing risk
Do not diversify prematurely.
Diversification has a cost. It fragments attention, reduces volume per channel, and slows learning.
Reduce a concentration only when:
1. The core engine is already functioning.
2. The concentration creates material existential risk.
3. The alternative can be developed without damaging the core.
4. There is enough management capacity to support it.
---
# Part VII: Choose the intervention
## 17. Separate the constraint from the proposed fix
Example:
```text
Constraint:
Onboarding capacity is limited to 100 customers per month.
Possible interventions:
- Remove unnecessary onboarding steps.
- Create group onboarding.
- Automate account setup.
- Improve training.
- Hire another onboarding specialist.
- Charge for custom onboarding.
```
The constraint is not “we need another employee.”
That is one possible intervention.
## Intervention priority formula
A useful approximation is:
```text
Priority =
Expected impact × confidence × speed
────────────────────────────────────
Cash required × effort × complexity
```
This is not precise mathematics. Its purpose is to force explicit comparison.
For each intervention, estimate:
* Expected change in the final metric
* Confidence based on evidence
* Time until evidence appears
* Cash required
* Founder attention required
* Reversibility
* Downside risk
Choose the smallest intervention capable of testing the constraint.
---
# Part VIII: Run the experiment
## 18. Use an experiment brief
```text
PROJECT:
_________________________________________
90-DAY OUTCOME:
Increase _________________________________
from __________ to __________ by __________
CURRENT CONSTRAINT:
_________________________________________
EVIDENCE:
_________________________________________
_________________________________________
HYPOTHESIS:
Because _________________________________,
changing ________________________________
should increase __________________________
from __________ to __________.
INTERVENTION:
_________________________________________
PRIMARY LOCAL METRIC:
_________________________________________
FINAL BUSINESS METRIC:
_________________________________________
GUARDRAILS:
Quality: _________________________________
Margin: __________________________________
Retention: _______________________________
Delivery time: ___________________________
Complaints: ______________________________
TEST VOLUME OR DURATION:
_________________________________________
SUCCESS CONDITION:
_________________________________________
KILL CONDITION:
_________________________________________
OWNER:
_________________________________________
REVIEW DATE:
_________________________________________
```
## Experiment rules
* Change one major variable at a time.
* Use enough volume to distinguish signal from noise.
* Run for at least one complete business cycle.
* Define success before seeing the results.
* Track both local and final metrics.
* Include quality and margin guardrails.
* Do not change the test halfway through because early results feel uncomfortable.
* Record unexpected effects.
---
## 19. Interpret the result correctly
### Local metric improves and final output improves
The constraint diagnosis was probably correct.
Scale the intervention.
### Local metric improves but final output does not
Possible explanations:
* It was not the real constraint.
* Another stage immediately became the constraint.
* The local metric was a vanity metric.
* Downstream capacity absorbed none of the improvement.
* Customer quality deteriorated.
### Final output improves but a guardrail collapses
You increased activity, not scalable throughput.
Examples:
* Sales rise but refunds double.
* More customers arrive but gross margin disappears.
* Delivery volume rises but customer outcomes worsen.
* Leads increase but quality falls.
### Nothing changes and volume was low
The result is inconclusive.
Do not confuse a tiny sample with a failed strategy.
### Nothing changes after sufficient volume
Stop the intervention and update your model.
---
# Part IX: Scale the winner
## 20. More, Better, New
Acquisition.com includes “More Better New” as a formal part of its lead-generation course. A practical default is to allocate roughly 70% of resources to More, 20% to Better, and 10% to New. Treat the percentages as a starting point, not a law.
## 70%: More
Repeat what already works.
Examples:
* Increase advertising budget on a profitable campaign.
* Publish more versions of a proven content format.
* Send more of the outreach that receives responses.
* Add capacity to a productive sales process.
* Expand a successful offer to more suitable prospects.
* Create small variations of a winning advertisement.
This is normally the lowest-risk allocation.
## 20%: Better
Improve or extend the winner.
Examples:
* Better targeting
* Stronger hook
* Better proof
* Higher-converting landing page
* Faster onboarding
* Improved sales script
* Better packaging
* More efficient delivery
* Adjacent customer segment
This carries moderate risk because meaningful changes can damage what already works.
## 10%: New
Test something fundamentally different.
Examples:
* New acquisition channel
* New product
* New customer segment
* New pricing model
* New market
* New sales motion
* New delivery mechanism
Most new experiments should be expected to fail.
The goal is not immediate efficiency. The goal is discovering the next winner.
## Promotion ladder
```text
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
Move when:
* Volume cannot be increased safely.
* Marginal returns are declining.
* The channel is reaching capacity.
* Quality is deteriorating.
* Additional volume is becoming prohibitively expensive.
## When to move from Better to New
Move when:
* The process has been materially optimized.
* Additional improvements produce small returns.
* The market or channel is saturated.
* Concentration creates unacceptable risk.
* A new opportunity has a higher expected return than further optimization.
Do not jump to New because you are bored.
---
# Part X: Standardize and delegate
## 21. Turn the result into an operating asset
When an experiment repeatedly works:
1. Document the exact inputs.
2. Document the required behaviors.
3. Define the expected output.
4. Define quality standards.
5. Define common exceptions.
6. Assign an owner.
7. Train through real examples.
8. Review performance.
9. Remove founder approval where possible.
10. Continue testing improvements.
A process is not complete because a document exists.
A process is complete when another competent person can repeatedly produce the expected result without the founder directing every action.
---
# Part XI: Operating cadence
## 22. Daily cadence
Focus on primary actions tied to the current constraint.
Examples:
* Outreach attempts
* Sales conversations
* Customer interviews
* Follow-ups
* Delivery units
* Recruiting conversations
* Experiment variants
* Churn interventions
Do not confuse activity with output, but do measure the activity necessary to produce the output.
## 23. Weekly constraint review
Use a 30 to 60-minute meeting.
### Agenda
1. What is the 90-day outcome?
2. What is the current result versus target?
3. What is the current constraint?
4. What evidence supports that diagnosis?
5. Did the constraint metric improve?
6. Did the final metric improve?
7. Did any guardrail worsen?
8. What did we learn?
9. What will we continue, stop, or change?
10. Who owns the next action and by what date?
Do not fill the meeting with general status updates.
Status can be written. Meetings should produce decisions.
## 24. Monthly review
Review:
* Funnel conversion
* Cohort retention
* Customer outcomes
* Acquisition cost
* Gross margin
* Contribution profit
* Payback period
* Delivery capacity
* Headcount productivity
* Founder dependencies
* Cash requirements
Ask:
> Is the constraint still the same?
## 25. Quarterly review
For every project:
1. Recalculate the economic model.
2. Re-run the 2× test.
3. Identify the current stage.
4. Identify the current constraint.
5. Decide whether to scale, improve, maintain, pause, or kill.
6. Allocate founder time and capital.
7. Choose one company-level outcome for the next cycle.
---
# Part XII: Use the system across many projects
## 26. Classify every project
### Explore
There is a plausible market, but no meaningful paid evidence.
Objective:
```text
Learn whether the problem and customer are real.
```
### Prove
Customers have paid, but the business is still manually delivered or inconsistent.
Objective:
```text
Prove repeatable demand, delivery, and customer value.
```
### Scale
Demand, delivery, retention, and economics are sufficiently proven.
Objective:
```text
Increase volume while protecting economics and quality.
```
### Maintain
The project works but is not currently the highest-return use of additional attention.
Objective:
```text
Preserve performance with minimal founder involvement.
```
### Pause or kill
Evidence does not justify continued investment.
Possible reasons:
* No paid demand after the predeclared test volume
* Weak retention
* Structurally bad economics
* No realistic distribution path
* Excessive regulatory or platform risk
* No available operator
* A better project has materially higher expected value
* The original thesis is no longer true
Do not keep a project alive merely because significant work has already been invested.
---
## 27. Portfolio allocation
A reasonable default adaptation of More, Better, New is:
```text
70%:
Proven projects and proven growth engines
20%:
Adjacent improvements and promising projects with evidence
10%:
Completely new experiments
```
Adjust the allocation to the portfolio stage.
An early portfolio may require more exploration. A mature cash-generating portfolio should usually allocate more to proven engines.
## Project scorecard
Score each project from 1 to 5.
| Factor             | Question                                                    |
| ------------------ | ----------------------------------------------------------- |
| Pain               | How severe and frequent is the problem?                     |
| Willingness to pay | Is there paid evidence?                                     |
| Retention          | Do customers continue using or buying?                      |
| Economics          | Can each customer produce attractive contribution profit?   |
| Distribution       | Is there a credible path to reaching customers?             |
| Founder advantage  | Do you possess unusual insight, skill, audience, or access? |
| Speed to learning  | How quickly can the core assumption be tested?              |
| Capital efficiency | How much cash is required before evidence appears?          |
| Operational burden | How difficult is delivery?                                  |
| Upside             | How large can the opportunity reasonably become?            |
Do not simply add the scores.
A single fatal weakness can invalidate the entire project:
* No willingness to pay
* Impossible economics
* No legal route
* No distribution
* No ability to deliver
## Portfolio decision
For every project, choose one:
```text
SCALE:
The engine works and remains unsaturated.
FIX:
One identifiable constraint prevents growth.
PROVE:
Important assumptions still require evidence.
MAINTAIN:
The project works but deserves little incremental attention.
PAUSE:
Preserve the option 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 are unsure what to do next.
```text
No clear painful customer problem?
→ Research and manually solve problems.
People care but do not 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 offer, sales process, targeting, or trust.
You have sales but delivery breaks?
→ Fix capacity and operations.
Delivery works but customers do not succeed?
→ Fix product quality and time to value.
Customers succeed but leave?
→ Fix continuing value, retention, or customer fit.
Customers stay but growth consumes too much cash?
→ Fix CAC, payback, collection timing, or money model.
Everything works but the founder is overwhelmed?
→ Standardize, delegate, hire, and transfer authority.
The proven mechanism has unused capacity?
→ Do More.
More produces declining marginal returns?
→ Do Better.
More and Better are substantially exhausted?
→ Test New.
An intervention succeeds repeatedly?
→ Document and delegate it.
The constraint disappears?
→ Diagnose the business again.
```
---
# Part XIV: Common mistakes
## Optimizing the non-constraint
Improving an unconstrained stage rarely changes final output.
## Scaling before retention
More customers entering a leaky system creates more churn, support work, and reputational damage.
## Buying traffic before proving the offer
Paid advertising cannot permanently rescue an offer qualified buyers do not want.
## Hiring to solve ambiguity
A new employee cannot execute a process nobody understands.
## Automating too early
Automation makes a process run faster, including a bad process.
## Launching too many channels
Every new channel has a learning curve. Fragmenting volume slows learning in all of them.
## Serving too many avatars
Different avatars require different messaging, sales, pricing, features, delivery, and support.
## Changing several variables simultaneously
You may improve performance without learning what caused it.
## Mistaking low volume for randomness
Tiny samples produce volatile results. Run enough primary actions before drawing conclusions.
## Measuring revenue without gross profit
High revenue can hide poor margins and negative contribution profit.
## Using theoretical lifetime value
Future retention assumptions do not pay current bills.
## Discounting instead of creating value
Lower prices can increase conversion while weakening cash flow, positioning, delivery quality, and customer commitment.
## Failing to define guardrails
An experiment can improve the target metric while damaging the business elsewhere.
## Never re-diagnosing
The solution to one constraint creates the next constraint.
---
# Part XV: The reusable one-page operating sheet
```text
BUSINESS OR PROJECT:
________________________________________________
CURRENT STAGE:
Discover / Monetize / Acquire / Stabilize / Focus /
Productize / Optimize / Organize / Specialize / Capitalize
90-DAY OUTCOME:
Increase _______________________________________
from __________________ to ______________________
by _____________________________________________
FINAL BUSINESS METRIC:
________________________________________________
GUARDRAILS:
Margin: ________________________________________
Quality: _______________________________________
Retention: _____________________________________
Delivery time: __________________________________
Cash: __________________________________________
SYSTEM MAP:
Market
→ Offer
→ Attention
→ Lead
→ Sale
→ Payment
→ Delivery
→ Result
→ Retention
→ Expansion
2× TEST:
Could we successfully handle twice the demand?
YES / NO
CURRENT CONSTRAINT:
Market / Offer / Acquisition / Sales / Delivery /
Retention / Economics / Operations / Founder / Capital
EXACT CONSTRAINED STAGE:
________________________________________________
EVIDENCE:
________________________________________________
________________________________________________
________________________________________________
COUNTERFACTUAL:
If this stage improved by 50%, final output would:
________________________________________________
PROPOSED INTERVENTION:
________________________________________________
PRIMARY LOCAL METRIC:
________________________________________________
EXPECTED CHANGE:
From __________________ to ______________________
TEST VOLUME OR TIME:
________________________________________________
SUCCESS CONDITION:
________________________________________________
KILL CONDITION:
________________________________________________
OWNER:
________________________________________________
REVIEW DATE:
________________________________________________
RESULT:
Confirmed / Rejected / Inconclusive / New constraint found
NEXT ACTION:
More / Better / New / Standardize / Delegate / Stop
NEXT CONSTRAINT:
________________________________________________
```
---
# The complete operating loop
```text
1. Choose one project.
2. Identify its current business stage.
3. Define one 90-day economic outcome.
4. Map the full customer and delivery system.
5. Measure volume, conversion, capacity, quality, and economics.
6. Run the 2× demand test.
7. Identify the single stage limiting final throughput.
8. Confirm it with the counterfactual, queue, and throughput tests.
9. Choose the smallest intervention capable of testing the diagnosis.
10. Define success, failure, duration, and guardrails in advance.
11. Run enough volume to learn.
12. Evaluate the final business outcome, not merely the local metric.
13. Kill failed interventions.
14. Scale successful ones using More, Better, New.
15. Standardize repeated winners.
16. Delegate the process and transfer authority.
17. Re-run the diagnosis.
18. Repeat indefinitely.
```
The central rule is:
> Work on the one problem that currently limits the whole business. Once it stops being the constraint, stop optimizing it and find the next one.