Jeff This article was written by an expert AI about the Notifizz product and martech more broadly. If you notice any issue with the content, please let us know.

Build or buy your SaaS notification system: what you have to build after v1

Comparisons and alternatives

The first notification is easy: a password reset sent through an email provider's API, a bell in the corner of the app. Building a reliable system that lasts is another matter, and the difference shows up months later, when marketing, dev and product all depend on it.

This guide is for the people who make that call in a B2B SaaS team: the CTO or head of product weighing an in-house system, and the marketing lead who will live with the result. It sets out the three realistic options, the six components that appear as notifications multiply, a way to estimate the cost over three years, and the cases where building is the better answer. It is written by Notifizz, which sells one of the options; the last section says what Notifizz covers and what it does not.

The first notification is a small part of the work

Picture a B2B SaaS a year after launch. It sends password resets and invoices through an email provider's API, and shows a bell in the app. Then the requests arrive.

  • Marketing wants an onboarding sequence that stops as soon as the trial converts. The sequence needs to know who converted, and that lives in your database, not in the event that started it.
  • The newsletter goes out to every account. It needs an unsubscribe link, and a complaint spike on it must not push the password resets into spam.
  • A recipient marks a promotional message as spam. Their address has to stop receiving promotional email, whatever the campaign, while their transactional email keeps arriving.
  • A customer in France asks whether you measure email opens with consent.
  • The marketing lead wants to test the new sequence on a real event without emailing real users.
  • Someone asks whether last month's campaign worked.

None of this is the first send. Each request adds a piece that has to keep running in production, and each piece crosses the boundary between marketing, dev and product. That is where the cost of building lies: not in the first version, but in what it takes to keep the next twenty campaigns correct.

Three ways to get there

The choice is rarely between writing everything yourself and buying a product. There are three options.

  • Build everything, sending infrastructure included. Rare, and justified mainly when notifications are the product itself.
  • Assemble services: an email sending service, a push service, a message queue, a database, and your own code for orchestration, eligibility, preferences and measurement. This is the most common path, and the most credible alternative to a platform.
  • Adopt a specialised platform, integrate it, and keep the parts that belong to your team.

Between the last two, the trade-offs look like this:

  • First setup. Assembled: quick for simple needs. Platform: depends on the integration work.
  • Customisation. Assembled: full control. Platform: within what the platform offers.
  • New channels. Assembled: one more integration to build and maintain. Platform: depends on the channels it ships.
  • Preferences and unsubscribe. Assembled: to build or to assemble. Platform: usually included.
  • Change over time. Assembled: depends on your engineering team. Platform: also depends on the vendor's roadmap.
  • Cost. Assembled: services and infrastructure, plus the time to build and maintain. Platform: subscription or usage, plus integration, plus what stays with your team.

Neither column wins everywhere. What decides is how much of the next section your team is ready to own.

The six components that appear after the first send

As your notifications multiply, six components appear. Depending on how complex your product is, some will be essential, others can stay very simple or not be needed at all. For each: what it takes, the part nobody sees at the start, and what stays with your team even if you buy.

1. Distribution: sending streams and channels

Mixing transactional and promotional email on the same sending path hurts deliverability: a complaint spike on a newsletter weighs on the reputation that also carries password resets. Building it means two sending streams and a category on every campaign that routes it to the right one. Then each channel is its own integration, with its own delivery guarantees, failure modes and measurement: the in-app notification centre, email, web push, a chat channel.

The part nobody sees at the start is the category decision. A promotional campaign filed as transactional loses its unsubscribe link and rides the stream meant for password resets. And separating sending streams is narrower than it sounds: unless the sender domain is separated too, its reputation stays shared. How the separation works, and where it stops, is covered in our article on separating transactional and promotional email.

What stays with your team: choosing each campaign's category, and agreeing between marketing and product on what counts as transactional.

2. Eligibility: who may receive this message now

Before anything is sent, each recipient goes through an ordered chain of pass-or-fail checks: erasure, so that a deleted user receives nothing; suppression, so that a hard bounce or a complaint blocks future sends; the person's own refusals, on promotional sends; membership of the audience, when a campaign must keep talking only to the people it started with; and the objective, so that someone who already converted stops receiving the rest of the sequence. The first check that fails decides, and the reason has to be recorded, or nobody can later explain why a customer did not get an email.

The part nobody sees at the start is the edge cases. Suppression depends on scope: a hard bounce or a complaint on a transactional message should block every email, while a complaint on a promotional message blocks promotional email only. An erasure request has to stop the sequences already running for that person. And when the suppression list cannot be checked, the safe answer is to drop the recipient rather than send, and to raise an alert.

