# RevStart Growth Bible

## A marketing think tank that produces useful work

Version 2 · editorial update September 16, 2026. Original reading-room and portfolio observations: September 15. Additional claim checks are dated in section 12.

**RevStart helps a builder find the next credible way to win users, deliver repeat value, and earn revenue. It prepares the work to test each recommendation.** A recommendation is incomplete until it names a customer, an observable problem, a specific action, a usable asset, the evidence behind it, and a decision rule.

This handbook is RevStart's original synthesis. It draws on the public materials listed below. The authors are sources of ideas, not participating advisers, endorsements, simulated people, or a unanimous authority. Public essays, selected archive passages, interviews, and official book/course descriptions were reviewed. Full commercial books and private courses were not ingested. No course worksheets are reproduced. Anecdotes and marketing claims are not treated as causal research.

Explore the five worked examples at [revstart.dev/think-tank](https://revstart.dev/think-tank). They cover Skills Tech Talk, OutDuet, OpenThunder, Leopard Sentinel, and My Christian Bible. Each has a users, usage, and sales plan, prepared material, competing arguments, and a separate practice test. Their real business metrics remain unknown.

**Start here:** choose one product and one goal in the think tank. Use the prepared example, or [browse 24 methods](https://revstart.dev/think-tank#growth-methods) to understand which approach fits. Sections 10 and 11 organize the council and methods. Section 12 explains how the supplied Growth Bible was incorporated and corrected. The [public roadmap](https://revstart.dev/roadmap) describes the broader direction; current capabilities and future implementation must remain distinct.

## 1. Three different growth questions

| Area  | Useful question                                                        | Outcome to count                                               | Misleading substitute                                      |
| ----- | ---------------------------------------------------------------------- | -------------------------------------------------------------- | ---------------------------------------------------------- |
| Users | Are suitable people finding a relevant reason to try?                  | Qualified first-use starts and completions by source           | Raw impressions, shared account registrations              |
| Usage | Do people accomplish something useful and return when the need recurs? | First-value completion and eligible return cohorts             | Page views, time spent, notification opens alone           |
| Sales | Does a buyer pay for a deliverable benefit with sustainable economics? | Reconciled paid customers, net receipts, renewal, contribution | Interest, waitlists, checkout clicks, AI-estimated revenue |

These areas interact, but the next experiment should have one primary question. If no one has tried the product, do not pretend a retention percentage exists. If visitors arrive and repeatedly encounter a broken first step, buying more traffic is premature. If a product is useful but the payer is unclear, design an offer-discovery test rather than a checkout redesign.

“Zero users” and “zero traffic” are different observations. A missing event is not a measured zero. For anonymous tools, signup may be unnecessary. For an occasional weekend planner, daily use is not inherently better. For a Bible reader, session length is not evidence of spiritual value.

## 2. Curated reading room: what each perspective contributes

The selections prioritize materials that answer a distinct product decision, come from the author or an authorized publisher/archive, and can be applied without purchasing a service. They are a working reading list, not an objective ranking of everything these authors have published.

### Steve Jobs: product focus

**Read:** [Make Something Wonderful](https://book.stevejobsarchive.com/), especially the 1997 discussion of simplifying the product roadmap and the 1998 product strategy remarks.

Focus gives a team the opportunity to make a smaller set of experiences excellent and understandable. RevStart application: identify the one useful result a first visitor should reach, then remove competing decisions from that path. Counterweight: taste and a compelling demonstration still need customer observation. This is not permission to ignore feedback or conceal limitations.

### Seth Godin: a specific audience worth serving

**Read:** [The smallest viable audience](https://seths.blog/2022/05/the-smallest-viable-audience/).

A precise audience is a starting commitment to relevance and quality, not necessarily a permanent ceiling. RevStart application: choose a recognizable situation, a reachable group, and a reason to care now. “Software engineers explaining a project in an upcoming interview” is testable; “everyone who wants to learn” is not. Check whether the segment can support the business before expanding investment.

### Neil Patel: demand and search intent

**Read:** [What is Search Intent?](https://neilpatel.com/blog/search-intent/).

The task behind a query matters to the page and next action. RevStart application: separate learning, comparing, and buying situations; inspect current search results before writing. Record useful actions after a visit, not just search volume. A high-volume informational query can produce little demand for the paid offer.

### Ann Handley: editorial usefulness and voice

**Read:** [Everybody Writes, second-edition overview](https://annhandley.com/everybodywrites/); [Total Annarchy](https://annhandley.com/newsletter/) is a further reading destination.

The reviewed book overview emphasizes writing process, original stories, voice, and relationships. RevStart application: make drafts useful to a specific reader, include concrete demonstrations, edit out vague claims, and preserve the founder's real knowledge. Publishing more generated text does not create experience or evidence. The full book was not reviewed in this pass.

### Brian Dean: a page that satisfies the actual task

**Read:** [Search Intent and SEO: How to Optimize for User Goals](https://backlinko.com/hub/seo/search-intent), credited to Brian Dean.

Use the searcher's goal to determine content and format. RevStart application: build one demonstrably useful page around a real question, with original examples and a relevant product step. Recheck current results and competing explanations. Do not turn SEO into word-count targets, mass page generation, or a promise of ranking.

### Mari Smith: relevant conversation and trust

**Read:** [The Human-First Marketing Method public overview](https://www.marismith.com/humanfirst/), relationship and conversation sections.

The useful contribution here is connecting social attention to meaningful conversation and trust. RevStart application: prepare a native contribution that belongs in the community and obtain permission before promotion. Do not treat the sales page as proof of universal performance or algorithm claims. Personality-system material is excluded from RevStart's evidence base. Private training was not accessed.

### Shama Hyder: connected journeys and learning

**Read:** [Five marketing principles from Momentum](https://zenmedia.com/video/5-marketing-strategies-all-entrepreneurs-need-to-learn-from-momentum/), her interview transcript.

Hyder connects analytics, customer context, integration, curation, and cross-pollination. RevStart application: make one strong asset useful across a relevant partner, demonstration, and product experience; learn from each part. Sharing ownership across products does not establish audience overlap. Cross-promotion needs a customer reason, not an ecosystem mandate.

### Jay Baer: differentiation people experience

**Read:** [The Baer Facts #54](https://www.jaybaer.com/newsletter/the-baer-facts-issue-54-why-something-that-occurs-trumps-something-that-exists); [official books](https://www.jaybaer.com/books) for Youtility and Talk Triggers, the latter coauthored with Daniel Lemin.

An experience gives someone a story to share; a feature statement may not. RevStart application: identify a repeatable, affordable moment that is useful enough to describe. Measure voluntary referrals and the referred person's useful experience. Do not assume a share button creates word of mouth or transplant another brand's anecdotal results.

### David Ogilvy: research, benefit, and commercial purpose

**Read:** [Official quotations archive](https://www.ogilvy.com/sites/g/files/dhpsjz106/files/pdfdocuments/O23_OGILVY75_Quotations%20of%20David%20Ogilvy_WEB_0.pdf), selected research, consumer, writing, and advertising passages.

Study what is being sold and whom it helps. RevStart application: show a concrete benefit and credible proof with a clear next action; judge the work against its commercial objective. Historic examples are not current universal benchmarks. Distinguish a demonstrated product capability from an unverified claim about customer outcomes.

### Alex Hormozi: offer value and effort

**Read:** [Official pricing/value course excerpt](https://www.acquisition.com/hubfs/Offer%20Checklists%20-%20PDF%20Downloads/Pricing-Value-Checklist.pdf?hsLang=en) and [public offers lesson](https://www.acquisition.com/training/offers4).

Outcome, confidence, delay, and effort are useful dimensions for examining an offer. RevStart application: define what will be delivered, why it is credible, and how hard it is to start. Check willingness to pay and the cost of delivery. Never convert an attractive promise into a guaranteed result, fake scarcity, or an undeliverable package. No copyrighted checklist is reproduced.

### Mark Ritson: diagnosis before tools

**Read:** [Tactics without strategy is dumbing down our discipline](https://www.marketingweek.com/mark-ritson-beware-the-tactification-of-marketing/).

Make the market choice and objective before choosing the tactic. RevStart application: state why this buyer, alternative, and advantage justify the channel. Keep the diagnosis proportional to the next decision; a solo founder does not need a complex segmentation exercise to observe five first-use sessions. Tool availability is not a strategy.

### Rory Sutherland: context and counterintuitive hypotheses

**Read:** [Finding the Why behind consumer behaviour](https://business.google.com/uk/think/consumer-insights/consumer-behaviour-in-marketing/), a direct interview.

Behavior can reflect context and perception that stated preferences or simple price logic miss. RevStart application: investigate uncertainty, effort, framing, and social context; test a plausible alternative explanation. Do not use an entertaining explanation as causal proof. Keep choice and terms honest; no hidden charges, coercive defaults, or fabricated urgency.

### Rand Fishkin: influence beyond a click

**Read:** [Why Do We Need Zero Click Marketing?](https://sparktoro.com/blog/why-do-we-need-zero-click-marketing/), authored video transcript.

Useful content can reach people on the platform where attention already exists. RevStart application: produce a complete insight or demonstration, then evaluate discovery, buyer-reported sources, and later useful use. Avoid importing dated platform ratios as present-day facts. Zero-click influence is difficult to attribute and must not become invented revenue credit. Related zero-click work includes Amanda Natividad's contributions.

### Donald Miller: the customer's story and next step

**Read:** [StoryBrand publisher overview](https://www.pearson.fr/fr/book/?GCOI=27440100103800) and [official site](https://storybrand.com/).

Put the customer's problem and desired change at the center of a clear message. RevStart application: explain whom the product helps, the practical result, and the next action without making the company the hero of a feature list. Do not exaggerate stakes or imply certification. The proprietary workbook and full commercial book are not reproduced or claimed as reviewed.

## 3. A useful disagreement is part of the output

Do not average every perspective into “make content, run ads, and improve onboarding.” The following are RevStart's decision rules, not claims that the authors debated these products.

| Tension                                             | How RevStart resolves it                                                                                                                                             |
| --------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Narrow first audience versus large revenue ambition | Test relevance and access in one segment; estimate the reachable adjacent market before calling it scalable.                                                         |
| Search traffic versus influence without clicks      | Deliver a useful native answer and maintain an owned destination; report platform reach, referral traffic, self-reported discovery, and paid attribution separately. |
| A stronger offer versus an immature product         | Promise only what can be delivered. Reduce unnecessary effort, then measure the useful result before expanding the offer.                                            |
| Product focus versus acquisition urgency            | Fix a reproducible blocker to the promised outcome; avoid a broad redesign while access to customers remains the main unknown.                                       |
| Quick conversion versus lasting trust               | Make claims inspectable, terms clear, and opting out easy. A conversion that creates refunds or distrust is not a win.                                               |
| More measurement versus a tiny sample               | Instrument the relevant steps, inspect qualitative failures, and avoid treating a handful of sessions as a statistically established lift.                           |

A reviewer should see: the supporting argument, the strongest objection, why the next cheaper option was not chosen, and the evidence that would reverse the decision. For example, an STT campaign loses priority if practice fails; an OutDuet venue offer loses priority if there is no measured local audience to deliver.

## 4. The operating workflow

### Diagnose with the least founder typing

1. Require a public site URL. Inspect the main promise, first action, proof, pricing, and relevant product path. Store observation date and access limitations.
2. Offer suggested descriptions based on the site for the founder to confirm. Distinguish site claims, observed behavior, founder reports, and hypotheses.
3. Ask for the immediate goal using choices: first relevant users; first useful result; repeat use; paid offer; sales friction; measurement; not sure; other.
4. Pull only authorized measurements for this product. Show property, domain, event mapping, date range, freshness, and gaps. Zero and missing must remain distinct.
5. Identify the single most important uncertainty. If two explanations compete, design the cheapest observation that distinguishes them.

### Prepare, rather than assign vague homework

Each action needs:

- A specific audience and situation, with the reason it was selected.
- A named destination or owned product flow and a current permission check.
- A finished draft: post, page copy, demonstration storyboard, partnership proposal, or engineering brief.
- Prerequisites and acceptance checks. An engineering brief should identify the exact user behavior to improve, errors to preserve/recover from, and a verification method.
- A time cap, cash budget, target observation, review date, and stop/change rule.
- A concrete alternative if the founder has no audience, contacts, data, or relevant permission.
- Sources for factual claims. General marketing principles do not establish subreddit permissions, current prices, or feature availability.

A prepared draft is not a sent message. A proposed product change is not a deployed improvement. An offer concept is not inventory. Opening an example does not contact anyone or spend API credits.

### Review and compound learning

At review, record the actual denominator, outcome, source, time, cash, blockers, and counterevidence. Choose keep, change, stop, or not enough evidence. Preserve the original hypothesis so later edits cannot rewrite history. Carry the lesson into the next brief and retire stale recommendations.

## 5. Five different products, five different value loops

These are starting hypotheses based on public observations, not market validation. Use the interactive examples for complete steps and drafts.

| Product            | Users                                                                    | Usage                                                               | Sales                                                                                         |
| ------------------ | ------------------------------------------------------------------------ | ------------------------------------------------------------------- | --------------------------------------------------------------------------------------------- |
| Skills Tech Talk   | Project-answer demonstration for engineers with an interview approaching | Feedback leads to a useful revision and another practice occasion   | Validate a focused paid preparation benefit through existing STT plans                        |
| OutDuet            | One Cary weekend-planning occasion, then relevant local distribution     | A plan agreed and saved, followed by another planning occasion      | Existing venue promotion model, conditional on measured local audience and delivery           |
| OpenThunder        | Reproducible evidence from a real public change                          | Another reviewer can use the report, then repeat on a second change | A qualified team evaluation for working shared capabilities                                   |
| Leopard Sentinel   | Actual gameplay and a clear safe-training entry                          | Unassisted first objective, then voluntary replay or continuation   | Investigate an optional supporter concept only after repeat play; no new pack is claimed live |
| My Christian Bible | A reviewed bilingual reading path shared with permission                 | Continue a chosen path with context and gentle opt-in return        | Investigate a concrete group-preparation need; no paid offer is verified                      |

### Evidence boundaries

- [STT practice](https://app.skillstechtalk.com/try): public interface; no new paid grading or payment test conducted.
- [OutDuet](https://outduet.com/) and [business offer](https://outduet.com/business): free consumer positioning and published venue promotion model; no audience or delivery data verified.
- [OpenThunder](https://openthunder.ai/): published local workflow and team positioning; no new customer repository evaluation or security certification.
- [Leopard Sentinel](https://leopardsentinel.com/): live menu inspected. Its online co-op entry conflicts with older local-only repository documentation; validate actual connectivity before using it as a campaign promise.
- [My Christian Bible](https://mychristianbible.com/en): public bilingual reading and guided paths; reminder delivery, group tools, payments, and analytics unverified.

Two additional route checks: [Triangle on the Cheap](https://triangleonthecheap.com/submit-an-event/) accepts event submissions under its own requirements; a software advertisement is not a community event. [itch.io HTML5 documentation](https://itch.io/docs/creators/html5) informs a possible game distribution route; it does not mean a compatible package or live listing exists.

Do not import private data between portfolio products or infer a person's religious beliefs for marketing. For My Christian Bible, keep prayer contents and named recipients out of analytics. Shared ownership does not authorize sharing customer lists. Cross-sell only when there is an explicit, useful customer connection and appropriate consent.

## 6. Progress dashboards that answer decisions

Every chart needs a question, a data source, an eligible denominator, a comparison period, and an action it can change.

| Dashboard area | Chart                                                               | Decision enabled                                     |
| -------------- | ------------------------------------------------------------------- | ---------------------------------------------------- |
| Discovery      | Qualified visits/first-use starts by source over comparable periods | Which audience route earns another test?             |
| First value    | Matched steps from start to meaningful completion; time and errors  | Which obstacle should be fixed next?                 |
| Repeat use     | Cohorts by first-value week and natural return interval             | Does value recur without founder rescue?             |
| Sales          | Qualified opportunities, offers, verified payments, refunds         | Is the problem access, offer, checkout, or delivery? |
| Economics      | Cash cost and founder time beside net contribution                  | Can this acquisition method pay back?                |
| Experiments    | Work completed, goal, actual result, sample, decision               | Which effort produced usable learning?               |
| Data quality   | Freshness, coverage, event mapping, source and missing data         | Can we trust this apparent change?                   |

Separate GA4 event totals cannot establish an ordered funnel or a retention cohort. Require matched eligible journeys for those views. A before/after change may also reflect seasonality, acquisition mix, or another release. Display those limitations near the interpretation. Exclude staff/test traffic when possible; document the exclusion.

Revenue comes from reconciled billing records, not a front-end purchase event alone. Net receipts exclude refunds and adjustments. Contribution also subtracts payment fees, inference, delivery, and variable support costs. A dashboard should not silently invent customer lifetime value before retention is known.

### Integration sequence

**Available foundation:** RevStart has its existing GA4 connection/import flow, private workspace, research, tests, and progress dashboard. Connection setup and actual event availability still determine what a specific workspace can show. Worked examples do not connect a user's accounts.

**Next integration work, not claimed shipped by this handbook:**

1. Product-specific event definitions and verified first-value events. Reuse existing telemetry where appropriate; do not purchase another analytics subscription by default.
2. Search Console for owned query/page opportunity and indexing evidence, using explicit read-only authorization.
3. STT-authorized read-only billing summaries for relevant ecosystem products. No second billing or entitlement system in RevStart; no direct queries into another product's database.
4. Consented aggregate product cohorts, release annotations, and error summaries. Avoid session replay or sensitive payloads by default.
5. Channel delivery data for channels actually used; no connector collection for its own sake.
6. Prepared pull-request handoffs with acceptance checks. Publishing, ads, email, or customer outreach require the user's authorization.

## 7. From zero toward significant revenue

Dollar bands are illustrative planning contexts, not deadlines or universal stage gates.

| Stage                                     | Work worth doing                                                               | Evidence to proceed                                                             |
| ----------------------------------------- | ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------- |
| Pre-revenue                               | Confirm a problem, reachable buyer, useful first result, and basic tracking    | Non-founder users can complete a relevant task                                  |
| First sales                               | A narrow, deliverable offer and honest purchase discussion                     | Reconciled payment, actual delivery, specific objections                        |
| Early repeat revenue                      | Repeat useful use and the same acquisition process across periods              | Renewal or repurchase, manageable support, contribution path                    |
| Roughly $10k–$100k annual revenue context | Improve onboarding, focus the strongest route, document repeatable sales       | Results survive beyond one founder relationship or campaign                     |
| Roughly $100k–$1m annual revenue context  | Capacity, retention, channel economics, brand consistency, selective expansion | Growth does not destroy contribution or reliability                             |
| $1m+ ambition                             | Expand one market or offer at a time with budget and operational discipline    | Reachable demand, cash, retention, and delivery support the marginal investment |

Different models require different arithmetic. A consumer game, a venue advertising business, a team developer tool, and a devotional resource should not inherit the same subscription funnel.

### An honest million-dollar scenario

At an **assumed** $25 monthly price, $1,000,000 annual gross subscription revenue requires about **3,334 average full-price paying customers for the entire year**: `ceil(1,000,000 / (25 × 12))`. Ending the year at that customer count is a run-rate milestone, not a million collected during the year.

At an **assumed** $50 one-time price, the same annual gross target requires **20,000 sales in the year**. These are arithmetic examples, not recommended prices for the five products. They exclude ramp-up, discounts, refunds, tax, churn, and all costs.

Before treating a scenario as a plan, answer:

- How many suitable buyers can we actually reach? Start from named channels, geographies, or organizations, not an unsupported global TAM.
- What observed conversion range and sales cycle apply to this audience? If unknown, budget research rather than inventing a percentage.
- What is contribution per sale or account during a stated payback window?
- How much cash and founder capacity can be committed before evidence returns?
- What happens if acquisition costs double or renewal is weaker than expected?
- Which operational limit fails first: support, AI cost, venue quality, game reliability, content review, or team onboarding?

For an early campaign: `economic cost = cash spent + founder hours × chosen hourly value`. Break-even incremental customers are `ceil(economic cost / contribution per customer during the payback window)`, only when contribution is positive and known. Without credible incremental attribution, label the result an observation, not causal ROI. Do not use unlimited-lifetime revenue assumptions to justify acquisition spending.

## 8. How the think tank should run inside RevStart

The coordinator selects the relevant problem and at least three competing perspectives, then produces a decision. Specialist names describe jobs: market strategy, audience access, editorial quality, product experience, offer design, revenue analysis. The product should never say “Steve Jobs says your product will succeed” or fabricate a conversation between living or deceased experts.

The initial implementation uses a bounded editorial context in the existing research workflow. It does not create fourteen separate paid model calls. Existing login, provider selection, usage limits, source restrictions, and output validation remain in effect. Context versioning separates new research from old cached prompts. Saved reports remain accessible; research does not rerun automatically.

Next evaluation work should test whether generated plans:

1. Correctly distinguish unknown traffic, zero users, and measured abandonment.
2. Respect the actual business model and current feature availability.
3. Produce a usable draft or engineering brief, not “pick a channel” homework.
4. Ground every factual product/channel claim in an inspected source.
5. Explain a real objection and a reasonable cheaper alternative.
6. Fit the founder's actual time, budget, and access to an audience.
7. Keep concept interest, first use, repeat use, and paid outcomes distinct.
8. Avoid harmful pressure, invented proof, and unauthorized publishing.
9. Improve after actual experiment outcomes and contrary evidence.

## 9. Maintenance and next product milestones

- **Now:** five real-product examples, fifteen prepared plans, a source library, guided practice tests, four council role groups, and 24 conditional methods. Subsequent live research receives two relevant method candidates and three lens questions within the existing bounded context.
- **Next:** close the loop from authorized first-value events and reconciled sales to a specific recommendation; show the reason it changed.
- **Then:** a campaign workbench with editable assets, release-ready engineering handoffs, and a review queue for authorized execution.
- **Later:** refresh changed site facts and stale channel rules, compare acquisition cohorts and marginal economics, and support portfolio decisions based on measured evidence.

The standard is practical: can a founder open RevStart, understand the next decision, use work that has already been prepared, and return to see what happened? If the answer is no, adding another expert name or another chart does not fix the product.

### Editorial maintenance rules

Date every factual review. Recheck volatile channel rules, prices, and feature claims before recommending execution. Prefer original articles and authorized excerpts; distinguish publisher descriptions from full-book reading. Keep summaries brief and original, and link to the work. Record disagreement and limits. Do not buy new services or change account/billing contracts to implement these concepts.

Write in a clear, conversational voice. Do not use em dashes in original copy or generated drafts. Rewrite naturally with periods, commas, colons, or parentheses. Preserve exact quotations, URLs, and user-authored content.

## 10. Four council roles, one accountable decision

The supplied Growth Bible contributes a useful grouping of the fourteen perspectives. These are areas of responsibility, not four simulated people or four extra provider calls. The source authors did not review these products. RevStart owns the synthesis and its decisions.

| Council role               | Published perspectives          | Required contribution                                                                        |
| -------------------------- | ------------------------------- | -------------------------------------------------------------------------------------------- |
| Strategy and positioning   | Ritson, Godin, Jobs, Sutherland | Initial audience, actual alternative, supported difference, objective, and work to defer     |
| Offer and economics        | Hormozi, Miller, Ogilvy         | Delivered benefit, credible proof, payer, terms, costs, and purchase uncertainty             |
| Attention and distribution | Fishkin, Patel, Dean, Handley   | Named current destination, permission check, complete useful asset, and route to first value |
| Trust and experience       | Baer, Smith, Hyder              | First useful result, reliable experience, natural return, and voluntary referral             |

### The operating sequence

1. **Diagnose:** separate facts, founder reports, and missing measurements. State the uncertainty.
2. **Choose:** name the reachable audience, relevant situation, and one primary goal.
3. **Position:** compare the actual alternative with a difference the product can demonstrate.
4. **Offer:** explain the useful outcome, effort, delivery, and terms. A deliberately free product can defer paid-offer work.
5. **Attract:** prepare a contribution for a researched destination or an owned-channel fallback.
6. **Convert:** make the next useful action understandable and verify that it works. A signup is not always necessary.
7. **Deliver:** observe whether a suitable person reaches the useful result; fix the first demonstrated obstacle.
8. **Learn and repeat:** review outcomes, costs, contrary evidence, and the next natural need before expanding.

This is a decision checklist, not eight mandatory campaigns. A known broken practice flow can justify an immediate engineering fix. An idea without customers can start discovery without first earning an unprompted request to pay. A mature product may start with an observed retention problem.

### Council output contract

Every decision needs a lead argument, a credible objection, a cheaper alternative, and the observation that would change it. Prepare one selected investigation with complete usable material. Keep at most two alternatives visible; defer the rest. Do not turn eight methods per area into twenty-four chores.

The live implementation selects **two candidate methods by the saved challenge** and **three relevant perspective questions**. These are starting points for the existing research workflow, not a diagnosis or proof of fit. The research must check prerequisites, current site facts, and the actual business model before adapting or rejecting them. A future evidence-driven selector is specified separately; it is not shipped by adding this library.

### A useful STT session

Suppose the founder reports zero users while traffic is unknown. The strategy role should not conclude that conversion is poor. First inspect the public practice route and the available measurement. If the route fails, use G1 to prepare a reproducible change brief. If it works and audience access is the uncertainty, use U1 to research real destinations and prepare a contribution. With no personal contacts, U2 is not the default.

The existing STT example supplies a project-answer demonstration and a guided test. Future live research should adapt it from inspected sources, not invent a community's permission, feedback speed, learner improvement, or guaranteed interview outcome. Useful completions, repeat practice, and verified payments remain different observations.

## 11. Twenty-four practical methods

The complete interactive records include required inputs, three steps, a deliverable, measurement, a review rule, boundaries, and reading links. The catalog lives in `src/domain/growth-methods.ts`. Individual downloads are **method guides**, while the five product examples contain prepared product assets. Opening or downloading a method does not create an experiment, send a message, or run AI.

These methods are RevStart's original applications of the reviewed ideas. Their labels, conditions, and evaluation rules are not attributed as prescriptions from the authors.

### Users: find relevant demand and make the first action useful

| Method                      | When it fits                                              | Work RevStart should prepare                                                                  | What changes the next decision                                                    |
| --------------------------- | --------------------------------------------------------- | --------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- |
| U1: Audience destinations   | Access to suitable people is unknown                      | Three named places with URLs, audience evidence, rules, a finished contribution, and fallback | Relevant access and useful starts from the chosen route                           |
| U2: Personal invitation     | Real relevant contacts and permission exist               | Outcome-led invitation, direct next action, respectful follow-up                              | Delivered invitations, replies, and useful completions; no universal volume quota |
| U3: Complete native content | People learn on platforms before visiting a site          | Useful post or video storyboard with an optional next step                                    | Appropriate audience response, discovery reports, and useful starts, separately   |
| U4: Useful search asset     | A specific query connects to a real product benefit       | Page brief, original example, draft section, internal path to value                           | Indexing, discovery, visits, and useful actions as distinct checks                |
| U5: Clear product reference | The product or its terms are difficult to understand      | Visible what/who/how copy, real answers, crawlability checklist                               | Observed comprehension and a usable next action                                   |
| U6: Original evidence       | Inspectable observations or permissioned aggregates exist | Findings report with method, limitations, demonstration/chart, distribution draft             | Relevant references and buyer conversations, not invented authority               |
| U7: Useful occasion         | A real upcoming need makes the product relevant           | Occasion-specific demonstration, message, destination, timing                                 | Qualified useful starts within that occasion window                               |
| U8: Community contribution  | A suitable community welcomes useful participation        | Complete answer/resource, permission request where needed, reply plan                         | Relevant conversations and voluntary next actions                                 |

Before running a distribution method, inspect the actual destination. The library itself does not establish subreddit rules, event eligibility, current channel popularity, or permission to promote. An owned page is a viable fallback when external access is unavailable. A low number of users is not evidence that a particular channel is wrong.

### Usage: deliver value and make the next occasion easier

| Method                          | When it fits                                      | Work RevStart should prepare                                                       | What changes the next decision                                     |
| ------------------------------- | ------------------------------------------------- | ---------------------------------------------------------------------------------- | ------------------------------------------------------------------ |
| G1: First-value repair          | An observed failure blocks the promised result    | Reproduction, bounded engineering change, acceptance checks, measurement, rollback | Matched useful completion and failures, not unrelated event totals |
| G2: Outcome path                | Features exist but the useful sequence is unclear | Suggested route, example result, guided choices, recovery                          | Unassisted completion and where help is still needed               |
| G3: Keepable result             | The result disappears or is hard to reuse         | Private save/export design and useful example artifact                             | Reuse and voluntary recipient value                                |
| G4: Honest response expectation | Uncertain waits or support undermine completion   | Wait-state copy, measured expectation, recovery/escalation brief                   | Successful recovery and unresolved request age                     |
| G5: Clear next step             | A screen's wording causes observed confusion      | Replacement copy, example, defaults, error recovery                                | Suitable people understand and complete the intended action        |
| G6: Real progress               | Completed work is hard to recognize               | Accurate summary, comparison to prior work, one next action                        | Useful continuation and quality, without fabricated rankings       |
| G7: Support-to-product learning | Repeated issues suggest a fixable obstacle        | Redacted failure summary, response draft, verified corrective change               | Repeat failure per eligible attempt, not fewer tickets alone       |
| G8: Natural return              | A useful need recurs                              | Resume design and optional reminder with user-selected cadence                     | Eligible return for useful value, with opt-outs and interval shown |

Choose a natural return interval. Interview practice, a weekend plan, a code review, a game, and a reading path should not share a mandatory daily habit. Do not infer spiritual value from time spent or ability from a generated score. Speed claims require measurement; genuine progress must never be replaced by invented peer percentiles.

### Sales: match a deliverable benefit to a real payer

| Method                   | When it fits                                           | Work RevStart should prepare                                                | What changes the next decision                                                |
| ------------------------ | ------------------------------------------------------ | --------------------------------------------------------------------------- | ----------------------------------------------------------------------------- |
| S1: Deliverable offer    | Payer, paid benefit, or terms are unclear              | Scoped offer, price hypothesis, proof, costs, exclusions, buyer question    | Objections, payment, delivery, and refunds tracked separately                 |
| S2: Benefit-led message  | Suitable visitors cannot explain why to buy            | Three headlines, proof block, one CTA, comprehension questions              | Understanding and qualified next actions; small samples do not establish lift |
| S3: Next paid step       | Customers have a related need the business can serve   | Simple offer progression using verified capabilities and clear terms        | Net paid expansion, delivered value, support and refund burden                |
| S4: Price and package    | Purchase unit, price, or framing is uncertain          | Two hypotheses, buyer script, contribution worksheet                        | Paid acceptance and contribution, not founder discomfort with price           |
| S5: Inspectable proof    | An important claim lacks accessible evidence           | Real demonstration or permissioned case note with limitations               | Qualified objections resolved and useful next actions                         |
| S6: Bounded pilot        | A buyer needs an evaluation before a larger commitment | Scope, responsibilities, terms, review date, decision rule                  | Completed evaluation, any payment, and separate follow-on decision            |
| S7: Suitable payer model | A free product's commercial path is uncertain          | Comparison of payer models and one discovery proposal                       | Requests for a specific paid benefit; interest is not revenue                 |
| S8: Useful referral      | Someone received value and knows a relevant recipient  | Voluntary invitation, recipient benefit, transparent incentive terms if any | Referred useful use and verified sales, not invitations sent                  |

Guarantees, urgency, discounts, and recurring billing are optional business choices requiring honest terms and delivery capacity. They are not required ingredients. Calculate contribution consistently so delivery costs are not subtracted twice. Set payback requirements from cash needs and the sales cycle; do not install a universal LTV:CAC ratio or a 90-day gate.

### Different starting choices across the portfolio

These are candidates to investigate, not diagnoses. Reinspect product facts before execution.

| Product            | Users candidate                                                                  | Usage candidate                                           | Sales candidate                                                                       |
| ------------------ | -------------------------------------------------------------------------------- | --------------------------------------------------------- | ------------------------------------------------------------------------------------- |
| Skills Tech Talk   | U1/U3: researched engineer destination and complete project-answer demonstration | G1/G5: verify the attempt, feedback, and revision path    | S1/S5: supported preparation benefit using existing STT offers                        |
| OutDuet            | U7/U3: timely local planning example                                             | G2/G8: useful plan and next natural planning occasion     | S7/S6: venue buyer and bounded promotion evaluation, conditional on audience delivery |
| OpenThunder        | U6/U3: reproducible public-change evidence                                       | G3/G1: usable reviewer artifact and a working review path | S6/S5: a team evaluation with evidence, scope, and actual capabilities                |
| Leopard Sentinel   | U3/U8: real playable demonstration and a permitted audience route                | G1/G3: first playable objective and optional useful recap | S7: discover a supporter/purchase need; no paid pack is claimed live                  |
| My Christian Bible | U3/U8: reviewed reading material in a permitted context                          | G2/G8: clear continuation and gentle opt-in return        | S7: investigate group/support needs or explicitly keep sales out of scope             |

## 12. Editorial review of the supplied Growth Bible

Reviewed September 16, 2026. The supplied document is product input, not a source of observed business metrics. Its four-role council, operating loop, three-area method library, useful native content, offer clarity, and experience design were incorporated. The raw attachment is not injected into prompts or published as verified doctrine.

| Supplied claim or rule                                                                                      | RevStart treatment and reason                                                                                                                                                                                                                                                            |
| ----------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| All fourteen experts agree on ten conversations plus one unprompted payment request before any plan can run | Unsupported consensus and universal gate removed. Discovery and first-use repair must remain available without that prerequisite.                                                                                                                                                        |
| OutDuet is only a concept/domain; sell consumer preorders                                                   | Corrected. Public pages currently describe a live free consumer planning product and a venue promotion model. Published claims do not verify actual demand or delivery. See [OutDuet](https://outduet.com/) and [business offering](https://outduet.com/business), checked September 16. |
| Named features, speed promises, customer counts, team guarantees, or game/community offers                  | Retained only when already supported by dated observations; otherwise labeled proposals or excluded. [OpenThunder's current site](https://www.openthunder.dev/) supports local review evidence and team-pilot positioning, not guaranteed findings or certified safety.                  |
| Fixed outreach, retention, channel-count, and financial thresholds                                          | Converted to product-specific hypotheses and founder-confirmed limits. No automatic growth-stage promotion or forecast.                                                                                                                                                                  |
| Ritson's universal 60/40 budget rule                                                                        | Excluded as an allocation rule. His [brand-building discussion](https://www.marketingweek.com/ritson-brand-building-boost-short-term-sales/) credits Binet and Field and describes an average with context variation.                                                                    |
| Special FAQ/schema work guarantees AI discovery                                                             | Corrected using [Google's AI features guidance](https://developers.google.com/search/docs/appearance/ai-features). Normal SEO eligibility and useful content still matter; special AI markup is not required and inclusion is not guaranteed.                                            |
| Precise 2026 zero-click ratios and unverified article/book assertions                                       | Omitted from recommendations until the exact study, population, date, and primary source can be inspected. Absence of verification is not proof that a claim is false.                                                                                                                   |
| Every offer needs a guarantee, high price, scarcity, and continuity                                         | Replaced with deliverable scope, truthful terms, buyer fit, costs, and explicit testing. Free and mission-led models remain valid.                                                                                                                                                       |
| Simulated expert speeches or asserted expert agreement                                                      | Replaced with role-based arguments, objections, sources, and RevStart's accountable decision.                                                                                                                                                                                            |
| Customer lists or portfolio ownership as automatic distribution access                                      | Replaced with product-specific fit, appropriate consent, and explicit execution authorization.                                                                                                                                                                                           |

**Reading scope:** the books in the attachment remain reading suggestions unless a specific public source was inspected. The source summaries in section 2 define what was actually reviewed. Do not imply that the full books, private courses, or newer editions were ingested.

**Maintenance:** recheck volatile facts before execution, review the conceptual library quarterly, and reconsider a method when contrary evidence appears. A slow or inconclusive experiment is not automatically a failed method. Retain its sample, timing, costs, and uncertainty so the next decision can improve.