The LSD All-Hands: The Origin Story of Iterable

The board meeting that ended Justin Zhu's tenure as CEO of Iterable was not supposed to go the way it went. It was April 2022. Iterable had just crossed $100 million in ARR nine months earlier. The company had raised $200 million at a $2.85 billion valuation less than a year prior. Silver Lake had led the round. Viking Global had come in. The brand-name investors who spend their lives watching for exits were watching closely.
Blog post featured image

The LSD All-Hands: The Origin Story of Iterable

Generated by Master Biographer | Source for LinkedIn Content


I. THE HOOK: The Most Unusual Firing in Silicon Valley History

The board meeting that ended Justin Zhu's tenure as CEO of Iterable was not supposed to go the way it went.

It was April 2022. Iterable had just crossed $100 million in ARR nine months earlier. The company had raised $200 million at a $2.85 billion valuation less than a year prior. Silver Lake had led the round. Viking Global had come in. The brand-name investors who spend their lives watching for exits were watching closely. Everything pointed toward IPO, toward liquidity, toward the decade of hard work finally paying out.

Instead, Justin Zhu — co-founder, chief executive, the engineer who had imagined this company into existence from the broken infrastructure of Twitter's notification pipeline — was removed from the company he had built from nothing.

The reason reported by The Wall Street Journal: he had taken LSD before an all-hands meeting.

Silicon Valley, a place whose founding mythology includes Steve Jobs crediting LSD as one of the most important experiences of his life, a place where microdosing became a professional optimization strategy that venture-backed wellness startups were founded to serve — fired its chief executive for taking psychedelics before speaking to his company. It was the kind of story that felt both completely absurd and completely revealing at the same time.

But the story, as it emerged over the following months, was more complicated than that. In November 2022, Zhu filed a racial discrimination lawsuit against the company's investors and board members. He alleged that the LSD story was a pretext. That investors had told him he didn't have "the right face" to be a tech CEO. That Asian stereotypes had been invoked to justify a decision that had already been made for other reasons. That the firing had less to do with drug policy and more to do with a board that had decided the company had outgrown its founder — and had chosen the most humiliating available instrument to make the exit happen.

The suit was filed. The company disputed it. The case wound its way toward whatever resolution it found.

What remained, underneath all the noise, was the company itself: a cross-channel marketing platform built by two engineers who had watched Twitter fail to send the right notification to the right person at the right time, and who decided — in 2013, when the rest of the world was still arguing about whether email marketing would survive — that they could solve that problem properly, forever, and for everyone.

They very nearly did.


II. THE BACKSTORY: What Twitter Taught Them

Justin Zhu and Andrew Boni met at Twitter when Twitter still felt like the internet's central nervous system.

It was 2011, 2012 — the years when Twitter's growth charts still curved upward and the engineering challenges were genuinely hard. Every time someone famous tweeted, the servers melted. Every time a major news event broke, the fail whale returned. The infrastructure was constantly outrunning itself, teams were constantly patching the cracks, and the notifications team — the people responsible for making sure users heard about the things that mattered to them — were living inside one of the core unsolved problems of consumer internet at scale.

The problem was deceptively simple to state and brutally complex to solve: how do you send the right message to the right person at the right time, across multiple channels, at a scale of hundreds of millions of users, without alienating people who don't want the message, while reliably reaching the ones who do?

Twitter was sending notifications. But they weren't personalized notifications. They were batch operations — the same email to millions of accounts, the same push trigger for everyone who met a crude behavioral filter, the same timing logic regardless of what each individual user's history suggested about when they were actually online. It worked well enough at the scale Twitter needed. But it worked the way a jackhammer works — it got the job done and it destroyed everything around it.

Zhu and Boni saw the gap.

They left Twitter. Andrew Boni had done a stint at Google before Twitter, giving him a different lens on data infrastructure — the kind of engineering rigor that Google had applied to search indexing and ad targeting was not being applied to email marketing. The people in charge of sending emails were using tools built for a pre-smartphone era. The people in charge of push notifications were operating in a separate silo from the people sending SMS. In-app messages were someone else's problem. Web push barely existed as a channel.

