GTMcraft Plays · The Cost To Serve Play

Your worst-fit accounts eat the capacity you would point AI at; total the true cost, then exit, contain, or invest.

Play visual

cost-to-serve-signal.html

The 90-second read

Every team carries an account it privately knows should be cut. It never gets cut, because its true cost hides across four budgets nobody totals. The ACV sits proud in the CRM while the cost eats it in silence. Meanwhile your team has finite hours, so every hour on a money-loser is stolen from an account that would grow. Total the cost, rank by contribution, and make one call per account.

• The money-loser survives because its full cost is never on one line.
• Cost to serve hides in CSM hours, custom builds, escalations, and roadmap.
• Capacity is finite, roughly 200 accounts per person per year.
• Your three most expensive accounts are rarely your three biggest.
• Exit, contain, or invest is a per-account call, not a purge.

Read time: about 5 minutes. First step runnable Monday morning.

The #1 move this week

List your three most expensive-to-serve accounts next to their ACV, not your three biggest.

The biggest accounts get the reviews. The costly ones hide, because their cost lives in four different budgets and nobody sums them. Put CSM hours, engineering builds, escalations, and roadmap slots on one line next to the revenue. The accounts costing more than they pay become obvious the moment you total them.

Start here: pick your ten largest accounts by support and CSM load. Total the four cost budgets next to ACV for each. You need CRM data, support tickets, and one focused afternoon.

Ignore this week: do not buy a tool to add capacity. Free the capacity you already burn on money-losers.