Listening for events…
← All Docs

TerraPulse Monetization — Implementation Plan

Companion to the monetization brainstorm. For each idea: the dexes/data sources required, the site expansions required, and the concrete to-dos on your end (data sourcing, licensing, API research, content) vs. Brad's end (backend). Ideas are grouped as in the brainstorm, but read Part 1 first — it changes how much work everything else is.

PART 1 — The Six Shared Foundations

Almost every idea on the list is a thin product layer on top of one of these six capabilities. Build these once and roughly 80% of the brainstorm becomes "configure a new vertical," not "build a new product." This is the real implementation plan; everything after it is routing.

F1. Geometry Query Engine ("what happened HERE?")

The single most load-bearing piece. Today the Dex answers "tell me about this earthquake/station/storm." Nearly every paid idea inverts that: given a user-supplied point, parcel, route, or asset list, return every measured event that touched it.

  • What it is: point/polygon/route → spatial+temporal intersection against every peril dex (hail, wind, tornado paths, freeze, flood stage, quake shaking radius, smoke, lightning).
  • Powers: Field Dossier (ag), roofer verification, homeowner dossiers, construction weather-days, forensic reports, CarFax-for-parcels, private asset Dexes, site-selection reports, freight routes — i.e., most of Parts 2, 6, and 7.
  • Brad: PostGIS or DuckDB-spatial layer over existing tables; parcel draw/upload UI (GeoJSON, KML, CSV of lat/lons).
  • You: research county parcel-boundary data (many US counties publish open GIS parcels — vet licensing per county; Regrid is the commercial fallback, note its cost); define per-peril "touch" rules in plain English for Brad (e.g., hail = SPC report within X km OR radar-indicated MESH over polygon; freeze = nearest station ≤32°F for ≥N hrs).

F2. Evidence PDF Generator

  • What it is: a templated, provenance-stamped PDF: event list, raw source records attached, citation per line, checksum/QR verification link back to a permanent TerraPulse URL.
  • Powers: every claims/evidence product, compliance logs, forensic reports, site-selection reports, novelty reports.
  • Brad: PDF render pipeline + permanent verification URLs (tamper-evidence is the brand).
  • You: write the template copy (this is content strategy — the PDF must read credibly to an insurance adjuster, not a data scientist); collect 2–3 real FSA/insurance claim forms to mirror their language; draft the "About this evidence / methodology" boilerplate page.