Nobody was looking at the whole journey. Nobody was looking at the customer as a unified entity moving through multiple touchpoints, needing different messages at different moments, and deserving something better than a batch.

In 2013, Zhu and Boni founded Iterable.

They went through Y Combinator. They raised $1.2 million in seed funding in early 2015 from a small group of angels and institutional backers who were willing to bet on two infrastructure engineers trying to fix a problem that most people in marketing didn't know was broken.

The pitch was not "we are building a better email tool."

The pitch was: we are building the infrastructure that lets you treat every customer as an individual, across every channel you use to reach them, from a single place, with data flowing in real time.

That was a harder sell in 2013 than it sounds. Most companies were still using Mailchimp to send newsletters and Twilio to send one-off SMS messages and some home-built system for push notifications. The idea that these channels should be unified, orchestrated, and driven by behavioral data — that you should know that the user opened the email but didn't click, then waited 48 hours and abandoned their cart, and that those two facts should combine to trigger a very specific push notification at the precise moment when re-engagement probability was highest — that idea required a level of infrastructure investment that only a handful of companies could afford to build.

Iterable's pitch was: what if every company could afford to build it, because we already built it for them?


III. THE GRIND: Building Cross-Channel for the Companies Nobody Else Served

The company that Iterable spent its first years competing against was not Braze. It was not Klaviyo. It was not Customer.io.

It was Salesforce Marketing Cloud.

Salesforce Marketing Cloud, and Marketo, and Eloqua, and the rest of the legacy marketing automation stack had been built for a world of batch communications and email newsletters. They were powerful, expensive, deeply integrated with enterprise procurement processes, and almost entirely useless for the kind of real-time, behavior-driven, cross-channel orchestration that modern consumer apps needed.

A company like DoorDash, or Redfin, or Wolt — companies where the customer relationship was mediated through a mobile app, where the customer's behavior was generating thousands of data events per session, where the right message sent at the right moment could convert a churning user back into an active one — could not use Salesforce Marketing Cloud in any meaningful way without a team of consultants, a six-figure implementation budget, and a year of calendar time.

These were the companies Iterable built for. Not Fortune 500 enterprises with IT departments and eighteen-month procurement cycles. The modern digital consumer brands: subscription services, fintech apps, online marketplaces, media platforms, consumer apps of every description.

And crucially — because Zhu and Boni were engineers — Iterable was built to be both developer-friendly and marketer-usable.

This was rarer than it sounds.

Most marketing tools of the era lived in one of two worlds: either they were built for developers (powerful, API-first, requiring engineering resources to actually use) or they were built for marketers (visual, drag-and-drop, but sitting on top of a data model so rigid that anything genuinely complex required a workaround). Iterable threaded the needle. The APIs were clean enough that engineers could trust them. The interface was visual enough that marketers could build journeys without writing a line of code. The data model was flexible enough to ingest events from Segment or Mixpanel or a custom pipeline without forcing customers into a proprietary schema.

This is what made the early traction possible. Engineers approved Iterable because it wouldn't become a maintenance nightmare. Marketers loved Iterable because they could actually do things without filing tickets and waiting for the engineering queue.

The company crossed $1M ARR in September 2015. $10M ARR by November 2017. By the time the Series C closed at $50 million in March 2019, Iterable was serving companies like Zillow and Care.com and building toward the next tier of enterprise. The Series D at $60 million followed later that year. Viking Global Investors and Harmony Partners believed in what they were seeing.

The product kept expanding. Email. Push notifications. SMS. In-app messages. Web push. Each channel added was another reason for a growing company to standardize on Iterable rather than manage a patchwork of vendors. The platform became the nervous system — the place where all the signals about customer behavior converged and all the messages went out.


IV. THE BREAKTHROUGH: $2.85 Billion and the Braze Question

In June 2021, Iterable announced it had closed a $200 million Series E led by Silver Lake at a $2.85 billion valuation.

The number that mattered most was not the $200 million. It was the $100 million ARR milestone that the company reached in October 2021, a few months after the round closed. That meant the valuation — set at the peak of the growth-multiple era — implied roughly 25x revenue at the time of the round. Silver Lake was betting not on what Iterable was but on what it was becoming.

