Your Product Cycle Is Dead. Revenue Just Hasn’t Gotten The Memo
In military intelligence, one of the easiest mistakes is confusing activity with momentum. A unit can be moving, communicating and burning through ammunition — and still be losing ground.
Software markets work the same way.
Revenue can keep climbing long after a product has stopped creating the market it sits in. By the time the dashboard turns red, the strategic battle is usually already lost.
I started thinking about this seriously in late 2021, not long after launching my first fund. Public software multiples were falling apart while private prices kept behaving as though nobody had told them the war had started.
For close to two years, every slowdown got blamed on the capital cycle — rates were higher, investors had rediscovered that cash flow matters, customers were suddenly examining budgets like devout auditors. All of that was true. It also missed something more fundamental: some of these categories weren’t just being repriced. They were aging out.
A recent Invest Like the Best conversation with David George, who runs growth investing at Andreessen Horowitz, brought this back into focus for me. The capital cycle sets what investors are willing to pay. The product cycle determines whether the technology is still creating real new value for customers. Those aren’t the same question, and conflating them is how good investors miss the turn.
Investors tend to be decent at spotting the start of a product cycle — a breakthrough makes something possible that wasn’t practical before, early customers put up with rough edges because the improvement is dramatic, incumbents explain patiently why the category doesn’t matter, and TAM slides start multiplying like rabbits.
The end is harder to see. It never arrives with a press release titled “Our Product Cycle Is Now Over.” Financial results can stay attractive for years after the underlying dynamic has already shifted.
Here’s my working definition: a product cycle is ending when incremental innovation stops creating materially more value for the customer, and competition shifts to bundling, procurement and price.
The category can keep growing. The leader can keep taking share. But the thesis has changed — and investors who don’t notice are fighting the last war with the last war’s playbook.
Revenue Is Usually The Last Signal To Move
In my book, Decoding the Software Landscape, I argue that financial metrics are symptoms of deeper strategic forces, not the forces themselves. Growth, retention, margins — they tell you what’s happening, rarely why.
That gap matters most as a cycle matures. A company can post strong net revenue retention because existing customers keep adding seats or modules, even as new-logo growth quietly slows because almost every plausible buyer already owns the category. The blended number still looks fine. Underneath it, the greenfield is disappearing.
So here’s the question I’d put in every growth-stage memo: what share of new ARR comes from first-time category adoption, versus vendor replacement, versus expansion of an existing account?
Early in a cycle, customers usually aren’t replacing anything — they’re leaving spreadsheets, email or some manual process behind for a new category of software altogether, and every new logo expands the market. Think about the first wave of cloud data warehouses: a customer adopting Snowflake generally wasn’t choosing between two similar cloud products, they were escaping the operational weight of an on-prem system. Or Figma — the breakthrough wasn’t a nicer toolbar, it was browser-native, multiplayer design at a moment when emailing files back and forth was still considered normal.
Later in the cycle, one company’s growth increasingly comes out of another company’s pocket. A vendor can still post 30% growth as an excellent consolidator — but that growth isn’t coming from category creation anymore, it’s coming from winning share in a knife fight.
Video conferencing is a good illustration. Zoom pulled millions of organizations into a behavior they’d never adopted at that scale. Today a new video deal is far more likely to be a renewal, a consolidation or a displacement among Zoom, Teams, Meet and Webex. The market is still huge. Where the growth comes from has changed completely.
Cybersecurity works the same way. A company selling the first real defense against a new attack surface is creating budget. A mature endpoint vendor signing its thousandth customer is more likely replacing an incumbent or attaching a module to an existing platform. Both show up as ARR. Only one is opening new ground — and that distinction should show up in the multiple, not just the footnotes.
Listen To Why The Customer Buys
There’s a diligence question I keep coming back to because it’s uncomfortable in a useful way: what can this product do that the next-best alternative fundamentally cannot?
Early in a cycle, customers usually have a crisp answer — this is the only product with the performance, accuracy or scale to do the job, and they’ll forgive a dozen missing features because the core capability doesn’t exist anywhere else. Salesforce let you run CRM in a browser instead of maintaining another on-prem box. Twilio gave developers an API for something that used to require a telecom negotiation. Shopify let a merchant stand up a real online store without hiring anyone to build a commerce stack. Nobody bought any of these because the buttons were nicer.
As the cycle matures, the answers get softer. Customers like the interface, or the support team, or the fact that procurement already has a vendor number for this company. None of that is nothing, but it’s a sign the product frontier is closing.
I think of this as the half-life of differentiation. If a company ships something important and it takes competitors two years to catch up, the frontier is probably still open. If every meaningful feature shows up across the market within a quarter or two, whatever rents existed are already gone.
Generative AI is a live version of this experiment right now. A model or product that does something genuinely nobody else can — much better reasoning, dramatically lower latency, reliable completion of a hard workflow — can drive real adoption. But when that same capability turns up in five competing products before the enterprise even finishes its security review, the feature was real and the moat mostly wasn’t.
You also hear it in the vocabulary. Early buyers talk about adopting, building, deploying. Mature-category buyers talk about consolidating, standardizing, cutting vendors. A CIO who says “we need a vector database because our architecture can’t support this” is describing category creation. A CIO who says “we have four observability vendors and want one bill” might still hand someone a very large check — but that check is funding consolidation, not discovery, and it prices very differently.
“Good Enough” Is A Powerful Weapon
Early in a cycle, the best technology usually wins because the gap between products is enormous. Over time the gap closes — standards emerge, integrations get built, features get copied — until the difference between an excellent product and a merely good one no longer justifies another contract and another security review.
That’s when bundling gets dangerous. A startup with a product customers rate a 9 out of 10 runs into an incumbent offering a 7 or 8 inside a contract the customer already signed. The startup wants to argue about the missing points. The customer would rather skip another six-month procurement cycle. They haven’t stopped caring about the problem — they’ve just stopped being willing to pay a premium for the last bit of product quality.
Slack versus Teams is the textbook case. Slack genuinely redefined how teams communicate. But once chat, meetings, calendar and identity all sit inside the same Microsoft tenant, Teams doesn’t need to win every feature comparison — it just needs to be good enough and already there. Dropbox went through something similar: the folder that magically synced everywhere was a real breakthrough, until sync became a standard feature of Microsoft 365 and Google Workspace and the question shifted from “does it work” to “why would we approve a second vendor for this.” Dropbox’s push into search and organization through products like Dash isn’t a random pivot — it’s what a company does when it needs a new layer of value sitting on top of a core that’s become table stakes.
None of this means incumbents win automatically. An incumbent entering a category is often a sign the category matters, not that it’s dying. The real question is whether the incumbent’s version has become good enough to make the standalone product economically unnecessary. In software, “good enough” has quietly buried a lot of technically superior products.
When “Platform” Starts Appearing In Every Slide
When a category leader starts talking constantly about platforms, adjacencies and new personas, there are two explanations, and in practice it’s usually some mix of both: either the company earned the right to expand into a genuinely larger market, or the original product can’t absorb any more capital at attractive returns and management is looking for somewhere else to point it.
You see this pattern everywhere. Zoom has stretched from meetings into phone, contact center and AI. CrowdStrike has gone from endpoint to a full security platform. Shopify has moved from storefronts into payments, fulfillment and capital. Each expansion might be the right strategic call. But it forces a separate question for the investor: how strong is the original beachhead on its own, and how much of today’s valuation is actually a bet on management’s ability to build the next act.
Docusign is a good case study. E-signature created a genuine product cycle by moving contract execution off paper. As the category matured, the opportunity moved from signing itself toward the broader agreement lifecycle. In fiscal 2026, Docusign’s total revenue grew 8%, while its Intelligent Agreement Management product grew from 2.3% of ARR to 10.8% — and reached 12.6% by April 2026. None of that proves e-signature is exhausted, or that IAM becomes the next growth engine. It does tell you where the center of gravity in the growth story is moving.
Salesforce did the same thing from sales automation into service, marketing and data. Adobe did it from boxed software to subscriptions and cloud workflows. Intuit did it from tax prep into payroll, payments and lending. A strong core can fund a genuinely great second act — or it can be used to paper over a first act that’s stalling. The word “platform” on a slide doesn’t tell you which one you’re looking at; the math does.
Which is why I’d ask management directly: if you stopped launching new categories today, what would the core product’s growth rate be three years out? If the answer is 8% against a company-wide target of 25%, you’re no longer underwriting product-market fit — you’re underwriting management’s ability to invent, launch and sell an entirely new business inside the old one. That’s a much harder thing to get right than a slide with the word “platform” on it seventeen times would suggest.
New Technology Can Reopen An Old Battlefield
One idea I keep coming back to from Decoding the Software Landscape is the difference between the terrain and the architecture sitting on top of it. Businesses will always need to store information, protect assets, run workflows and make decisions faster — that need is the terrain, and it doesn’t go away. The architecture on top of it does: on-prem moved to cloud, manual integration moved to APIs, and human analysis is now moving toward machine-assisted, increasingly autonomous decision-making.
That’s the mechanism by which a mature category reopens: the object being managed changes.
Identity is a clean example. Workforce identity has always been built around employees — someone joins, gets permissions, uses some apps, eventually leaves. AI agents break that model. An agent can act autonomously on someone’s behalf, hold application permissions, exist for ten minutes, and take more actions in a day than a human does in a month. Microsoft’s Entra Agent ID now issues distinct identities and governance for agents specifically, because the old framework genuinely doesn’t fit. Identity didn’t disappear as a category — its underlying object changed, and that reopened the whole product cycle.
You can see the same shift starting in software development, where the first generation of AI coding tools suggested lines of code to a developer sitting at a keyboard. Newer coding agents take an issue, read the repo, write and test the code, and open the pull request themselves. The unit being sold is starting to shift from “assist one developer” to “complete a task” — and that can reopen testing, code review, security and infrastructure, all markets that looked completely settled.
Accounting may be next. The ledger isn’t going anywhere, but if an agent can continuously classify transactions, investigate anomalies and prepare reconciliations instead of a human doing it once a month, the product cycle around that workflow effectively restarts. Payments are moving the same direction — Stripe now documents agentic-commerce flows where an AI agent discovers a product, completes checkout and transacts on someone’s behalf. Payments aren’t new. Autonomous buyers with no human in the loop raise entirely new questions about permissioning, fraud and limits that the old rails weren’t built for.
Customer service is going through the same rewrite. A chatbot that pulls up an article is a feature. An agent that reads the account, changes the reservation, issues the refund and logs what it did has changed what’s actually being purchased — from software that helps an agent to work that gets completed without one.
A mature category can become an early market again whenever a new technological primitive changes the unit customers are actually consuming.
A Three-Front Test For Every Investment Memo
Instead of asking whether a market is “early” or “late,” I look at three separate frontiers:
The capability frontier — how many economically important problems remain technically unsolved?
The adoption frontier — how many customers or workflows haven’t adopted the category yet?
The consumption frontier — can each existing customer consume meaningfully more over time without the company just adding headcount to sell to more logos?
The best setup is when all three are still open.
Cloud infrastructure shows why adoption alone can mislead you: nearly every large enterprise already runs on the cloud, so the logo frontier looks mature — but AI training, inference and data pipelines keep expanding how much compute and storage each of those same customers consumes. The workload frontier is nowhere near closed.
Cybersecurity is a version of the same story. Endpoint protection is broadly deployed, but the surface being protected keeps growing — laptops, cloud workloads, APIs, identities, now AI agents. A company can sit inside an old, familiar budget line while actually attacking a brand-new consumption object.
The opposite case is a large market where all three frontiers are closing at once: most customers already have a solution, the competing products are converging, and usage is capped by a relatively fixed number of seats. Seat-based software for a stable headcount is the plain example — once every employee who needs it has it, growth has to come from price, cross-sell or taking share. Compare that to usage-based infrastructure, where one customer can create ten times the workload without hiring ten times the people. Two companies can show identical growth this year and have completely different growth physics underneath it. A large TAM slide doesn’t fix that; it just makes the slide look bigger.
Late-Cycle Does Not Mean Uninvestable
None of this means mature categories are bad investments — it means the early-cycle playbook, and the early-cycle multiple, stop applying.
Adobe is a good reminder of what a mature-category winner looks like. Creative software was never a hidden category, but Adobe built extraordinary economics through subscription pricing, file-format lock-in and a professional ecosystem nobody wants to leave. Microsoft has repeatedly turned mature categories into durable cash flow through distribution and bundling. Intuit benefits from trust and workflow depth in categories that businesses don’t casually swap out on a whim. None of these are category-creation stories anymore — they’re mature-market power stories: switching costs, distribution efficiency, pricing discipline. The returns can still be excellent. The source of the return is just different, and it should be underwritten differently.
Early in a cycle you’re underwriting product superiority and technology risk. During scaling, you’re underwriting execution and distribution. Late in a cycle, you’re underwriting consolidation, pricing power, capital allocation and whether management can credibly build an Act II. All four can work. They require different assumptions about how long growth lasts and what’s actually defending it.
In the 3X Framework from Decoding the Software Landscape, this sits inside “Nail The Target” — before deciding how a company should attack a market, you first need to know what kind of target the market has become: still being created, still expanding, or already being consolidated.
The most dangerous phrase in growth investing is “it’s still growing.” The better question is always what’s causing the growth. When customers pick a company because it does something real that nothing else can, the cycle is probably still alive. When they pick it because of the bundle, the existing relationship or the lower price, the cycle is probably ending — the income statement just hasn’t gotten the memo yet.