Champions Network

Internal Document

This page is password protected.

← Main Site Internal · Planning Doc
Champions Advocate Weekly · Email Delivery

Sending the Advocate Weekly with Resend

How we'd send the newsletter straight from champions-network.com — no logging into a separate email app — plus how we'd hold the contact list and what it costs as we grow.

The goal & why Resend

Build the issue on the site, hit one button, it goes out. We looked at EmailOctopus first — but its API can't create or send a broadcast (it only manages contacts and fires pre-built automations). Resend's API can.

1 How it works

The piece we already built (build & approve an issue on the site) feeds a small Netlify function that talks to Resend. Mark still blesses every send.

Build on siteIssue assembled in the Advocate composer
ApproveMark reviews & clicks Send
Netlify functionHolds the Resend key, calls the API
Resend → inboxBroadcast to the contact list

Safety rail

The Send button always opens a test send to ourselves first and a confirm step before the real blast — so no issue goes out by accident.

2 One-time setup

A few hours of setup, most of it DNS that propagates on its own. Roughly in order:

  1. Create the Resend account

    One account for the Champions Network / LCRL. Free to start (see Costs).

  2. Verify a sending domain

    Add Resend's DNS records (SPF, DKIM, DMARC, and a return-path) to a subdomain like news.champions-network.com. Using a subdomain protects the main domain's reputation. This is the single most important step for landing in inboxes, not spam.

  3. Create an Audience

    Resend's term for a contact list. This becomes the one home for Advocate subscribers.

  4. Generate a restricted API key

    A send-only key, stored in Netlify as RESEND_API_KEY — exactly like CLOCKIFY_API_KEY. Never committed to the site code.

  5. Build the send function + button

    A send-advocate Netlify function plus a "Send this issue" button on the composer. One-time build on our side.

  6. Wire the signup form

    Point the site's "Subscribe" form at a small function that adds the person to the Audience (double opt-in — see next section).

3 The contact list — setup & upkeep

One source of truth, kept clean and compliant. This also resolves the current split between MailChimp and the larger "Abba Dabba" account.

Getting the list in

Growing it from the site

Keeping it healthy

Doctrinal review is unaffected

None of this changes the review posture — curated/quoted news still needs no review; only our own added words do. Resend is just the delivery pipe.

4 What it costs

The newsletter uses Resend's Marketing / Broadcasts product, which is priced by number of contacts — with unlimited sends. That's the headline.

Frequency is free

Because you pay per contact, sending weekly, twice a week, or daily costs exactly the same. The only thing that moves the price is how many people are on the list.

Cost by list size (the newsletter)

ContactsResend planMonthlySends included
Up to 1,000Free$0Unlimited
Up to 5,000Pro (Marketing)$40Unlimited
5,000 → 150,000Scale tiers$40 → $650Unlimited

Pricing scales with contacts between the $40 and $650 anchors; exact intermediate tiers are on Resend's pricing page. Today's ~70 and even a 1,000-person list cost $0.

What we'd actually pay

ScenarioList sizeFrequencyResendvs MailChimp
Today~70Weekly$0$20/mo
Old MailChimp cap500Weekly or daily$0$20/mo
Healthy growth1,000Weekly or daily$0~$26/mo
Network scales up2,500Any$40/mo~$45/mo
Big5,000Any$40/mo~$75/mo

The interactive version

$0
Resend / month
~2,150
Emails / month
Free
Plan tier

Sign-up confirmations (a separate, tiny cost)

Double-opt-in confirmation emails use Resend's Transactional side, which is free up to 3,000 emails/month (100/day). We'd send a handful a week — comfortably free. Only matters if we ever do a huge one-time import.

5 What we can measure

Yes — Resend tracks opens and click-throughs on every broadcast. This directly answers Shelly's question from the June 12 call about reader behavior.

The bigger win

Because each story now lands on our site first, we get true on-site analytics too — which stories get read, how long, and onward clicks to the source. That's the real engagement signal the old "link straight out" emails could never measure. We'd see both the email numbers and what people actually do.

One honest caveat

Apple Mail (Privacy Protection) pre-loads images, which inflates open rates across every email tool — so treat opens as directional, not exact. Clicks and on-site visits are the trustworthy numbers.

6 Suggested rollout & open decisions

Phases

  1. Prove it (test mode)

    Build the send-advocate function + button; send test issues only to ourselves and a small internal group.

  2. Verify the domain & warm up

    Set DNS on news.champions-network.com; send a few real issues to the current ~70 to establish reputation.

  3. Switch fully off MailChimp

    Once deliverability looks good, retire the $20/mo MailChimp and move signups to the site form.

Decisions needed

1. Subdomain to send from (news. vs email.).  2. Double opt-in: yes/no.  3. Resolve the "Abba Dabba" account merge before importing the master list.  4. Who owns list upkeep day-to-day (Carly / Shelly).