The company that served as the constant benchmark was Braze.

Braze had gone public in November 2021, also on the strength of cross-channel customer engagement infrastructure. Also founded by engineers. Also targeting the consumer app ecosystem. Also promising personalization at scale across multiple channels.

The two companies were not identical. Braze had originated in mobile push notifications, building from a mobile-first thesis. Iterable had originated in email and expanded into mobile. Braze had gone through a longer go-public process, had a mature investor relations function, and had built the kind of financial rigor that public markets require. By 2021, Braze's market cap on listing day exceeded $7 billion.

The question that hung over Iterable's board discussions was obvious: if Braze could do $7 billion, why couldn't Iterable?

The IPO window that both companies were aimed at — the extraordinary growth multiples of 2021, when SaaS companies traded at 30x, 40x, 50x ARR — would not stay open indefinitely. Both companies knew this. The race was implicit even if it was never stated explicitly.

Iterable was at $115 million in revenue in 2021 when the $2.85 billion valuation was set. Braze was at roughly $238 million. The size gap was real. But Iterable's growth rates were strong, its net revenue retention was reportedly healthy, and the cross-channel marketing category was still in early innings.

And then, in April 2022, Justin Zhu was fired.

Whatever the full truth of why — drug policy violation, board fatigue with the founder, racial bias in the boardroom, or some combustible combination of all three — the institutional reality was clear: the company lost its CEO nine months before it would have needed to file an S-1, if the IPO timeline that many assumed was approaching had actually been approaching.

The market for high-growth SaaS IPOs collapsed in 2022. Braze's stock, listed at $65, fell below $30 by mid-2022. The valuation environment that had made $2.85 billion feel like a reasonable number for a company with $115 million in revenue became a historical artifact within eighteen months.

Iterable did not go public. It kept building.


V. THE AFTERMATH: Andrew Boni, Nova, and the Question Nobody Wants to Answer

Andrew Boni became CEO after Justin Zhu was removed. He had been there from the beginning — co-founder, president, the other half of the Twitter-origin story. If Zhu had been the more visible figure, the face of the company at conferences and in interviews, Boni had been running the internal machinery: the go-to-market engine, the sales team, the operational infrastructure that turned a good product into a revenue-generating business.

Under Boni, Iterable continued to grow. The company reached $200 million ARR by end of 2023, representing 38% year-over-year growth from $145 million in 2022. That is not a company in distress. That is a company finding its footing and continuing to compound. The valuation was reset to approximately $2 billion by 2024 — down from the $2.85 billion peak, a correction that reflected the broader re-pricing of private SaaS multiples rather than any particular failure of the business.

The company opened a Lisbon office. It signed a strategic AWS partnership. It achieved Gartner Magic Quadrant Challenger status in 2023, a signal that the enterprise buying cycle was validating Iterable at a level of institutional credibility that the earliest cross-channel marketing tools had never achieved.

And then there was the AI question.

In 2024, Iterable launched 37 AI-powered features. It introduced Nova — a marketing AI agent designed to automate what they called "moments-based marketing" in real time, making decisions about which message to send, through which channel, to which customer, at which moment, without a human in the loop. The company reported that 90% of clients had adopted the MCP Server integration for agentic AI workflows. Customers using the GenAI tools were reporting 44% conversion gains. Wolt reported 60% revenue growth in a single month using Iterable's predictive goals.

But the AI question — the one that Boni and every other MarTech CEO has to sit with quietly — is not whether AI can help marketers work faster.

The question is what happens to the marketing platform business when AI writes the messages, AI decides the timing, AI picks the channel, AI generates the segments, and AI runs the journeys.

When every step that used to require a marketer using software becomes a step that an AI agent executes autonomously, the nature of the business changes. The value is no longer in the canvas where the marketer paints the campaign. The value is in the data that trains the AI to make good decisions. The value is in the customer profile — the thousand behavioral signals that accumulate over a customer's lifetime with a brand. The value is in the infrastructure that sits underneath the AI and makes its decisions actionable.

Which means Iterable's destiny, like every marketing platform's destiny, is to become either a data company or a commodity workflow.

