Written by DOMA at the end of the live three-way conversation that produced the connection strategy and the flagship essay. This is the brief DOMA captured as the work landed — strategy doc at v5, essay live, joint byline confirmed. SPINE format. DOMA's voice is unedited except for the CTA keyword (which changed from START to OTW for closing-rate measurement just before this brief was written).
Situation
Domain beta launching in ~2 weeks. 400 existing users (pre-aware, not pre-converted), ~500 waitlist, original goal of 1,000 in 4 weeks. v5 strategy doc locked. Flagship essay now live at on-the-work.pages.dev — the 20%-bucket artifact the strategy kept asking for. Joint byline (DOMA + Matt's Claude). CTA: text OTW to Signal number. Deployed on Cloudflare Pages via Matt's markdown-pages-starter kit.
Missing: Waitlist signup source data. Current weekly waitlist inflow rate. Whether session-2 product mechanic has an owner or spec.
Problem
The moment-generation engine runs on founder voice, bounded to 4-8 dense artifacts in 4 weeks at ~2.5x multiplier = 10-20 moment-events. Each would need 30-60 conversions to hit 600 net new users, which no single artifact delivers. The 10% agentic bucket produces zero in-window users — it's aspirational, not operational. Controllable channels max ~350 net new without product mechanics that don't exist (session-2, post-session WOM). The 4-week target requires those mechanics.
Missing: Can session-2 ship in 3 weeks? If not, what's the revised target with real numbers?
Implication
Without product mechanics, the math caps at ~750 total users. The flagship essay is now the first live test of the closing constraint — if the CTA converts readers before they close the tab, the 20% bucket works. If it doesn't, the moment-generation engine has a closing-rate problem on top of the throughput ceiling.
Need / Payoff
v5 strategy doc complete with four layers, two independent findings, honest bridges. Flagship essay live. Next: bring the reframes to the Domaneers for execution planning — especially the product dependencies (session-2, post-session WOM), the revised target (~750 realistic, 1,000 with product), and the essay as first artifact to measure closing rate against.
Missing: Toby and Andrew's reactions to the reframes and the honest ~750 target.
External perspectives
Matt's Claude co-authored the strategy and the flagship essay. The Domaneers (Toby, Andrew, Matt C, Kelani) own execution but haven't seen any of the reframes yet. Andrew Rosen is the canonical failure case for moment-decay. The essay's joint byline (DOMA + Matt's Claude) is itself a positioning move — resolved during the session after debating agent-as-author vs human-as-author.
Missing: Toby and Andrew's reactions to the reframes, the essay, and the honest ~750 target.
Open questions
- Does the team have waitlist signup source metadata for segmentation?
- Who owns the session-2 product mechanic — assigned or floating?
- Can session-2 ship in 3 weeks? If not, what's the revised target?
- What's the current waitlist inflow rate — growing, flat, or plateaued?
- What's the essay's closing rate — does the Signal CTA convert before tab-close?
- Does the team accept ~750 as the realistic target, or does 1,000 stay as a stretch goal with named product dependencies?
Next move
Bring the reframes and the live essay to the Domaneers for execution planning. The essay is the first measurable artifact — its closing rate tests whether the 20% bucket works.
An earlier version of this brief — DOMA's mid-conversation v2 snapshot — is preserved in the repo at doma-brief-v2-snapshot.md. Comparing the two shows how the strategy evolved through the pressure-test: the v2 brief asked whether the on/in distinction works as a channel selector; v3 reflects the answer (it doesn't — it's a closing constraint, not a channel filter).