We spent a decade building the dashboard. Then we decided it was the bottleneck.

Three founders, three email companies, six billion emails across the first two. Nitrosend is what we built once we stopped defending the interface we had spent ten years perfecting.

What we watched, and the order we fixed it in.

Most companies arrive at AI email from the outside, as a feature to bolt on to something that already exists. We arrived from inside the thing being replaced. George spent six years running SmartrMail, and the conclusion did not come from a market report. It came from watching his own paying customers use the product he had built for them.

"I built SmartrMail (12K customers, billions of emails, acquired 2022) and watched every single customer waste hours dragging composer blocks doing work that AI can now do in seconds. The gap between what AI can do and what email platforms let you do with it is enormous."

That is the observation this company rests on, and it is not a complaint about dashboards looking dated. It is a specific charge. The work people were doing by hand in a composer was work a model could already do, and the interface was the only reason they were still doing it by hand.

We fixed the knowledge problem before we shipped the product.

This is the part of the story that runs against our own sales pitch, which is why we lead with it. In February 2026, five months before Nitrosend launched, George published the Email Marketing Bible: a free, open source reference now built from 908 sources and the published insights of 49 practitioners. He published it because AI is bad at email.

"It's 2 problems: the tools don't connect well to AI yet, and AI doesn't actually know email marketing nuance. Ask it to write a welcome sequence and you get generic, unsourced fluff. Ask about deliverability and it confidently makes things up."

Saying that out loud while selling AI email is uncomfortable, and it is still true. His response was to take the two problems in the order he could actually solve them. "I couldn't fix problem one in a week," he wrote, so he fixed problem two first and gave the answer away rather than selling it. The rule that came out of that work is the one we build against now: "The fix for mediocre AI-generated email isn't better prompts. It's better references."

It is why Nitrosend ships a Brand Kit and a separate AI Memory document instead of a longer prompt box. The agent that writes your email reads your colors, fonts, logo, voice and stated strategy before it writes a word, because a model with no references produces slop in any tool, including ours.

Then we removed the dashboard.

The platform came second, and by then the argument had already been made in public:

"The dashboard was never the product. It was the bottleneck."

The version of that claim we would defend in a room is narrower and more useful. Every campaign anyone has ever dragged and dropped was, underneath, a single sentence of intent that a person then spent an afternoon translating into blocks. The dashboard was the translation layer. Once a model can do the translating, the layer is cost, not product. George's own framing of the shift: "In 2026 the job changed. Agents now build the campaign, segment the audience, draft the copy, and stage the send. The marketer is the director, not the operator."

That is a real change in what the job is, not a change in who clicks the button. A director sets intent, judges the result and approves it. An operator assembles it. We think the assembly is over, and we are not neutral about it, because we built two companies on the assembly.

If you have questions, want to argue with any of this, or just want to say hello, reach us at [email protected].

"Humans approve. Agents operate."
George Hartley, on the day Nitrosend launched agentic email marketing
George, Kam and Ed - the Nitrosend team

It's our third rodeo, and the first one without a dashboard in it.

I really don't know why we love email so much.

Between us we have built two email platforms, sent over six billion emails, and scaled three technology companies. We have been on both sides of the email stack, which is mostly useful because it means we know exactly which parts of it were never worth the effort. This is a tool we started for ourselves. We needed it, and it turns out other people wanted it too.

George HartleyDesigner. Ex-CEO & Co-founder SmartrMail. Co-founder Bluethumb. Author of the open source Email Marketing Skill for Claude.
Kam LowDeveloper. Ex-CTO SmartrMail (6B emails, acquired 2022). Built the sending infrastructure that carried it.
Edward HartleyOperations. Ex-CEO Bluethumb. Co-founder SmartrMail. Ex-CEO Sendicate Email (28K users).
What this commits us to

Four things we gave up by believing this.

A conviction is only worth stating if it costs you something. Each of these is a decision we argued about internally and then wrote into the product.

The approval gate stays

We did not ship autonomy we could not back.

The fastest demo is an agent that sends the moment it is asked. We built the opposite into the tool surface instead. Approval, test sends and delivery review are first-class tools rather than a buried setting, so a person can sit between the draft and the list by default. Kam's view in April 2026 was that agents were not yet ready to be handed a skill file and left to run, and we would rather the gate be there and unused than absent.

Tools: nitro_control_delivery, nitro_send_test_message, nitro_review_delivery
MCP is not the only surface

We admitted where the protocol runs out.

An MCP-only company would be a cleaner story. It would also be wrong. A large flow on an asset-rich brand can exceed an agent's context budget before it finishes being described, so bulk work and app-triggered sends belong on the REST API, the SDK and the CLI, not in a chat window. We built all four surfaces and we tell you which one to reach for.

MCP, REST API, @nitrosend/sdk, CLI
References over prompts

We put the brand context in the account, not the prompt.

If better references are the fix for generic AI email, they cannot live in whatever the user happened to type. Brand Kit holds the identity, colors, fonts, logo and voice. AI Memory holds the goals, audience and strategy as a document you edit. Both are readable by the agent before it drafts, so the quality of the email stops depending on the quality of one sentence.

nitro_set_brand_kit, nitro_set_memory, nitro://brand-kit
The API key is the fallback

We made the easy integration the discouraged one.

Handing out API keys is the path of least resistance for a platform, and it is what every developer expects. Kam's rule is the reverse: "API keys should always be discouraged when MCP is an option." A key gives an agent permission and nothing else. An MCP connection gives it the Brand Kit, the account state, the schema and the guide before it writes anything, which is why the standard setup is an OAuth sign-in with no key to paste at all.

MCP with OAuth is the default; API keys remain for REST, SDK and CI
Companies built and run

Where each of these opinions came from.

Two email platforms built to scale, one acquired. An art marketplace, a book library George owns, and the reference corpus we published before the product.

Want to work with us?

We are a small team shipping fast. If you are obsessed with email, agents, or developer tools, and you think the dashboard era is over too, we would love to hear from you.