The support team typically appears in the budget under COGS as a service delivery cost. This accounting treatment shapes how support is managed — minimize cost, maximize ticket throughput, maintain acceptable resolution times. This is optimizing the wrong variable.

The SaaS companies that treat customer support as a revenue engine see it differently. They measure support on revenue outcomes, not cost metrics.

The revenue impact of world-class support:

Retention impact. Customers who have a great support experience in year one retain at significantly higher rates than customers who had poor experiences. At $100K ACV with 80% retention, improving year-one support quality from "adequate" to "exceptional" could be worth $20K per customer in additional lifetime value.

Expansion signal identification. Support conversations are the highest-fidelity signal of customer health and expansion readiness. A customer who has asked how to do something that's currently in your paid tier is an expansion conversation waiting to happen. A customer who's been hitting a workflow limit for three months is an upsell conversation your account team doesn't know about.

Reference quality improvement. Customers who had exceptional support experiences when things went wrong become better references than customers who had smooth experiences from the start. The "they fixed our problem fast and professionally" story is more persuasive than the "nothing ever went wrong" story.

The operational shift from cost center to revenue engine:

Route expansion signals from support tickets to account team or CSM. When support identifies that a customer is doing something manually that your paid tier automates, that's a lead.

Track NPS by support experience, not just product experience. Customers who had support interactions have a different NPS distribution than those who didn't. Understand the impact.

Invest in first-response quality, not just first-response speed. Fast wrong answers are worse than slightly slower right answers.

Support is your customer relationship layer. Build it accordingly.