I run 7 Notion databases to track every EFER product launch. Here is the schema.
The 7 databases
- Articles — title, slug, category, target keyword, status (draft/published)
- Products — lore book, EFURC, T-shirts, bundle. Price, Gumroad URL, launch date.
- Lore book chapters — chapter number, faction, thesis, status (outline/draft/polished)
- EFURC cards — name, cost, faction, effect, lore hook, status (concepted/arted/coded/playtested)
- T-shirt drops — faction, design, TeePublic URL, launch date, sales (post-launch)
- Press releases — title, embargo date, outlets targeted, status (drafted/sent)
- Email sends — subject, list segment, send date, open rate (post-send)
Why 7 databases
Each database represents one product line. The cross-database views (Notion relations) let me see everything in one place. When I am planning a launch, I can see: which articles are scheduled, which lore book chapter is in draft, which EFURC card is being playtested, which T-shirt drops next Friday.
What this means for your launches
If you are running multiple products (which you should — see 7 routes to monetize), build a Notion schema. The schema is what makes multi-product launches possible.
See what is shipping right now.
