TerraPulse Monetization — Implementation Plan, Part 2

Companion to Brainstorm Part 2. Same format as the first plan: per idea — dexes/data needed, site expansions, your to-dos (sourcing, licensing, API research, content) vs. Brad's (backend). This plan assumes the Part 1 foundations (F1 geometry, F2 evidence PDFs, F3 alerts, F4 billing, F5 API, F6 private objects) exist or are in flight — Part 2 adds no new foundations, only two new capability extensions (X1, X2 below) and a handful of data sources. Where the Part 1 plan already covers the mechanics, this one just states the delta.

PART 0 — Two New Capability Extensions

X1. Accumulation & Interval Metrics

Part 1 products mostly ask "did an event touch this place?" Part 2's compliance and snow products ask "what accumulated / persisted over an interval?" — cumulative snowfall, freeze-thaw cycle counts, hours below a temp, dew-point spread during a window, GDD totals.

Brad: windowed aggregation functions over station time-series, per-location: sum, count-of-cycles, consecutive-hours-above/below, min/max within user-defined windows. One generic engine; every product below is a config.
You: write the metric definitions in plain English per product (what exactly is a "freeze-thaw cycle"? air temp crossing 32°F down then up within 24h? define it, cite a standard where one exists — ACI, ASHRAE, MSU Extension definitions — so the docs can say "computed per X standard").
Note: these are derivations of measurements, not models. Document each formula openly on a /methodology page — that page is both compliance armor and brand.

X2. Batch File Processing

Claims-triage, invoice auditing, and consultant data packs all take an uploaded file (policies, service addresses, county list) and return an annotated file.

Brad: CSV in → F1 queries per row → CSV/PDF out, async with email-when-done.
You: define the input templates (column specs) per product; write the "how to format your file" docs.

PART 1 — The Snow Economy

Shared data prerequisite for the whole cluster: NOHRSC National Snowfall Analysis + SNODAS (snow depth & snow-water-equivalent grids). NOAA, public domain.

You: vet NOHRSC/SNODAS (expect green-light; note grid resolution ~1km so per-address claims should say "measured analysis at your location," and pair with nearest-station observed snowfall for ground truth); also vet CoCoRaHS (volunteer precipitation/snow network — dense, beloved, check their data-use terms) as the station-level complement.
Brad: one gridded-ingest pipeline (also reusable later for MRMS hail from Part 1's plan — coordinate these two builds, they're the same shape).

1.1 Snow Removal Invoice Verification

