Claude Code Build Night · Part 1 · Coming soon

Company Stack

Form the company. Set up its tools.

How the night runs.

Twenty minutes of AI news, then we set up the company behind What's for Dinner in founder order, then five-minute demos from the room.

  1. 01

    Legal

    Address, incorporation, bank and cap table.

  2. 02

    Comms

    Email, phone, chat, wiki and passwords.

  3. 03

    Sell

    Hosting and a CRM pipeline, ready early.

  4. 04

    Helpers

    AI notes and an AI teammate, last.

The deck.

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

Company Stack · slidesOpen full size →

Tonight's checklist.

The company behind the app, set up in the order a founder needs it. Paste it into Notion and check items off as you go.

STACK.mdWhat's for Dinner

What's for Dinner

Thirteen tools, in founder order: legal and money first, then identity and comms, then build and sell, then the AI helpers.

The ruleClaude Code drafts. You sign up, pay and sign.

  • Stripe Atlas
  • Mercury
  • Carta
  • Google Workspace
  • 1Password
  • Notion
  • Twenty
  • Grok Bot
Done when
  • The company exists, with its tax ID
  • Money lands in the company account
  • hello@ reaches both founders
  • Every login in 1Password, with 2FA
  • A CRM pipeline ready for five interviews
The full STACK.md
# What's for Dinner - STACK.md

The company behind the app, set up in the order a founder actually needs it. Claude Code drafts the checklists, plans and templates. You do every signup, payment, signature and legal acceptance yourself.

This is a checklist, not legal or tax advice. Bring the questions to a lawyer or accountant when the answer matters.

## 1. Legal and money

### Stable - business address (usestable.com)
- [ ] Pick the address you'll use on formation, banking and tax forms (keeps your home address private)
- [ ] Turn on mail scanning and decide who gets the scans
- Ask: Can this address be used for the IRS, my bank and my state filings?

### Stripe Atlas - incorporation (stripe.com/atlas)
- [ ] Decide the legal name, plus two backups
- [ ] Decide C corporation or LLC (Atlas offers both; ask an advisor which fits)
- [ ] List founders, ownership split, vesting period, cliff and start date
- [ ] Have a US address and phone number ready for the tax ID (EIN) step
- Ask: Who files the 83(b) election, by when, and how do I get proof it was filed?
- Ask: What do I file every year to stay in good standing?

### Mercury - banking (mercury.com)
- [ ] Apply from the Atlas dashboard perks if you want to apply before the EIN arrives
- [ ] Two accounts: operating and tax set-aside
- [ ] Debit cards per person, with limits
- Ask: Who else needs access, and at what permission level?

### Carta - cap table (carta.com)
- [ ] Enter founder shares exactly as the Atlas documents say
- [ ] Upload the signed stock purchase agreements
- Ask: What changes when we sign our first SAFE?

## 2. Identity and comms

### Google Workspace - email and calendar (workspace.google.com)
- [ ] Buy or connect the domain
- [ ] Add the DNS records Google's admin console shows you (MX, SPF, DKIM, DMARC)
- [ ] Founder inboxes, plus groups: hello@, support@, billing@
- [ ] One shared calendar for customer calls

### 1Password - shared secrets (1password.com)
- [ ] Vaults: Founders, Banking and Legal, Engineering, Vendors, Social
- [ ] Every account in this file gets an item, with 2FA turned on
- [ ] Recovery: a second admin who can get back in if you can't

### Quo - business phone, formerly OpenPhone (quo.com)
- [ ] One business number, shared by the founders
- [ ] Greeting and business hours
- [ ] Text replies for the three questions people will ask

### Slack - team chat (slack.com)
- [ ] Channels: #general, #build, #customers, #research, #alerts, #random
- [ ] Alerts from Vercel and the CRM go to #alerts, never #general

### Notion - docs and wiki (notion.com)
- [ ] Home, Company, Product, Research, Customers, Ops, Decisions
- [ ] Paste this file into Ops and check items off there

## 3. Build and sell

### Vercel - hosting (vercel.com)
- [ ] A team for the company, not your personal account
- [ ] Connect the domain; the app arrives in Part 3

### Twenty - CRM (twenty.com)
- [ ] Opportunity stages: Found, Contacted, Interview booked, Interviewed, Beta tester, Paying
- [ ] Import companies.csv first, then people.csv
- [ ] Every interview from Part 2 gets a record
- [ ] Deals live in Opportunities; Part 6 adds an Outreach stage field on People for creators

## 4. AI helpers

### Granola - meeting notes (granola.ai)
- [ ] Use it for customer calls; tell people you're taking AI notes
- [ ] Share notes to the Customers space in Notion

### Grok Bot - an AI teammate on a cloud computer (x.ai/bot)
- [ ] Connect Gmail, Google Calendar, Slack, Notion and Granola only after the rest is set up
- [ ] One weekly routine: drafts the founder update for your approval (check your plan includes routines)