What stays with your team: deciding when a campaign should keep talking only to its first audience, choosing each campaign's objective, and sending the business events that mark it reached.

Every promotional email has to offer an easy way to unsubscribe, and the large mailbox providers ask more of bulk senders: Gmail requires one-click unsubscribe for marketing and subscribed messages from senders of more than 5,000 messages a day. Building it means a hosted preference page, an unsubscribe state per person and per category, the one-click header, and a link that still appears when a template forgets it.

Measurement adds a second layer. European regulators treat an open pixel and a per-recipient tracked link as trackers: measuring one person's opens and clicks needs that person's prior consent, and the French regulator has ruled out legitimate interest as a basis for it, B2B email included. Transactional email is no blanket exemption: outside two narrow purposes, measuring its opens needs consent too, as our article on the CNIL's 2026 recommendation on tracking pixels explains. Building it means storing each person's answer, reading it at the moment of the open or the click so that a refusal also stops the counting on emails already sent, and statistics that say "Not measured" rather than 0 % when nothing could be measured.

The part nobody sees at the start: a preference that was never refused is not an authorisation. A preference system that records refusals tells you who said no; it does not tell you who said yes. In France, prospecting individuals by email generally requires their prior consent, while for professionals it is generally enough that the message relates to their job and that they were informed and can object, as the CNIL explains. And answers change: a person who refused measurement can consent again later, so the system has to keep each person's latest answer, without letting a refusal the person expressed be overwritten by a consent they never gave.

What stays with your team: the promotional categories and the texts that explain them; deciding who may receive promotional email and, where your audience must agree first, collecting that agreement and keeping its proof; asking for measurement consent and passing on each answer.

4. Business data at send time

A useful notification needs data the triggering event did not carry: the customer's plan, the amount due, the name of the account owner. Teams usually get it in one of two ways: a sync project that copies the customer database into the notification tool upfront, or a developer who writes the code for each campaign by hand.

The part nobody sees at the start: with the first, the copied data drifts from the source; with the second, every new campaign becomes a ticket in the development backlog, and marketing waits.

What stays with your team: deciding which business data a notification may use, and exposing it, whether as a sync to maintain or as small functions that fetch it at send time.

5. Rehearsal outside production

A preview shows what a message looks like. A rehearsal shows how a campaign behaves. Building it means firing the campaign's real trigger event on a non-production environment, running it through the same pipeline as production, and watching each step: what was delivered, when, on which channel, whether the objective was reached. Delivery has to be capped to the team's own verified test inboxes and browsers, so that a campaign that is not live can never reach a real user.

The part nobody sees at the start is the gap between the two. A preview does not fetch business data, resolve recipients, check eligibility, or fire on a real event, which is precisely where campaigns break.

What stays with your team: sending the campaign's events from a non-production copy of your app, registering the test inboxes and browsers, and deciding when a campaign is ready to go live.

6. Observability: measurement and sending health

Each campaign needs its own funnel: sends, reads, clicks, and the objective it was built for. Email needs its sending health: delivered, bounced and complaint counts by mailbox provider, a complaint rate compared with the thresholds the providers publish for bulk senders, and a brake that holds back bulk sends when the rate turns critical. And every recipient who was dropped needs a count and a reason.

The part nobody sees at the start: the figures have to say what they do not know. Under consent, an open rate covers measured recipients only, and a screen that shows 0 % where nothing could be measured tells the marketing lead that a campaign failed when it was simply not observed.

What stays with your team: deciding what counts as success for each campaign, and acting when the complaint rate climbs.

What a notification system costs over three years

There is no honest universal figure: the cost depends on your volume, your channels and your team. What can be shared is a method. Over three years:

Total cost = initial cost + 36 × (monthly running cost + monthly maintenance cost)

  • Initial cost: building or integrating each of the components you need, migrating the notifications you already send, and getting marketing and product working in the new setup.
  • Monthly running cost: for an assembled system, the services and infrastructure behind it; for a platform, the subscription or usage.
  • Monthly maintenance cost: the time spent keeping each component working in production: changes in providers and in mailbox provider rules, regulator recommendations, new channels, incidents, and the coordination between marketing, dev and product.

To fill it in, take the six components one by one and estimate, for each option, three things: the time to build or integrate it, the time per month to keep it working, and who does that work. Requirements will move during those three years: the CNIL's 2026 recommendation on tracking pixels, for example, clarified when an email tool needs consent to measure opens. A component counted as finished at launch is rarely finished.

Two lines are easy to get wrong. For a platform, the maintenance line does not fall to zero: it holds the "what stays with your team" items above, and the integration itself. For an assembled system, the maintenance line is where the six components live, and it grows with each channel and each new kind of campaign.

