Council Post: The Contract Is No Longer The Finish Line: How B2B Revenue Is Being Rebuilt
Abhishek Yadav is the founder and CEO of Meza AI, an AI customer success platform for B2B SaaS companies.
getty
For most of the software-as-a-service (SaaS) era, the commercial model was refreshingly simple. A company sold a set number of seats; the customer paid for them whether anyone used them; and revenue was booked the moment the contract was signed.
Everything after that signature was framed as protection work, a matter of defending revenue that had already been counted.
That model is now coming apart, and the implication for anyone working in customer success, account management or customer engineering is larger than most of us have fully internalized.
Revenue is no longer captured at signing but must be earned, repeatedly, in the months that follow.
Pricing is moving to where the value actually shows up.
When an AI agent completes work that previously required several employees, headcount stops being a sensible proxy for the value software delivers. The industry is rebuilding its commercial models accordingly.
Deloitte’s 2025 analysis anticipates that traditional pricing will likely shift away from seat-based and subscription licensing toward hybrid approaches blending consumption- and outcome-based models, as SaaS applications become more autonomous and evolve toward a federation of real-time workflow services.
Likewise, Gartner’s 2025 projection that 40% of enterprise applications will be integrated with task-specific AI agents by the end of 2026, up from less than 5% the previous year, tells you how quickly the unit of value is changing underneath us.
Read that as a customer success practitioner rather than an analyst, and the consequence becomes personal. Under a seat model, a dormant account still pays. Under consumption and outcome models, a dormant account pays very little, and an unsuccessful deployment pays almost nothing.
Adoption, therefore, stops being a health metric that predicts renewal and becomes the billing event itself. The distance between whether a customer uses the product well and whether the vendor gets paid will collapse to nearly zero.
The deployment gap is where value is won.
This is also why the post-sale portion of the lifecycle has become the hardest and most valuable part of the business.
A report from MIT’s Project NANDA analyzed more than 300 enterprise AI deployments alongside executive interviews and survey responses. The report found that roughly 95% of pilots delivered no measurable impact on profit and loss.
The authors were explicit that the core barrier was not model quality, infrastructure, talent or regulation. Instead, the issue was, along with a learning gap, that tools failed to retain context, adapt to feedback and fit the specific realities of enterprise workflows. Software can be demonstrated in twenty minutes and can still fail for a year inside a customer’s security model, data stack and internal politics.
That gap is precisely the territory the post-sale organization occupies, and the market is repricing the people who can close it. Job postings for forward-deployed engineers, the technical role that embeds inside a customer’s environment to make systems work on real data, were roughly 729% higher (subscription required) in April 2026 than a year earlier, according to Indeed data reported by Business Insider.
Notice what that role actually is when you strip away the title: customer success with commit access, invented because companies discovered that value realization is an engineering problem as much as a relationship problem.
The lifecycle is becoming one revenue motion.
The practical effect is that the traditional boundaries between our roles are dissolving. The customer success manager owns adoption and outcomes. The account manager owns commercial expansion. The customer engineer owns technical value realization.
However, under consumption and outcome pricing, these are three views of a single number rather than three separate jobs.
A customer who does not onboard properly never consumes, a customer who does not consume never expands, and a customer who never expands caps the vendor’s growth regardless of how strong the original contract looked.
The economics already reflect this. High Alpha’s benchmarking found that companies above $50 million in ARR generate roughly 60% of new ARR from existing customers, with expansion becoming the dominant growth engine beyond about $20 million in ARR.
Meanwhile, Deloitte’s 2026 software industry outlook projects the application software market could reach $780 billion by 2030 on the back of agentic value capture, and then states plainly that reaching those growth levels will require companies to focus on building better customer success strategies.
When a firm of that size names customer success as a precondition for an industry-level growth forecast, the function has stopped being a cost line in the model.
Customer success must be rebuilt.
The uncomfortable part is that this changes the job rather than simply elevating it.
Owning a number means being accountable for it, which requires reading consumption patterns with the fluency a finance team expects, understanding the economics of your own accounts and being able to say early and specifically that a deployment is not producing value rather than discovering it at renewal.
It means treating onboarding as revenue activation rather than administrative setup because, under these models, it literally is. The people who thrive will be the ones who can hold a commercial conversation and a technical one in the same meeting without handing either off.
For those of us who have spent careers explaining why post-sales deserves a seat at the revenue table, the argument has been settled by the business model itself. When customers pay for outcomes, the team that produces outcomes becomes the team that produces revenue.
Forbes Technology Council is an invitation-only community for world-class CIOs, CTOs and technology executives. Do I qualify?