scope: client-account - Rye Valley delivery decision about how we build Adam Gillman’s app email infrastructure.
- Date: 2026-10-07
- Decider(s): Michael Houck
- Status: decided
Decision
Use Beehiiv exclusively for all of Adam Gillman’s email needs - both newsletter and transactional automations (Capture, Qualified, Downsell, Direct, Preselling sequences). Resend is not being added. The goal is one tool to manage, not two.
Context
Rafael (contractor on the Adam G build) asked Hermes to create a Resend email service adapter and upload templates. Hermes raised the question of whether Beehiiv could handle transactional-style automations instead. Michael engaged: asked whether we lose anything with Beehiiv, noted that the Hard Calls personal brand does the opposite (Resend for transactional). Hermes made the case for Beehiiv covering the automation use cases. Michael agreed: “Let’s stick with Beehiiv.”
Michael’s reasoning: Adam will likely want specific comms for purchase or Skool community join events - Beehiiv can handle those. Keeping one tool avoids managing two systems.
Options considered
- Resend for transactional + Beehiiv for newsletter (what Rafael originally asked for)
- Beehiiv for everything (chosen)
Consequences
- No Resend workspace to be created for Adam
- Email automation PRs (Capture, Qualified, Downsell, Direct, Preselling) use Beehiiv API
- Beehiiv API key and publication ID already in env: BEEHIIV_API_KEY and BEEHIIV_PUBLICATION_ID
- No real subscribers to be enrolled during development (Michael explicit: “do not send anything real”)
- Rafael to give further instructions in eng thread once Beehiiv integration PR is done