Dexes: the snow ingest above; nothing else.
Site: /snow landing page; register service addresses (F6), per-event snowfall records with citations, season log, per-event evidence PDF (F2). Two skins, one product: "prove your work" (contractors) and "audit your invoices" (property managers).
You: join/scan ASCA and SIMA (snow-contractor associations — pricing norms, pain language, and the Part 2 brainstorm's group-licensing channel in one move); competitor check (there are a couple of snow-verification services — find their pricing); write both landing pages; list 20 GR-area snow contractors + 10 property management firms for pilot outreach before November — this product is seasonal, the sales window is Sep–Oct.
Effort above foundations: small. Sequence: this is the top new-build priority of Part 2 — Michigan-perfect, tight deadline, proven willingness-to-pay.

1.2 Municipal Slip-and-Fall Defense Logs

Dexes: snow ingest + existing temp/precip. X1 freeze-thaw metrics.
Site: standing-subscription version of the Part 1 forensic report: registered locations auto-accrete daily condition logs; incident lookup by timestamp.
You: the buyer is risk managers — research MML (Michigan Municipal League) and the municipal-insurance pools (they insure many cities at once — ONE sale covers dozens of members; find Michigan's pool and its risk-services contact); adapt the forensic methodology doc.
Effort: small. Sales cycle slower than 1.1 — start the conversation, don't gate the season on it.

1.3 Roof Snow-Load Watch

Dexes: SNODAS SWE (that's the load-relevant number, not snowfall depth).
Site: register buildings (F6) + threshold alerts (F3) + season log.
You: research design snow loads (ASCE 7 ground snow-load values by county — public) so default thresholds are defensible; write alert copy that says "caution threshold" not "your roof will collapse" (liability tone matters — flag for the attorney conversation already scheduled in Part 1's plan); target list: warehouse/facility managers, school facilities directors, ag co-ops with flat-roof storage.
Effort: small. Bundle with 1.1 as "Winter Ops."

1.4 DOT / Anti-Icing Verification

Dexes: existing weather; F1 route queries (already needed by Part 1's freight idea — shared build).
You: validate first — one conversation with a county road commission (Kent County Road Commission is local) about how treatment callouts are verified today. Park the build until that conversation says yes.
Effort: small if validated; demand-gated.

1.5 Ski Resort Ops

Dexes: existing temp/humidity → X1 wet-bulb computation.
Site: alert preset + season report template.
You: Michigan has ~40 ski areas — get the MSIA (Midwest ski areas association) list; one pilot resort (Cannonsburg is 20 minutes away) in exchange for a case study.
Effort: trivial on foundations. Charm-and-press play as much as revenue.

1.6 School & Business Closure Documentation

Dexes/site: none new — it's a daily F2 report preset on existing data.
You: copy + a one-page pitch to 3 local superintendents. Effort: trivial; do it opportunistically alongside 1.2's municipal outreach.

PART 2 — Site-Condition Compliance Logs

Cluster note: 2.1–2.4 share one product chassis — "Jobsite Compliance": register a site (F6), pick active spec modules (concrete / crane / coating / roofing / heat from Part 1's OSHA product / weather-days from Part 1), get continuous logs + threshold alerts + monthly PDF. Build the chassis once; each spec module is config + copy. Sell as one bundle, one price, one buyer (the GC or specialty contractor).

2.1 Concrete Pour Logs

Dexes: existing temp; X1 interval metrics (curing-window tracking).
You (the real work): get the ACI 306 (cold weather) and ACI 305 (hot weather) requirements — the standards themselves are paywalled (~$100 total; buy them, it's product spec); extract the documentation requirements into the module definition; write copy in contractor language ("protect your pour, protect your pay app").
Effort: small. First module on the chassis — most universal need.

2.2 Crane Wind Logs

Dexes: existing wind obs. Honest-limitation note for the methodology page: station wind ≠ wind at hook height; position as "documented area conditions," not anemometer replacement. You: read OSHA 1926.1431 wind provisions + a couple of manufacturer load-chart wind limits to set default thresholds; write the limitation language yourself (your credibility instinct is the asset here).
Effort: trivial as module #2.

2.3 Coating & Paint Application Windows

Dexes: confirm dew point/humidity are first-class metrics in the weather dex (flagged in the brainstorm; likely trivial — Open-Meteo/NOAA carry them). X1 computes the temp-minus-dew-point spread.
You: SSPC/AMPP application standards research (same pattern as ACI); niche outreach later — industrial painting contractors, bridge maintenance.
Effort: trivial as module #3; park marketing until chassis has customers.

2.4 Roofing Installation Temperature Compliance

Dexes/site: none new — module #4. You: shingle manufacturer spec sheets (free, public) for default thresholds; copy. Cross-sell to every 2.1-Part-1 roofer customer. Effort: trivial.

2.5 Frozen Pipe Fault-Finder

Dexes: none — hourly temp history exists. Site: per-report checkout on the existing forensic/verify flow; add an "hours below 20°F" X1 summary to the report. You: copy + a "frozen pipe claims" SEO article (seasonal search spike every January — publish by December). Effort: trivial.

2.6 Fleet & Dealership Hail Logs

Dexes: rides on MRMS hail (already queue item #2 in the Part 1 plan). Site: F6 lot registration + F3 alerts + post-event F2 package. You: list of GR-area dealer groups; one-page pitch. Effort: trivial after the roofer product ships — same event data, third buyer.

PART 3 — Insurance, Other Side of the Table

3.1 Anti-Fraud Verification for Insurers

Dexes/site: none new — the Part 1 verify engine with a "negative finding" report template (F2): certifying absence needs different language ("no measured hail within X km during Y window; sources checked: …; coverage limitations: …").
You: the negative-report template is a careful writing task — do it yourself; it must state coverage honestly (station density, radar gaps) or it's worthless in a dispute. Then: this sells via the insurer relationships the ag Proof-of-Peril oracle creates — sequence the outreach behind that, not before.
Effort: small build, relationship-gated sales.

3.2 Claims-Triage Feed

Dexes: none. Build: X2 batch processing + event-swath polygons (SPC/NWS polygons already ingested; MRMS adds radar swaths).
You: none until an insurer conversation exists (same channel as 3.1). Design input-file template now (10 minutes) so the demo is ready when the meeting happens.
Effort: small; demand-gated.

3.3 Crop Insurance Agent Dashboards

Dexes: none — multi-client wrapper over the ag Field Dossier (F6 with an agency→clients hierarchy; Brad: one permissions layer).
You (high leverage): this is a distribution weapon disguised as a product. Find the crop-insurance agencies serving the Fruit Ridge (a handful of firms write most of it); pitch the dashboard free-for-season-one in exchange for them putting the Field Dossier in front of every client. Do this during the ag sales motion, not after — same meetings.
Effort: small-medium (permissions layer). Priority: high — it multiplies the ag plan.

3.4 Weather Derivatives Settlement Data

You: research task only for now — how CME weather contracts settle today (settlement agent, station list, data terms) and whether OTC desks use third parties. One afternoon; write a memo; park.
Effort: research-only.

3.5 Event-Driven Trading Timestamps

Dexes: none — it's a latency-optimized F5 feed with revision tracking ("USGS magnitude revised 6.8→7.1 at T+43min" is itself the product).
Brad: revision-history capture per event (may partly exist via lineage), low-latency push.
You: park sales; this buyer finds you via the API tier — just make sure the API docs mention revision streams so the right person recognizes it.
Effort: small-medium; build the revision capture (it improves everything), defer the productization.

3.6 Port & Supply-Chain Disruption Feed

New sources for you to vet: USACE Great Lakes water levels + Soo Locks status (public), USCG marine safety broadcasts (check reusability), NOAA CO-OPS (have).
Site: a "Great Lakes shipping" dex page — doubles as Lab content ("we watched every Soo Locks closure this season").
You: vet the two sources; write the dex page; park B2B sales until it has a season of data.
Effort: medium (new ingests); the content value alone may justify it.

PART 4 — Small-Business Verticals

Cluster mechanics: every one of these is an F3 alert preset + X1 metric + landing page. Brad's build for ALL of Part 4 combined is roughly one week once F3/X1 exist. The real cost is your copy + community outreach per niche. So: ship the presets in batches, market only 2–3 at a time, and let the rest sit as landing pages catching SEO.

Per-idea deltas only:

Product	Data delta	X1 metric	Your key task	Ship batch
4.1 Maple syrup freeze-thaw	None	Freeze-thaw cycle count	MI Maple Syrup Assoc. outreach; pitch the story to MI press in Feb (season)	A — press play
4.2 Greenhouse/nursery frost	None (ag build)	Hours-below threshold	MNLA (nursery/landscape assoc.) contact; copy	A
4.3 U-pick/agritourism	None (ag build)	Weekend condition summaries	Copy; sell alongside ag motion — same rooms	A
4.4 Apiary alerts	None	GDD + drought status	Beekeeper club circuit (they meet monthly, love talks — offer one)	B
4.5 Aquaculture/hatchery	Confirm water-temp/DO coverage on relevant streams	Threshold alerts	Check USGS water-quality param coverage at MI hatchery sites first	B
4.6 Golf/turf	None	Frost delay + GDD disease windows	GCSAA-Michigan chapter; supers are online — content marketing works	B
4.7 Outdoor venue ops	Lightning (GLM — Part 1 queue #5)	Proximity + wind alerts	Copy; venue list; needs GLM live first	C — after GLM
4.8 Pool/marina winterization	None	First-freeze + water temp	Copy; service-company list	C

PART 5 — Data-Infrastructure Products

5.1 GovData Status Page ⭐ ship early — it's marketing that charges rent

Dexes: none — instrument the fetchers you already run (source up/down, latency, last-success, payload anomalies).
Site: public /govdata-status dashboard (free) + paid F3 alerts and history API.
Brad: expose existing internal health checks publicly; a status-history store.
You: launch content — "We monitor 370 government data feeds; here's what breaks and how often" is a Lab investigation, a Hacker News post, and a product launch in one artifact. Write it. Also: neutral-tone policy for outage reporting (you're reporting on agencies you depend on — factual, never snarky).
Effort: small. Sequence: alongside the earliest Part 1 work — nothing else on either list markets the brand this cheaply.

5.2 Dataset Change-Detection Alerts

Rides on 5.1's instrumentation + lineage diffing (Brad: revision/schema diff alerts — overlaps 3.5's revision capture; one build serves both).
You: docs + a "silent revisions we've caught" article series (each catch is content).
Effort: small after 5.1.

5.3 Provenance Engine Licensing

You: write the one-pager now (what the engine is, what a license would include), then park. No build. Its purpose is recognizing serious inbound.

5.4 "TerraPulse Verified" Certification

You: register the phrase/badge concept (trademark search — add to the attorney conversation agenda); draft criteria in a doc; park.

5.5 AI / LLM Data Licensing

Dexes: none. Brad: bulk corpus export (extends Part 1's 3.4 dataset pipeline).
You: research task — who's buying (AI labs' data-partnership programs), what terms protect upstream source licenses (KEY: verify each source's terms permit sublicensing into training corpora — Copernicus and some networks have specific redistribution language; this is squarely your vetting lane and it gates everything here).
Effort: small build, real licensing homework, potentially large checks. Worth your research hours this quarter.

5.6 TerraPulse MCP Server

Brad: thin MCP wrapper over the existing REST API (small, well-documented protocol; days not weeks).
You: docs page + a "query the planet from your AI agent" launch post; include in API tiers (metered).
Effort: small. Ship with the API productization — it's a differentiator in the docs.

5.7 Data-Broker / Reseller Layer

You: no build — this is a policy decision (does TerraPulse resell commercial feeds?). Write a pro/con memo with Brad; the lightning question (NLDN vs. GLM, Part 1 plan 2.3) is the first live test case. Decide there, generalize later.

PART 6 — Consumer & Engagement

6.1 Outdoor Date Picker

Dexes: none — F1 point queries over historical station records + X1 summaries.
Site: dedicated landing page: place + candidate dates → "the last 40 Septembers, weekend by weekend" report (F2, designed beautifully — this one's shared on wedding Pinterest or it doesn't work).
You: design direction + copy; wedding-planner affiliate/partnership scan; seasonal SEO articles ("best measured-weather weekends in northern Michigan" etc. — this compounds).
Effort: small. Bundle-launch with Part 1's novelty report — same audience, same gift flow, same October build deadline.

6.2 Trip Climate Reality-Check

Same engine as 6.1, travel skin + affiliate links. You: copy; affiliate signups (already in Part 1's 11.2 task). Effort: trivial after 6.1.

6.3 Daily Data Game

Dexes: none — yesterday's events, gamified.
Brad: game frontend, daily generation job, share-card renderer, streak state. The only real new frontend build in Part 6 — scope it to ONE game mode first (suggest: "place yesterday's biggest quake on the map," GeoGuessr-style).
You: game design doc (modes, scoring, share-card copy); name it; launch plan (HN/Reddit); sponsorship one-pager for later.
Effort: medium — and it's an engagement bet, not revenue. Worth it IF traffic is a current bottleneck; sequence after the money products, before the membership push (it feeds the email list).

6.4 Prediction League

Brad: prediction capture + scoring against measured outcomes; leaderboards.
You: rules design (crucially: free entry, sponsor prizes — document the no-gambling reasoning); community seeding plan.
Effort: medium. Park behind 6.3 — the game validates whether the audience wants to play at all.

6.5 Home Dashboard License

Brad: a full-screen "display mode" route + license key check. You: copy; Tidbyt/TRMNL app-store research (their marketplaces distribute for free). Effort: small.

6.6 ICS Calendar Feeds

Brad: ICS endpoints from ephemeris + event data. You: decide free/paid split (basic feeds free with branding = every subscriber's calendar advertises you). Effort: trivial. Quick win — ship anytime.

6.7 Personal Station Vanity Pages

Requires the PWS ingest path from Part 1's contributor network (10.1) — park together; when 10.1 wakes, this is its billing model. You: nothing now.

6.8 Junior Scientist / Homeschool Kits

You: this is a content product you can build solo — 4-week pilot unit ("Track the Planet") from existing dex pages + printable PDFs (F2 templates); price $10–15/unit; homeschool co-op and curriculum-fair distribution research. Brad: nothing.
Effort: your weekends, zero backend. Genuine fit for your background (journalist-researcher writing curriculum).

6.9 Gift Cards

Brad: Stripe gift-card/promo flow (near-native in Stripe). You: nothing. Effort: trivial; ship with 6.1's October launch.

PART 7 — Institutional & Civic

7.1 County EM After-Action Packages

Dexes: none — county-scoped F1 sweep + F2 package ("everything measured in County X, dates Y–Z").
You: intro meetings with Kent/Ottawa County EM offices (they're nearby and approachable; bring a sample package for a recent real event — make one first); learn their after-action format so the PDF mirrors it.
Effort: small build; relationship sales. The sample package doubles as Lab content.

7.2 Hazard-Mitigation Consultant Data Packs

Build: X2 batch + F2, formatted per FEMA guidance. You: read FEMA's Local Mitigation Planning Policy Guide data requirements (free, public — one evening); find the 5–10 consultancies writing Michigan county plans; one cold email each with a sample. Effort: small; niche but the buyer genuinely needs exactly this.

7.3 Public-Health Research Feeds

Build: none — academic-tier pricing flag on F5. You: pair with the Part 1 grant research (9.3); a health-department pilot makes grant applications stronger. Effort: pricing-page work only.

7.4 Tourism Board Verified-Climate Data

Build: none — F2 report + badge license. You: park until the certification concept (5.4) and brand equity mature; note Pure Michigan as the someday-whale. Effort: zero now.

7.5 Museum & Science-Center Installations

Brad: kiosk display mode (shares 6.5's build — same route, bigger screen). You: pitch deck + Grand Rapids Public Museum approach (they do local-tech exhibits; propose a pilot wall). Effort: small on top of 6.5; prestige play.

7.6 Digital Signage Feeds

Same display mode + F5 licensing. You: signage-network research (Screenly-type platforms have app stores) — an afternoon. Effort: trivial after 6.5/7.5.

PART 8 — Go-to-Market Mechanics

8.1 Association Group Licensing — Brad: group-billing support in F4 (one org pays, N members entitled). You (this is the big one): build the association target list NOW as a living doc — Farm Bureau (ag), ASCA/SIMA (snow), GCSAA-MI (turf), MNLA (nursery), MI Maple Syrup Assoc., beekeeper clubs, MML + municipal pools — with contact, meeting calendar, and which product each maps to. Every Part 4 niche converts from retail grind to one B2B conversation through this list. Treat it as a standing sales asset you maintain like a source-vetting queue.
8.2 Launch Lifetime Deals — Brad: a Stripe price flag. You: decide policy up front (consumer products only, capped count, never API/B2B — write it down so future-you resists the temptation) and reserve it for ONE launch moment (suggest: the 6.1/novelty-report October consumer launch).
8.3 Referral Program — Brad: referral codes in F4 (Stripe-adjacent tooling exists — Rewardful-class; you: pick one, pricing research). You: recruit from people met in Part 1 outreach (inspectors, adjusters, agents). Effort: small; wait until there's revenue to share.
8.4 Seasonal Bundles — Brad: bundle SKUs in F4. You: define the three bundles (Winter Ops / Spring Risk / Jobsite) and their pages; align launch to seasons (Winter Ops live by Oct 1, Spring Risk by Feb 1, Jobsite by construction season Apr 1). This is packaging, not product — but it's where Part 4's long tail becomes ARPU.
8.5 Free-Tool SEO Farm — Brad: one reusable "free lookup" widget (address in → teaser result out) reskinnable per vertical. You: the compounding content program — one free tool + one pillar article per launched vertical, on a calendar you own. This is the growth engine and it is 90% your lane; budget standing weekly hours for it rather than treating it as launch-day chores.

PART 9 — Additions to the Master Queues

Source-vetting queue (extends Part 1's Part 12; new items):

Priority	Source	Unlocks	Expected verdict
13	NOHRSC snowfall analysis + SNODAS	Entire Snow Economy (1.1–1.6)	Public domain; gridded — coordinate with MRMS ingest build
14	CoCoRaHS	Station-truth snow/precip for 1.1	Vet volunteer-network terms
15	USACE Great Lakes levels + Soo Locks	3.6 + Lab content	Public; easy
16	Dew point/humidity as first-class metrics	2.3 coatings, wet-bulb (1.5, Part 1's 5.1)	Likely already ingested — confirm, don't build
17	ACI 306/305, SSPC standards (purchase, not ingest)	2.1–2.3 module specs	~$150 total; product spec, not data
18	ASCE 7 snow-load reference values	1.3 defaults	Public summaries exist; verify licensing if reproducing tables

Attorney-conversation agenda (extends Part 1's Part 11 item): evidence-report disclaimer (already listed) + negative-finding/anti-fraud report language (3.1) + roof-load alert liability tone (1.3) + trademark search for "TerraPulse Verified" (5.4). One meeting, four agenda items.

PART 10 — Merged Sequence (Part 2 slotted into Part 1's timeline)

Now / weeks 1–4 (unchanged from Part 1, plus):

Add queue items 13–16 to your vetting pipeline (NOHRSC is the urgent one — snow season gates it)
Start the association target list (8.1) — it's a doc, costs nothing, pays everywhere
Brad: fold X1 (accumulation metrics) into the F1 build spec now — cheaper designed-in than bolted on

Months 2–3 (alongside Part 1's evidence-PDF + alerts phase):

GovData status page (5.1) — launch with the "370 feeds" article; earliest, cheapest brand win on either list
Snow Removal Verification (1.1) — build in Sep, sell Sep–Oct, live by first snowfall; Winter Ops bundle (with 1.3) by Oct 1
Jobsite Compliance chassis + concrete module (2.1) — merges with Part 1's construction weather-days build
MCP server (5.6) + ICS feeds (6.6) ship with the API productization
October consumer launch: date picker (6.1) + novelty report + gift cards (6.9) + the one lifetime deal (8.2)

Months 4–6 (alongside Part 1's asset-monitoring/OSHA phase):

Crop-insurance agent dashboards (3.3) — during the ag sales motion, same rooms
Remaining jobsite modules (2.2–2.4) + fleet hail (2.6) — config passes
Part 4 batch A niches (maple/greenhouse/u-pick) — Feb press window for maple
Change-detection alerts (5.2) + revision capture (3.5 infrastructure)
County EM sample package (7.1) + FEMA consultant packs (7.2)
AI-licensing homework (5.5) — your research hours, no build

Demand-gated / parked: 1.4 DOT (one validation call first), 3.1–3.2 (behind insurer relationships), 3.4 (memo only), 4.7–4.8 (behind GLM), 5.3–5.4 (docs only), 6.3–6.4 game (after money products; before membership push), 6.7 (with contributor network), 7.4–7.6 (behind display mode + brand), 8.3 (behind revenue).

One-sentence version: Part 2 adds two small capability extensions, one urgent seasonal deadline (snow, by first snowfall), one free brand cannon (the GovData status page), and one sales weapon (the association list + agent dashboards) — everything else is configuration on the machine Part 1 already told you to build.