Outliers can move the market's measuring stick

A business milestone is useful only while it separates one stage of development from another. For cloud software companies, $100 million in annual recurring revenue once signalled that a product had escaped the experimental phase, won a substantial customer base and developed a credible route toward a public offering. The number was never a guarantee of quality, but it gave founders, employees and investors a common reference point.

By 2024, that reference point was losing power. A small group of cybersecurity companies reached extraordinary scale so quickly that investors began judging the rest of the software market against exceptional cases. The result was not simply a higher revenue target. It changed how much growth capital appeared available, how efficiency was discussed and which companies could expect an attractive exit.

This is a recurring feature of capital markets. Success attracts money, money finances faster expansion, and the most visible expansion becomes a new benchmark. Yet the benchmark may describe the winners rather than the underlying population. Boards that copy it without examining product economics can force a sound company into an unsuitable race.

The 2024 cloud market raised the threshold

Steven Rosenbush reported the shift in a September 19, 2024 article in The Wall Street Journal. The report said that $100 million in annual recurring revenue had previously been enough to place many cloud companies on a path toward large late-stage rounds and perhaps an initial public offering. By 2024, some institutional investors were looking closer to $300 million.

The reason was visible in the performance of Wiz and Rubrik. Wiz had moved from $100 million in recurring revenue only 18 months after its 2020 launch to about $500 million. Rubrik reported $919.1 million in subscription annual recurring revenue for the quarter ended July 31 and expected to cross $1 billion during its fiscal year. These were not ordinary growth curves.

The shift occurred while higher interest rates made future profits less valuable in present terms and while customers concentrated spending among fewer software providers, especially companies linked to security and artificial intelligence. A startup could therefore grow well in absolute terms and still appear slow relative to a small set of category leaders.

The report focused on the United States venture and public-market environment, but the management problem is broader. Every subscription company must decide whether a market benchmark reflects customer value, investor fashion or a combination of both.

Annual recurring revenue is a forecast packaged as a metric

Annual recurring revenue, commonly shortened to ARR, estimates the annualised value of active recurring contracts at a point in time. It helps operators compare subscription businesses whose accounting revenue may lag contract activity. Sales teams can see the installed base, investors can estimate scale, and managers can track expansion and churn without waiting for a full reporting year.

But ARR is not a standard accounting measure. Definitions vary. A company may annualise monthly subscriptions, include committed future capacity or assume that contracts expiring within the next 12 months renew on existing terms. Two businesses can publish the same figure while carrying different contract lengths, cancellation rights, usage exposure and collection risk.

The metric is most useful when accompanied by a bridge. Management should show opening recurring revenue, new customers, expansion, contraction, churn and currency effects. It should explain which products qualify and reconcile the total with recognised subscription revenue. Without that discipline, a rapidly rising number can hide weak retention or generous assumptions.

ARR is therefore a leading indicator, not a substitute for cash, accounting revenue or profitability. It describes the current recurring base under stated assumptions. It does not prove that customers will renew, that gross margins will remain high or that acquiring the next customer will create value.

Why $100 million stopped carrying the same signal

A milestone loses meaning when too many different business qualities sit behind it. During an era of inexpensive capital, $100 million in recurring revenue could imply access to another round even if a company still spent heavily on sales and product breadth. Investors expected future growth to repair current inefficiency. When the cost of capital increased, the same revenue base had to support a more demanding case.

At the same time, the strongest cloud companies made $100 million look like an intermediate checkpoint. Their growth suggested that a true category leader could reach several hundred million dollars before entering public markets. Late-stage investors seeking large returns preferred companies capable of producing a sufficiently large offering and liquid public stock.

That logic can be rational for the investor and dangerous for the operator. A fund with a large portfolio needs a few outcomes big enough to return the fund. It may therefore reject a company that could become durable and profitable but not enormous. The rejection says something about the fund's return model, not necessarily about the quality of the company.

Founders should distinguish a financing threshold from an operating threshold. The former indicates what a particular capital provider needs. The latter indicates whether customer value, retention and contribution economics support continued expansion. Confusing the two can make management spend to satisfy an investor screen rather than build the right business.

Isometric infographic of four rising cloud platforms representing higher recurring-revenue thresholds
When a few companies climb unusually fast, the milestone used to identify scale can rise for the entire market.

The benchmark contains survivor bias

The Wall Street Journal article cited an estimate that fewer than one in 1,000 enterprise software companies backed by leading venture firms reach $100 million in annual revenue. That denominator matters. Wiz and Rubrik provide lessons, but their trajectories are not a normal planning assumption. They combine market timing, experienced founders, established investor networks, urgent security demand and access to large customers.

Benchmarking becomes misleading when management observes only companies that survived. The market does not display with equal prominence the businesses that spent aggressively, missed product-market fit and disappeared. Nor does it show how many founders preserved more ownership by choosing slower growth. A visible winner supplies a possible path, not the probability of achieving it.

A useful peer set should match sales motion, contract size, product complexity, gross margin, customer concentration and market maturity. A security platform selling to global enterprises cannot be compared mechanically with a vertical application serving small businesses. Both may report recurring revenue, but their acquisition costs, implementation burden and expansion opportunities differ.