For Notifizz, only the billing model can be stated here, because plan amounts live on the pricing page: volume is metered on the notifications a live campaign hands to delivery, counted per channel and on a cross-channel total. Tests and rehearsals cost nothing. There is no per-profile, per-contact or per-MAU billing, and AI usage is an allowance included in the plan.

When to build, and when to buy

  • You send a handful of transactional emails. Build: an email provider's API and a few templates are enough, and a platform would add more than it saves.
  • Notifications are your product's differentiator. Build: you will want control over every component, and their maintenance is part of the product.
  • Your first need is mobile push or SMS. Look beyond Notifizz, which ships neither.
  • You need branching journeys, A/B tests or cross-channel fallback. A marketing automation suite or your own code will fit better than a platform built on linear campaigns.
  • Your team already runs most of the six components, and marketing, dev and product work well together. Keep building: the hard part is behind you.
  • Marketing, dev and product share notifications across in-app, email and web push, and campaigns depend on live business data. This is the case a platform is built for: the six components are needed, and the coordination between three teams is the cost you are trying to reduce.

What Notifizz covers, and what it does not

Notifizz is a notification orchestration platform for SaaS teams. Against the six components:

  • Distribution: transactional email travels on its own sending stream, apart from the promotional stream that Product and Marketing campaigns share. The campaign's category decides, with nothing to configure; the sender address and domain stay the same. Four channels: an in-app notification centre with React, Angular and vanilla JavaScript SDKs, email, web push (opened account by account; on iOS, installed web apps only) and Intercom (rolling out account by account).
  • Eligibility: the chain runs before every send, and each dropped recipient is counted with its reason in the campaign's send attrition.
  • Preferences and consent: one-click unsubscribe and a hosted preference centre on every promotional email; email opens and clicks measured only for the recipients covered by consent, with "Not measured" rather than 0 % where nothing could be measured. The customer, as controller, collects consent; Notifizz applies it.
  • Business data: enrichers, declared once, fetch live business data at send time, with no sync project. An AI orchestrator, generated from the campaign's plain-language description, enriches incomplete events and flags what is genuinely missing. A new campaign is dashboard configuration with no code redeploy, as long as the events and enrichers it needs already exist; otherwise the orchestrator opens an implementation task, and the campaign cannot reach Review until a developer resolves it. Only a signed-in team member can publish it live.
  • Rehearsal: in Review, the team fires the campaign's real event on a non-production environment and watches the run step by step, with delivery capped to verified test inboxes and browsers.
  • Observability: a funnel per campaign up to its objective, email sending health by mailbox provider family, and a complaint-rate brake that holds back list and segment sends while event-triggered campaigns keep sending. List and segment sends are in closed beta.

Some of these capabilities depend on the plan, enrichers and multiple environments among them: the pricing page details what each plan includes.

What Notifizz does not do, and what you would still build or buy elsewhere:

  • Mobile push (there is no iOS or Android SDK), SMS, Slack, WhatsApp and outbound webhooks.
  • A/B testing, per-person frequency capping, and statistics export: measurement lives in the dashboard only.
  • Branching workflows: one campaign is one linear sequence with one objective. Notifizz is not a full cross-channel marketing automation suite.

One integration limit, finally: you cannot plug in your own email sending provider, because Notifizz handles the sending itself.

The documentation details how each piece works.

Before you decide

Whichever way you lean, write the six components down, put a name next to each, and estimate what keeping it running will take for three years. If most of the names are already on your team and the coordination works, build. If that list is where your roadmap stalls, buy, and keep the lines that belong to you.

Transactional and promotional emails: why separate your sending streams image.

Transactional and promotional emails: why separate your sending streams

A password reset the user just requested can end up in spam because last week's newsletter generated complaints. Here is why mixing transactional and promotional email on the same stream creates that problem, and how Notifizz keeps them apart.

Notification fundamentals

Jeff

This article was written by an expert AI about the Notifizz product and martech more broadly. If you notice any issue with the content, please let us know.

Tracking pixels in SaaS emails: the CNIL's 2026 recommendations and alternatives to the open rate image.

Tracking pixels in SaaS emails: the CNIL's 2026 recommendations and alternatives to the open rate

The CNIL's 2026 recommendation spells out how consent applies to email tracking pixels, transactional emails included. What changes for a SaaS's emails, what the exemptions cover, and how to measure a campaign without relying on the open rate.

Notification fundamentals

Jeff

This article was written by an expert AI about the Notifizz product and martech more broadly. If you notice any issue with the content, please let us know.