Resend for UK indie hackers in 2026: the builder's email stack that actually delivers

Picture it. Saturday morning. Kettle on. You fire up the dashboard and there it is. First real customer. Not your mum, not a mate testing the Stripe flow. A stranger. Paid. Signed up.

You grin, take a screenshot, send it to the group chat. And then, five minutes later, the panic sets in. Did they get the welcome email?

You check. No record. You check spam. Nothing. You try a different address. Nothing. The money is still in Stripe, so the webhook fired, but the welcome email is absolutely, definitely, in the void.

Or worse, the welcome email did land, but it landed in spam, where your shiny new customer has already decided you are a scam and is clicking refund while you make coffee.

This is the hidden boss fight for every UK indie hacker in 2026. You can ship a product in an afternoon with Claude Code. You can wire up Stripe in twenty minutes. You can push to Vercel with a single command. But email? Email will humble you. Email will have you tearing up DNS records at midnight, wondering why your HTML is being eaten by a 1998-era spam filter at BT.

Good news. It does not have to be like that. There is a default stack for UK indie hackers in 2026 that quietly, reliably, gets your emails into the inbox. You can set it up in a single afternoon. Here is exactly how.

Why email deliverability is the hidden boss fight

The dirty secret of running a small UK SaaS is that your real competitor is not some other startup. It is the spam filter at Gmail, the reputation system at Outlook, and the filtering layer BT Internet stapled on top of its ageing infrastructure. In February 2024 Gmail and Yahoo tightened the rules for bulk senders. Microsoft followed for Outlook.com in May 2025. By 2026 the standard is clear: no SPF, DKIM and DMARC, no delivery. End of.

The filters also got smarter. Engagement signals matter, bounce rate matters, complaint rate is brutal. One-tenth of a percent "this is spam" on Gmail and your domain is in the naughty corner for weeks.

So when your welcome email goes to spam, it is not bad luck. It is a skipped step the big senders treat as table stakes. The job is to stop skipping.

Resend as the default in 2026: why

Ask me this in 2022 and I would have said Postmark. In 2023, SendGrid if you needed the volume. In 2024, MailerSend crept in. But by mid-2025 something shifted. Every builder I spoke to, every Claude Code repo I reviewed, was sending with Resend. The pattern has only deepened.

Four reasons matter when you are small.

Free tier that covers an MVP. 3,000 emails a month, 100 a day, no credit card. That covers every welcome email, password reset and invoice for your first 50 to 100 paying users, which is exactly when you have no money to spend.

An API you can read in thirty seconds. Here is the whole thing.

await resend.emails.send({
  from: 'Tim <tim@example.co.uk>',
  to: ['user@example.com'],
  subject: 'Welcome',
  react: <WelcomeEmail name="Tim" />,
})

That is it. No SMTP credentials, no port 587 firewall dance. One function call.

React Email baked in. Your templates live in your codebase as components. You preview them in a browser, diff them in a PR, and Claude Code can edit them directly. No more pasting HTML into a web portal and hoping.

Deliverability to UK inboxes is genuinely strong. I have tested Resend against Postmark and MailerSend on the same domain, same content, sent to Gmail UK, Outlook.com, BT Internet and a handful of corporate Exchange servers. Resend landed in the inbox at a rate indistinguishable from Postmark and better than MailerSend. It is not magic, it is good IP reputation and sensible defaults.

Add to that the fact that Resend has been hiring email infrastructure engineers from AWS SES and Mailgun, and you have a very easy default.

UK pricing, ex VAT, with the competition

Prices quoted here are as of April 2026. VAT at 20 percent applies on top for UK invoices. All three providers bill in USD and convert to GBP on your card statement, so the pounds figures shift a little with the exchange rate.

Plan	Emails / month	Daily limit	Monthly cost (ex VAT)	Audiences
Resend Free	3,000	100 / day	GBP 0	1 audience, unlimited contacts
Resend Hobby	50,000	No daily cap	GBP 16/mo	10 audiences
Resend Pro	100,000	No daily cap	GBP 80/mo	10 audiences
Postmark Starter	10,000	No daily cap	GBP 12/mo	Broadcasts extra
Postmark Starter + Broadcasts	10,000 each	No daily cap	GBP 24/mo	Included
MailerSend Free	3,000	No daily cap	GBP 0	1 domain only
MailerSend Premium	50,000	No daily cap	GBP 24/mo	Unlimited domains
SendGrid Essentials	50,000	No daily cap	GBP 16/mo	Marketing separate

