What breaks in a 90-day SaaS-to-agents transition?

THE SHORT ANSWER

Three things break in the first 90 days, and none of them show up in the strategy deck. The CFO conversation is not actually done even when you think it is, because the comp set and board narrative tone were never agreed, only the trough math. The lead customer legal review takes 8 weeks, not 4, because the unit definition triggers legal, security, and procurement questions in sequence. And the maintenance team's morale drops sharper than expected because stability is not a story people want to tell. Each is solvable, but together they cost you a quarter of execution speed if they catch you by surprise.

This is grounded in a field report from the first 90 days of a $30M ARR SaaS-to-agents transition. Per-seat pricing, 110 percent NRR, 80 percent gross margin, an agent-native product in private beta with five lead customers. The trough was pre-sold to the board at roughly 12 points, from 80 percent down to 68 percent bottoming at month 12, recovering to 72 percent by month 24. The strategic frame held. Three operational things broke anyway.

The three breaks

The CFO conversation was not done. Agreement on the trough math is not agreement on the comp set, the leading indicators, the board narrative tone, or the level of detail the board expects. All five are separate sub-agreements. We surfaced the comp-set disagreement during board-deck drafting instead of a quarter earlier, and it cost a week of prep. The fix was moving to weekly 30-minute CFO working sessions instead of quarterly check-ins.

Legal review of the lead customer contract took 8 weeks, not the 4 I budgeted. The contract had to define the unit: a resolved support ticket where the customer does not escalate within 48 hours. The customer's legal team had questions about escalation, their security team about how we measure it, their procurement about the dispute mechanism. Each was reasonable. The accumulated reasonableness was four extra weeks. Pre-share the template with their legal team in week one, not week six, and have a senior product engineer on call for security.

Maintenance team morale dropped sharper than modeled. Renaming the team to Migration Engineering and tying their bonus to migration tool adoption turned it around by day 90.

What was still unsolved at day 90

The dispute mechanism was unproven at volume: fewer than 30 disputes handled total, with 200 to 500 customers coming in Wave 2. Two of 20 Wave 1 strategic accounts declined and started competitor evaluations, roughly $1.8M in ARR at risk. And the agent's quality bar was not yet where it needed to be for un-white-gloved mid-market migration.

What to do about it

If you are about to start a transition like this, do five things before day one. Surface every CFO sub-agreement explicitly in week one. Pre-share the lead customer contract template in week one. Frame Maintenance as Migration Engineering from the start, not after the morale drop. Budget 8 weeks for lead customer legal review. And plan for 10 to 15 percent Wave 1 attrition so it does not surprise you. Write down which of these three breaks you have actually staffed for before your next planning cycle.

SOURCES

THE LONG VERSION

RELATED ANSWERS

Last reviewed 2026-07-31 · 3 min read