F3. Alert & Webhook Engine

  • What it is: user-defined thresholds on any dex metric + geography → email/SMS/push/webhook. One engine, many skins.
  • Powers: RTK guard, aurora, ham radio, drone, buoy, smoke/AQ, quake-watch, drought money-triggers, OSHA heat, parametric trigger notifications — all of Part 4 and half of Part 5.
  • Brad: rules engine, delivery infra (email first; SMS via Twilio-class provider later — SMS costs money per message, so gate it to paid tiers), webhook signing.
  • You: research SMS/push provider pricing; write the alert copy library (each alert type needs a template that tells the user what to do, not just what happened — the ag plan's "you're now eligible, deadline X" pattern).

F4. Accounts, Billing & Entitlements

  • What it is: the boring prerequisite for charging anyone: signup, Stripe, subscription tiers, per-product entitlements, usage metering for the API.
  • Brad: Stripe integration, auth (you likely have admin auth already; this is customer auth), entitlement checks on API keys and site features.
  • You: decide the initial tier map (recommendation below in Part 12); write pricing page copy; set up the Stripe account, business entity question (see Part 11 — do this early), sales-tax/SaaS-tax registration research for Michigan.

F5. API Productization

  • What it is: the REST API you already serve, wrapped in keys, rate limits, docs, and tiers.
  • Powers: all of Part 3, the B2B feeds in Part 2, developer platform in Part 10.
  • Brad: API keys, rate limiting, usage dashboards.
  • You: write the docs (developer docs are content strategy and you're the writer); competitive pricing research (OpenWeather, Tomorrow.io, Xweather API pricing pages — position under them); draft attribution requirements for the free tier.

F6. Private Objects ("bring your own dex entries")

  • What it is: let a user register their own objects — parcels, stores, towers, boats, worksites — as private dex entries that accrete peril history exactly like public objects do. It's the Dex concept, sold.
  • Powers: Field Dossier, asset-portfolio monitoring, construction sites, OSHA worksites, freight, private-dex enterprise deals.
  • Brad: private namespace in the dex schema, per-account visibility, bulk CSV import.
  • You: define the object schema per vertical (what fields does a "worksite" need vs. a "parcel" vs. a "vessel"?) — one page each.

Sequencing of foundations: F4 (billing) and F1 (geometry) first — nothing sells without them. F2 rides on F1. F3 is parallelizable. F5 is mostly config. F6 extends F1.

PART 2 — Evidence & Claims Products

2.1 Roofer/Adjuster Hail Verification

  • Dexes needed: none new — severe weather dex already has SPC hail/wind reports. Upgrade it: onboard NOAA MRMS radar-derived hail (MESH grids) so you can verify hail where no human filed a report. That upgrade is the entire product moat.
  • New sources for you to vet: NOAA MRMS (public domain, huge volume — flag storage cost to Brad), NWS damage survey polygons, NLDN alternative lightning sources (see 2.3).
  • Site expansion: /verify landing page: enter address → free teaser ("3 hail events since 2020") → paid full report (F1+F2).
  • Your to-dos: competitor teardown of HailTrace/Interactive Hail Maps (features, pricing, report format); write the roofer-facing landing copy; list 20 Grand Rapids-area roofing companies for a pilot outreach email.
  • Effort above foundations: small. Sequence: first evidence product after ag — same engine, hotter buyer.

2.2 Homeowner Claim Dossier

  • Dexes: same as 2.1 + streamflow/flood stage (have) + wildfire/smoke (have) + lightning (2.3).
  • Site: consumer-toned version of the same /verify flow; one-time Stripe checkout (no subscription friction).
  • You: consumer copy; a "how to use this with your insurance claim" guide article (content marketing + SEO).
  • Effort: trivial once 2.1 exists.

2.3 Lightning Strike Verification

  • Dexes: new lightning dex. This is the one real data-sourcing problem in Part 2: the gold-standard network (Vaisala NLDN) is commercial.
  • You (critical path): licensing research — options to vet: GOES-16/18 GLM (Geostationary Lightning Mapper — public, satellite-based, coarser but free and green-list compatible), Blitzortung (community network — vet their license carefully, likely non-commercial), ENTLN/Earth Networks (commercial quote). Recommendation: start with GLM, be honest in the report about resolution, upsell later.
  • Site: lightning dex family page + it plugs into the existing verify flow.
  • Effort: medium (one new ingest for Brad).

2.4 Construction Weather-Day Documentation

  • Dexes: none new — weather dex (precip, temp, wind) covers it.
  • Site: project-based UI: register a worksite (F6), set contract thresholds ("rain day = ≥0.10 in"), get an auto-maintained log + monthly PDF.
  • You: research what AIA/ConsensusDocs contracts define as a compensable weather day (this defines the default thresholds — a few hours of reading); write the "defensible weather log" pitch page; identify GR-area general contractors for pilots.
  • Effort: small. Strong candidate for the second vertical after ag.

2.5 Forensic Weather Reports for Attorneys

  • Dexes: none new (weather, severe, lightning once 2.3 lands).
  • Site: /forensic page; higher price point, same F1+F2 engine, plus a "certified by TerraPulse, methodology attached" cover page.
  • You: research CompuWeather/Forensic Weather Consultants' offerings and pricing; draft methodology documentation rigorous enough to survive a deposition (this is a writing task squarely in your lane); check whether "expert report" framing creates any legal exposure vs. "data report" framing → keep it "data report."
  • Effort: small. High margin.

2.6 Event Cancellation Proof

  • Dexes: none new. Site: none new — it's the homeowner dossier pointed at a venue+date. Add an "event" preset. You: copy only. Effort: trivial; bundle, don't build.

2.7 Marine Incident Reconstruction

  • Dexes: extend streamflow/ocean coverage: NDBC buoys (vet — NOAA, public domain, easy green-list add), CO-OPS tides/currents (have via NOAA), Great Lakes-specific: GLERL/GLOS (vet licensing — you're 30 minutes from Lake Michigan; Great Lakes-first is your beachhead angle again).
  • Site: buoy dex pages; verify flow accepts open-water coordinates.
  • You: vet NDBC + GLOS; marine insurer/surveyor market scan.
  • Effort: small-medium.

2.8 Freight & Cargo Claims

  • Dexes: none new; needs route-shaped queries (F1 handles polygons; add polyline+time support).
  • Site: upload a route (GPX/CSV with timestamps) → conditions along it.
  • You: talk to one freight broker or cargo insurer before building anything — this is the least-validated idea in Part 2. Effort: small, but park until validated.

2.9 Solar/Wind Underperformance Verification

  • Dexes: new irradiance data: NREL NSRDB (vet — free for most uses, check commercial terms), NOAA SURFRAD stations (public), Copernicus CAMS radiation (already green-list family). Wind: existing station obs.
  • You: vet NSRDB commercial licensing (the one real question); market scan of solar O&M software.
  • Effort: medium. Park behind the higher-heat verticals.

2.10 Film/TV Production Weather Logs

  • Dexes/site: nothing new — construction product (2.4) with different copy. You: copy + a list of Michigan film-incentive-adjacent production contacts, someday. Effort: trivial; dormant preset.

PART 3 — API & Data Products

3.1 Tiered Public API

  • Dexes: none. Site: /developers portal — docs, key management, usage dashboard, pricing (F4+F5).
  • You: write the docs (biggest single writing task on this list — budget real time; good docs ARE the product); attribution policy; pricing teardown of competitors.
  • Effort: foundation work only. Ship early — it monetizes existing traffic with zero new data.

3.2 Per-Dex API Products

  • Site: pricing page variants + entitlement flags. You: decide which 3 dexes get standalone SKUs (suggest: space weather, earthquakes, severe weather — most distinct buyer profiles). Effort: trivial after 3.1.

3.3 Webhooks-as-a-Service

  • Rides entirely on F3 + F5. You: docs section + examples ("POST when Kp≥7"). Effort: trivial after foundations.

3.4 Historical Bulk Exports

  • Site: /datasets catalog page; Stripe checkout → signed download link.
  • Brad: export pipeline (Parquet/CSV).
  • You: curate the first five datasets from existing Lab investigations (the 13,547-storm IBTrACS set, the 53-year syzygy-tagged quake set, etc. — the investigations already did the cleaning); write dataset cards; licensing check per dataset: confirm each upstream source permits redistribution (IBTrACS/NOAA yes; Copernicus requires attribution language; document per dataset).
  • Effort: small. Quick win.

3.5 SLA/Uptime Tiers

  • Site: enterprise contact page. You: draft a simple SLA doc (99.5%, support email, status page you already have). Effort: paperwork, not code. Wait for the first inbound enterprise ask.

3.6 White-Label Widgets & Embeds

  • Brad: embeddable JS widget versions of the pulse feed + a dex map, keyed and domain-locked.
  • You: pitch list — local TV meteorologists (start with Grand Rapids stations), county EM offices, niche weather blogs; one-page media kit.
  • Effort: medium. Park until API tier proves demand.

PART 4 — Consumer Alert Subscriptions

All of Part 4 is one build: F3 alert engine + F4 billing + a landing page per audience. No new dexes for most — space weather, severe weather, weather, streamflow, radiation, wildfire are live. Per-idea deltas only:

Product New data needed Your to-dos Notes
4.1 Aurora alerts None (Kp/Dst live). Nice-to-have: NOAA OVATION aurora oval — check: it's a model. Skip or clearly label; stay measured (Kp/Bz/solar wind). Landing copy; photographer-community seeding plan (aurora FB groups, r/aurora) Best marketing-to-effort ratio on the whole list
4.2 Ham radio Add solar flux F10.7 if not ingested (NOAA SWPC, public) Copy in ham vocabulary (you'll need to learn it — fun rabbit hole); ARRL/club outreach Hams will scrutinize provenance — your strength
4.3 Stargazer bundle Satellite passes: you have CelesTrak; pass prediction is computation not modeling of nature — decide if it violates the no-forecast stance (recommend: allow, it's orbital mechanics) Copy Bundle with 4.1, don't price separately
4.4 Drone pilots None (Kp + wind live) Copy; Part 107 community outreach Doubles as RTK-guard marketing
4.5 Buoy alerts NDBC ingest (also needed by 2.7 — shared) Vet NDBC; spot-name UX ideas Great Lakes surfers are a real, underserved niche
4.6 Smoke/AQ Confirm AQI ingest (AirNow — vet: public, attribution required) Copy for parents/coaches/outdoor employers Employer angle feeds 5.1
4.7 Quake watch None Copy; diaspora-community angle research Simplest of all — ship first as the F3 test case
4.8 Radiation watch None (Safecast/RadNet live) Copy — careful, non-alarmist tone (APOC lessons apply) Small but loyal audience

PART 5 — Compliance & Regulatory

5.1 OSHA Heat-Stress Compliance Logging ⭐ treat as a first-class product, not a list item

  • Dexes: weather dex + heat index / WBGT computation. WBGT from station data is a derivation, not a model — document the formula openly. Optionally onboard OSHA-relevant references.
  • You (critical path): read the current status of OSHA's proposed heat rule (it's been moving — check where it stands as of now, plus existing state rules in CA/WA/OR/MN that already bind employers); this determines required log format. Then: define the worksite object schema (F6), write the "audit-ready heat log" pitch, list target segments (landscaping, roofing — overlaps with 2.1's customer list! — warehousing).
  • Site: worksite registration, daily auto-log, threshold alerts ("heat index crossed 90°F at Site 3 — rest-break trigger"), monthly compliance PDF (F2).
  • Effort: medium. Revenue ceiling: high. Same buyer as construction weather-days — sell them together.

5.2 Environmental Compliance Archive

  • Brad: immutable storage layer (append-only, hashed, timestamped — you already have provenance; add tamper-evidence guarantees).
  • You: research which regulated industries must retain ambient-condition records (mining MSHA, air permits) — validate before building. Effort: medium; park until a real prospect appears.

5.3 ESG / Climate Disclosure Data

  • Dexes: none new — it's F1 historical queries per facility + F2 reports with an ESG-vocabulary skin.
  • You: read one CSRD physical-risk disclosure and one TCFD report to extract required data shapes; write the "measured, not modeled — auditable by construction" positioning piece (genuinely differentiated; most competitors sell black-box model scores).
  • Effort: small on top of foundations; long sales cycles. Content-first: publish the positioning essay on the Lab, let inbound come.

5.4 Insurance Rate-Filing Support

  • Dexes: none new; county-aggregated event histories.
  • You: this sells through relationships — park until the Proof-of-Peril oracle (ag plan #3) creates insurer contacts. Effort: trivial data-wise, hard sales-wise.

PART 6 — Real Estate & Finance

6.1 CarFax for Parcels

  • Dexes: everything already planned (severe, flood, wildfire, lightning-2.3, freeze). Optional depth: FEMA disaster declarations dex (OpenFEMA API — vet: public domain, easy; also needed by the ag money-triggers, so it's already on your list).
  • Site: address-first landing page, teaser-then-pay flow (same as 2.1/2.2 — literally the same product with realtor copy).
  • You: copy; a distribution idea memo (home inspectors as channel — they hand the report to every buyer); GR-area inspector list.
  • Effort: trivial after 2.2. High volume potential.

6.2 Lender Due-Diligence Feeds

  • Dexes: none new; batch version of 6.1 (upload 10,000 addresses → portfolio exposure file).
  • Brad: batch pipeline. You: positioning doc ("measured history vs. modeled scores"); park sales until an inbound. Effort: small-medium.

6.3 Commercial Site-Selection Reports

  • Dexes: none new (seismicity, flood, hail, temp extremes, geomagnetic latitude — all live).
  • You: design the report ToC; price high ($500+); publish one free sample report for a famous site (a data-center corridor) as Lab content → inbound marketing. Effort: small; it's an F2 template.

6.4 Municipal/Infrastructure Risk

  • You: research whether MI county EM offices have budget lines for this; check state/federal grant programs (BRIC, hazard-mitigation planning funds — consultants who write those plans could be the actual customer). Effort: park; grant-shaped, slow.

PART 7 — Asset Monitoring (Private Dexes)

7.1 Bring-Your-Own-Assets Monitoring ⭐ the most scalable B2B product here

  • Dexes: none new — F6 + F1 + F3 + F2 in one product. Every peril layer you add anywhere makes this better automatically.
  • Site: portfolio dashboard: CSV upload → map of assets → per-asset event ledger → alert rules → monthly portfolio PDF.
  • You: per-vertical object schemas (retail, telecom, utility, marina — one page each); pricing model research (per-asset/mo comps: sensor-monitoring SaaS runs $1–5/asset/mo); pick ONE launch vertical (recommend telecom towers or retail chains — geographically dispersed, weather-exposed, insurance-motivated).
  • Effort: the foundations ARE the product. Sequence: immediately after the ag Field Dossier proves the engine.

7.2 Custom Source Onboarding as a Service

  • Site: a services page. You: write it; define a rate-card (setup fee + monthly hosting); this productizes what you two already do daily. Effort: near-zero. Ship the page now.

7.3 On-Prem / Self-Hosted

  • Brad: massive packaging work when real. You: nothing until an inbound with a budget appears. Effort: park hard.

PART 8 — Media, Content & Community

8.1 Lab Membership / Paid Newsletter

  • Site: membership gate on notebooks + early access; email list infrastructure (Buttondown/Ghost — you: pick one, research pricing).
  • You: editorial calendar (one investigation cadence promise members can rely on — e.g., 2/month); migration of existing readers to the list starting NOW (collect emails before monetizing — add the signup box this week regardless of everything else).
  • Effort: small tech, real ongoing editorial commitment. This is your lane entirely.

8.2 Sponsored Investigations

  • You: sponsorship one-pager (audience, format, disclosure rules — write the disclosure policy FIRST, it protects the credibility that makes this sellable); prospect list (weather-station makers, prep/outdoor brands). Site: clearly-labeled sponsor slot in the article template. Effort: trivial build; sales-gated.

8.3 Syndication & Data-Journalism Licensing

  • You: media kit; pitch the tornado-alley piece to MI TV meteorologists as the opener; standard licensing terms doc. Effort: pure outreach.

8.4 Commission-an-Investigation

  • Site: /lab/commission request form + published methodology/independence policy (you write it — you keep editorial control of conclusions, they choose the question; that policy is the product).
  • Effort: trivial. Ship the page early; even one commission/quarter is meaningful garage-stage revenue.

8.5 Annual Report / Posters

  • You: pick 3 charts (the 13,547-storms chart first); print-on-demand vendor research (Printful/Gelato); order proofs. Site: simple /shop (Stripe payment links work — no store build needed). Effort: a weekend.

8.6 Merch

  • Same vendor pipeline as 8.5; the mission patch as an actual embroidered patch. Effort: rides along with 8.5.

8.7 YouTube / Short-Form

  • You: one pilot video from an existing investigation (script is written — the article IS the script); assess effort honestly after one. Effort: ongoing time sink — pilot before committing.

8.8 "What Was the Universe Doing?" Novelty Reports

  • Dexes: none — cross-dex query by date/place (quakes, Kp, cosmic ray flux, nearest storm, moon phase from ephemeris computation).
  • Site: playful landing page + F2 with a beautiful template (design matters more here than anywhere else).
  • You: template design direction + copy; gift-season timing plan (build by October, market for the holidays).
  • Effort: small. Marketing value exceeds revenue — every report shared is an ad.

PART 9 — Research & Education

9.1 University/Classroom Licenses — You: package 3 existing datasets + notebooks as a "teaching pack"; email 5 earth-science departments (start MSU — you already plan MSU Enviroweather contact for ag; one relationship, two doors). Effort: small; slow.

9.2 Kaggle-Style Datasets — You: publish 2 free datasets on Kaggle with TerraPulse branding + link (pure funnel); premium ones live in 3.4. Effort: trivial.

9.3 Grants — You (worth real hours): NSF SBIR Phase I research (deadlines, topic fit — "commercializing public environmental data infrastructure" fits), NOAA/NASA commercialization programs, climate philanthropy scan. Non-dilutive money that funds everything else. Put 2 days into this.

9.4 Citizen-Science Pro Tools — Gate advanced Lab query/export features behind the 8.1 membership. No separate build. Effort: zero marginal.

PART 10 — Platform & Marketplace (all parked, minimal pre-work)

10.1 Sensor Contributor Network — You: one-page design doc only (ingest standards, what contributors get); revisit when the alert products have users who own stations.

10.2 Developer Rev-Share — Requires 3.1 traction first. Nothing now.

10.3 Data Escrow / Neutral Arbiter — Falls out of the ag plan's Proof-of-Peril oracle. You: just make sure the trigger-API design doc (ag plan already calls for it) uses neutral, two-party language so this reframe is free later.

PART 11 — Support-the-Mission (ship this month)

  • 11.1 Donations/Sponsors: GitHub Sponsors + a support page. You: set up accounts, write the page. A weekend.
  • 11.2 Affiliate: Amazon Associates + direct programs (weather stations, radiation detectors); add reviewed-gear links to relevant dex pages and investigations. You: sign up, write first two gear guides (SEO content that compounds).
  • 11.3 Adopt-a-Source: sponsor credit line on dex family pages + a Stripe payment link per tier. Effort: trivial, charming, do it.

Also in Part 11 because it blocks everything: ⚠️ Business formation. Before the first paid PDF: LLC (you + Brad, decide split), EIN, business bank account, Stripe on the entity, basic terms of service + privacy policy, and a liability disclaimer reviewed for the evidence products specifically ("data report, not professional advice/expert testimony"). You: research MI LLC filing (it's cheap and fast online); budget one real conversation with a small-business attorney about the claims-evidence disclaimer language — this is the one place I'd actually spend money on counsel.

PART 12 — Master Source-Vetting Queue (your licensing pipeline, prioritized)

Priority Source Unlocks Expected verdict
1 MSU Enviroweather Ag plan #2 (already committed) Vet terms; likely needs a partnership email — which is also your MSU relationship opener
2 NOAA MRMS (hail/MESH) 2.1 roofer product moat Public domain; storage-heavy — warn Brad
3 OpenFEMA (disaster declarations) Ag money-triggers + 6.1 Public domain, easy
4 NDBC buoys 2.7 + 4.5 Public domain, easy
5 GOES GLM (lightning) 2.3 + strengthens every dossier Public; resolution caveats to document
6 AirNow AQI 4.6 + OSHA-adjacent Public, attribution required
7 SWPC F10.7 solar flux 4.2 Public, trivial
8 USDA NASS QuickStats Ag benchmarking (already committed) Public
9 GLOS/GLERL (Great Lakes) 2.7 Great Lakes angle Vet — likely fine
10 SMAP + Sentinel-2 NDVI Ag plan (already committed) Green-list family
11 NREL NSRDB (irradiance) 2.9 Vet commercial terms — the one genuinely uncertain license
12 County parcel GIS (Kent/Ottawa/Allegan first) F1 for the local beachhead Varies by county — vet each; Regrid as paid fallback

PART 13 — Suggested Sequence (everything above, in time order)

Now / alongside the ag build (weeks 1–4):

  1. Business formation + Stripe (Part 11 ⚠️)
  2. F4 billing + F1 geometry engine (these are also ag-plan prerequisites — no conflict, same work)
  3. Email signup box on the site (8.1 prep); support/adopt-a-source pages (11.x); services page (7.2)
  4. Source vetting queue items 1–5

Next (months 2–3): F2 evidence PDFs (ag Field Dossier ships) → immediately re-skin for 2.1 roofers and 2.4 construction; F3 alert engine → ship 4.7 quake-watch as the test, then 4.1 aurora; 3.1 API tiers + your docs push; 3.4 first five datasets; 8.5 posters.

Then (months 4–6): 7.1 asset monitoring (the engine is now proven); 5.1 OSHA heat product; 6.1 CarFax-for-parcels; 8.1 membership launch on the email list you've been growing; 2.3 lightning dex; 9.3 grant applications.

Demand-gated (build only on real interest): 2.8 freight, 2.9 solar, 3.6 embeds, 5.2 archive, 6.2 lenders, 7.3 on-prem, all of Part 10.

The one-sentence version: foundations F1–F6 are the ag plan's prerequisites anyway; build them once, and every other vertical on this list is a landing page, a PDF template, an alert preset, and a licensing check — which means the fastest path to "as soon as possible" for fifty products is finishing the ag build exactly as planned, generically.

Live Feed