How software companies are valued

The question every software valuation discussion starts with

Ask a candidate to value a software company and a large share will default to the standard toolkit: comparable companies on EV/EBITDA, a DCF, maybe a leveraged buyout analysis. For a mature, profitable software business, that toolkit still works. For a high-growth software company, and a large share of the ones you will actually be asked about in a TMT interview are high growth, EV/EBITDA quietly breaks. The interviewer wants to see you notice the break and explain why, not silently push through a multiple that does not mean anything.

Why EBITDA breaks down for high-growth software

Start with the mechanics of a software income statement. Gross margins are high, often the highest of any sub-sector in TMT, because the marginal cost of serving one more customer with the same product is low once the product is built. That gross profit does not fall to the bottom line, though. A high-growth software company plows a large share of it back into sales and marketing, hiring salespeople and running demand-generation programs to acquire new customers as fast as possible, plus continued research and development to keep improving the product and fend off competitors. The result is a company that might be growing revenue quickly while showing breakeven or negative EBITDA.

Divide enterprise value by an EBITDA number that is at or near zero and the resulting multiple is either meaningless or wildly distorted by small changes in the denominator. A company with $1 of EBITDA and one with negative $1 of EBITDA might be nearly identical businesses, but a multiple built on that number would treat them as infinitely different. This is not a flaw in the company; it is usually a deliberate choice, because growth compounds and a dollar spent acquiring a customer today can be worth many multiples of that dollar in recurring revenue over the life of the relationship. The market's response is to stop using EBITDA as the denominator and use revenue, or better, annual recurring revenue (ARR), instead.

Revenue and ARR multiples as the working tool

A revenue multiple (enterprise value divided by revenue) sidesteps the EBITDA problem entirely, because revenue is much harder to distort through a reinvestment decision than earnings are. An ARR multiple goes a step further for subscription businesses specifically: ARR is the annualized value of active recurring contracts at a point in time, which strips out one-time fees and other revenue that will not repeat, giving a cleaner read on the durable, recurring core of the business. The specific metrics that separate a high-quality ARR base from a fragile one, retention chief among them, are covered in the SaaS metrics bankers actually use.

Revenue and ARR multiples are not applied uniformly across every company, though, which is the second half of what an interviewer is checking for. A company growing revenue quickly deserves a higher multiple than one growing slowly, all else equal, because a dollar of revenue this year is worth more in a fast-compounding business than in a slow one. That is why practitioners often talk about a growth-adjusted multiple, dividing a company's revenue multiple by its growth rate, as a rough way to compare companies growing at very different speeds on a more even footing. It is a heuristic, not a precise formula, but it is the kind of mental shortcut interviewers expect a TMT candidate to reach for.

The Rule of 40

The Rule of 40 is the framework that ties growth and profitability together into one judgment instead of forcing a choice between them. It states that a healthy software company's revenue growth rate plus its profit margin, commonly measured as free cash flow margin or EBITDA margin, should add up to 40% or more. A company growing quickly with negative margins can still pass; a mature, slower-growing company with strong margins can also pass. What the rule flags as a problem is a company that is neither growing quickly nor generating real margin, since that combination suggests the business has neither an obvious growth story nor an obvious profitability story to justify a premium multiple.

The Rule of 40 is a rule of thumb, not a valuation methodology on its own, and interviewers will sometimes push on that distinction directly: passing the Rule of 40 does not tell you what multiple a company deserves, only whether the growth-versus-margin trade-off it has made looks defensible. A company well above 40% (very high growth, or very high margin, or a strong combination of both) generally commands a premium multiple within its peer group, while a company well below it tends to trade at a discount, but the rule is a screening heuristic, not a plug-and-play valuation formula.

DCF limits, and when the standard toolkit comes back

Why DCF gets harder, not impossible

A discounted cash flow analysis technically still works for a high-growth software company, but the honest caveat an interviewer wants to hear is that a huge share of the implied value sits in the terminal value, years out, built on an assumed steady-state margin the company has not yet proven it can reach. Get the assumed terminal margin wrong by a few points and the entire valuation swings dramatically, far more than it would for a mature, stable-margin business. Good candidates do not refuse to build the DCF; they flag this sensitivity explicitly and often triangulate with a revenue or ARR multiple from comparable companies as a sanity check, rather than trusting the DCF output in isolation.

When EBITDA multiples come back