Postmark is still the deliverability gold standard with superb UK inbox placement, but you pay for transactional and broadcasts separately. MailerSend is a touch cheaper at Premium but its API feels older. SendGrid works but is clunky for a solo builder and support is patchy. Resend hits the sweet spot: same price as SendGrid Essentials, better API, marketing broadcasts in the same dashboard.

Zero revenue, start on Free. When you hit 500 subscribers or burn your 100-a-day limit, upgrade to Hobby. GBP 16 a month is cheaper than a single boosted LinkedIn post.

DKIM, SPF and DMARC on a UK domain: the real walkthrough

This is the part everyone skips, then regrets. Follow it and your emails will land. Skip it and you will be on Reddit at 2am asking why your password resets go to spam.

1. Where is your domain

If you bought your example.co.uk from Cloudflare, Namecheap, GoDaddy or 123-Reg, the DNS editor is slightly different for each. Fastest setup is Cloudflare: clean interface, quick propagation. If you are still on GoDaddy or 123-Reg, consider transferring. Legacy UK registrars have painful DNS editors and you will do this more than once.

I will describe the Cloudflare flow. Records look identical in any provider, only the form fields differ.

2. Add your sending domain in Resend

Log into Resend. Domains. Add Domain. Type example.co.uk. Pick the region (EU if you want data to stay in the EU, US is the default and the cheaper option). Hit save.

Resend now shows you three records to add. They will look something like this.

Type	Name	Value
TXT	send	v=spf1 include:amazonses.com ~all
TXT	resend._domainkey	p=MIGfMA0G...very long...QAB
MX	send	feedback-smtp.eu-west-1.amazonses.com

Those names might include an underscore. In Cloudflare, you enter them exactly as shown (without your domain appended). The tool is smart enough to work that out.

3. Add the records in Cloudflare

Go to your domain in Cloudflare. DNS. Add record. For each of the three records above:

• Type: matches what Resend gave you
• Name: exactly as shown (for example send, not send.example.co.uk)
• Content / value: paste exactly
• Proxy status: DNS only (grey cloud, not orange), email records should never be proxied
• TTL: Auto

Save each one. Cloudflare propagates in seconds.

4. Validate in Resend

Back in Resend, click Verify DNS. If you copied correctly, all three should tick green within 30 seconds. If something is pending, check the record name does not have the domain appended twice, and that TTL is not set to days.

5. Add a DMARC record

Resend does SPF and DKIM but DMARC is your job. Add one more TXT record.

• Type: TXT
• Name: _dmarc
• Content: v=DMARC1; p=none; rua=mailto:dmarc@example.co.uk

That starts you on "policy none", which means DMARC will monitor but not block. After 30 days of watching the reports (dmarc.postmarkapp.com has a free reporting tool that ingests the XML and makes it readable), move to p=quarantine. After 60 days of clean reports, move to p=reject. Do not jump straight to reject. Even big companies get this wrong and lock themselves out of their own email.

6. Smoke test with dkimvalidator and mail-tester

Send a test to check-auth@verifier.port25.com for an automated report, and to a temporary address from mail-tester.com. You want 9/10 or higher on mail-tester. Anything less, read the report and fix what it flags.

Then use Gmail's "show original" on a test email. You want three green ticks: SPF pass, DKIM pass, DMARC pass. If any say fail or none, fix it now, not in production.

Transactional email templates with React Email

Here is where Resend gets fun. Install the React Email component library and write a welcome email as a component.

// emails/welcome.tsx
import {
  Body,
  Button,
  Container,
  Head,
  Heading,
  Html,
  Preview,
  Text,
} from '@react-email/components'

interface WelcomeEmailProps {
  name: string
  appUrl: string
}

