Add newsletter platform decision doc - #53
Open
erinstanley358 wants to merge 2 commits into
Open
Conversation
Captures the strategic question that surfaced today: stay on beehiiv (upgrade to Grow for automations + better editor) or build custom on infrastructure we already have (Resend + Neon Postgres + repo- based content). Doc lives at docs/decisions/newsletter-platform.md as an open decision the captain reads when fresh tomorrow. Not deciding for her - just laying out the trade-offs honestly so she can think clearly. Sections: - The question (open, not yet decided) - Where we are right now (working state + blocked items) - Option A: stay on beehiiv + upgrade to Grow ($30/mo) - Option B: build custom on Resend + Neon ($0/mo, 2-3 hours engineering) - Option C: hybrid (keep beehiiv, store subscribers in Neon as sovereignty backup; ~1 hour engineering) - Honest answer on "send from iCloud" (not viable for bulk; alternative: erin@evoked.dev via Resend) - Decision matrix: 5 questions whose answers tip the scale - What to do this week regardless of choice - Phased implementation plan if she picks Option B - "Decision recorded" section at the bottom for her to fill in Voice register: founder-public. Vuong + McEnerney discipline. Voice-tells audit clean: 0 em-dashes, 0 sycophancy markers, 0 AI slop, 0 weak hedges. ~1720 words. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Record the newsletter-platform decision and correct a false substrate claim: the doc listed beehiiv auto-sync as 'working', but the Posts API is Enterprise-plan gated (403 SEND_API_NOT_ENTERPRISE_PLAN) — it never worked on Launch/Grow. That finding removed Option A's headline benefit; four of five matrix questions tip custom. Build ~3 hrs, $0/mo, own the list. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Captures the strategic question that surfaced today: stay on beehiiv (upgrade for automations + better editor) or build custom on the infrastructure we already have (Resend + Neon Postgres + repo-based content).
Doc lives at
docs/decisions/newsletter-platform.mdas an open decision to read fresh tomorrow.What's in it
erin@evoked.devvia Resend)Voice
Founder-public register. Vuong + McEnerney discipline applied.
Voice-tells audit clean:
~1720 words / ~7 min read.
How to use it
Read tomorrow morning with coffee. Sit with the 5 decision-matrix questions. Pick a direction. Record the decision at the bottom of the doc. Open a follow-up PR/issue to implement whichever path you choose.
🤖 Generated with Claude Code