TerraPulse monetization roadmap

Claude's working advice to Brad and Mike on if/when to activate monetization, and what to do in the meantime. Companion to weekly-cadence.md and research-arcs-and-idle-projects.md. This is advice for them to weigh against context Claude can't see (Brad's existing reputation, conversations with potential customers, runway, competitive pressure). Push back wherever it's wrong.

Core view

Don't activate monetization yet. Target 6–9 months out.

Activating too early on too-thin a foundation costs more than it earns. The work needed in the meantime IS the monetization work — it isn't a separate effort.

Why "not yet"

TerraPulse has the assets a paid product needs (180M+ observations, the V-series methodology, the API, live-event capture, knowledge graph) but doesn't yet have demand evidence. No waitlist, no inbound asking-to-pay, no external citations of V-series papers. Without that, pricing and offering design is a guess.
Infrastructure is still in the "occasional incident" phase. Two connection-pool-saturation incidents in five days (the 2026-05-06 dedup query, then 2026-05-11's stats refresh). Paying customers can't see those — but a 504 on day three of a trial is fatal to retention. Target 90+ consecutive days of zero unplanned outages before charging.
terrapulse.info isn't polished to "credible commercial product" standard yet. The Wednesday cadence block is doing this work but it's months, not weeks.
The V-series papers are technically rigorous but don't yet have a headline result broadly shareable to non-specialists. A hedge-fund analyst or insurance underwriter won't read a revtex PRL paper cold and convert.

Monetization paths, ranked by feasibility

Audience-first creator path (X subscriptions, sponsorships, eventually a paid newsletter)

The path you've been gesturing at. Realistic. Requires audience size — roughly 10k engaged followers before X creator revenue is meaningful, ~50k before it's a real income line. Organic time-to-build: 12–24 months at consistent cadence. Can compress dramatically with one same-day live-event paper going viral (the Enid EF-4 template).

API subscription / freemium

Open the read-only API to everyone, charge for higher rate limits, structured exports, and knowledge-graph access. Target: data-curious developers, small research shops, hobbyist trading communities. Low ACV ($10–50/mo) but high potential count. Easiest infrastructure lift since the API already exists.

Research-subscription / early-access papers

Paid newsletter for the V-series. Target: weather hobbyists, prepper-adjacent community, citizen scientists. Low ACV ($5–20/mo). Easy to implement. Hardest part is the audience to convert from — so this path is downstream of the audience-first path.

Enterprise bespoke research

Custom analyses for specific clients (insurance carriers, energy traders, agritech firms wanting climate-risk reports). Very high ACV ($10k–100k engagements) but lumpy revenue and slow sales cycles. Probably not viable without a dedicated sales motion or a marquee customer logo. Year-two consideration.

Live event alerting / pager service

Email or SMS when interesting events fire (M6+ earthquake near population, X-class flare, tornado outbreak forming). Mid ACV. Differentiates on cross-source integration. Year-two consideration.

What to do for the next 6 months (this IS the monetization work)

Start posting on X immediately

No monetization expectation. Pick one consistent format — e.g., a "what TerraPulse saw this week" Friday digest — and commit. The Friday brand-readout block in weekly-cadence.md already produces this content; just publish it.

Build a 30–50 paper catalog

At the current cadence that's 6–12 months of papers. Each paper is a brick in the credibility wall and a candidate for going viral when a relevant event fires.

Add email signup to terrapulse.info

Name + email only. "Get a monthly summary." No commitment. Captures the demand evidence currently missing. If 500 people sign up in 6 months with zero marketing spend, the audience exists. If 12 do, it doesn't — and that's equally useful information.

Run 15–20 customer-discovery conversations

Not pitching — listening. "What would you pay for, and how much, and why." Across the segments above. Brad probably has a network here. Claude can help draft outreach text.

Capture 3–5 more live events

Same-day analyses on tornadoes, hurricanes, M6+ earthquakes, X-class flares, eruptions. The Enid EF-4 paper is the template. Each one is both a finding and a marketing moment. The Project #8 entry in research-arcs-and-idle-projects.md is the scaffolding work.

Lock in zero-incident infrastructure

Thursday cadence block exists for this. By month 6 the admin should not have had an unplanned outage in 90+ days.

Activation criteria — when to switch monetization on

All of these must be true, not most:

Newsletter / email signup list ≥ 500 organic subscribers
~10k X followers OR five external citations of V-series papers
30+ consecutive days of zero unplanned outages on terrapulse.info (running counter, reset on any incident)
At least one specific person or org saying in writing "I would pay $X for Y, when can I?"
A concrete pricing model tested verbally against 5+ prospects
A working billing integration (Stripe is simplest) and live ToS / Privacy pages

When all six land, switch on the easiest tier (likely freemium API or research subscription) first. Don't launch all paths simultaneously. Pick the cheapest-to-operate, watch conversion, iterate.

The mistake to avoid

Activating monetization on the timeline of "we've done a lot of work and feel ready" rather than the timeline of "demand evidence accumulated enough to validate a specific offering." The work is real; the demand evidence isn't there yet. Six months of disciplined audience-building solves both: you'll have the readiness AND the data to know what to sell.

How Claude tracks progress

Per Mike's instruction (2026-05-12), Claude keeps a running watch for monetization milestones during the weekly cadence. Specifically:

Monday data audit also checks for inbound monetization signals: any external citation of a V-series paper appearing in loader_runs source URLs, any email captured by terrapulse.info signup, any X DMs / mentions, any inbound contact via the site.
Tuesday editorial review flags any V-series finding that's a candidate "viral catalyst" — a result with a clear single-sentence summary, an obvious figure, and a non-specialist hook.
Wednesday public-surface QA explicitly tracks: X follower count, email signup count, organic site traffic (when analytics land), incident-free-days counter.
Thursday infra block maintains the incident-free-days counter and resets it on any unplanned admin-down.
Friday brand readout publishes the weekly digest to X, updates the running monetization-readiness scorecard, and reports week-over-week deltas on each activation criterion above.

A docs/monetization-scorecard.md will get added once there are any non-zero numbers to track. Until then the criteria above sit dormant; the Friday block confirms "still zero" each week so silence isn't ambiguous.

Stashed implementations (ready to ship)

Work that's been built but deliberately not activated, parked on feature branches for later. Each entry lists the activation steps.

Email signup form

Branch: feature/email-signup-stash (pushed to origin)
What it ships: Astro signup component on the homepage, FastAPI POST /api/v1/subscribe endpoint with honeypot + per-IP rate limit + idempotent inserts, SQLAlchemy EmailSubscriber model, Alembic migration creating email_subscribers table, GET /api/v1/subscribers/count for the cadence scorecard.
Why stashed: Per the activation criteria above, deferred until 6–9 months out. Built ahead of time on 2026-05-12 so it's ready to ship the day the email-list line gets prioritized.
To activate: git merge feature/email-signup-stash, python -m alembic upgrade head, cd web && npm run build, sudo systemctl restart terrapulse.service terrapulse-web.service, smoke-test POST /api/v1/subscribe.

Status as of 2026-05-12 (baseline)

Recording the starting line so future deltas are measurable.

Email signup list: built but stashed (see feature/email-signup-stash) — not active on terrapulse.info
X account: not yet created (or at least, no posting cadence established)
Inbound paying interest: zero documented
External citations of V-series papers: zero known
Incident-free days counter: resets today (2026-05-12 had the #189 stats-refresh incident); Day 0
Papers shipped to date: ~35 (counting the V-series + related arcs)
Active datasources: 373
Total observations: ~181M (reltuples estimate)
Live events captured same-day: 1 confirmed (Enid EF-4, 2026-04-24)
Pricing model: not defined
Billing integration: not built

This is the starting line. Friday brand-readouts going forward will note movement on any of these.