Decision
Build of a dedicated creator campaign dashboard is on hold. No build until an actual campaign arrives to justify the cost.
Context
Ben Ornstein submitted two audio memos and a detailed Notion SOP outlining the three most time-consuming parts of running creator campaigns: (1) finding and filtering the creator universe, (2) sending templated outreach emails with per-creator customizations, and (3) recording proof of engagement and passing it to Rafael or Hermes for backend input. Additional requests included: creator self-service login to update prices and multi-account listings, automated live-link delivery to creators once a post goes live, auto-application of the 40% upcharge for sponsored posts, automated engagement reminders after one hour if creators have not acted, and outreach to new creators outside the existing network.
Michael reviewed Ben’s memos and a design doc (https://docs.google.com/document/d/1wkGSzrEBHbfHN20f5UJHO09xV2gGpxrA7Hlicqt3Nck/edit). Ben also shared a campaign performance tracker (https://docs.google.com/spreadsheets/d/1lGqzIyP5SdsTc-7WNMTTdRYzUzobJ6R-PrTm65Lq1RU/).
Hermes estimated the build at $1.5-3k. Michael decided the investment does not make sense without a confirmed campaign on the books.
Options considered
- Build now (proactive): rejected due to cost vs. uncertain near-term volume.
- Build on next campaign: selected.
Consequences
- No engineering work starts until a paying creator campaign is confirmed.
- Ben continues manual process per existing SOP in the meantime.
- Notion SOP (https://app.notion.com/p/ryevalley/Megaphone-Creator-Campaign-SOP-3e58ab5fb6c780138f8dd9a3a0c04519) and Ben’s audio memos are the reference materials when the build does get kicked off.
- When a campaign lands: re-scope against Ben’s full list and decide which modules to build first.
Source
Megaphone thread, 2026-10-15. Permalink: https://ryevalley.slack.com/archives/C06UJ3V2HEV/p1792068922477929