Boards should ask what must be true for the outlier path to work. Is customer urgency comparable? Can the product support several adjacent use cases? Are founders able to recruit an enterprise sales organisation? Does the investor group have enough reserves to fund the next stage? The answers turn admiration into a testable strategy.

Growth efficiency becomes the second axis

When capital was abundant, companies could defend heavy spending by pointing to a large market and fast recurring-revenue growth. In a tighter market, growth needs an efficiency context. One common lens is the burn multiple: net cash consumed divided by net new recurring revenue. The lower the ratio, the less capital the company uses to add each dollar of recurring business.

The WSJ report described earlier periods when some startups spent $4 or $5 to acquire $1 of new annual recurring revenue. By 2024, some investors wanted a ratio closer to $2 for every new dollar. Neither number is universally correct. A company entering a new market or building a major product platform may rationally invest ahead of revenue. A mature company with stable products should usually demand greater efficiency.

The ratio also needs clean inputs. Cash burn can change because customers pay annually in advance, because hiring slips or because a company capitalises development work. New recurring revenue can reflect acquisitions or pricing changes. Management should analyse cohorts and unit economics rather than celebrate a single blended number.

A board dashboard for sustainable cloud growth

  • Recurring revenue growth separated into new customers, expansion, contraction and churn.
  • Gross retention and net retention by customer size and product cohort.
  • Gross margin after hosting, support and third-party infrastructure costs.
  • Sales payback period and customer acquisition cost by channel.
  • Net cash burn, runway and the burn multiple over several quarters.
  • Product adoption, implementation time and concentration among the largest accounts.
  • Capital required to reach the next operating milestone under base and downside cases.

Together these measures show whether growth compounds or merely consumes funding. A company can accept a temporarily high burn multiple when retention, product adoption and gross margin indicate that future cohorts will repay the investment. It should be cautious when spending rises while those underlying signals weaken.

Capital quality matters as much as capital quantity

The WSJ article argued that strong, committed investors helped the outliers. This is more than a reputation effect. A company pursuing enterprise customers may need years to build a broad feature set, security certifications, integrations and a global sales force. Investors with sufficient reserves can support that development through a weak financing market.

Good capital also brings governance. Experienced directors can separate temporary underperformance from a broken thesis, help recruit executives and introduce potential customers. They can finance an acquisition or bridge a delayed public offering. A crowded cap table of investors with short time horizons may create the opposite effect, pressing for incompatible outcomes.

Terms matter. A high valuation accompanied by strong liquidation preferences can reduce flexibility if the next round is lower. Debt can extend runway but add covenants and repayment pressure. Strategic investment may create distribution opportunities while complicating relationships with competing platforms. The largest cheque is not automatically the most resilient funding package.

Founders should evaluate whether an investor can support the company in three scenarios: faster growth than expected, a two-year funding drought and a strategic sale below the last private valuation. The answer reveals whether capital is aligned with the operating plan or only with the headline valuation.

Wiz combined speed with market architecture

Wiz was founded in 2020 by a team that had already built and sold a security startup, then worked inside Microsoft on cloud security. That history supplied technical credibility, knowledge of enterprise procurement and a network of investors. The company could approach large customers early and shape the product around complex environments rather than climb slowly from a small-business base.

Its financing demonstrated the scale of the opportunity. In a May 7, 2024 company announcement, Wiz said it had raised $1 billion at a $12 billion valuation. The company described capital for talent, product expansion and strategic acquisitions, while arguing that customers wanted consolidated security platforms instead of sprawling tool stacks.

This platform logic helps explain why revenue could expand rapidly. A product that discovers risk across multiple clouds can enter through one security need and broaden into additional workflows. Large customers create sizable contracts and reference value. The same model, however, requires constant investment: the platform must cover changing cloud services, threats and development practices.

Wiz should not be reduced to a lesson that every startup must spend faster. Its path depended on founder experience, urgent demand, enterprise access and investors willing to finance expansion. The transferable lesson is to identify a distribution or product advantage strong enough to justify acceleration before raising the burn rate.

Rubrik showed scale and the cost of reaching it

Rubrik offered a second kind of evidence. The company had entered public markets in April 2024, giving investors more detailed financial information than a private startup normally provides. Its growth showed strong demand for cyber resilience and data security, while its losses illustrated the investment required to build a large subscription platform.

In its September 9, 2024 quarterly release, Rubrik reported subscription annual recurring revenue of $919.1 million as of July 31, up 40% year over year. Total quarterly revenue increased 35% to $205 million, while 1,969 customers contributed at least $100,000 each in subscription recurring revenue.

The release also defined its measure. Rubrik annualised active subscription contracts and assumed contracts expiring in the next 12 months renewed on existing terms. That disclosure is essential: it lets readers understand why ARR can lead accounting revenue and where renewal assumptions enter the figure.

