← All logs
Investors · 7 min read

What UiPath's $400 Million Burn Year Teaches Founders and Investors About Being Right for the Wrong Reasons

Emrah ·

Daniel Dines set a growth target his own board called crazy, then hit a number so far off his cash projections that UiPath had to lay off ten percent of its staff. Both the founder and the board were right. That is exactly the problem worth studying.

The Story

Daniel Dines spent eight years bootstrapping a company in Bucharest that could not find product-market fit. The turning point came almost by accident: an email requesting a demo led him to send three engineers to India for three months to work inside a business process outsourcing company. What they found there became UiPath, and it eventually became one of the defining companies in robotic process automation, a category UiPath did not just enter but effectively invented.

By 2017, UiPath was doing somewhere between 35 and 45 million dollars a year in revenue. Board member Luciana Lixandru remembers the moment Dines proposed the plan for 2018. Her expectation, and the board's, was that doubling that number would already be a great year. Dines had a different number in mind: 200 million dollars, close to six times where the company had started. He wanted to be twice as large as his competitors on revenue alone, not just competitive with them.

The company closed 2018 at roughly 175 million dollars. It missed Dines's own target, but it landed at more than double what the board had called a great outcome, and it was enough to let UiPath define the RPA category before any competitor could catch up. For a moment, the story reads as simple vindication: the founder saw further than the board did.

Then came 2019. The company had projected around 150 million dollars in cash burn to sustain that growth trajectory. The actual number came in near 400 million. UiPath had to cut 10 percent of its staff to bring the business back into line. Dines has since described this as one of the hardest moments of his career, saying there is no tougher feeling than telling someone the company has to part ways with them.

The Idea

The idea at the center of this story is not "founders should ignore their boards" or "boards are always too conservative." It is narrower and more useful than that: an aggressive growth target and a disciplined burn plan are two separate decisions, and winning the argument for one does not automatically produce the other.

Dines was right that the market was bigger than his board's projections assumed, and he proved it by capturing the category before anyone else could. But the same conviction that let him set an audacious revenue number was not matched by an equally rigorous model of what that growth would cost to sustain. The board's original number, doubling to roughly 70 or 90 million, was not reckless caution. It was a reasonable extrapolation from the data the board actually had. Both sides were reasoning correctly from what they knew, and the gap between what they knew and what turned out to be true is exactly where the 250 million dollar burn overshoot lived.

How Founders Should Read This

The lesson for founders is not to tone down ambition. It is to treat an aggressive growth target and its burn plan as two decisions that require the same level of rigor, made at the same time, not one followed by the other as an afterthought.

A founder who sets a bold number and stops there has only done half the job. The natural next question, the one a board is entitled to ask and a founder should ask first, is what the cash position looks like if the target is hit, what it looks like if the company lands at 70 percent of the target, and which specific monthly metric would trigger a hard stop before the burn compounds into a crisis. Dines had the first kind of conviction in abundance. What UiPath was missing in 2018 was the second kind: a burn model built with the same seriousness as the growth model.

This matters most for founders running lean teams where finance is still improvised. The instinct to defend a big number in the room is natural. The habit of pairing that number with a stress-tested cash scenario, before anyone in the room has to ask for one, is what separates a founder who gets lucky from one who gets it right on purpose next time.

How Investors Should Read This

For an investor, the useful takeaway is not that boards should push back harder on ambitious targets. Lixandru's initial reaction was not wrong given the information in the room at the time, and pattern-matching against past growth rates is exactly what a board should do with the data it has.

The gap was somewhere else. The board debated the target itself extensively but never demanded the burn scenario that should accompany it. A target of 200 million dollars is not, on its own, a risk. A target of 200 million dollars with no modeled answer to "what does our cash position look like the month this becomes real" is a risk that a board can catch before it becomes a headline.

This reframes what a red flag actually looks like in a board meeting. It is not the size of the number a founder proposes. It is the absence of a matching financial scenario for that number, presented and interrogated with the same energy the growth target itself received. A fund underwriting a company on the power law logic that one outsized winner can return the whole vehicle still needs that winner to survive its own growth curve, and burn discipline is what keeps a category-defining year from turning into a preventable layoff.

Where the Two Views Collide

Picture the board meeting in 2017 again, before anyone knew how 2018 would actually turn out. Dines is confident the market is bigger than the data shows. The board is confident that doubling is already an excellent outcome given everything they can measure. Neither side is bluffing, and neither side is being unreasonable.

What makes this moment hard to navigate in real time, not in hindsight, is that both positions can be true simultaneously and still produce a bad outcome together. The founder's read on market size turned out to be accurate. The board's implicit assumption that growth this fast could be financed within a modest burn envelope turned out to be wrong. Neither of those two facts contradicts the other, and neither one alone would have caused the crisis. It was the absence of a shared, explicit answer to what happens financially if the aggressive scenario comes true that let a correct growth call turn into an avoidable layoff two years later.

The founders and investors who handle this well do not resolve the tension by picking a side, ambition over caution or caution over ambition. They resolve it by insisting the ambitious number and its financial twin get built and defended together, in the same meeting, before either one gets approved on its own.

The Takeaway

Dines was right about the size of the opportunity. The board was right about the risk sitting inside that opportunity. Both of those things happened at once, and the company still had to lay off a tenth of its staff to find out where the gap between them actually was.

If your team has recently agreed on an aggressive growth number, the useful next step is not to revisit the ambition. It is to ask whether anyone has actually written down what the cash position looks like the month that number comes true, and what specific signal would tell you to pull back before it does.


Source: Daniel Dines, "UiPath ft. Daniel Dines: From Bootstrapping in Bucharest to One of Software's Biggest IPOs," Crucible Moments (Sequoia Capital) — sequoiacap.com/podcast/crucible-moments-uipath

Past editionsLondonBerlinIstanbulAmsterdam
LegalTerms & Privacy
© 2026 Prompt Network Inc.
Prompt

New York is open. AI, 16 to 17 November.

Apply now