The support conversation that changed our pricing (a case study in listening)

Eight months ago, a support conversation led directly to us restructuring our pricing tier.

Here's exactly what happened.

A customer emailed asking: "Do you have anything between your basic and pro plans? Basic doesn't do enough but pro is more than I need and more than I want to pay."

Standard response would have been: "Unfortunately we don't have a middle tier at this time, but I can share some details on what's included in each plan."

Instead, I asked a follow-up question: "What specifically does basic not do enough of, and what in pro do you feel you wouldn't use?"

Their answer was detailed. And when I looked back at our support archive, I found 11 other customers who had expressed almost identical confusion in the past 3 months.

Twelve customers had all hit the same gap in our pricing — and only one had been asked to explain it clearly.

We restructured our pricing within 6 weeks.

Conversion rate from trial to paid improved. Churn in the first 90 days dropped. Average revenue per user went up because customers were on the right plan.

The trigger: one support conversation where someone asked a follow-up question instead of giving a standard answer.

The lesson: support conversations contain product and business decisions waiting to be made. Most teams are too focused on closing the ticket to notice them.

Have you ever had a support conversation that directly changed your product or business? What happened?