Scale did not eliminate the need for efficiency. Rubrik highlighted improvement in its subscription ARR contribution margin, a nonstandard measure designed to compare the recurring base with the costs and operating expenses supporting it. The broader lesson is that a billion-dollar recurring base and a credible path toward sustainable economics must be evaluated together.

Abstract cloud business engine connecting product infrastructure, customers, recurring revenue and capital burn
Recurring revenue compounds only when product, customers and capital form a controlled system rather than a one-way spending pipeline.

The middle cohort faces the hardest financing question

Most cloud companies are neither category-defining outliers nor obvious failures. They may have loyal customers, improving products and tens of millions of dollars in recurring revenue, but lack the speed now expected by late-stage funds. Their decision is not simply whether to grow. It is which form of growth preserves the most strategic value.

Jeremy Burton, chief executive of Observe, told the Journal that fundraising remained difficult despite a strong year. Observe raised a $115 million Series B round in March 2024 and expected recurring revenue, then around $21 million, to exceed $30 million by year-end. The company needed engineers, features and sales capacity to compete in observability, yet some investors wanted very tight spending efficiency.

This tension is real. Underinvesting can leave a platform too narrow for enterprise buyers. Overspending can force the next financing at punitive terms. Management needs a milestone plan tied to customer evidence: which integrations unlock deals, which product gaps cause losses, how much sales capacity can be productive and when existing cohorts repay acquisition cost.

A company that cannot meet the new venture benchmark still has choices. It can narrow its market, improve retention, move toward profitability, partner with a larger platform, seek growth equity with different return expectations or sell strategically. The best choice maximises durable enterprise value, not resemblance to the fastest peer.

A difficult exit can erase a celebrated valuation

Private valuations are negotiated financing prices, not cash that shareholders can spend. They depend on security preferences, investor rights and an expectation about the next transaction. If growth slows and capital becomes scarce, the value available to common shareholders can fall much faster than the headline valuation suggests.

The Journal used Lacework to illustrate the risk. The cybersecurity company had been valued at $8.3 billion in 2021 and later reached roughly $80 million to $100 million in annual recurring revenue. By 2024, a possible sale to Wiz was being reconsidered and was expected, if completed, at a fraction of the earlier private valuation. The episode showed how a company can build meaningful revenue yet fail to satisfy the scale and financing assumptions embedded in its last price.

Management cannot control market multiples, but it can preserve options. Longer runway reduces the need to accept the first offer. Clean intellectual-property ownership and auditable metrics make diligence easier. A diversified customer base supports strategic value. Realistic internal valuations prevent compensation and retention plans from depending on an outdated number.

Customer value must anchor the growth plan

Recurring revenue is an outcome of recurring customer value. A cloud company earns durable growth when its product becomes embedded in an important workflow, delivers measurable benefit and remains easier to renew than replace. Sales incentives can accelerate bookings, but they cannot manufacture long-term necessity.

The strongest plan starts with renewal reasons. Security customers may value risk visibility, faster incident response and simpler tool consolidation. Observability customers may value shorter outages and lower infrastructure costs. Those outcomes should appear in product telemetry, implementation milestones and executive reviews. Expansion should follow demonstrated use rather than contract pressure alone.

Pricing also affects the quality of the recurring base. Seat-based, usage-based and platform pricing distribute risk differently between provider and customer. Heavy discounts can increase reported ARR while weakening future expansion. Complex consumption pricing can grow quickly in good conditions and contract when customers optimise workloads. The metric needs interpretation through the commercial model.

Scenario planning is better than chasing one threshold

A board should not organise the company around a single revenue number borrowed from the market. It should build several internally consistent paths. An acceleration case can show the hiring, infrastructure and capital required to capture urgent demand. A balanced case can preserve strong growth while improving efficiency. A resilience case can extend runway through slower sales and constrained financing.

Each case needs trigger points. If customer acquisition cost rises, retention falls or implementation capacity tightens, management should know which spending changes follow. If expansion exceeds plan and sales payback remains healthy, the company can add capacity with evidence rather than optimism. Scenario discipline makes speed a decision instead of a habit.

The financing strategy should match these paths. Enough cash to reach a meaningful milestone is more valuable than a large round that merely supports the current cost base. The milestone might be a new product adopted by existing customers, a defined gross-margin improvement, positive free cash flow or a recurring-revenue level that opens a different investor pool.

The right benchmark explains economics, not prestige

Wiz and Rubrik changed expectations because they demonstrated that cloud security platforms could reach enormous recurring scale. Their performance is strategically relevant, but it should sharpen questions rather than dictate identical answers. The most useful comparison reveals which capabilities create customer demand, which costs are temporary and which advantages compound.

For investors, the lesson is to compare recurring-revenue definitions, cohort quality and capital requirements before ranking companies by size. For founders, it is to choose capital whose return model fits the attainable market. For employees, it is to understand that option value depends on preferences, dilution and exit terms as well as the last funding price.

The market's rising threshold can improve discipline when it exposes weak retention or uncontrolled spending. It becomes destructive when a company abandons a viable strategy merely to resemble an outlier. Sustainable software businesses are built through repeated customer value, sound economics and financing that leaves time for both to develop.