The company seems to know this. The strategic push toward data warehouse integration — connecting natively with Snowflake, building CDP-like capabilities, positioning "Activate Data" as a core product module rather than an afterthought — reads as a deliberate bet that the future of the category is in the fat data layer, not the interface where the marketer drag-and-drops a journey.

Iterable was built by engineers who understood that the hard problem was never the email. The hard problem was always the data behind the email — who gets it, when, why, and what happens next.

Twelve years later, they are still solving that problem. Under different leadership. In a different market. Against different competitors. But the same problem.

The notifications are still imperfect. The journey is still ongoing.


5 THINGS NOBODY KNOWS ABOUT ITERABLE

1. The founding insight came from Twitter's notification failures, not from a marketing problem.
Justin Zhu and Andrew Boni were not marketers frustrated by their tools. They were engineers watching Twitter fail to send personalized notifications at scale and thinking: this problem has an engineering solution and nobody is building it. Iterable was never primarily a marketing company — it was an infrastructure company that chose marketing as its application layer. That distinction explains everything about its developer-friendliness, its API-first architecture, and why it competes so effectively against platforms built by people who started with the marketer's workflow instead of the data model.

2. The LSD firing story was legally contested as a cover for racial discrimination.
The WSJ story about Justin Zhu being fired for taking LSD before an all-hands meeting became one of the most-read tech business stories of 2022. It was astonishing, absurd, and perfectly calibrated for viral distribution. What got far less coverage: Zhu subsequently filed a racial discrimination lawsuit alleging that investors told him he didn't have "the right face" to be a CEO, that Asian stereotypes were explicitly invoked in conversations about his leadership, and that the drug policy violation was a pretext for a decision the board had made for other reasons. The case raises questions that Silicon Valley is structurally reluctant to examine about which founders get to keep the companies they build.

3. At $2.85 billion, Iterable was valued at roughly 25x revenue — and then the market corrected 40% before anyone had to defend that number publicly.
The Series E valuation was set in June 2021 at the precise peak of growth-multiple mania. Braze went public that November and saw its stock cut in half within a year. Iterable's private valuation followed suit, resetting to approximately $2 billion by 2024. The company grew its revenue from $115M to $200M during this period — meaning the business was legitimately improving while the valuation contracted. The gap between what a company is worth on paper in a bull market and what it is actually building in the background can be enormous. Iterable is a case study in the difference.

4. Iterable competes against Braze, but they were built from opposite directions.
Braze started in mobile push notifications and expanded into email. Iterable started in email and expanded into mobile. This sounds like a trivial origin distinction, but it shapes everything — the data model, the buyer relationship (mobile teams vs. email teams), the integration priorities, the way the platform handles events. Companies shopping between them are often not comparing features; they are comparing philosophies about what the center of gravity of a customer relationship is. Braze says it's the mobile moment. Iterable says it's the unified behavioral signal across every channel.

5. The AI wave threatens to commoditize the exact interface that made Iterable valuable.
The thing Iterable sold — the visual journey builder, the drag-and-drop campaign canvas, the interface that made sophisticated orchestration accessible to marketers who couldn't write code — is exactly the thing that AI agents are making unnecessary. If Nova and its successors can construct the entire campaign journey from a natural language prompt, the canvas becomes invisible. The race Iterable is now running is not against Braze or Klaviyo. It is a race to own the customer data layer before the interface disappears beneath it. The company that wins marketing automation in the AI era is the one that owns the data, not the one that owned the drag-and-drop. Iterable knows this. That is why "Activate Data" is now a core module, not an integration footnote.

Ready to see a real-time data integration platform in action? Book a demo with real engineers and discover how Stacksync brings together two-way sync, workflow automation, EDI, managed event queues, and built-in monitoring to keep your CRM, ERP, and databases aligned in real time without batch jobs or brittle integrations.
→  FAQS

Syncing data at scale
across all industries.

a blue checkmark icon
POC from integration engineers
a blue checkmark icon
Two-way, Real-time sync
a blue checkmark icon
Workflow automation
a blue checkmark icon
White-glove onboarding
“We’ve been using Stacksync across 4 different projects and can’t imagine working without it.”

Alex Marinov

VP Technology, Acertus Delivers
Vehicle logistics powered by technology