← First DeployArrows or space to advance · F for fullscreen · ⌘P to save as PDFSessions

Day One · Session 03 · Dates TBD

First Deploy

A marketing site, built and deployed in one sitting

Ship AIPhoenix, ArizonaPress → to begin

Ship AIFirst Deploy01/17

Everything so far has lived in a chat window. Tonight it gets a URL.

Same business, same files, same voice. A stranger can finally read it.

Ship AIFirst Deploy02/17

Tonight

  1. 01The chat, in your files
  2. 02Setup, together — the slowest fifteen minutes we run
  3. 03Your one-pager becomes the hero
  4. 04Structure: one CTA, proof over adjectives
  5. 05Pages at scale, without the spam
  6. 06The articles get a home
  7. 07Deploy — a real URL, tonight
Ship AIFirst Deploy03/17

Where we are

  1. Session 01First Threads
  2. Session 02Daily Driver
  3. Session 03First Deploy
  4. Session 04The Night Shift

Four sessions, one business — yours. Every session is free and standalone, each one leaves a folder the next one reads, and catching up late is explicitly allowed.

Ship AIFirst Deploy04/17

Act one

The chat, in your files

Claude Code and Codex are the same model you've been talking to for two sessions. The difference is that they can open your files, run the build, and read the error themselves.

Ship AIFirst Deploy05/17

The jump

The chat window

  • You paste the code in
  • You paste the answer back
  • It can't see the other forty files
  • Every session starts blank
  • You are the copy-paste layer

The agent in your repo

  • It reads the project itself
  • It writes the file
  • It runs the build and sees the error
  • It remembers what's in here
  • You review and decide

It's a terminal, which is the part that puts people off. Nothing tonight needs you to memorise a single command.

Ship AIFirst Deploy06/17

Setup, together

~/

npm i -g @anthropic-ai/claude-code && claude

node v22 — oklogged inready in ~/day-one

The slowest fifteen minutes in the program, and we spend them as a room: Node, an account, an agent that starts, the template cloned. Nobody moves on while the person next to them is still installing.

Instructions went out in Discord before tonight, and this session needs a paid plan or an API key — said plainly rather than discovered halfway through. If you did the setup at home, this is your coffee break.

Ship AIFirst Deploy07/17

Act two

The site

Every section has a job. Anything without one gets cut, however nice it looks — and the hero is a test of session 01, not a writing exercise.

Ship AIFirst Deploy08/17

Top to bottom

  1. HeroWhat it is, who it's for, one thing to do next. Your one-pager, unchanged if it was any good.
  2. ProofImmediately after. A number, the product doing the hard case, one sentence a real person said.
  3. How it worksThree steps. If it needs five, the product is explaining itself badly.
  4. The objectionName what they're worried about before they leave to go worry about it.
  5. One CTAThe same one, repeated. A second call to action is the same as none.

If the positioning doesn't survive contact with the page, the positioning was the problem — not the page.

Ship AIFirst Deploy09/17

Scaffold, then say something

~/your-product

/site-scaffold → /landing-copy → /og-image

scaffolding app/ …hero ← 01-voice/positioning.mdpreview: your-site.vercel.app

Routing, metadata and sections first, because an empty page you can deploy beats a perfect page you can't. Then the copy, pulled from the one-pager you wrote in session 01. Then links that preview properly, which is ten minutes you spend once.

Proof over adjectives, all the way down. "Blazing fast" is discounted by every stranger who reads it; a number with a method behind it isn't.

Ship AIFirst Deploy10/17

Act three

Pages at scale

One table of real data and one template becomes a page per row. Done carelessly it's spam. Done once, carefully, it's the cheapest traffic you'll ever build.

Ship AIFirst Deploy11/17

One dataset, many pages

The same rows, refracted into whichever shape someone actually searches for. Your ICP file already says what they're looking for — this is that list, turned into pages that answer one query each.

  • Comparisons
  • Use cases
  • Integrations
  • Locations
Ship AIFirst Deploy12/17

The line between scale and spam

  • The doorway testRead one generated page out loud. If it's a keyword with a header on it, that's a doorway page — search engines are explicitly built to bin those.
  • Sample of fiveGenerate five before you generate five hundred. Five is enough to see whether the template has anything to say.
  • Templated where the data is realRows that genuinely differ get a template. Anything that needs judgement gets written by a human, or doesn't get written.

The test isn't "would this rank". It's "would a person be glad they landed here".

Ship AIFirst Deploy13/17

Tonight's run

~/your-product

/content-map → /programmatic-pages → deploy

18 real queries → 12 pagesgenerating 5 as a sample…deployed — live in 34s

Work backwards from what your ICP types into a search box, generate five pages from real data, read one of them properly, then push. The articles you drafted in session 01 get a home on the same deploy.

Ship AIFirst Deploy14/17

Your site

Live

tonight

Not staged, not on your laptop. A URL you can paste into a message and watch someone open.

Ship AIFirst Deploy15/17

If it ships, it speaks.

Ship AIFirst Deploy16/17

Next

The Night Shift — Session 04, Workuity Biltmore

The site you just shipped grows a support agent that answers from your own pages, and a workflow that drafts next week's article while you sleep. Same repo, prepared branch, nothing built from scratch.

shipai.club · Free, always

Session page
Ship AIFirst Deploy17/17
01/17