← Growth EngineeringArrows or space · F for fullscreen · Print to saveTalks

CLAUDE CODE BUILD NIGHT · PART 7

Growth
Engineering

Tonight, keeping them. Every night stands on its own.

Ship AI · TalksGrowth Engineering01/21

Who's hosting

How you do anything is how you do everything.

Santos Hernandez
Santos HernandezFounder, Ship AI
$25k+/moggbucks, built with agents
$0 to $12MARR at ZBD
EU firstMiCAR approval
THE COMMUNITY

Ship AI

Free workshops and talks in Phoenix.

shipai.club
THE STUDIO

Ship AI Studio

AI built into your business, in two weeks.

shipaistudio.com

Ship AI · TalksGrowth Engineering02/21

Join the room

SHIP AI DISCORD

Scan it now.
Prompts later.

Open the Discord invite

Ship AI · TalksGrowth Engineering03/21

Our partner

Ship AIWorkuityAI Exchange

Building Phoenix's AI community, together. Workuity hosts tonight, and we present Founder Weekend side by side.

Ship AI · TalksGrowth Engineering04/21

THE IDEA

Signups aren't users.
Habits are.

Ship AI · TalksGrowth Engineering05/21

Measure the habit

VANITY

"We hit 100 signups."

LIFECYCLE

How many cooked in week 4?
That's the number.

Ship AI · TalksGrowth Engineering06/21

Tonight

01

Define

02

Measure

03

Fix

04

Nudge

Ship AI · TalksGrowth Engineering07/21

Tonight's metrics plan

GROWTH.md
Activation

Their first three dinners found.

Retention

Still finding dinners in week 4.

Churn

No dinners found in 14 days.

Done when

Events tied to user ids

One dashboard

One experiment running

Ship AI · TalksGrowth Engineering08/21

Five stages, one app

01

Acquire

Signed up

02

Activate

First three dinners

03

Engage

Cooks weekly

04

Retain

Back in week 4

05

Churn

Quiet 14 days

Ship AI · TalksGrowth Engineering09/21

Write the definitions first

claude · ~/whats-for-dinner

claudeWhat moment shows someone got the value?

youTheir first three dinners come back.

claudeAnd how long quiet before they're gone?

✓ GROWTH.md: five stages, one event each

Copy · define the stages
Define acquisition, activation, engagement, retention and churn as measurable events for this app, write GROWTH.md, and wait.

Full prompt

Copy this entire prompt into Claude Code.

Read SPEC.md and GTM-PLAN.md. Help me write GROWTH.md for this app.

We use five stages: acquisition, activation, engagement, retention and churn. Ask me one question at a time to define each one for this app, as a specific event or query, not a vague goal. Suggest a default for each and let me change it. Push back if a definition can't be measured.

Then write GROWTH.md with: Goal, The five stages (a table of stage, definition, event or query), Events (name, when it fires, properties, server or client), Dashboard, Biggest leak, Experiment, Lifecycle email, Weekly review, Done when.

No personal data or ingredient text in event properties. Stop and wait for my OK.

Ship AI · TalksGrowth Engineering10/21

Instrument the events

claude · ~/whats-for-dinner

✓ signed_up · server, with UTM values

✓ dinners_found · server, after 3 recipes

claudeFind dinners once, then check PostHog's activity feed.

Copy · instrument the events
I run the PostHog wizard myself. Then add the events from GROWTH.md on the server, tied to user ids, and verify each one arrives.

Full prompt

Copy this entire prompt into Claude Code.

Read GROWTH.md.

1. Tell me to sign up for PostHog and run npx @posthog/wizard in my own terminal. Wait until I tell you it's done, then read what it changed and summarize it.
2. Add server-side capture with posthog-node for the server events in GROWTH.md (signed_up, dinners_found, dinners_failed). Use the user id as the distinct id, call identify on the client after sign-in, and flush events before the route returns.
3. Add the client events in GROWTH.md, and nothing else custom.
4. Never log email addresses, ingredient lists or recipe text as properties.
5. Tell me to sign up a test account and find dinners once, then confirm each event arrived with the right properties. Stop there.

posthog.com/docs/libraries/next-js

Ship AI · TalksGrowth Engineering11/21

One dashboard

CLAUDE CODE BUILDS ITPostHog MCP

You log in.
It builds the insights.

01

Funnel

Signed up to first dinners found.

02

Weekly actives

Users finding dinners each week.

03

Retention

Weekly cohorts through week 4.

Copy · build the dashboard
I add PostHog's MCP server and log in. Then Claude builds the funnel, weekly actives and retention dashboard from GROWTH.md.

Full prompt

Copy this entire prompt into Claude Code.

Read GROWTH.md.

1. Tell me to add PostHog's MCP server by running npx @posthog/wizard mcp add in my own terminal, then restart Claude Code and log in when asked. Wait until I tell you it's done.
2. Use the PostHog tools to create a dashboard called "What's for Dinner growth" with the insights listed under Dashboard in GROWTH.md: the activation funnel, weekly active users, weekly retention through week 4, and activation by utm_content.
3. For at-risk and churned counts, write a small SQL query against our dinners table and tell me how to run it.
4. Give me the dashboard link and today's number for each insight. If there isn't enough data yet, say so plainly.

Ship AI · TalksGrowth Engineering12/21

Find the biggest leak

claude · ~/whats-for-dinner

Signup → first dinners: 41%

Activated → week 4: 63%

claudeBiggest leak: activation. Most quit at the empty input.

