Claude Code Build Night · Part 6 · Coming soon

GTM Engineering

Your first 100 users, from a system you can run every week.

How the night runs.

A short AI news briefing, then we engineer What's for Dinner's first 100 users live, then five-minute demos from the room.

  1. 01

    Focus

    One ideal customer, one channel, written down.

  2. 02

    List

    Fifty leads from public sources, scored, in Twenty.

  3. 03

    Outreach

    Messages that open with their problem, sent by you.

  4. 04

    Loop

    Tracked links and a Friday report on replies and signups.

The deck.

Every slide from the night, free to share. Open it full size to step through.

GTM Engineering · slidesOpen full size →

Tonight's plan.

The go-to-market plan we write on the night for What's for Dinner. Copy it, swap in your own customer and channel, and run it next week.

GTM-PLAN.mdWhat's for Dinner

What's for Dinner

Type what's in your fridge. Get three dinners you can make tonight.

The goal100 signups from home cooks, each one traced to the message that brought them.

  • Claude Code
  • Twenty CRM
  • UTM links
  • Neon
  • Vercel
Done when
  • One ICP and one channel, plus what we're not doing
  • 50 scored leads in Twenty, each with a public source
  • Three outreach drafts that open with the reader's problem
  • Signups saved with their UTM values
  • The first Friday report: sent, replies, signups, one change
The full GTM plan
# GTM-PLAN.md · What's for Dinner

## Goal
100 signups from people who cook dinner at home, in six weeks, tracked to the message that brought them.

## ICP
Busy parents who cook weeknight dinners, decide what to make after 5pm, and already follow food creators for ideas.

## One channel
Small family-dinner and meal-prep creators (roughly 5k to 50k followers) who post weeknight recipes. One creator who shares it reaches people who already have the problem.

Not now: paid ads, cold email to strangers, Product Hunt, every social network at once.

## Lead list
Built from public sources only: creator profiles, their blogs, and the business contact they list publicly.
Fields: name, handle, platform, followers (approx.), niche, recent post that fits, public contact, source URL, fit score 1-5.
Anything we couldn't open (many Instagram and TikTok pages need a login) stays blank. Never filled from memory.
Never collect personal emails or phone numbers a person didn't publish for business.

## System of record
Twenty CRM. Deals stay in Opportunities from Part 1. For creators we track outreach on People, with an Outreach stage field: New, Contacted, Replied, Trying it, Shared, Not a fit.
Two timestamps on each Person: contacted_at (set when the first message goes out) and replied_at (set on their first reply).
Every reply and next step is a note on that Person.

## Outreach
Lead with their audience's problem, not our product.
- First line: a specific post of theirs and the question their followers keep asking ("what can I make with what's left?")
- One line on what the app does
- One small ask: try it free, reply with what's in your fridge tonight
- Their own tracked link
- An easy out: "Not your thing? No reply needed."

Rules: the human sends every message by hand. Ten a day, maximum. Follow each platform's rules on DMs and promotion. One follow-up after five days, then stop. Anyone who says no or asks to stop is marked Not a fit and never contacted again.

## Tracking
One link per creator:
https://whats-for-dinner.vercel.app/?utm_source=instagram&utm_medium=creator&utm_campaign=first-100&utm_content=<handle>
The app saves first-touch UTM values on the user record at signup.

## Weekly loop
- Monday: add 20 new leads, score them, drop anything below 3
- Tuesday to Thursday: send 10 a day; in Twenty set Contacted and contacted_at
- Friday: count contacted_at and replied_at this week, signups by utm_content; read every reply; change one thing for next week

## Numbers we watch
- Reply rate = replies / messages sent
- Signups per creator = signups with that utm_content
- Weekly signups toward 100

## Done when
- [ ] One ICP and one channel written down, with what we're not doing
- [ ] 50 scored leads in Twenty, every one with a public source URL
- [ ] Three outreach drafts, each opening with the reader's problem
- [ ] A tracked link per creator, and signups showing utm_content in the database
- [ ] The first Friday report: sent, replies, signups, one change

The prompts.

