You asked where to take this. I've read every surface, every doc, and every commit — here is my honest read. Five pitches, each one buildable from parts that already exist. None of them are fantasies; all of them are choices. The last section is the order I'd play them in.
PITCH 01 · START THIS WEEK
The Open Notebook
Make the site's own evolution the content product. The most interesting thing happening here isn't any single surface — it's that a personal site ships 20–60 commits a day with an AI in the loop, films itself, QAs its own games, and writes essays about its own architecture. That story is half-told. Close the loop and the audience compounds.
Already on the board
- Newsletter capture with double opt-in (homepage, blog, /ask, /tools) — but nothing ever sends
- LinkedIn orchestrator + weekly YouTube Shorts train, both running on cron
- The Strata essays + /studio reels — the narrative voice already exists
- RSS/Atom, sitemap, OG images, JSON-LD — distribution plumbing is done
The bet
Building-in-public only works with a cadence. A weekly 'what the site shipped, what the agents did, what broke' digest — written from the commit log and the pipeline telemetry, human-gated like everything else — turns passive plumbing into a compounding audience. The audience then de-risks every other pitch on this page: it's distribution for Boards, proof for the Studio of One, and a waitlist for anything.
First 90 days
- Ship the newsletter send pipeline (the deliberately-cut follow-up): compose from the week's merges, human gate, batch send with per-recipient unsubscribe
- A public /changelog surface — the weekly digest's permanent home, indexed and shareable
- One studio reel per major feature, cut into the digest and the Shorts train
The honest risk
Consistency. Audience growth is humiliatingly slow for months, then suddenly isn't. The engines remove most of the labor, but the human gate means you still show up weekly.
The Studio of One
Sell the meta. The differentiated asset isn't the blog or the boards — it's the way this site builds itself: the enrichment pipeline, the orchestrators, the autonomous playtest rig, the agent org with human gates everywhere it matters. Other people want exactly this installed in their company, and /hire already takes money.
Already on the board
- Stripe rail live end-to-end with fixed-scope offers ($150–$750) and auto-fulfillment
- The proposal pipeline: lead intake, agent-drafted proposals, weekly digest with referrer attribution
- The portfolio IS the case study — every pipeline doubles as a demo
- Hire CTAs now on every reading surface, with per-surface conversion measured
The bet
One productized high-ticket engagement — 'I'll install an agentic content + QA pipeline in your org, fixed scope, fixed price' — at $5–15k, replacing hourly consulting with a repeatable package. Each engagement ends with a public case-study essay, which feeds the Open Notebook, which sells the next one. Services don't compound like products, but they fund everything else on this page while the products grow.
First 90 days
- Write the offer: one page, one price, one deliverable, on /hire next to the existing offers
- Land one design-partner engagement at a founder-friendly price; over-deliver
- Publish the case study as a Strata-grade essay; cut a reel; feed the digest
The honest risk
Time. A real engagement competes with everything else here for the one human in the loop. The package has to be ruthlessly scoped or it eats the quarter.
Boards
The four free tools are one product wearing four coats. Todo boards, weather dashboards, trips, countdowns — each is 'spin up a small shared board at a private link and invite your people in one click.' Converge them into a family with a shared account home, a template gallery, and a paid tier, and you have a real freemium consumer product sitting in the gap between the group chat and the heavyweight app.
Already on the board
- Multi-tenancy, invites, roles, and demo boards across all four surfaces
- /tools — the public, indexed landing with reels and a create-yours funnel
- Stripe billing rail (one catalog, several storefronts) ready for a paid tier
- The add-ons registry as the product family's single source of truth
The bet
Families and small groups are chronically underserved: real SaaS is too much, the group chat is too little. Free tier: one board of each kind. Paid tier ($4–6/mo): more boards, more members, custom board types, calendar feeds everywhere. Distribution is SEO on /tools plus every invite being a growth loop — each board invites 2–25 people who didn't know the site existed.
First 90 days
- A unified /boards account home: every board you own or belong to, one provisioning flow
- Paid-tier limits wired through the existing catalog (the tenancy caps already exist as code)
- Activation funnel measurement: visit → sign-in → board created → second member joined
The honest risk
Consumer freemium needs volume, and the site doesn't have it yet — which is why this sequences after the Open Notebook, not before. Conversion at low traffic will read as zero for a while.
PITCH 04 · WHEN THE PULL APPEARS
Heddle, Outside
Heddle is the only surface that's already shaped like a B2B company: a real workspace with roles, AI budget rails, event telemetry, an in-product agent, and a login flow with its own brand. It runs one internal program today. Take it to one real external institution and it stops being a feature of the site and starts being a business.
Already on the board
- The full member app: dashboards, exams, attention digest, AI usage budgets
- Auth with magic links, the branded login, the marketing landing with a demo CTA
- The CRSS pipeline as the worked example of a whole program run through it
- Telemetry from day one — heddle_events already records what users actually do
The bet
Small certification programs (the CRSS-shaped ones: recovery support, allied health, trades) have real money, real deadlines, and no tooling between 'spreadsheet' and 'enterprise LMS they hate.' Three design-partner pilots at honest pilot pricing would tell you in one semester whether this is a company.
First 90 days
- A pricing page and a real onboarding wizard (workspace → program → first exam)
- Terms, privacy, and the legal review the docs already flag as the external-launch gate
- Three warm pilot conversations from the niches the CRSS work touched
The honest risk
This is the biggest commitment on the page. B2B means support, uptime promises, and legal exposure — it's a company, not a surface. Exercise this option when an institution pulls, rather than pushing it cold.
The Civic Stack
Every small town, village, and HOA in America has a corpus of rules nobody can search and a clerk drowning in process. The Rules Stack (cited ask-the-corpus over Pingree Grove's ordinances) and the Josephine court console are two ends of the same product: civic text, made answerable, with citations and a strict data boundary. Generalize it.
Already on the board
- The corpus schema + cited agent with anon-read posture (rules are public by design)
- The court-collections console — proof the PII-boundary discipline holds under real client data
- Topic derivation, per-neighborhood pages, sitemap enumeration — the SEO shape works
- A real municipality and a real court as the first two worked examples
The bet
Start where there's no procurement: HOAs and homeowner groups self-serve a corpus upload and get a cited Q&A site for their covenants at $20–50/mo. Municipalities come later, slowly, by referral. Govtech sells glacially but never churns — every customer is a decade-long annuity.
First 90 days
- Self-serve corpus intake: upload PDFs → chunked, embedded, cited — the pipeline exists, the wizard doesn't
- A second corpus live (any HOA — even a free one) to prove the generalization
- One landing page that says 'searchable, cited answers for your community's rules' with a demo
The honest risk
Sales cycles and document jank. Civic PDFs are where text extraction goes to die, and the buyer often isn't the user. Lowest conviction not because it's bad — because it's slow, and the page above it is faster.