Operator’s manual / rev 0.5
The newsletter is the storefront. This is the machine.
Regional Newsletter is the complete operating system behind The Austin Newsletter: the content pipeline, the edition production runbook, the SEO guide engine, the outreach rails, the inbound reply automation, and the kill criteria that decide when to stop. Written while the machine runs, not reconstructed after an exit.
RN-01 / The system
One machine, four rails
The Austin operating system as it runs today. Every box on this sheet has its own runbook in the package.
RN-02 / Spec
Depth you can recount
12
playbook sections, plus two appendices
66
growth-system docs, one per tactic
25
setup runbooks, one per system
141
operational scripts in the working repo
75
database migrations, forward-only
Counted from the working repo on 2026-08-14. Nothing rounded up.
RN-03 / Contents
What’s inside the playbook
The playbook is v0.5 and says so on page one. Sections locked from the Austin launch are marked locked. Sections that depend on live growth and revenue data are marked as backfilling, because writing them before the data exists would be fiction.
RN-04 / Systems tour
The rails, one by one
setup-runbook/edition-production.md
Edition production
The full build sequence for a weekly edition: structure, data-dependent slots, card art, and the checks that run before a send. The same runbook produces the Austin edition every week.
growth-systems/guide-flywheel.md
SEO guide engine
Evergreen city guides built to a written page standard, with gated directory tools behind an email wall. The search rail is designed to compound while the send list is still small.
setup-runbook/outreach-engine-ops.md
Outreach rails
Local business outreach with a mailbox-wide daily send ledger, address verification before any send, deterministic follow-ups, and per-campaign instruments so a dead shape gets retired instead of repeated.
setup-runbook/inbound-reply-engine.md
Inbound reply engine
Every inbound thread lands in a CRM table, replies are drafted in the publication’s voice and reviewed before send, and warm repliers are subscribed only when the original invite carried consent language.
setup-runbook/referral-program.md
Referral program and welcome flow
Beehiiv’s native referral milestones wired into a welcome flow, with crediting built to never break a signup on a bad ref code.
growth-systems/reddit/ + facebook-groups/
Social rails
Drafting engines for Reddit and Facebook groups with review gates, veto windows, per-community cooldowns, and reconcile jobs that read the platform instead of trusting the database.
kill-criteria.md
Measurement and kill criteria
A morning growth report, retro gates on every tactic, and six pre-registered pivot triggers written down before the results came in. The playbook says when to stop as clearly as when to ship.
RN-05 / No claims
What this page will not claim
- No testimonials. The first cohort does not exist yet, so there is no one to quote.
- No revenue screenshots. The Austin operation is pre-revenue and the playbook says so in writing.
- No subscriber-count promises. Your city, your writing, and your consistency decide that.
- No countdown timer. This page looks the same tomorrow.
What is real is the depth: the scripts, the runbooks, and the rails that run every night whether or not anyone is watching. That is the product.
RN-06 / Fit
Who this is for
BUILT FOR
- An operator who will write every week and wants the machine around the writing handled.
- Someone picking a growing mid-size city with real transplant inflow, or already living in one.
- Someone who can hold a technical playbook: the stack is Beehiiv, Next.js, Supabase, and Vercel, and the runbooks are specific.
- Anyone who would rather have kill criteria than a pep talk.
WRONG FOR
- Anyone shopping for passive income. Nothing in here runs without an operator.
- Anyone who needs revenue proof before doing the work. It does not exist yet, and we will not invent it.
- Writers who want prompts and inspiration. This is plumbing, schedules, and checklists.
- Agencies looking for a white-label content mill. The playbook’s growth rules forbid exactly that.
RN-07 / Founder
A note from Joe
I run the systems behind The Austin Newsletter. Carissa, my wife, is the byline and the voice; the machine that gets her edition out every week is mine.
The playbook this page sells is not a summary of that machine. It is the actual document we work from: the same file gets edited when a rail changes, and the same kill criteria decide what we stop doing. When we clone to city #2, this is what we clone from.
I want to be plain about the state of it. Austin is live and pre-revenue. The sections that depend on long-run data are marked as backfilling, and the monetization section fills in from real sponsor invoices, not projections. That honesty makes the product less shiny. It is also the reason to trust the rest of it.
Joe Spisak
RN-08 / Price
The playbook opens soon
One purchase, once: the city-launch playbook, the runbooks and growth-system docs it references, and a lifetime seat in the operator community. Organized to be run, not read once.
- – the playbook, all 12 sections
- – the per-system setup runbooks
- – the growth-system docs, one per tactic
- – the kill criteria, pre-registered
- – the operator community, lifetime, no renewal ever
$999
One-time. No subscription, no royalty, no upsell waiting behind the checkout. 30 days, any reason, full refund.
The waitlist hears first, and nothing on this page will pressure you in the meantime.
RN-09 / FAQ
Fair questions
Is this a course with videos?
It is a written operating system: the playbook plus the runbooks and system docs it references, and a lifetime seat in the operator community where the people running it compare notes. Format details land with the launch email.
Will this work in my city?
Honest answer: not every city qualifies, and most sellers in this market refuse to say so. Two tests before you spend anything: can you name 25 local businesses that would plausibly pay to reach your audience, and does your metro have roughly 150,000 people within a short drive. The professionals who launch city newsletters for a living qualify only 100 to 150 US cities at their scale. A full market-qualification rubric ships inside the playbook, and it is built to be able to tell you no. A free four-question version lives at /city-check on this site.
What is the refund policy?
30 days, any reason, full refund, no exercises to show and no forms to fill. With no testimonials on this page, the guarantee is doing their job, so it is the strongest one we could write.
Do you promise revenue or subscriber numbers?
No. The Austin operation is pre-revenue and the playbook’s monetization section stays thin until real sponsor data exists. Anyone selling you certainty in this market is selling the certainty, not the market.
What stack does it assume?
Beehiiv for email, Next.js on Vercel for the site, and Supabase for the backend. You can substitute, but the runbooks are deliberately specific, and the specificity is most of their value.
Why sell the playbook instead of just launching more cities?
The plan is both. Each city is a separate publication on the same playbook, and the playbook is the parent product. Selling it forces it to stay clean enough for a stranger to run, which is exactly what city #2 needs.
How current is it?
The playbook is versioned (v0.5 today) and edited while the machine runs. Sections are individually marked locked or backfilling, so you always know which parts are settled and which are still earning their data.
When does it open?
When the payment link goes live. The waitlist doubles as the Regional Newsletter operator letter: free tools and working pieces from the running machine while you wait, then the launch email. Unsubscribe anytime.