Every prompt from the deck, in order. Open one, copy it, paste it into Claude Code, Codex or any coding agent.

  1. 01
    Pick one customer, one channel
    Read SPEC.md and RESEARCH.md if they exist. Help me write GTM-PLAN.md for getting this app its first 100 users.
    
    Interview me one question at a time and wait for each answer:
    1. Who has this problem most often, and when?
    2. Where do those people already go for help with it?
    3. Which one channel could reach 100 of them in six weeks without paid ads?
    
    Push back if I pick more than one customer or more than one channel. Then write GTM-PLAN.md with these sections: Goal, ICP, One channel (with a short "Not now" list), Lead list, System of record, Outreach, Tracking, Weekly loop, Numbers we watch, Done when. Leave Lead list onward as headings for now.
    
    Stop and wait for my OK before doing anything else.
  2. 02
    Build the list from public sources
    Read GTM-PLAN.md. Build a lead list for the ICP and channel it names.
    
    1. Search the web for 50 candidates that fit the channel. Use public pages only: profiles, blogs, about and contact pages.
    2. For each, record: name, handle, platform, approximate followers, niche, one recent post that fits our problem (with its URL), the business contact they publish, the source URL, and a fit score from 1 to 5 with one line of reasoning.
    3. Do not guess or construct email addresses, and skip anyone who only lists a personal contact. Leave the contact blank if none is published.
    4. Many Instagram and TikTok pages need a login, so you may not be able to open them. Leave blank any field you couldn't read on a page you actually opened, and mark the row "needs a look". Never fill a field, follower count or post from memory.
    5. Save it as leads.csv. Show me the top 10, the rows marked "needs a look", and anything you were unsure about.
    
    Then fill in the Lead list section of GTM-PLAN.md and stop. Don't contact anyone.
  3. 03
    Twenty is the system of record
    Read GTM-PLAN.md and leads.csv. We're using Twenty as the CRM from our Company Stack setup.
    
    1. Tell me to create an API key in Twenty's settings and add it to .env.local as TWENTY_API_KEY myself. Wait until I tell you it's done. Never print the key.
    2. Read Twenty's current REST API docs for people and custom fields. Tell me which fields I should add to the Person object myself and wait until I tell you they exist: handle, platform, fit score, source URL, utm_content, Outreach stage (a select with New, Contacted, Replied, Trying it, Shared, Not a fit; deals stay in the Opportunity stages from Part 1), contacted_at and replied_at (date and time).
    3. Write scripts/import-leads.ts that reads leads.csv and creates one Person per row with Outreach stage New, skipping anyone already in Twenty by handle. Run it on the first 3 rows only and tell me to check them in Twenty.
    4. After my OK, import the rest and report the count.
  4. 04
    Lead with their problem
    Read GTM-PLAN.md and the top 10 leads in Twenty or leads.csv.
    
    Write three short outreach drafts for the channel in the plan. Each one:
    - Opens with a specific post of theirs and the problem their audience keeps raising, in their words
    - Says in one line what What's for Dinner does
    - Makes one small ask (try it free, or reply with what's in your fridge tonight)
    - Includes a placeholder for their tracked link
    - Ends with an easy out, like "Not your thing? No reply needed."
    - Stays under 80 words, with no hype words and no fake urgency
    
    Then personalize draft 1 for the top 3 leads and save everything to outreach.md. Do not send anything or open any messaging app. I send every message myself. Fill in the Outreach section of GTM-PLAN.md and stop.
  5. 05
    The human sends
    Read GTM-PLAN.md and outreach.md. Before I send anything, check the current rules for the platform in our One channel section: its terms on direct messages and promotion, and any rules a community posts for itself. Summarize what's allowed in five bullets with links to the source. Add a Rules line to the Outreach section: I send by hand, ten a day maximum, one follow-up after five days, and anyone who says no is marked Not a fit and never contacted again. Flag any draft that breaks a rule. Don't send anything.
  6. 06
    Track every link
    Read GTM-PLAN.md and SPEC.md.
    
    1. Generate one tracked link per lead in this format: our live URL plus utm_source=<platform>, utm_medium=creator, utm_campaign=first-100, utm_content=<handle>. Save them to a links column in leads.csv and update the utm_content field in Twenty.
    2. In the app, when someone lands with UTM parameters, keep them in a first-party cookie for 30 days. At signup, save utm_source, utm_medium, utm_campaign and utm_content on the user record. Add the columns with a migration, and don't overwrite values that are already set.
    3. Mention the cookie in the privacy page if we have one.
    4. Tell me to sign up with a test link at phone width, then show me the saved row. Stop there.
  7. 07
    Run the weekly loop
    Read GTM-PLAN.md. Write scripts/friday-report.ts and run it.
    
    1. From Twenty: count People whose contacted_at falls in this week (first messages sent) and whose replied_at falls in this week (replies). If either field is empty on someone marked Contacted or Replied, list them so I can fix it.
    2. From the database: count signups this week grouped by utm_content, and the running total toward 100.
    3. Print: messages sent, replies, reply rate, signups, signups per creator, and the five best creators.
    4. Read this week's reply notes in Twenty and sum up what people said in three bullets.
    5. Suggest exactly one change for next week, based only on these numbers, and wait for me to pick it.
    
    Append the report to a Weekly log section in GTM-PLAN.md. Never print API keys.
  8. 08
    Sort replies, draft answers
    Bonus round. I'll paste replies I received below this prompt, one per line, with the sender's handle.
    
    For each reply:
    1. Find the person in Twenty by handle.
    2. Pick the new Outreach stage: Replied, Trying it, Shared or Not a fit. If replied_at is empty, set it to when the reply arrived. Anyone who says no or asks to stop is Not a fit, with no draft.
    3. Draft a short answer under 50 words that responds to what they actually said.
    4. Save the stage, replied_at and a note with the draft on their record.
    
    Show me a table of handle, stage and draft. Don't send anything. I review and send each one myself.

The toolkit.

The tools behind the weekly loop, one job each. Claude Code drafts and counts; you send every message.

Skip the hustle. Run the loop.

Date to be announced. Dates go out in the Discord first.

Harbor at dusk · Phoenix, Arizona