Customer Success Is the Best Product Research You Aren't Reading

5 MINS

Before I was a Product Manager, I spent a year as a Customer Success Manager at a B2B SaaS company. I thought, at the time, that I was taking a break from "real" product work. I was wrong. CS turned out to be the most concentrated source of product truth I have ever sat next to — and once I moved back into product, I started asking my CS counterparts the questions other PMs were too busy to ask.

This blog is for PMs who don't yet realise the goldmine sitting next to them.

What CS sees that PMs don't

A PM and a CSM look at the same product through different windows.

The PM sees: usage analytics, NPS averages, the loud feedback in user interviews.

The CSM sees: which steps customers actually skip, which workarounds they invent, which onboarding question gets re-asked at month four, and which feature they swore they wanted but never opened. That second view is gold. It's the closest thing a B2B PM has to a live ethnography of the product. The reason most PMs miss it is mundane: CS doesn't write it down in product-friendly language. PMs need to do the translation themselves.

Three habits I picked up from CS that made me a better PM

When I moved back to product, I kept three habits from my CS days that quietly changed how I work:

Read the renewal notes before the roadmap. A renewal note from a CSM is more honest about your product than any quarterly review. If a customer is staying despite the product, that's information.

Watch the workarounds. A workaround is a feature request the customer didn't bother to file because they assumed you wouldn't build it. Workarounds are the closest thing to honest demand you'll ever see.

Ask "what did you wish was already true?" This question, asked of a CSM, usually produces the cleanest backlog item I've heard all month. PMs ask "what should we build?" CSMs hear "what would have stopped that ticket?" — which is the better version of the same question.

The pattern most PMs miss

In B2B SaaS, the loudest customer is rarely the most important. The most important customer is the one who is quietly succeeding without you noticing — because they are about to renew, expand, and refer. PMs who only listen to the loud accounts end up building features for the customers who are about to churn anyway.

The CSM, sitting between both, knows the difference. Use them.

A short note on building this bridge

If you're a PM and you don't have a recurring 30-minute slot with a senior CSM, build one. Not a status meeting — a research meeting. Bring three questions, no agenda, and write down what surprises you. The first three sessions will rewrite your roadmap.

A few guardrails I follow:

Keep it small. One CSM is a focus group. Three is research. Twelve is a survey, and everyone hates surveys.

Take their words, not their solutions. CSMs propose features. Don't ship the feature; ship the underlying job.

Close the loop publicly. When a CS-sourced insight ships, name it. CS will trust you with more.

Closing thought

Most PMs treat customer success as a downstream team that "consumes" what product builds. The PMs who treat CS as an upstream research team end up building products customers actually like. The flip is small. The compounding is enormous.

Lean Six Sigma Made Me a Better PM (Even Though I Don't Use the Charts)

Lakshmi skipped presentations and built real AI products.

Lakshmi Prasanna was part of the March 2026 cohort at Curious PM, alongside 17 other talented participants.