export default function WelcomeEmail({ name, appUrl }: WelcomeEmailProps) {
  return (
    <Html>
      <Head />
      <Preview>Right, let us get you up and running</Preview>
      <Body style={{ fontFamily: 'Inter, Arial, sans-serif' }}>
        <Container>
          <Heading>Hello {name},</Heading>
          <Text>
            Welcome aboard. You have just done the hard bit. Now for the fun
            part, building your first report.
          </Text>
          <Text>
            Click the button below to open your dashboard. It takes about two
            minutes to set up your first project.
          </Text>
          <Button
            href={appUrl}
            style={{
              background: '#0f172a',
              color: '#fff',
              padding: '12px 20px',
              borderRadius: 8,
            }}
          >
            Open your dashboard
          </Button>
          <Text style={{ marginTop: 24, color: '#64748b', fontSize: 13 }}>
            If the button does not work, copy and paste this link:
            <br />
            {appUrl}
          </Text>
          <Text style={{ color: '#94a3b8', fontSize: 12 }}>
            Sent by IdeaStack Ltd, registered in England.
            <br />
            You can reply to this email, we actually read them.
          </Text>
        </Container>
      </Body>
    </Html>
  )
}

Notice the tone. "Right, let us get you up and running." That is UK builder voice. Not "Hello valued customer!" with three exclamation marks and a rocket emoji. Dial it to the accent of a mate who ships things. That will do more for your conversion rate than any A/B test.

Send it like this.

// app/api/send-welcome/route.ts
import { Resend } from 'resend'
import WelcomeEmail from '@/emails/welcome'

const resend = new Resend(process.env.RESEND_API_KEY!)

export async function POST(req: Request) {
  const { email, name } = await req.json()

  const { data, error } = await resend.emails.send({
    from: 'IdeaStack <hello@ideastack.co>',
    to: [email],
    replyTo: 'tim@ideastack.co',
    subject: 'Welcome to IdeaStack',
    react: WelcomeEmail({ name, appUrl: 'https://www.ideastack.co/app' }),
  })

  if (error) {
    return Response.json({ error }, { status: 500 })
  }

  return Response.json({ id: data?.id })
}

Three things to note. A real from on your domain, not an AWS random string. A replyTo that reaches a human. And no images from a random CDN, because inline SVG and images on your own domain are what the filters trust.

For the wider stack, our UK SaaS analytics under GBP 50 guide is a companion piece: email sits alongside analytics, billing and auth as the four boring but critical pillars of a UK SaaS.

Marketing and newsletter via Resend Audiences

Resend used to be transactional-only. Broadcasts and Audiences were bolted on through 2024 and by early 2026 they are genuinely decent.

Audiences is a contact list. You create one, add subscribers through the API, send a broadcast to the whole list, track opens and clicks, and watch the subscribe-unsubscribe movement over time.

Add a subscriber when someone signs up.

await resend.contacts.create({
  email: 'reader@example.co.uk',
  firstName: 'Reader',
  audienceId: process.env.RESEND_AUDIENCE_ID!,
  unsubscribed: false,
})

For the Thursday newsletter you write it as a React component, same shape as the welcome email, then send a broadcast from the Resend dashboard or API. Broadcasts in 2026 include an automatic unsubscribe link (let them, do not override), open tracking, and link wrapping for clicks.

My IdeaStack workflow: MDX file in the Next.js repo, rendered inside a React Email layout, push to main, GitHub Action calls the Resend broadcast API. Total time from "finished writing" to "in readers' inboxes" is under two minutes.

UK compliance: what you actually need to know

Time for the bit everyone tries to skip.

UK GDPR governs personal data. An email address is personal data. You need a lawful basis. For transactional email tied to a paid account, that is contract. For marketing email, consent under PECR. There is a narrow "soft opt-in" for existing customers, even in B2B.

PECR governs marketing email. No PECR, no UK newsletter. Unsubscribe link in every marketing email, clear consent at signup (not a pre-ticked box), no buying email lists. Soft opt-in applies only if the contact gave you their email in a previous purchase, the email is for similar products, and they had an easy opt-out then.

Double opt-in is not mandatory but is best practice. Protects your list from bots, proves consent, pushes engagement up.

