Outreach metrics — TheFittClub
Convention: add one row per completed piece. The generator counts non-placeholder rows per section. Do not delete rows (history matters); to retire a piece, mark its row with [retired YYYY-MM-DD] in the notes column.
Production model — one topic, four outputs
Critical context (2026-05-13): Instagram has been the single source of every paying customer to date. It is the primary acquisition channel, not a complement. The production model is therefore one topic → quadrant of coordinated outputs:
| Channel | Output per topic | Cadence |
|---|---|---|
| ≥1 post (carrusel / reel) + stories ronda | every topic — primary channel | |
| Blog | 1 article (1500-2500 words) at /blog | every topic |
| Newsletter | 1 email (600-900 words, links to blog) | every topic |
| YouTube | 1 video (5-15 min, uses pro setup: cámaras / micros / luces ya disponibles) | every topic once YouTube cadence arranca |
The four outputs share the same topic anchor, voice, and editorial guardrails. They reinforce each other and amortize the research/scripting cost across four channels. Tracker covers all four below.
Instagram posts published
The vital channel — 100% of historical conversions came from here. Reactivation is non-negotiable.
| # | Date | Pillar | Format (reel / carrusel / single / story-set) | Topic | Saves | Notes |
|---|---|---|---|---|---|---|
| (none yet — first row when IG reactivation starts; see T62 cross-channel workflow) |
YouTube videos published
Long-form companion to each topic. Pro setup ya está (cámaras, micros, luces). Arranca cuando la cadencia editorial estabilice (post-T62 activación).
| # | Date | Pillar | Topic | Duration | Views | Notes |
|---|---|---|---|---|---|---|
| (none yet — placeholder; first video targets one topic also covered by IG + blog + newsletter the same week) |
Newsletter emissions
| # | Date | Pillar | Title | Open rate | Click rate | Notes |
|---|---|---|---|---|---|---|
(none yet — first emission targets H4 in mvp-scope.md → Outreach pillars; depends on T62) |
Blog articles published
| # | Date | Pillar | Slug | Word count | Notes |
|---|---|---|---|---|---|
| (none yet — first article ships under T53; one article per pillar in the first month) |
Lead magnet downloads
Aggregated per week (cohort signal — not per-user). Captured from Resend webhooks or analytics dashboard (T55).
| Week starting | Downloads | Pillar (if magnet themed) | Notes |
|---|---|---|---|
| (none yet — first row when T61 lead magnet goes live on T36 landing) |
Beta sessions completed
Survey + interview interactions during the closed beta (T63). One row per interaction, not per tester.
| # | Date | Tester ID | Type (survey/interview/incident) | NPS | Notes |
|---|---|---|---|---|---|
| (none yet — first row when T63 beta program activates) |
How the generator counts
The dashboard generator parses this file and counts the non-placeholder rows in each section’s table. Rows that start with | _(none yet or with the header row pattern are skipped. To add a tracked entry, replace or insert above the placeholder line with a real row in the table’s format.
How to update this file
- After publishing a newsletter / blog article / running a beta session, append a row to the matching section.
- Use the exact column structure shown — the parser is strict about column counts.
- Push to main. The vault dashboard updates automatically on next sync (via
.github/workflows/sync-vault-dashboard.yml). - Periodically (monthly suggested) review the cumulative counts and the resulting cadence — if you’re below target on a pillar, that’s a calibration signal to adjust the newsletter schedule or topic mix.