Copy · find the leak
Stage-to-stage conversion for 30 days, name the biggest drop with evidence, write it in GROWTH.md, change nothing.

Full prompt

Copy this entire prompt into Claude Code.

Read GROWTH.md and use the PostHog tools and our database.

1. For the last 30 days, give me the conversion from each stage to the next as a table, with the number of users at each step.
2. Name the stage with the biggest drop. If the sample is too small to trust, say how many users we need first.
3. For that stage, look at what users did before dropping off (session recordings, if I've turned them on, and events) and list three possible causes, each with the evidence.
4. Write the leak and its number under Biggest leak in GROWTH.md.

Don't change any code. Stop and wait.

Ship AI · TalksGrowth Engineering13/21

Ship one experiment

GUESSING

Change five things at once.

EXPERIMENT

One change, one metric.
Then decide.

Copy · ship the experiment
Restate one hypothesis, metric and decision rule, put one change behind a PostHog flag for new signups, and log it in GROWTH.md.

Full prompt

Copy this entire prompt into Claude Code.

Read GROWTH.md, especially Biggest leak and Experiment.

1. Restate the hypothesis, the one metric, the split and the decision rule in four lines. Wait for my OK.
2. Use the PostHog tools to create the experiment and its feature flag as a draft, and show me what you made. Wait for my OK before starting it.
3. Build the variant behind the flag, for example three tappable starter ingredients on an empty fridge input. The control stays exactly as it is. New signups only.
4. Show me both variants at phone width. Log the experiment, start date and decision date in GROWTH.md, then stop.

Ship AI · TalksGrowth Engineering14/21

Catch them before they churn

claude · ~/whats-for-dinner

3 users quiet for 10 days

✓ "What's in your fridge tonight?" sent via Resend

claude1 unsubscribed: skipped. Check your test inbox.

Copy · the at-risk email
I set up Resend. Then a daily, protected route emails users quiet for 10 days, once a month at most, with a working unsubscribe.

Full prompt

Copy this entire prompt into Claude Code.

Read GROWTH.md, section Lifecycle email.

1. Tell me to create a Resend account, verify our sending domain and add RESEND_API_KEY to .env.local myself. Wait until I tell you it's done. Never print the key.
2. Add an email_opt_out column and a one-click unsubscribe route that sets it.
3. Write a route that finds activated users with no dinners for 10 to 13 days who haven't opted out and weren't emailed in the last 30 days, then sends "What's in your fridge tonight?" with resend.emails.send: two sentences, one tracked link back to the app, the unsubscribe link, and a footer with our physical postal address (use the placeholder [your Stable address] from Part 1 and tell me to fill it in). Add List-Unsubscribe and List-Unsubscribe-Post: List-Unsubscribe=One-Click headers that point at the same route, so mail apps can unsubscribe in one click. Record each send.
4. Add an advisor question to the Lifecycle email section of GROWTH.md: if any users are in the EU, UK or Canada, do their consent rules mean we need an opt-in first? It's a checklist item, not legal advice.
5. Protect the route with CRON_SECRET and add a daily Vercel cron for it.
6. Run it once against a test account only, and tell me to check the inbox, the postal address footer and the unsubscribe link. Stop there.

resend.com/docs

Ship AI · TalksGrowth Engineering15/21

Review it every Monday

claude · ~/whats-for-dinner

youWeekly review, please.

Activation 41% → 48% · Week 4 63% · Churned 11

claudeStarter chips are ahead. Decision date is Friday.

Copy · the weekly review
Every Monday: five stage numbers, experiment status without calling it early, email results and one next step.

Full prompt

Copy this entire prompt into Claude Code.

Read GROWTH.md. Using the PostHog tools and our database, write this week's review:
1. The five stage numbers, and the change from last week.
2. Experiment status: users per variant, the metric for each, and whether we've reached the decision rule. Don't call a winner early.
3. Lifecycle email: sent, clicks back to the app, unsubscribes.
4. One next step.

Append it to a Weekly review log in GROWTH.md and stop.

Also in the series: Part 8, AI Workflows, makes those emails and plans durable.

Ship AI · TalksGrowth Engineering16/21

BONUS ROUND

Which creators bring cooks?
Follow the cohort.

Ship AI · TalksGrowth Engineering17/21

Retention by source

claude · ~/whats-for-dinner

@weeknightmeals · 22 signups · 59% week 4

@mealprepdaily · 31 signups · 18% week 4

claudeFewer signups, better cooks. Update GTM-PLAN.md?

Copy · retention by source
Activation and week-4 retention by utm_content, sorted by who stays, then one suggested change to GTM lead scoring.

Full prompt

Copy this entire prompt into Claude Code.

Bonus round. Read GROWTH.md and GTM-PLAN.md.

Using the PostHog tools or our database, show activation and week-4 retention grouped by utm_content, for sources with at least 10 signups. Sort by week-4 retention, not signups. Flag any group too small to trust.

Then suggest one change to the lead scoring in GTM-PLAN.md based on which kinds of creators bring people who stay. Wait for my OK before editing it.

Ship AI · TalksGrowth Engineering18/21

Take it home

THE TALK PAGE

Every prompt,
and this deck.

Open the talk page

Ship AI · TalksGrowth Engineering19/21

Founder Weekend

FEB 6‑7, 2027 · FREE

Tonight was one hour.
Take a weekend.

An Arizona AI hackathon. Teams of 1-4.

See the hackathon

Ship AI · TalksGrowth Engineering20/21

SHIP AI DISCORD

Free and open.
Build with us.

Scan to join

Ship AI · TalksGrowth Engineering21/21
01/21