None of this means EBITDA multiples are permanently irrelevant to software, and interviewers like testing whether you know when the toolkit flips back. Once a software company matures, meaning growth has slowed to a more moderate rate and the company has stopped reinvesting every dollar of gross profit into acquisition, margins expand and EBITDA becomes a meaningful, stable number again. At that point, EV/EBITDA becomes a perfectly reasonable primary valuation approach, the same as it would be for a mature industrial or consumer company. This transition, from growth-stage revenue multiples to mature-stage EBITDA multiples, is also exactly the transition that makes a software company attractive to a financial sponsor for a leveraged buyout, since a sponsor needs stable, predictable EBITDA to underwrite debt against. That connection is covered fully in TMT deal structures: take-privates and carve-outs.

Getting the comparable set and the diligence right

Choosing the right comparable set

A revenue or ARR multiple is only as good as the peer group it is benchmarked against, and picking that peer group is where a lot of the actual judgment in software valuation lives. Software splits broadly into horizontal software, sold to any company regardless of industry (a general-purpose collaboration tool or a broad customer relationship management platform), and vertical software, built specifically for one industry's workflows (a platform built only for dental practices, or only for trucking companies). The two rarely belong in the same comparable set even if their growth and margin profiles look similar, because a horizontal software company's total addressable market and competitive dynamics differ enormously from a vertical software company's, and the market often prices vertical software leaders at a premium precisely because they face less direct competition once they dominate their niche. Within the sub-sector map, it also matters whether a company is best compared to pure infrastructure software (the technical plumbing other software is built on) or application software (the end-user-facing product), since infrastructure software often commands different margin and growth expectations than application software does.

Growth cohort matters just as much as horizontal-versus-vertical. Grouping a company growing quickly with mature, slow-growing peers on a raw revenue multiple, without adjusting for growth, will make the fast grower look expensive and the mature company look cheap in a way that says nothing about which is the better investment. A careful analyst sorts the comparable set by growth rate first, then compares multiples within similar growth bands, which is the practical version of the growth-adjusted multiple concept discussed above.

Common mistakes candidates make

A few errors show up often enough in practice interviews that they are worth naming directly. The first is treating "high revenue multiple" as automatically meaning "overvalued," without checking the growth rate and retention quality behind it; a 15x revenue multiple can be cheap for a company growing very quickly with excellent retention and expensive for a company growing slowly with high customer churn. The second is applying an EBITDA multiple reflexively to any software company because that is the default taught for most industries, without pausing to check whether the company is still in its growth-investment phase. The third is forgetting that stock-based compensation is a real, recurring cost of running a software business even though it is a non-cash expense; excluding it entirely from a profitability picture, the way some companies present their own adjusted metrics, tends to flatter margins in a way a careful analyst should be skeptical of.

How this connects to a stock pitch or deal recommendation

If you are asked to pitch a software company or evaluate whether one is a good take-private candidate, the growth-stage table above is the fastest way to organize your answer. A company still deep in its growth-investment phase is a story about the durability of that growth and the eventual margin the business can reach, best supported by ARR quality metrics. A company that has already matured is a story about cash generation, capital allocation, and how much leverage the business could support, which is exactly the analysis in pitching a tech stock in a TMT interview. Getting the growth stage right first prevents you from applying the wrong framework to the rest of the answer.

Practice question

Why would you value a fast-growing, unprofitable software company on a revenue multiple instead of an EBITDA multiple?

Because EBITDA doesn't mean much for a company at that stage. A fast-growing software business typically has high gross margins but reinvests most of that gross profit into sales and marketing to acquire customers as quickly as possible, along with ongoing R&D, so reported EBITDA often sits near breakeven or negative even though the underlying business is healthy and compounding. Dividing enterprise value by a number that small or negative produces a multiple that's either meaningless or wildly sensitive to small changes in spending decisions the company is making on purpose. Revenue, and specifically annual recurring revenue for a subscription business, is a much more stable denominator because it isn't distorted by a reinvestment choice the same way earnings are. I'd also want to adjust that revenue multiple for growth rate, since a company growing quickly deserves a higher multiple than one growing slowly, and I'd check retention metrics to make sure the recurring revenue base is actually durable rather than churning out the back door as fast as it's being acquired. Once the company matures and growth slows enough that it stops reinvesting every dollar into acquisition, margins normalize and EBITDA becomes a meaningful number again, at which point EV/EBITDA becomes the more appropriate primary approach.

What the interviewer is listening for: That you can explain the mechanism (reinvestment suppressing EBITDA) rather than just stating the convention, and that you know the revenue-multiple approach is stage-dependent, not a universal rule for every software company regardless of maturity.