← Company StackArrows or space · F for fullscreen · Print to saveTalks

CLAUDE CODE BUILD NIGHT · PART 1

Company
Stack

Form the company. Set up its tools. Start it in one night.

Ship AI · TalksCompany Stack01/20

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 · TalksCompany Stack02/20

Join the room

SHIP AI DISCORD

Scan it now.
Prompts later.

Open the Discord invite

Ship AI · TalksCompany Stack03/20

Our partner

Ship AIWorkuityAI Exchange

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

Ship AI · TalksCompany Stack04/20

THE IDEA

Set up the company once.
Then build on it.

Ship AI · TalksCompany Stack05/20

Before the first line of code

LATER, SOMEHOW

"I'll sort the company out later."

ONE CHECKLIST

Thirteen tools, in order.
Claude drafts. You sign.

Ship AI · TalksCompany Stack06/20

Tonight

01

Legal

02

Comms

03

Sell

04

Helpers

Ship AI · TalksCompany Stack07/20

The stack, in order

Legal and money
  • Stable
  • Stripe Atlas
  • Mercury
  • Carta
Identity and comms
  • Google Workspace
  • 1Password
  • Quo
  • Slack
  • Notion
Build and sell
  • Vercel
  • Twenty
AI helpers
  • Granola
  • Grok Bot

Ship AI · TalksCompany Stack08/20

Prepare the paperwork

claude · ~/whats-for-dinner-co

claudeTwo founders. What's the split and the vesting?

you50/50, four years, one-year cliff.

✓ Wrote atlas-prep.md: 14 items, 9 questions

claudeYour turn: sign up at stripe.com/atlas.

Copy · legal and money prep
Interview me about founders, split and vesting, then write atlas-prep.md: checklists and advisor questions for Stable, Stripe Atlas, Mercury and Carta. I do the signups.

Full prompt

Copy this entire prompt into Claude Code.

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.

stripe.com/atlas

Ship AI · TalksCompany Stack09/20

One vault per job

claude · ~/whats-for-dinner-co

✓ 5 vaults: Founders, Banking and Legal, Engineering, Vendors, Social

✓ Wrote vaults.sh for you to run

claudeI never see a password. You run the script.

Copy · the 1Password plan
Propose 1Password vaults by job with a recovery plan, wait while I install the CLI, then write vaults.sh for me to run. Never touch a secret.

Full prompt

Copy this entire prompt into Claude Code.

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.

1password.dev/cli

Ship AI · TalksCompany Stack10/20

Who holds the pen

CLAUDE CODE

Checklists, plans, templates.

YOU

Signups, payments, signatures.
Never hand over the pen.

Ship AI · TalksCompany Stack11/20

Email, phone and chat

claude · ~/whats-for-dinner-co

✓ hello@, support@, billing@ as Google groups

✓ Quo greeting and three text replies

✓ Slack: 6 channels, alerts kept out of #general

Copy · the comms plan
Write comms.md: Google Workspace inboxes and groups, a Quo greeting and text replies, and a Slack channel plan. I do the signups and DNS.

Full prompt

Copy this entire prompt into Claude Code.

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.

quo.com

Ship AI · TalksCompany Stack12/20

A wiki that runs the company

claude · ~/whats-for-dinner-co

claudeNotion is connected. Create seven pages?

youYes, under a page called Company.

✓ Home, Company, Product, Research, Customers, Ops, Decisions

Copy · the Notion workspace
Draft notion-outline.md, wait for my OK, then connect Notion's MCP server and create the pages under one parent I choose.

Full prompt

Copy this entire prompt into Claude Code.

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.

developers.notion.com

Ship AI · TalksCompany Stack13/20

A pipeline before the first call

claude · ~/whats-for-dinner-co

✓ Stages: Found → Contacted → Interview booked → Interviewed → Beta tester → Paying

✓ companies.csv and people.csv

claudeImport companies first, then people.

Copy · the Twenty CRM setup
Propose Twenty pipeline stages with exit rules, then write companies.csv and people.csv import templates. Companies first, then people.

Full prompt

Copy this entire prompt into Claude Code.

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.

twenty.com

Ship AI · TalksCompany Stack14/20

Ship the checklist

claude · ~/whats-for-dinner-co

✓ STACK.md: 4 sections, 13 tools

✓ 5 checks under Done when

claudePaste it into Notion under Ops.

Copy · write STACK.md
Combine everything into STACK.md in founder order, with a Done when section, then show me what's finished and what's left.

Full prompt

Copy this entire prompt into Claude Code.

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.

Ship AI · TalksCompany Stack15/20

BONUS ROUND

Time on the clock?
Hire the helpers.

Ship AI · TalksCompany Stack16/20

Granola takes notes. Grok Bot follows up.

Grok Bot · Monday routine

you[ pasted routine brief ]

claudeRead 3 Granola calls, #customers and Decisions.

→ Founder update drafted. Approve to post?

Copy · the Grok Bot routine brief
Write a Grok Bot routine brief: every Monday it reads Granola, Slack and Notion and drafts a founder update for my approval.

Full prompt

Copy this entire prompt into Claude Code.

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.

Also in the series · Part 2: Market Research

Ship AI · TalksCompany Stack17/20

Take it home

THE TALK PAGE

Every prompt,
and this deck.

Open the talk page

Ship AI · TalksCompany Stack18/20

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 · TalksCompany Stack19/20

SHIP AI DISCORD

Free and open.
Build with us.

Scan to join

Ship AI · TalksCompany Stack20/20
01/20