The Messaging Engine Built for Teams Who Think in Events
How a lunch-break side project for developers turned into a $100M messaging engine trusted by Notion, Buffer, and thousands of other data-driven teams.
In 2012, two engineers named Colin Nederkoorn and John Allison spent their lunch breaks looking for a problem worth quitting a job over. Their first idea was a smarter analytics product. They pitched it around, and the answer came back flat: I already have ten tools that tell me what people did on my website. What I want is something that changes what they do next. So they built that instead, and called it Customer.io.
Fourteen years later, that pivot has grown into a customer engagement platform that more than 7,500 companies use to run their messaging - the onboarding emails, the re-engagement nudges, the push notification that arrives at the exact moment a user does the thing. Notion runs on it. So do Buffer, Angi, Lemonade, and Mixpanel. In 2025 the company crossed $100 million in annual recurring revenue. It did that on roughly $40 million in total funding, with a team that has been fully remote since before remote was a resume line.
01 — The IdeaBehavior, not lists
Most email tools, then and now, think in lists. You upload a spreadsheet of contacts, write one message, and hit send to everyone in the column. Customer.io was built on a different premise: that the useful unit is not the list but the event. A user signs up. A user finishes onboarding. A user abandons a trial on day 11. Each of those is a signal, and each can trigger a message tailored to the moment.
That sounds obvious now. It was less obvious in 2012, and it turned out to be a design decision that shaped everything downstream. When your product listens for events instead of reading rows, you need real-time data plumbing, you need a way to describe complex journeys, and you need customers who are comfortable wiring their app to yours. That last requirement quietly picked the company's audience for it.
02 — The ProductOne system, every channel
At the center is Journeys, the visual workflow builder where a marketer or growth engineer drags out a campaign: a trigger, some branching logic, a wait step, a message. The messages can go anywhere the customer lives - email, mobile push, SMS, in-app, and more recently WhatsApp and LINE. Personalization runs on Liquid, the same templating language developers already know, which tells you a lot about who is meant to feel at home here.
Underneath Journeys sits the less glamorous but arguably more important layer: Data Pipelines. This is where first-party data gets unified - through integrations, APIs, webhooks, warehouse sync, reverse ETL, and custom objects. It is the part that lets a team pull a segment out of Snowflake and act on it inside a campaign without a data engineer as a middleman. In a marketing world losing its third-party cookies, owning that pipe is the whole game.
In 2022 Customer.io bought Parcel, an email code editor, and folded it in. It is a small acquisition that says something: when your users are the kind of people who hand-write MJML, you invest in the code editor. Then in 2026 came the biggest release in the company's history - an AI Agent that turns a single prompt into a fully configured campaign, complete with triggers, content, timing, and logic, plus LLM Actions, Goals, and a redesigned interface.
03 — The FieldWhere it sits among the giants
The customer engagement category is crowded and well-funded. Braze went mobile-first and processes billions of messages on peak shopping days. Klaviyo built an empire on Shopify stores and abandoned-cart flows. Iterable chases enterprise marketing teams with a polished journey studio. Customer.io went somewhere else entirely - it went to the engineers, and to the growth teams technical enough to think like them.
| Platform | Sweet spot | Known for |
|---|---|---|
| Customer.io | Tech-savvy SaaS | Event-driven, developer-friendly |
| Braze | Mobile-first apps | Push at massive scale |
| Klaviyo | Ecommerce / Shopify | Revenue attribution |
| Iterable | Enterprise marketing | Journey studio |
The positioning has a cost and a payoff. The cost is that Customer.io will never be the easiest tool for a non-technical small-business owner to pick up. The payoff is a loyal base of teams who found most martech patronizing and finally got a platform that trusts them with a webhook. That base pays predictable, usage-based subscription fees - a B2B SaaS model priced on profiles and message volume, with an enterprise tier for the heavy senders - and it renews.
04 — The ProofWhat it looks like in production
Notion is the case study people point to. With roughly 80% of its users outside the United States and millions of people to reach, personalizing lifecycle messaging at that scale is genuinely hard. Running it on Customer.io, Notion reported open rates in the high-40s to low-50s percent on targeted campaigns - numbers that suggest the messages were landing as relevant rather than as noise.
There is a lesson buried in that curve. The company took about a decade to raise its Series A, a $35 million round from Spectrum Equity in 2022 that valued it at $690 million. Ten years is an eternity by venture-timeline standards. It also meant that when the money finally came, it came into a business that already worked - the kind of restraint that reads as boring right up until it reads as smart.
05 — The TeamRemote before it was cool
The company is legally named Peaberry Software - a peaberry is a small, single coffee bean, which is a nicer origin story than most SaaS incorporations get. It has been fully remote and globally distributed from the start, leaning on written communication, fewer meetings, and collaboration hours stitched across time zones. Employees get remote-work and home-office stipends, co-working reimbursement, and a learning budget. In 2026 it landed at #13 on the Best Practice Institute's Top 100 Global Most Loved Workplaces.
That line - "more powerful over time" - is doing quiet work. It is the promise that the data you feed the system compounds into better targeting, and now, with the AI layer, into campaigns that assemble themselves. Whether prompt-to-campaign holds up under real editorial scrutiny is the open question of the next few years. But the bet is coherent: a company that spent fourteen years hoarding first-party event data is exactly the kind that has something worth pointing an AI at.
Customer.io fits the market as the tool for people who would rather write a webhook than file a support ticket - a position it chose early, defended through a decade of patient growth, and is now extending into the AI era. It never tried to be everything. It tried to be the obvious choice for a specific kind of team, and 7,500 of them agreed.