Tonight, keeping them. Every night stands on its own.
How you do anything is how you do everything.

AI ExchangeBuilding Phoenix's AI community, together. Workuity hosts tonight, and we present Founder Weekend side by side.
Their first three dinners found.
Still finding dinners in week 4.
No dinners found in 14 days.
Events tied to user ids
One dashboard
One experiment running
Signed up
→First three dinners
→Cooks weekly
→Back in week 4
→Quiet 14 days
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
Define acquisition, activation, engagement, retention and churn as measurable events for this app, write GROWTH.md, and wait.
✓ signed_up · server, with UTM values
✓ dinners_found · server, after 3 recipes
claudeFind dinners once, then check PostHog's activity feed.
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.
posthog.com/docs/libraries/next-js
You log in.
It builds the insights.
Signed up to first dinners found.
Users finding dinners each week.
Weekly cohorts through week 4.
I add PostHog's MCP server and log in. Then Claude builds the funnel, weekly actives and retention dashboard from GROWTH.md.
Signup → first dinners: 41%
Activated → week 4: 63%
claudeBiggest leak: activation. Most quit at the empty input.
Stage-to-stage conversion for 30 days, name the biggest drop with evidence, write it in GROWTH.md, change nothing.
Restate one hypothesis, metric and decision rule, put one change behind a PostHog flag for new signups, and log it in GROWTH.md.
3 users quiet for 10 days
✓ "What's in your fridge tonight?" sent via Resend
claude1 unsubscribed: skipped. Check your test inbox.
I set up Resend. Then a daily, protected route emails users quiet for 10 days, once a month at most, with a working unsubscribe.
resend.com/docs
youWeekly review, please.
Activation 41% → 48% · Week 4 63% · Churned 11
claudeStarter chips are ahead. Decision date is Friday.
Every Monday: five stage numbers, experiment status without calling it early, email results and one next step.
Also in the series: Part 8, AI Workflows, makes those emails and plans durable.
@weeknightmeals · 22 signups · 59% week 4
@mealprepdaily · 31 signups · 18% week 4
claudeFewer signups, better cooks. Update GTM-PLAN.md?
Activation and week-4 retention by utm_content, sorted by who stays, then one suggested change to GTM lead scoring.
An Arizona AI hackathon. Teams of 1-4.
See the hackathon ↗