The Claude Code User Growth Setup

One prompt in your terminal: Claude Code builds landing pages, creator briefs, onboarding emails, pricing tests, a 30-day video plan and a referral loop, and you review and ship

<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:

WHAT THIS IS: a ready setup that turns Claude Code into a growth engineer for your AI product or app. You give it your product, your numbers and one goal. It builds the growth work as files in your repo, and you review every change before it goes live.

WHO IT'S FOR: founders, growth leads and engineers at AI products, apps and SaaS tools who want more signups and active users.

WHAT IT BUILDS

Workstream Output Metric to watch
Search landing pages 12 pages for the searches your users make Signups from search
Creator briefs and hooks 30 briefs for short videos Signups per 1,000 views
Onboarding emails 5 emails that get new users to first value Activation rate
Pricing page test One A/B test with a clear stop rule Trial or paid conversion
30-day video plan One short video a day across TikTok, Reels and Shorts Videos posted, views
Referral loop An invite flow inside the app Invites sent, invite to signup rate

THE RULES


STEP 1 - INSTALL AND OPEN

  1. Install Claude Code and open your project folder in the terminal.
  2. Create a branch: git checkout -b growth-sprint.
  3. Run claude in the project folder.

STEP 2 - GIVE IT YOUR GROWTH CONTEXT

Create a file called CLAUDE.md in the project root. Claude Code reads it at the start of every session.

# Growth context

Product: [one line: what it does, for whom]
Users: [who signs up, why they stay, why they leave]
Current numbers: [weekly signups, activation rate, D7 retention, top traffic sources]
Brand voice: [5 words we use, 5 words we never use]
Proof: [best reviews, quotes, results users report]

Rules for growth work:
- Work only from this file, the repo and the data I paste. Never invent numbers, quotes or results. Write [NEEDS INPUT: what].
- Put all growth files under /growth unless the task is a product change.
- For every change, explain what it is for and which metric it should move.
- Never deploy, push or send anything. I review and ship.