System 1: Offline-marketing CRM (the spine)

Everything else writes to this. It's the "track what works" line in the plan, made real. House pattern: a Cloudflare D1 database plus a password-gated hub page at annettethompson.com/rebuilding/, backed by Pages Functions, the same stack as the quote library. D1 name follows convention: rebuilding-offline-db (or reuse the existing rebuilding D1 if there is one).

Core tables:

• contacts: id, type (attorney / mediator / therapist / CDFA / reporter / editor / podcast_host / radio_producer / venue / church / group_organizer / retail_spot), name, org, specialty, address, city, phone, email, source_url, verified_date, notes.
• outreach: id, contact_id, channel, drafted_date, approved_by_bob (bool), sent_date, sent_by, method (in-person / email / mail / phone), follow_up_date, status (drafted / approved / sent / responded / declined / dormant), notes.
• referrals: id, contact_id, referred_prospect_initials, referral_date, became_consult (bool), became_enrollment (bool), cohort. This is the attribution engine: which attorney/office/talk/article actually produced consults and enrollments, so Bob can double down on the top two or three sources and quietly drop the rest.
• listings: id, event_name, event_date, surface (Patch / library / city / Nextdoor / county / small_paper), listing_url, posted_date, posted_by, status.
• collateral: id, asset_type (rack_card / flyer / postcard / sign_in / one_pager), version, generated_date, stats_snapshot, pdf_path, print_status, locations_distributed.
• queries: id, platform (SOS / HARO / SourceBottle), received_date, journalist, outlet, topic, matched (bool), draft_answer, approved (bool), sent_date, published_url.

Hub page: a simple dashboard behind the existing gated-page password showing the referral leaderboard (who's sending students), the open pitch/follow-up queue, upcoming award and PR-season reminders, and a collateral-freshness indicator. Raw contact data and the alumni list stay out of anything public; the gated page is for Bob and Annette only.

Build effort: Medium (a day of schema + Functions + one gated page). Payoff: high and permanent. Build this first; it's the thing every other system reports into.

System 2: Media + referral contact database

Populates contacts. Two feeds:

• Referral professionals: a script that pulls public directory listings (Colorado Bar family-law members, Psychology Today Boulder/Denver therapist profiles, mediation.com, CDFA/IDFA directories, Google Places for "divorce attorney" / "family mediator" / "therapist" in Boulder, Niwot, Cherry Creek). Dedupe, geocode, drop anyone who runs their own competing divorce group. Output: a clean 30-to-100-name list ready for Bob to prioritize by who he already knows.
• Media contacts: here the rule from the plan is load-bearing. Never invent an editor's name. The script pulls live current bylines from recent stories in the target beats (health, lifestyle, family, community) at each outlet, plus the known standing submission addresses already verified in the plan ([email protected], [email protected], [email protected], [email protected], the Camera guest-opinion form at prairiemountain.forms-db.com, KGNU's contact page). Re-verify bylines before each pitch wave, since reporters move.

Freshness: a quarterly Task Scheduler job re-checks bylines and flags stale contacts. Directories get re-pulled before each cohort's push.

Build effort: Medium. Payoff: high (feeds channels 1, 3, 7, 8).

System 3: Source-request monitor with Bob-voice draft answers (crown jewel)

This is the highest automation-leverage system in the plan, because the whole channel is email and the drafting is exactly what Charlie's good at.

How it works:

