Why email APIs should stay small

Transactional email does not need a marketing cloud. The best email API is the one that stays out of your way.

Most email products start simple and die of feature gravity. Templates. Builders. Audiences. A/B studios. Suddenly you needed a password reset and inherited a CRM.

That is not inevitable. It is a product choice.

The job is small on purpose

App email is boring — and that is a feature:

  • Password resets
  • Magic links and OTPs
  • Welcome / verify messages
  • Receipts and invoices
  • “Something happened in your account” notifications

None of that requires a newsletter suite. It requires a reliable send pipe and a way to see what happened when mail fails.

If your roadmap starts with “segmentation,” you are already building the wrong company for this customer.

Small API, honest product

Notify’s public contract is intentionally tiny: to, from, subject, message. Auth is one header. Observability is logs and webhooks. That is the product.

How you build the body — string template, React render, Markdown, a CMS — is your problem. An email API that tries to own your content layer is solving a different problem, usually so it can upsell a studio later.

Small APIs are easier to explain to a teammate, an LLM, and a future you who has forgotten the integration.

What “small” protects

  • Time to first email. Minutes, not a platform tour.
  • Pricing you can say out loud. Free / $10 / $50 without a calculator.
  • Docs that fit in a sidebar. Not a second product.
  • A roadmap that cannot betray transactional users by pivoting into marketing automation.

Feature gravity always pulls toward the bigger budget. Enterprise marketing clouds pay more than indie hackers sending password resets. If you do not draw a hard line, the product will.

The counter-argument

“But what if we need campaigns later?”

Then buy a marketing tool later. Do not tax every transactional send today with the architecture of a hypothetical newsletter. Most startups never become email marketers. Almost every app needs a reset email.

Frequently asked questions

Why should email APIs stay small?

Transactional email is a small job: send a message, observe delivery. Small APIs ship faster, price flatter, and resist pivoting into marketing suites that complicate password resets.

What does Notify include if it stays small?

Send via notifycx or one HTTP call, webhooks for delivery events, and logs in the dashboard. Official MCP for IDE agents. No template studio or newsletters. Quick start.

Is a small email API enough for production SaaS?

Yes for auth, receipts, and product notifications. You own the HTML; Notify delivers it. Add webhooks when bounces matter. Pricing.

When do you need a bigger ESP?

When you need marketing automation, audiences, or drag-and-drop campaigns. Keep that off your transactional domain and API.