Day Zero · Session 02 · Dates TBD
Routines, artifacts, and work that runs on a schedule
Ship AIPhoenix, ArizonaPress → to begin
AI that waits to be asked is a tool. AI on a calendar is a coworker.
Tonight is the difference between those two, built on screen with your files from session 01.
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.
Act one
A routine is three things: a skill that knows how, a trigger that fires it, and a checkpoint where you're still in the loop. All three start with something worth reading.
Dead
Live
The tell is simple: if the fix for a stale file is "regenerate it", it was never live.
Four weeks, from what they actually ask
/content-calendar
writing a one-page audience note4 weeks, 8 slots — 6 entries, 2 left openwrote 02-routines/calendar.md
Not topics that sound like marketing. The questions your ICP types into a search box, and the ones they ask you on a call — turned into a dated four weeks you can argue with.
Session 01 made a reusable skill, such as meeting notes. Start here with an audience, one problem, and three real questions; run /icp-builder if needed. Then add one calendar entry by hand.
Try the reusable skill
Use the prepared task and inspect the draft against the source facts.
Choose a task, then run the example.
Act two
Use the scheduler available in your account, or a demonstrated cron setup. Check plan access, connector permissions, and delivery before relying on a routine.
A checkpoint you never actually read isn't a checkpoint — it's theatre with your name on it. Remove it or mean it.
The report that shows up on its own
/weekly-report
5 numbers you can actually getscheduled: Mondays, 7:00 AMfirst run landed — 168 words
Three to five numbers you can genuinely obtain, under two hundred words, in plain English. It says what moved and what it thinks that means, and it's honest about small numbers instead of dressing them up as percentages.
If it hasn't run once, it isn't set up. Watch the first one land before you trust the second.
Act three
The most useful thing an agent does for outbound is the ninety percent before the send button. The send button stays yours.
| The agent | You | |
|---|---|---|
| The list | Twenty named accounts, each with a reason | Cut the ones that don't fit |
| The sequence | First touch, two follow-ups, a break-up | Cut anything you wouldn't reply to |
| The specifics | One line per account that couldn't be in anyone else's | Check that it's true |
| Sending | Never | Every one of them, by hand |
Twenty relevant emails take an afternoon. Five hundred bad ones take an afternoon too, and cost you the domain.
Drafts, into a folder
/icp-builder → /outbound-sequence
20 named accounts, 6 filtered out1 touch + 2 follow-ups, draftedwrote 02-routines/outbound/ — 0 sent
The audience note made tonight becomes a named list, then a sequence short enough to read on a phone. It writes to a folder and stops there — nothing in this program has your outbox.
None of this is new work. It's the same work, minus the remembering — and the last step is the one that keeps the whole loop honest.
Proof of work.
Next
Everything so far lives in a chat window and a folder. Next session it gets a URL. Bring Node, a GitHub account and a Vercel account — the setup instructions go out in Discord beforehand, and we do the install together in the room.
shipai.club · Free program sessions