​

Why AI

The notification platform market splits cleanly in two. Dev-first tools — Knock, Novu, Courier — give engineers clean APIs and ship fast. Marketing waits. No-code tools — Customer.io, Braze — give Marketing canvases and journeys. Engineering pipes data in. Both are honest about the trade-off they’re making; both leave money on the table. AI doesn’t fix this by adding a feature. It fixes it by reading the developer-side primitives so Marketing can author against them — without learning to write code, and without waiting for an engineer to translate.

​

TL;DR

• The AI generates the orchestrator — the code that decides who receives the message and what data flows in — not subject-line variants.
• It reads your event catalog and enricher catalog, so it proposes code against primitives that actually exist in your product.
• It also reads the knowledge base — working language, business context, vocabulary. Those three are written by your team, and they are the only organisation-level control you have over how the AI sounds.
• Marketing describes the campaign in plain language; the output is a diff a developer reviews before anything ships.
• Gaps become implementation tasks (add event properties, create enricher, add enricher fields); an unresolved one holds the campaign back from Review, and so from Live.
• The AI never sees customer data — only event and enricher schemas. Records flow at runtime, through your enrichers.

​

What we believe

The point of AI in a notification platform isn’t to generate subject-line variants. It’s to generate the orchestrator — the code that decides who receives the message, what data flows in, what the channel sends. Subject-line AI is local; orchestrator AI moves work across the team boundary. The first replaces a copywriter’s first draft; the second replaces a four-week ticket loop.

​

The status quo

​

Dev-first (Knock, Novu, Courier)

Pure-API platforms. Workflows are code; orchestrations are JSON or YAML; engineering ships every campaign. Marketing files tickets; engineering implements. The AI angle, when present, is “AI-suggested templates” or “AI subject-line variants” — useful but it doesn’t change who authors the campaign. What this gets right: clean primitives, good types, predictable behaviour. What it gets wrong: it assumes engineering wants to ship every campaign, and that Marketing’s role is writing tickets.

​

No-code (Customer.io, Braze)

Visual canvas. Marketing drags blocks: trigger, filter, branch, send. The AI here is segment suggestions, copy variants, send-time optimisation. Useful but local — none of it changes the fundamental data model. Marketing still operates on what was synced into the platform; the canvas can’t reach what wasn’t. What this gets right: marketing autonomy on the things the canvas allows. What it gets wrong: marketing dependency on the canvas’s expressive power, which is always less than what code can do. Both camps’ AI is decorative — it improves what already works, doesn’t change what doesn’t.

​

The Notifizz alternative

The AI generates the orchestrator — the code inside a campaign that runs server-side per matching event. Marketing describes the campaign in plain language. The AI reads:

• The event catalog for this org. Every event your code emits has a registered shape; the AI sees what subscription.upgraded carries.
• The enricher catalog. Every enricher you’ve registered with its input/output schemas. The AI knows fetchUser exists and what it returns.
• The campaign description Marketing wrote.
• The organisation’s knowledge base — the three inputs your team writes by hand: the working language the AI must write in, the business context (what the company does, its tone of voice, the rules it must never break), and the vocabulary of your terms and acronyms.

The first three come from how your product is built and what Marketing just typed. The fourth is the one you set on purpose, once, for every campaign that follows — and it is the difference between copy that names your things and copy that reads like a generic version of your industry. The orchestrator reads the working language and the vocabulary; the agents that write the actual message copy read all of it, including the tone. It produces real TypeScript-flavoured orchestrator code that:

• Reads event properties.
• Calls enrichers when the campaign description implies data Marketing didn’t pass in the event.
• Builds the recipient list.
• Branches on conditions.

The output is a diff against the previous orchestrator version. Dev reviews. Marketing approves. Ship. This is fundamentally different from “AI-generated subject lines”:

​

The implementation-task system makes this safe

The risk anyone should worry about: AI confidently produces wrong code. Notifizz’s answer is the implementation-task system. Every time the AI proposes orchestrator code, the dashboard validates it: Implementation tasks block promotion to Live. The AI proposes; Dev resolves; the platform doesn’t ship code that touches a primitive nobody acknowledged. The AI is fast and humble — it doesn’t claim authority over what it can’t verify. Combined with campaign versioning (every save = new version, in-flight messages run against the version they started on), the safety story is: AI-generated code can ship, but only after the catalog says it makes sense, only after a human reviewer accepts the diff, and only forward — past notifications are immune to future AI proposals.

​

Where it doesn’t help

Be honest about the limits.

• Genuinely novel logic the AI hasn’t seen. If your campaign requires a custom queueing strategy, a non-standard fanout, or business rules that don’t map to events + enrichers + recipients, the AI’s output is a starting point at best. Write it by hand.
• Cross-org generalisations. The AI is scoped to your org’s catalog. It doesn’t transfer “what worked for another customer” — by design, since that would leak.
• Brand voice in copy. Subject-line and body copy generation is opt-in but it’s a separate concern from orchestrator codegen. Some teams use it; some prefer human-authored copy with AI-generated structure.

The orchestrator-codegen lane is wide. Most marketing-led campaign work fits inside it. The lanes that don’t fit get implementation tasks and human review — exactly as they should.

​

But what about…

​

Where to go next