The Setup
CloudSync, a B2B project management tool, had a familiar problem: too many feature requests and not enough engineering capacity.
Sales wanted SSO/SAML — "we're losing enterprise deals without it." Support wanted bug fixes. Marketing wanted a mobile app for demos. The product team had a Notion doc full of feature votes with no clear winner.
The loudest voice in the room changed week to week. Decisions were being made by whoever had the last stakeholder meeting.
They had 6 customer research call transcripts and account data — ARR, health scores, churn risk, contract renewal dates. This is what the integrated analysis revealed.
The Data
What we had:
- 6 customer call transcripts (TechStart, MegaBank, Acme Corp, CreativeAgency, and 2 others)
customer_feature_requests.csv: account data including ARR, feature requested, churn risk score, contract end date, health score
| Feature | Total ARR at Stake |
|---|---|
| SSO/SAML | $513,000 |
| API Rate Limits | $490,000 |
| Reporting Dashboard | $287,000 |
| Mobile App | $73,000 |
The Investigation
Qualitative Coding
Five feature themes emerged from the calls:
- SSO/SAML Request — security requirement, enterprise IT mandate, blocking expansion
- API Improvements — rate limits hitting at scale, workarounds in production
- Reporting Needs — missing dashboards, manual spreadsheet exports
- Mobile App Request — field teams, access on the go
- Complexity Complaints — too many features, steep learning curve
TechStart's call set the urgency immediately:
"We need SSO. Our IT team won't approve any tool without SAML. It's a security requirement."
"If SSO isn't there by September, we'll have to switch."
September was 4 months away. TechStart had an $87K ARR contract. The renewal wasn't a negotiation — it was a countdown.
MegaBank added scale to the same problem:
"SSO... We have 400 users. Managing individual passwords is a security nightmare."
"We could expand CloudSync to more departments."
This wasn't just a retention risk. It was an expansion opportunity blocked by a single missing feature.
Acme Corp's call revealed a different flavour of urgency:
"The API rate limits are killing us. We've built caching layers just to work around it."
"We'd pay for higher tier."
Acme wasn't complaining — they were building workarounds in production and volunteering to pay more for the fix. That's a power user who's invested, and increasingly fragile.
CreativeAgency's call was the contrast:
"A mobile app would be amazing."
No renewal date mentioned. No deal blocking. No workarounds. "Would be amazing" is the language of a nice-to-have.
The Joint Display: Where It Came Together
The Visualization: ARR by Feature
Before building the joint display, a bar chart of the dataset told the first half of the story. Mobile app had the most individual mentions across the customer base. But the ARR behind it was $73K. SSO had fewer mentions — and $513K at stake.
Volume of requests is not a proxy for business impact.
The Integration Matrix: Adding Urgency
The Integration Matrix added the dimension the chart couldn't show — what customers actually said about each feature:
| Theme | arr_usd | churn_risk | renewal_in_6mo |
|---|---|---|---|
| SSO/SAML | Strong positive | High | 2 accounts |
| API Improvements | Strong positive | Medium | 0 accounts |
| Mobile App | Weak positive | Low | 0 accounts |
Hovering into the SSO row surfaced TechStart's exact quote: "If SSO isn't there by September, we'll have to switch."
That's not a feature request. That's a termination notice with a deadline.
The API row showed Acme's workaround memo — they'd built infrastructure to compensate for CloudSync's limitations. That's a loyalty signal worth protecting.
The Mobile row showed CreativeAgency's "would be amazing." Nice. Not urgent.
The Recommendation
Three ranked priorities, each backed by integrated evidence:
Priority 1: SSO/SAML — ship before September $513K ARR. 2 renewals in 6 months. One customer gave an explicit deadline. This also unlocks expansion at MegaBank, where a 400-user deployment is currently blocked by the same missing feature.
Priority 2: API Rate Limit Increase $490K ARR from power users who are actively building production workarounds. The upsell opportunity Acme mentioned is real — but only if the tier they'd pay for actually exists.
Priority 3: Reporting Dashboard $287K ARR. Quality-of-life improvement with no immediate churn risk. Important, but not on fire.
Deprioritised: Mobile App $73K ARR despite the most requests. "Would be amazing" urgency. The request volume is misleading — it reflects broad but shallow preference, not a business-blocking need.
The Outcome
The product team walked into the next sprint planning with a one-page priority list. Not ranked by feature votes. Not ranked by whoever shouted loudest at the last all-hands.
Ranked by ARR at risk, backed by customer quotes, with deadlines attached.
The debate that usually took 3 hours took 15 minutes. Because it wasn't opinion versus opinion anymore.
The qualitative showed what customers were saying — and the urgency behind it. The quantitative showed what each request was worth. The integration turned a feature debate into a business decision.