Resend (Email API)
Created by: Zeno Rocha and team

Resend prices on send volume with a generous free tier for indie devs. The model aligns with developer mental models.

TL;DR: Resend's pricing scales by emails sent per month, with a generous free tier (3,000/mo) that covers most indie SaaS in production. Paid tiers scale linearly from there. Pricing is in round numbers (3K, 50K, 100K, etc.) that match how developers reason about send volume. The lesson: when your buyer is technical, price in their mental units, not yours.

What they sell: A developer-first transactional email API with React Email integration.
Who it's for: Developers and indie SaaS founders sending transactional or marketing email.
Pricing model: Usage-based subscription priced per email-send volume
Payment frequency: Monthly subscription tied to volume tier; auto-upgrade as volume grows
Free trial behavior: Free tier IS the trial. 3K/month is enough for real production for most indie SaaS.
Number of tiers: 4

Anchor pattern: Round-number anchor
Volume tiers are round numbers (3K, 50K, 100K) that match how developers think about send rates. The Pro tier at $20/mo for 50K is the page's center of gravity; Scale and Enterprise anchor above. The unusual move is that the free tier is generous enough to be the trial, which keeps the pricing-page evaluation focused on volume planning rather than feature comparison.

Upgrade trigger: Volume cap and dedicated-IP need
Two triggers fire together: the 3K/month free cap is the structural volume trigger; the need for a dedicated IP (deliverability concern for marketing email) drives the upgrade to Pro independently. The first trigger is mechanical; the second is intentional. Both map to genuine SaaS growth needs.

What's working:
Volume tiered in round numbers (3K, 50K, 100K) matches developer mental model and removes evaluation friction.|Free tier (3K/mo) is genuinely production-grade for indie SaaS, which builds habit before the upgrade trigger fires.|Pro tier at round $20/mo is memorable and signals confidence rather than micro-optimized comparison-shopping.|Dedicated IP available on Pro creates a behavioral upgrade trigger for marketers concerned with deliverability.|Custom Enterprise tier captures the largest deals without exposing volume pricing to enterprise competitors.

What to adapt:
Price in the units your technical buyer already uses to reason about cost (sends, requests, GB, queries). Translation friction kills evaluation.|Use round numbers for tier thresholds. Memorable beats optimized.|Layer triggers: mechanical (volume cap) and intentional (specific feature need) so the upgrade fires reliably across buyer types.

What to avoid:
Do not use usage-based pricing if your buyer cannot predict their usage. Bill-shock is the biggest usage-pricing churn driver.|Do not price volume tiers in awkward units (e.g. 1,234 emails). The cognitive cost of unusual units exceeds the optimization value.|Do not make the free tier so generous that indie SaaS never upgrade. The free tier must have a structural ceiling that maps to growth.

Brunson lens:
Stack: Volume stack — each tier adds send capacity and minor feature unlocks. Pricing scales linearly with use.
Value ladder: Four-rung ladder with free tier as front-end lead funnel and Enterprise as high-ticket back-end.
Decoy/anchor: Round-number anchor mechanics; Scale tier reads as expensive next to Pro at $20/mo.
Payment mechanics: Monthly subscription scaled by volume tier; usage-based but tier-bundled to avoid bill-shock.

Pricing last verified: 2026-05-17