If you run, advise, or build a product inside a SaaS business today, this is what to do about the new AI landscape despite all the noise. This guide is organized around the six questions a leader has to answer.
On February 3, 2026, roughly $285 billion left software, financial, and asset-management stocks in a single day, on the release of an AI tool, not on any change in reported numbers. The dispersion told the story: LegalZoom fell 20% and Thomson Reuters 16%, while Salesforce and ServiceNow fell about 7%. The market did not sort on "is this priced per seat?" It sorted on "can the model replace the need for people to do this work?".
For two decades software helped a human do the work. What is emerging does it. We call it Software-as-a-Worker: it changes what you sell, who you sell it to, and the budget you compete for. The labor budget is an order of magnitude larger than the software budget, so the move rightward is a prize, not only a threat.
Incumbents are not doomed. They are trapped. Every asset you hold has a liability welded to its back.
Score seven questions 1 to 3 (pricing exposure, agentic readiness, data position, data rights, outcome accountability, org insulation, talent exposure) for 21 points. That lands you in one of four positions: Exposed (7-10), more fragile than the financials show; Instrumented (11-14), the most common and most deceptive, because the assets look strong so urgency reads low; Dual-Engine (15-18), a separate unit already running; or AI-Native (19-21), where the product works and the sales motion needs to catch up.
Before any plays, four legitimate routes exist to execute your play: Build (fund from operations, keep the equity), Buy (acquire an AI-native Engine 2), Partner (be the data and execution layer under someone else's agent), or Harvest (run for cash and sell while the multiple holds). The route choice has a clock: Harvest and Buy both price off a seat-revenue multiple that is compressing.
Stage the move, do not switch it: platform fee, then metered on the work, then outcomes only where attribution is clean and exposure is capped. Clear the permission to use your data first.
Design the tool, not the screen: agent-callable functions, event streams, a memory layer, a closed feedback loop. A data-infrastructure investment first, a model investment second.
Sell a digital worker to the executive who owns the outcome, against headcount and BPO budgets. Retrain the force, realign comp off seats, build the proof apparatus.
Engine 1 funds; Engine 2 builds, reports to the CEO, measured on execution not legacy KPIs. Separation only works if complete: distinct metrics, protected funding, ring-fenced talent.
There is more than one clock, and they run at different speeds. The revenue clock is slow and contractual (18 to 36 months to reprice at renewal). The talent clock runs out first: your seats are locked in, your people are not. The competitive and capability clocks you do not control at all.
The old metrics measure the era you are leaving: DAU, feature adoption, seat count. Watch six internal signals quarterly instead. The first four tell you how fast the new engine is coming up; the last two, how fast the assets funding it are running down.
A view that cannot be disconfirmed is not worth much, so we watch our own falsifiers:
If none of your signals ever move against you, you are almost certainly measuring the wrong things.
The assets that make the crossing possible are the ones you already own. The job is not to escape the old model; it is to take apart its liabilities without breaking the assets attached to them. Two must survive: your data, the fastest-moving asset and the one you cannot buy back, and your people, the only asset that can resign.
Your strongest people leave for AI-native challengers you cannot out-pay, so stop competing on comp and compete on what they cannot get there: real domain problems, real customers, and a decade of proprietary data to build against. The quieter risk is the stayers, frustrated on the core and staying only because the market is soft. Gallup put the share of US employees watching or seeking at 51%, even as actual turnover held steady: deferred attrition, on a clock you do not control.
The answer is a talent contract, its commitments declared to the whole company as much as possible rather than whispered in the halls:
In every platform shift, the value goes to whoever builds the trains, not the rails. As an incumbent you already own the track, the stations, and the passengers. The only question is whether you put a train on it before someone else runs one down your line.
The mistake we watch companies make is not moving too slowly on AI features. It is moving fast on features while leaving the business model, the architecture, and the org chart exactly as they were. That produces a Type 1 company: busy, full of demos, and structurally identical to the thing being disrupted. It is SaaS with better marketing. It is not SaaW.
The six questions are the whole method, in order: know what is changing, know where you are exposed and where you are strong, choose your route and run the plays it calls for, respect that the clocks move at different speeds, instrument the transition, and protect the assets that make it possible. The incumbent who reaches the far side with its data, its trust, and its bench intact is the one the challengers were never able to become.
It is in your customers' headcount, and it will trickle down; revenue is usually the last thing to move. Your advantages are real but have a half-life. Both things run down on clocks you do not control: the data that starts flowing through someone else's agent, and your talented people who understand it and can walk out at any time for other opportunities. The SaaS company incumbent who reaches the far side of this shift with its data, its trust, and its bench intact is the one that wins and defended its turf from challengers.
We'll email you the PDF and send new briefs as they publish.