## Done when
- [ ] The company exists, with its tax ID
- [ ] Money lands in the company bank account, not yours
- [ ] hello@ reaches both founders, and the phone number rings
- [ ] Every login lives in 1Password with 2FA
- [ ] The CRM has a pipeline ready for the first five interviews

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
    Prepare the paperwork
    We're forming the company behind What's for Dinner, a phone app that turns what's in your fridge into three dinners you can make tonight. Help me prepare. You are not a lawyer or accountant: write checklists and questions, never advice.
    
    Interview me one question at a time and wait for each answer: company name and two backups, founders and ownership split, vesting period, cliff and start date, the state I live in, and whether I have a US address and phone number for the tax ID.
    
    Then write atlas-prep.md with four sections in this order:
    1. Stable (business address): what to decide before signing up.
    2. Stripe Atlas (incorporation): everything Atlas will ask me for, as checkboxes, plus questions to ask an advisor, including C corporation or LLC, who files the 83(b) election and by when, and what I file each year to stay in good standing.
    3. Mercury (banking): what to have ready, which accounts to open, and who gets access.
    4. Carta (cap table): what to enter from the Atlas documents.
    
    Check each product's current website before you write about it, and leave out anything you can't confirm. No prices.
    
    Stop there. I do every signup, payment and signature myself. Wait until I tell you it's done.
  2. 02
    One vault per job
    Read atlas-prep.md. Design a 1Password setup for this company.
    
    1. Propose vaults by job (for example Founders, Banking and Legal, Engineering, Vendors, Social), who can see each one, and which accounts from atlas-prep.md go where. Include a recovery plan: who the second admin is. Wait for my OK.
    2. Tell me to install the 1Password CLI myself with brew install 1password-cli, turn on the CLI integration in the 1Password app, and confirm with op --version. Wait until I tell you it's done.
    3. Write vaults.sh with one op vault create command per vault, and show it to me. Don't run it; I'll run it myself.
    
    Never ask me for a password, recovery code or secret, and never put one in a file.
  3. 03
    Email, phone and chat
    Read atlas-prep.md. Write comms.md with three sections, then stop and wait for my review.
    
    1. Google Workspace: the founder inboxes, the groups (hello@, support@, billing@) and who is in each, and a checklist for the DNS step. Don't invent DNS values; tell me to copy the exact MX, SPF, DKIM and DMARC records Google's admin console shows me.
    2. Quo (the business phone, formerly OpenPhone): who shares the number, business hours, a 20-second greeting for What's for Dinner, and short text replies to the three questions a new user is most likely to ask.
    3. Slack: a channel plan with a one-line purpose for each channel (general, build, customers, research, alerts, random), and which tools post where.
    
    I'll do the signups, domain purchase and DNS changes myself.
  4. 04
    A wiki that runs the company
    Draft a Notion workspace for What's for Dinner as notion-outline.md: pages for Home, Company, Product, Research, Customers, Ops and Decisions, with the sections and starter content each one needs. Put atlas-prep.md and comms.md under Ops. Add a Decisions log template with date, decision, why and owner. Wait for my OK.
    
    Then, if I want it built for me: tell me to run this in my terminal and authenticate with /mcp in Claude Code:
    claude mcp add --transport http notion https://mcp.notion.com/mcp
    Wait until I tell you it's done, and tell me to restart Claude Code if the Notion tools don't show up.
    
    Use the Notion tools to create the pages under one parent page I choose. Show me the plan before creating anything, and don't edit or delete existing pages.
  5. 05
    A pipeline before the first call
    We'll use Twenty, the open-source CRM, to track the people we interview and recruit as beta testers for What's for Dinner.
    
    1. Check Twenty's current user guide on pipelines and CSV import before you start.
    2. Propose five to seven Opportunity stages from first contact to paying user (for example Found, Contacted, Interview booked, Interviewed, Beta tester, Paying), with a one-line exit rule for each stage. Deals stay in Opportunities; in Part 6 we'll track creator outreach separately with an Outreach stage field on People. Wait for my OK.
    3. Write crm/companies.csv and crm/people.csv as import templates with a header row and two clearly fake rows each. People link to a company by its name or domain. Write crm/README.md with the import order: companies first, then people, matching columns to the sample file Twenty offers in its import dialog.
    
    I'll create the workspace and run the import myself. Wait until I tell you it's done.
  6. 06
    Ship the checklist
    Read atlas-prep.md, comms.md, notion-outline.md and crm/README.md. Combine them into STACK.md, one checklist I'll paste into Notion.
    
    Order it the way a founder does it: 1. Legal and money (Stable, Stripe Atlas, Mercury, Carta). 2. Identity and comms (Google Workspace, 1Password, Quo, Slack, Notion). 3. Build and sell (Vercel, Twenty). 4. AI helpers (Granola, Grok Bot).
    
    For each tool: what it's for in one line, its website, the checkboxes, and any questions for an advisor. End with a Done when section of five checks. Put a line at the top saying this is a checklist, not legal or tax advice.
    
    Then mark what I've already finished tonight and list what's left, in order.
  7. 07
    Granola takes notes. Grok Bot follows up.
    Read STACK.md. Write grok-bot-routine.md: a brief I'll paste into Grok Bot, xAI's AI teammate, myself.
    
    The routine runs every Monday morning. It reads last week's Granola meeting notes, the #customers channel in Slack and the Decisions page in Notion. It drafts a short founder update: what we learned from users, what we decided, what's blocked, and the three most important things this week. It posts nothing without my approval.
    
    List the connections I need to turn on in Grok Bot (Granola, Slack, Notion; all three are on its connector list) and what it must never do: send email, change Notion pages, or post to any channel other than #general. Keep the brief under 200 words.
    
    Add a note to check that my Grok plan includes scheduled routines before I set it up. Don't sign up for or connect anything. I'll do that myself.

The toolkit.

Every tool the company needs, in the order you set them up. Claude Code drafts; you sign up, pay and sign.

Bring a company name. Leave with a checklist.

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

Harbor at dusk · Phoenix, Arizona