1. Register Bob as a source on Source of Sources (free, best volume), HARO/Featured free tier, and SourceBottle. Route all digests to a dedicated Gmail label (or a filtered folder) using the Gmail integration.
2. A scheduled job (Task Scheduler, 2 to 3 times daily to match SOS's digest cadence) reads new digest emails, splits them into individual queries, and filters to Bob's lanes: divorce, gray divorce, co-parenting, midlife/starting-over, therapy-meets-tech, empty nest, and the human-interest "left Google to become a therapist" angle.
3. For each match, Charlie drafts a tight, on-topic, Bob-voice answer with the correct stat (gray divorce roughly doubled since the 1990s and about 36% of divorces per Bowling Green research; the January-decide/March-file nuance; 3,000+ alumni since 1993) and the credential line, plus the deadline and outlet.
4. Drafts land in the queries table and surface on the hub dashboard (and optionally as Gmail drafts). Bob reviews, approves, and it sends from Bob's address, human-paced.

Honesty on limits: the strict one-strike spam rules (especially SOS) mean the filter has to be conservative. Only genuinely relevant queries get surfaced, never a spray. That's a feature, not a constraint. Qwoted's better queries sit behind a $99/mo wall and a 3-pitch free cap, so hold it in reserve until Bob wants national placements.

Build effort: Medium (Gmail filter + parser + draft step). Payoff: high and compounding. Every landed quote is a permanent credibility asset and the per-query cost is near zero once it runs.

System 4: Community-calendar + free-listing engine

A reusable listing template (event name, date/time, venue, one-paragraph description, funnel link, contact) stored once, filled per event. Two execution paths by platform terms:

• Form-based, browser-automatable (Patch, Boulder Public Library, city of Boulder, Boulder County, Denver neighborhood calendars, small-paper calendar forms): Charlie fills and submits via Annette's logged-in browser, human-paced, from the template.
• Terms-restricted (Nextdoor): Charlie prepares the exact post; a human clicks. No scripting the consumer product.

Trigger: a scheduled "every cohort, every talk" job. When a cohort start date or a booked talk gets added to the CRM, the engine generates the full listing set and queues it across every surface, logging each to the listings table. This is the workhorse that makes sure no talk ever goes unlisted.

Build effort: Low-medium. Payoff: medium-high, recurring.

System 5: Press-outreach + follow-up tracker

Ties System 2 (contacts) to the drafting and the calendar. For each pitch wave:

1. Pull the target outlets and live bylines.
2. Mail-merge personalized pitches off the verified hooks (gray divorce, holidays-and-divorce, January season, the 30-year milestone, the ex-Google angle), one tailored to each reporter's recent work.
3. Log each to outreach with a follow_up_date.
4. A daily Task Scheduler job surfaces due follow-ups on the hub dashboard so Bob's second and third touches actually happen. Most PR wins come from the follow-up nobody remembers to send.

Sending stays gated on Bob and runs human-paced from Annette's email. Charlie never blasts.

Build effort: Medium. Payoff: high.

System 6: Printable-collateral generator (Typst)

One Typst template family in Bob's real brand (terracotta/sage/gold/plum, Montserrat headlines, the real logo) that takes current stats as inputs and outputs print-ready PDFs, so collateral is never stale. Follow the house Typst pattern (a local package, @local/rebuilding:1.0.0 style, since Typst rejects C: paths in #import), 0.75in margins, writing rules honored (no em-dashes, contractions).

A single stats.toml holds the live numbers (4.96 stars, 293 reviews, 3,000+ alumni, since 1993, price $1,200 / $1,099 early-bird through Fri July 24 2026, fall cohort Sun Sept 20 2026, the four funnel destinations). Change the numbers in one place, rebuild every asset in one command. Outputs:

• 4x9 rack card (channel 5): emotional hook + stats on the front, three program facts + free 15-min consult + phone + QR to the self-assessment on the back.
• Flyer / small poster (channel 9): bulletin-board version.
• Referral one-pager (channel 1): the clean single page a professional keeps on file.
• Sign-in sheet (channel 2): captures emails at talks, offers the self-assessment.
• Postcards (channel 11): alumni-referral and EDDM versions.

Before any print run, screenshot the render and eyeball it (fonts, overflow, QR scans). Nothing goes to print unverified, and the print order itself is money-gated.

Build effort: Low-medium (templates are the work, then near-free forever). Payoff: high.

System 7: Seasonal PR calendar automation (Task Scheduler)

The plan's timely hooks turned into scheduled reminders with pre-drafted pitch shells, so a hook never gets missed because everyone was busy. Each fires a hub-dashboard reminder plus a drafted pitch ready for Bob to approve:

Phase 1 (build first, week 1): the spine + the crown jewel

• System 1 (CRM: D1 + gated hub dashboard). Everything reports into it.
• System 3 (source-request monitor). Highest automation leverage, and it starts producing "as seen in" assets in the background from day one. Register Bob on SOS + HARO free + SourceBottle, wire the Gmail filter and parser.

Phase 2 (week 2): the collateral and the contact base

• System 6 (Typst collateral generator). Unblocks channels 1, 5, 9, 11 at once, and gives Bob something tangible to react to.
• System 2 (contact database). Feeds the referral push and the press push.

Phase 3 (week 3): the outreach engines

• System 5 (press-outreach + follow-up tracker). Turns the contact base into pitches with follow-ups that actually happen.
• System 4 (calendar/listing engine). Make sure the first booked talk gets listed everywhere.

Phase 4 (ongoing): put it on rails

• System 7 (seasonal Task Scheduler jobs). Once the drafting and tracking exist, this is just scheduling. It's what makes the whole thing run without babysitting.