24 chapters · 50 copy-ready Claude prompts · 25 fill-in templates · 20 operating workflows · 10 growth audits.
A practical operating manual for mobile-app founders and growth teams. Build an acquisition, activation, retention, and revenue system with ready-to-use prompts, templates, workflows, and audits.
<aside> 🚀 🚀 FREE STRATEGY CALL Want to grow your product through viral reach? We help teams across iGaming, mobile apps, AI products, and SaaS build creator-led organic distribution generating tens of millions of views at CPMs starting from $0.03.
<aside> 🚀 Book a free strategy call
</aside>
On the call you'll receive:
Growth is not a posting schedule. It is a sequence of increasingly valuable user actions: a relevant person understands the promise, installs, experiences value, returns and produces sustainable revenue. Improving an upstream metric while breaking the next step is not a win.
Use this resource in three passes. First, read Chapters 01–03 and write your baseline in T01. Second, run the audit for the weakest stage; choose one workflow and its supporting templates. Third, use the prompts to accelerate the work, then check every output against your actual product and evidence. You do not need to execute all 20 workflows simultaneously.
Set experiment sample requirements from your baseline, minimum meaningful effect, and analysis method before launching.
| Area | Chapters | Prompts | Templates | Workflows | Audit |
|---|---|---|---|---|---|
| Positioning and audience | 01–03 | P01–P05 | T01–T03 | W01–W02 | A01 |
| Pre-launch validation | 04–05 | P06–P10 | T04–T05 | W03–W04 | A02 |
| Store conversion | 06–07 | P11–P15 | T06–T08 | W05–W06 | A03 |
| Creator-led acquisition | 08–10 | P16–P20 | T09–T11 | W07–W08 | A04 |
| Organic distribution | 11–12 | P21–P25 | T12–T13 | W09–W10 | A05 |
| Onboarding and activation | 13–14 | P26–P30 | T14–T15 | W11–W12 | A06 |
| Retention and lifecycle | 15–16 | P31–P35 | T16–T18 | W13–W14 | A07 |
| Referrals and sharing | 17–18 | P36–P40 | T19–T20 | W15–W16 | A08 |
| Monetization and value | 19–21 | P41–P45 | T21–T23 | W17–W18 | A09 |
| Experiments and measurement | 22–24 | P46–P50 | T24–T25 | W19–W20 | A10 |
Start with a situation, not a demographic. “Busy people” does not tell you what to build or film. “An intermediate runner trying to adjust a training plan after missing two sessions” identifies a trigger, an existing workaround and an outcome you can demonstrate. Interview recent users about the last time the situation happened. Ask what they did before your app, what failed and what made them act that day.
Capture verbatim evidence in T02, removing personal information. Separate frequent complaints from complaints that actually motivate a change. A narrow segment is useful only if you can reach it and your product delivers the promised result. Choose one initial segment in T01; record an explicit exclusion, such as people who need medical advice rather than training organization.
Output: one trigger-based audience definition, three evidence-backed problems and one reachable distribution context. Avoid: letting Claude invent interview findings. Use: P01, T01–T02, W01.
Your competitor may be a spreadsheet, a friend or doing nothing. Write the complete sentence: “For people facing this situation, we help achieve this outcome through this mechanism, unlike this current alternative.” Then ask what evidence would make a skeptical user believe it. Screenshots of a feature are weaker than a visible demonstration of the task being completed.
Compare alternatives on the decision the user actually makes: setup effort, time to first result, reliability, control and total cost. Do not automatically claim to be faster or cheaper. Record unknowns as unknowns. For a meal-planning app, “turn the ingredients already in your fridge into tonight's plan” is a more testable promise than “revolutionize nutrition.”
Output: a one-sentence promise, a demonstration and an objection list in T03. Avoid: feature lists masquerading as positioning. Use: P02–P03, W02.