# Customer requests report by company spend and renewal risk

> Review requests in a company-level report that includes spend, renewal risk, and opportunity value instead of treating every vote like the same customer.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/customer-requests-report-by-company-spend-and-renewal-risk/
- Source: [help.canny.io](https://help.canny.io/en/articles/9246592-the-customer-requests-report)
- GrowthDex source hub: [Canny Help Center: The Customer Requests report](/sources/canny-help-center-the-customer-requests-report-help-canny-io/)
- Last checked: 2026-05-29
- Rarity: rare
- Budget: medium
- Channels: Product, Customer Success, Sales
- Stages: account prioritization, renewal risk, revenue context, voice of customer


## Why this can grow

A raw board answers what people asked for. It does not answer which account the team should care about first. Canny's customer requests report is useful because it recasts the queue around company context. The report can surface spend, renewal risk, renewal date, account owner, vote priority, and opportunity value, provided the company data is synced in. That gives product, sales, and success a shared way to see whether a request is tied to expansion, churn prevention, or a low-stakes curiosity. It pushes the conversation away from vote theater and toward account economics.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. For conversion, I would strip the test down to one promise, one proof point, and one next step. Confusion kills good demand. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where customer requests report by company spend and renewal risk can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Product and Customer Success channel.
3. Use the evidence from help.canny.io to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Canny's customer requests report prioritizes feature development by company and can include company spend, renewal risk, renewal date, account owner, vote priority, and opportunity value when the data is synced through the SDK, API, or integrations such as HubSpot, Salesforce, Intercom, Zendesk, or Segment.

## Adjacent tactics in the same lane

- [Canny renewal date and account owner view before roadmap promise](/growth-ideas/canny-renewal-date-and-account-owner-view-before-roadmap-promise/) - same source, 3 shared channels
- [Segment-filtered voter list with opportunity value](/growth-ideas/segment-filtered-voter-list-with-opportunity-value/) - 3 shared channels, 2 shared stages
- [Trial feedback board with frontline teams before full rollout](/growth-ideas/trial-feedback-board-with-frontline-teams-before-full-rollout/) - 3 shared channels, 1 shared stage
- [Private roadmap portal with domain-based access](/growth-ideas/private-roadmap-portal-with-domain-based-access/) - 3 shared channels

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The feedback queue should carry revenue before volume](/blog/the-feedback-queue-should-carry-revenue-before-volume/) - product ops, feedback systems, revenue prioritization

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.