/
.webp)
Imagine a room in 2014 where every other founder in your category is saying yes.
Yes to term sheets. Yes to Series A pitches. Yes to the logic that says you cannot win a software market without a war chest, without headcount, without the kind of growth-at-all-costs velocity that venture capital buys you.
Intercom said yes. They raised $6 million in 2013, then $35 million in 2014, then kept going. Braze — still called Appboy — was raising aggressively. The behavioral messaging and customer engagement space was turning into an arms race, funded by the conviction that whoever hired the most salespeople first would own the market.
Colin Nederkoorn watched all of this and said no.
Not quietly, reluctantly, because he couldn't get a meeting. Publicly. On the company blog, in talks, in the stance Customer.io took as a company for an entire decade. Colin wrote about why he wasn't raising. He wasn't hiding the choice — he was arguing for it. In a moment when every signal in Silicon Valley pointed toward the same playbook, he built a different one.
This is the story of what happened next.
Colin Nederkoorn launched Customer.io in April 2012. He was solving a problem he understood viscerally: when you run a software product, you have this river of behavioral data flowing through your application — every login, every feature used, every drop-off, every upgrade — and the tools that existed to act on that data were built for a different era.
The tools that existed were batch tools. They were built around the idea of a list. You upload a CSV, you send everyone on it the same email, you see who opened it. It was broadcasting. It was the digital equivalent of a direct mail campaign — the same message to everyone, differentiated at best by a first name in the subject line.
What Colin wanted to build — what actually made Customer.io different from the first day — was something closer to a real conversation engine. The premise was simple and radical: software products know things about their users in real time. They know who just signed up but hasn't completed onboarding. They know who has been active every day for two weeks and then suddenly disappeared. They know who upgraded to a paid plan, who downgraded, who invited a colleague.
The question Customer.io answered was: what if you could send the exactly right message at the exact moment the user's behavior told you to?
Not "send this email to everyone who signed up this week." But: "send this email to anyone who signed up, completed step one of onboarding, but has not logged in for three days, unless they've already opened our previous onboarding email in the last 48 hours."
That distinction — behavioral triggers with stateful conditions — was the entire product. And building it cleanly, reliably, at scale, turned out to be a genuinely hard engineering problem.
The founding context matters: Customer.io launched on Hacker News in April 2012 and immediately found an audience in the developer-centric startup world. These were companies where engineering was involved in every decision, including marketing infrastructure. The concept of "email automation powered by user data" was intuitive to this audience in a way it wasn't to traditional marketers. You gave Customer.io a JavaScript snippet or a backend API call, and suddenly your application events were triggering messages with the precision of code.
By 2014, the company had crossed $1.5M in Annual Recurring Revenue. By the time Sacra Research profiled them in mid-2021, they were at $20M ARR — with only $4M in outside funding ever raised. That $4M figure deserves emphasis: in a category where competitors had raised tens or hundreds of millions, Customer.io built a twenty-million-dollar annual revenue business on four million dollars of external capital.
The $4M wasn't even a traditional VC round in the modern sense. It appears to have been early angel or seed-stage capital that gave the company initial runway — not the kind of growth-at-all-costs fuel that defines the modern venture-backed trajectory. After that seed, Customer.io ran on its own revenue for years.
Here is what it means, practically, to build a bootstrapped company competing against VC-funded ones in the same market:
Your competitors have unlimited hiring budgets. They run full sales floors with enterprise reps, SDRs, account managers, solution engineers. They sponsor every conference in your category. They outspend you on content, on SEO, on developer advocacy. They can afford to price at a loss for months to lock in a customer. They have the runway to wait.
Customer.io had none of that, and it won anyway — not in all segments, but in the segment that mattered most to Colin: technical teams inside product-led growth companies.
The insight that let them survive was one of the sharpest competitive insights in modern SaaS: high switching costs built into the product itself. Integrating Customer.io requires engineering work. You instrument your application, you pipe events through their Track API, you build segments around behavioral conditions that are deeply tied to your data model. When you do this properly, Customer.io becomes load-bearing infrastructure. Ripping it out isn't a one-afternoon decision. It's a project.
This meant that while competitors with sales teams could land enterprise accounts faster, Customer.io's customers tended to stay. Their gross MRR churn was 0.66% — exceptional by any SaaS standard. Their net MRR churn was negative 3.23%, meaning existing customers were expanding faster than any churned revenue. A dollar that came in grew over time.
This financial profile — slow to acquire, hard to leave, compounding over years — is exactly what bootstrapping requires. You cannot bootstrap a business with high churn and acquisition costs that outpace revenue. But you can bootstrap a business where every customer who integrates your product becomes structurally loyal to it.
The customer acquisition without a sales team happened through channels that were cheap in dollars but expensive in attention: developer community, word-of-mouth among technical founders, content marketing for a technical audience, the Hacker News launch that seeded the first wave of signups in 2012. Product Hunt. Integrations with tools that developers already used — Segment, Stripe, Salesforce. The company became a natural node in the modern SaaS stack for developers who needed behavioral messaging.
The team stayed lean. The company remained fully remote and async-first from early in its history — before remote-first was a trend, when most companies defaulted to San Francisco offices because that was what companies did. This wasn't ideology for its own sake; it was a structural advantage. A distributed team in a bootstrapped company can hire exceptionally talented people anywhere in the world without competing for San Francisco engineering talent at San Francisco salaries.
Against Braze, which raised over $400 million before going public in 2021, Customer.io didn't compete on budget. It competed on the depth and developer-friendliness of its product, on customer support that became a differentiator in a category where most enterprise tools are notoriously difficult to deal with, and on the fact that it didn't need to win every enterprise deal — it just needed to win the right ones.
By 2021, when Sacra Research published their analysis, the numbers told a stark story.
Customer.io was valued at approximately $400 million. They had $20M in ARR. They had 2,100+ monthly paying customers. They had 131% net dollar retention — top quartile for SaaS globally, meaning their existing customer base was growing faster than any customers left. And they had raised, in total, roughly $4M.
The ARR-to-funding ratio of 5x put them in the same tier as Zapier and Calendly as examples of radical capital efficiency. For context: Braze, by the time of its IPO, had raised over $400M to reach approximately $150M ARR. Customer.io reached $20M ARR on a rounding error of Braze's total capital consumption.
This is the number that makes the Customer.io story extraordinary: not the revenue itself, but the ratio. $20 million in annual revenue with 2,100 customers and a top-quartile retention profile built on $4 million. In a category where the prevailing wisdom was that you needed venture capital to compete, Colin had built proof that the prevailing wisdom was wrong — or at least, that it was wrong for a specific kind of company targeting a specific kind of customer.
The 70% year-over-year growth in 2021 was the critical evidence. This wasn't a slow, stagnant bootstrapped company grinding toward profitability while ceding the market to funded competitors. It was a company growing nearly as fast as its VC-backed peers while consuming a fraction of the capital. The product was working. The retention was world-class. The unit economics were compounding.
And then, in June 2022, something changed.
In June 2022, Customer.io announced a $55 million growth round led by PSG Equity.
This was, to put it gently, unexpected. Colin had spent years building a public case for why Customer.io didn't need outside capital. The company had become something of a flagship example in bootstrapper communities — proof that you could build a serious, durable software business without selling equity to venture investors. The Indie Hackers community had written about them. The SaaS Twitter world knew the story. Customer.io was the bootstrapped company that had endured.
The PSG round changed the framing immediately. But the details of how it happened are instructive about what "bootstrapping" actually means at different stages of a company's life.
PSG Equity is not a traditional VC firm. It's a growth equity investor that specializes in software companies — typically taking minority stakes in profitable, capital-efficient businesses that want to accelerate without the full venture-capital growth-at-all-costs model. The distinction matters. This wasn't a seed round betting on unproven ideas. This was a $55 million investment in a business that had already demonstrated a decade of profitable, compounding growth.
The company had already proved the model. By 2022, they were approaching $50M ARR by most estimates and had grown beyond 300 employees. The decision to take capital wasn't an admission that the bootstrapping thesis was wrong. It was a decision that the business had grown to a scale where capital could accelerate things — specific things, targeted expansion — without requiring the company to abandon the operating philosophy that made it successful.
What specifically convinced Colin to do the deal after a decade of refusals is not publicly documented in detail. But the context suggests several forces converging: the behavioral messaging market was consolidating rapidly; competitors like Braze had just gone public with enormous war chests; the product roadmap for competing at enterprise scale requires a specific kind of investment — infrastructure, compliance capabilities, dedicated enterprise support — that pure cash flow has limits in funding on a quarterly basis. And PSG's structure, as a minority growth equity investor rather than a controlling VC, offered capital without surrendering the company's fundamental operating culture.
It was the company taking money on its own terms, at the moment of its choosing, from an investor aligned with its values — rather than raising because runway was running out.
Post-investment, Customer.io moved quickly on the things that had been constrained by capital.
The team grew toward 300+ people. The company expanded its platform from a behavioral messaging tool into what it now calls a full customer engagement platform — adding mobile push, in-app messaging, SMS, and WhatsApp channels alongside email. The platform shifted toward what the market now calls "omnichannel" engagement, meeting customers wherever they are rather than just in their inboxes.
The customer base grew to 7,400+ brands, with a message volume that reached 56 billion messages sent in 2024 alone — a number that speaks to both the scale of the customers they serve and the extraordinary technical infrastructure required to process behavioral triggers and segment logic at that volume in real time.
The AI era poses a genuinely interesting strategic question for Customer.io. On one hand, AI-powered personalization is exactly the direction the behavioral messaging category has always been pointing: instead of writing static conditional rules ("send this if user did X but not Y"), large language models can potentially reason about user behavior dynamically and generate messages that are not just triggered by the right moment but composed for the right person in the right voice. Customer.io has begun building AI capabilities into its segment builder and workflow tooling.
On the other hand, the commoditization risk is real. If AI makes behavioral messaging substantially easier to implement — if the technical barriers that created Customer.io's switching costs begin to erode — the developer-centric moat that protected the company through its decade of bootstrapping becomes less durable. The companies with the most AI engineering talent and infrastructure are, not coincidentally, the ones with the largest capital bases: Braze, Salesforce's marketing cloud, Adobe Experience Cloud.
Customer.io's answer to that risk is to double down on what has always differentiated it: being the platform that developers and technically sophisticated growth teams prefer to use. Not the easiest platform. The most powerful one. The one where you can express any behavioral logic you need, instrument your product the way engineers want to instrument it, and trust that the data model underneath is flexible enough to handle what you actually build as opposed to what the platform's designers imagined you might build.
The PSG capital funded that direction. The question is whether a decade of compounding capital efficiency has built a foundation strong enough to compete against competitors that had ten years to scale their engineering teams on VC dollars.
1. The blog where Colin argued publicly against venture capital
Customer.io ran a section of their blog called "Is Open" — a transparency initiative where they shared metrics, decisions, and philosophy openly with the world. In this forum, Colin wrote about why Customer.io was not raising venture capital at a moment when every competitor was doing exactly that. These weren't private doubts. They were public arguments. He calculated what VC money would require in terms of growth rates and exit outcomes, compared it to the kind of business he wanted to build, and concluded the math didn't work for him. The posts have since been archived, but the 2014 year-in-review — published when the company crossed $1.5M ARR — laid out this philosophy with a clarity that would be remarkable from any founder, let alone one who ended up being right about it for eight more years.
2. The capital efficiency number that makes every VC uncomfortable
$4 million raised to reach $20 million in ARR. That's the number from Sacra Research's 2021 analysis. For comparison: Braze raised over $400 million to reach $150 million ARR at IPO. Customer.io needed roughly one percent of Braze's capital to build a similarly sticky, technically sophisticated platform for a slightly different customer segment. The business case for venture capital in behavioral messaging, as Customer.io demonstrated for a decade, was not that it was necessary — it was that it was available and that competitors chose to use it.
3. Ruby lives at the core, in 2025
Customer.io built on Ruby from the beginning. Their Ruby client for the event API was one of the first integrations they shipped, created in May 2012 — the same year they launched. While they have since built SDKs in TypeScript, Swift, Kotlin, Dart, and Go to support mobile platforms and modern development environments, the Ruby lineage is still visible in the codebase. At a moment when the software industry spent much of the 2010s debating whether Rails could scale, Customer.io processed behavioral events for 2,100+ companies and grew to 56 billion annual messages without abandoning the language and philosophy that built the company in the first place. This is a quiet form of conviction.
4. The metric that proves the moat better than any NPS score
Negative 3.23% net MRR churn. In practical terms: Customer.io's existing customers were, on net, spending more money every month rather than less. The dollar amount leaving through cancellation was smaller than the dollar amount growing through upgrades. This number exists because of how Customer.io integrates. When developers instrument their product with Customer.io's Track API, the platform becomes structural — not a plug-in that can be swapped, but part of how the product knows what to do next. The switching cost isn't a contract or a data hostage; it's the engineering work of re-instrumenting your entire behavioral data layer. That work is real, and most companies don't do it unless they have a serious reason. Customer.io used this structural loyalty, rather than sales pressure or feature checkboxes, as its primary competitive defense for ten years.
5. The $55M raise was not a pivot — it was a choice made from strength
The framing in some coverage was that Customer.io eventually "had to" raise, as if the bootstrapped model finally ran out of road. The evidence does not support that reading. When PSG invested in June 2022, Customer.io was profitable, growing over 70% year-over-year on $20M+ ARR, with world-class retention and a customer base of over 2,000 paying companies. They did not need the money to survive. They took it because the behavioral messaging market was consolidating around well-funded public companies, and because a minority growth equity round from PSG — not a traditional venture firm, not a controlling stake, not a board with exit pressure — let them accelerate on their own terms. Colin spent a decade building a business strong enough that when he finally said yes to outside capital, he could choose who, how much, and under what structure. That is a different story from the one where the bootstrapped company finally runs out of road.
Customer.io is headquartered in Beaverton, Oregon. It was founded in 2012 by Colin Nederkoorn. It serves 7,400+ brands and sent 56 billion messages in 2024. It took its first outside investment — $55M from PSG Equity — in June 2022, ten years after launch.