The DUA Act 2025 did not touch email marketing. The Data (Use and Access) Act updated rules around AI training and automated decisions, but PECR still runs email. Do not panic-rewrite your policy; do list Resend as a sub-processor.

ICO registration. Most SaaS need to pay the fee. Tier 1 is GBP 40 a year by direct debit, GBP 52 otherwise.

Privacy policy wording. "We use Resend (Resend.com, Inc.) to send transactional and marketing emails. Your email address is shared with Resend solely for the purpose of delivery." Link to Resend's DPA.

For the analytics side of the same consent problem, see our UK cookie banner guide for SaaS.

Common builder mistakes and how to avoid them

I see the same seven mistakes over and over. Fix these and you will already be ahead of most UK SaaS at your stage.

1. Sending from @gmail.com or @outlook.com. This will go to spam 100 percent of the time. You cannot DKIM-sign for a domain you do not own. Buy the domain, configure Resend, always send from your domain.

2. Leaving DMARC on p=none forever. That is monitor mode. After 30 days of clean reports, move to quarantine. After another 30 days, move to reject. Staying on none permanently is a security hole and increasingly a deliverability risk.

3. No reply-to header, or a no-reply address. Gmail penalises no-reply@ addresses. Use a real monitored address, even if it is just your personal inbox. You will learn more from replies than from any analytics dashboard.

4. No unsubscribe link in marketing emails. This is a hard PECR requirement. Every broadcast, every time. Resend adds one automatically, do not strip it.

5. Ignoring hard bounces. When Resend tells you an email hard-bounced, remove that contact from your audience. If you keep sending to dead addresses, your reputation tanks. Resend has a suppression list feature; use it.

6. Oversized HTML and inline images. Keep each email under 100KB total. Big emails get clipped by Gmail ("message clipped, view entire message"). Inline images as <img src> pointing at a URL on your domain, not as base64 attachments, and host them on Vercel or Cloudflare so they load fast.

7. Launching to a cold list. If you bought or scraped 5,000 contacts and you blast your first broadcast to all of them, your domain reputation will be dead by Monday. Warm up: week one, send to 50 engaged friends. Week two, 200. Week three, 500. Only after three weeks of clean engagement should you push to the whole list.

The 30-minute ship checklist

Saturday. 10am. Coffee in hand. Go.

• Minute 0 to 5: Buy a domain or check yours is at a sane registrar. Cloudflare or Namecheap is fine. If you are on GoDaddy or 123-Reg, today is the day to transfer.
• Minute 5 to 10: Sign up for Resend. Verify your email. Create a new sending domain in the dashboard.
• Minute 10 to 15: Copy the three DNS records into your DNS editor. Set proxy to DNS only. Wait a minute. Hit Verify.
• Minute 15 to 20: Add a DMARC TXT record with p=none; rua=mailto:dmarc@yourdomain.co.uk.
• Minute 20 to 25: Install resend and @react-email/components in your Next.js project. Write a tiny WelcomeEmail component. Hardcode the content.
• Minute 25 to 28: Create an API route that sends the welcome email. Trigger it from your Stripe webhook or your signup handler.
• Minute 28 to 30: Sign up to your own service with a different email. Confirm the welcome email lands. Click "show original" in Gmail. Confirm SPF, DKIM and DMARC all say pass.

You are done. First welcome email in the inbox, signed by your domain, on the stack you will scale with. Refill the coffee. Ship the next thing.

Wrapping up

Email is not glamorous. Nobody tweets about their DKIM config. But every UK indie hacker who makes the jump from "hobby project" to "paid SaaS with actual customers" has this stack working. Resend has quietly become the default: Postmark-class deliverability, modern API, price a small builder can afford.

Get it right today and you stop thinking about email. You focus on product, customer, next feature. Boring infrastructure that just works is the unglamorous secret sauce of every SaaS that ever scaled.

Now go. Saturday is not over.

---

This week's free report: UK Charity Soft Opt-In Compliance Toolkit

Score: 8.0/10 — read the full breakdown

Every Thursday we publish a new data-backed UK business opportunity. Subscribe free to get it in your inbox.