A full week of reflection: what building a support-focused product taught me about running support

There's something ironic about building a product for customer support teams while simultaneously running customer support for that product.

You get very honest feedback very fast.

Some things I've learned from being on both sides:

1. The gap between what founders think customers care about and what customers actually care about is enormous.

I've had customers write 400-word emails about something I thought was a minor UX detail. And say nothing about something I considered a major feature.

You cannot predict what will feel important to your customer. You can only listen.

2. The first reply sets the entire tone of the relationship.

A first reply that shows you read carefully, understood the problem, and took it seriously — that customer will be patient with you for the rest of the conversation even if resolution takes time.

A first reply that feels templated or misses the point — that customer will be critical of every subsequent message regardless of quality.

The first 60 seconds of a support relationship defines the next 60 days.

3. "Closing" a ticket and "resolving" a problem are genuinely different things.

I've closed tickets where I knew the customer wasn't satisfied. It felt wrong every time. But volume pressure wins.

The companies that resist volume pressure on individual tickets — that take the extra message, the extra 10 minutes — tend to have significantly better retention numbers.

4. Support is the clearest mirror your product has.

Every week of doing support taught me something about the product I didn't know before.

Not from surveys. Not from analytics. From someone trying to use it and hitting a wall.

If I had to give one piece of advice to any founder building a product: do your own support for longer than feels necessary. You will learn things you cannot learn any other way.

What's the most valuable thing you've learned from doing your own support?