Skip to content

Which product requests are renewing customers holding over us?

Link every feature request in Intercom to the account's ARR, renewal date and Jira status. Bring product the requests with the most renewing ARR behind them, and tell each customer where theirs stands before renewal.

Open Querri

What you'll need

Querri (Free trial) to link the exports and build the briefing

Intercom, Jira and Salesforce exports: Step 1 says what each adds

Your renewal window: so every request is weighed the same way

Need help?

If you have any questions, you can request a demo or email our team.

Before we begin

Every CS leader carries customer feedback into the roadmap meeting, and most of it arrives as the requests heard most often. Then a renewal call comes up and the customer brings up the one thing they asked for months ago. Customers give plenty of feedback; using it is the hard part. The requests live in the support inbox, the status in Jira and the renewal dates in the CRM, so lining them up means a spreadsheet nobody keeps current.

This playbook weighs every request by the renewing ARR behind it, checks what product has planned, and gives each CSM the accounts to update.

How it works:

  • • Upload Intercom, Jira and Salesforce
  • • Link every request to an account
  • • Rank requests by renewing ARR
  • • Match each request to the roadmap
  • • Give each CSM the accounts to update

Follow the steps

Open Querri →
1 Step 1:

Upload Intercom, Jira and Salesforce

Three exports, one project:

  • •

    Intercom: conversations tagged feature-request, with the linked Jira issue.

  • •

    Jira (or Productboard): each request's status and target quarter.

  • •

    Salesforce (or HubSpot): ARR, renewal date and CSM for every account.

Add your renewal window in a small sheet, so it's easy to change. Prefer live data? Querri connects to Intercom and Salesforce directly.

Tip: Pull a full year of conversations. A request asked once in October still counts at a December renewal.

  • Intercom requests
  • Jira issues
  • Salesforce accounts
Querri One project
2 Step 2:

Link every feature request to an account and its renewal

Join each request to the account that asked, and count the ones with no Jira link:

Prompt

"Link every feature-request conversation to its account in Salesforce and its Jira issue. How many are linked, how many aren't, and how much ARR renewing in the next two quarters sits behind the linked ones?"

730 of 925 requests are linked to a Jira issue. Accounts renewing in the next two quarters asked 444 of them.

Link every feature request to an account and its renewal
Feature requestsConversations
All, from 329 accounts925
Linked to a Jira issue730
Unlinked, counted only195
Linked, from 168 accounts renewing in two quarters444

Feature-request conversations, July 2025 to June 2026.

3 Step 3:

Rank requests by renewing ARR, not ticket count

Put the two rankings side by side before the roadmap meeting:

Prompt

"Rank the linked requests two ways: by number of conversations from all accounts, and by the ARR of the accounts renewing in Q3 and Q4 that asked, counting each account once."

The most-asked request comes mostly from small accounts and ranks fifth by renewing ARR. SCIM provisioning leads with $1.5M.

Rank requests by renewing ARR, not ticket count
RequestConversations, all accountsRenewing ARR
SCIM user provisioning36$1,496,979
Audit log export to a SIEM25$988,813
Two-way Salesforce sync56$890,650
Conditional approval routing53$844,150
Bulk edit rows in Builder98$636,800

Top five requests by renewing ARR, with their conversation counts from all accounts.

4 Step 4:

Match each request to what product has planned

Check each request's Jira status against the renewal date of every account that asked:

Prompt

"Sort each request into shipped, planned or not planned from its Jira status and target quarter, and show how many accounts renewing next quarter are waiting on each."

The two requests with the most renewing ARR have no target quarter. 11 accounts renewing next quarter asked for something that has already shipped.

Match each request to what product has planned
StatusAccountsARR
Shipped, tell them11$629,575
Planned, share the target36$1,625,450
Not planned, prepare the answer42$2,213,563

Accounts renewing next quarter, by the status of their requests. An account with several requests can appear in more than one row.

5 Step 5:

Produce the renewal briefing

Four numbers for the roadmap meeting, and a list of accounts to update for each CSM.

The narrative Querri writes:

Weighed by renewing ARR, the roadmap conversation changes: the two requests with the most renewing ARR behind them have no date.

What you can create or export:

Produce the renewal briefing
AccountRequestStatus
Pearson-MasonPowerPoint exportShipped, tell them
Parks LLCSCIM provisioningNot planned
Burns, Warren and JamesConditional routingPlanned, Q3 2026
Crawford-HensleyConditional routingPlanned, Q3 2026

Four of the accounts renewing next quarter, with what to tell them.

Walk into the roadmap meeting with the requests renewing customers have raised.

Try it on your own data
Querri for SaaS customer success See how Querri helps customer success teams see every customer, from every system, in one place. See Querri for customer success

Tips for feedback product will act on

Count each account once

One customer can ask for the same thing ten times. Weigh requests by distinct accounts and their ARR, so the loudest account doesn't set the roadmap.

Close the loop before renewal

A request that already shipped is the easiest good news a CSM will ever deliver. Check the shipped list first, every month.

Teach Querri your rules once. Every answer after that follows them.

What counts as a request, which renewals are in the window, how a status maps to planned: say each rule once and Querri applies it to every question on that data.

Show me how

Say it in chat

Settle a rule in conversation and the Librarian records it as a fact under Facts & Rules, attached to the table it governs. Every later question on that data applies it, whoever asks, and every view built afterwards carries it.

Prompt

"A feature request is a conversation tagged feature-request with a Jira Issue filled in, and renewing ARR counts each account once per request. Save that as a rule for the Intercom conversations table."

Or bring the document that already says it

Upload your voice-of-the-customer process or product feedback policy like any other file. Querri files a From a document card in the Inbox with the statements it found, each with its page and exact words; tick the ones to keep and they become facts. The rules this playbook depends on:

  • Feature request: a conversation tagged feature-request
  • Linked request: the conversation's Jira Issue is filled in
  • Renewal window: Renewal Date in the next two quarters
  • Renewing ARR: each asking account's ARR, counted once per request
  • Shipped: Jira status Done, resolved in the last 12 months
  • Planned: In Progress, or a target quarter set
  • Not planned: Backlog with no target quarter
Prompt

"Read our product feedback policy and propose the rules it states about logging requests, linking them to Jira and what counts as planned. I'll review them in the Inbox."

Where the rules reach

A rule is attached to the data, not to one person's chat, so it follows the data everywhere:

  • • Every question asked in chat, by anyone on the team
  • • Every view the Librarian builds on that data
  • • Every step of a project, including the code it writes
  • • Dashboards and scheduled runs, each time they refresh
  • • Claude and ChatGPT, when they ask Querri

You stay in control

Every rule is listed under Facts & Rules next to the data it governs, where you can edit or remove it. Rules from a document wait for your tick in the Inbox, and a Worth remembering card is how Querri offers one it noticed itself. Workspaces and roles decide who can change what. Company-wide rules go in Settings → Customize; the Library is where the rest lives.

The payoff at the roadmap meeting

The meeting starts on the requests with the most renewing ARR behind them, not on the loudest thread. Changing the window is a sentence.

Frequently asked questions

What counts as a feature request here?
An Intercom conversation tagged feature-request. It counts toward a request when the conversation is linked to a Jira issue, the link most teams already keep. Here 730 of 925 feature-request conversations were linked; the other 195 are counted, not guessed at.
What is renewing ARR behind a request?
The ARR of every account that asked for it and renews in the next two quarters, counted once per account per request. An account that asked six times still counts once, so a loud customer can't outweigh a quiet large one.
Why not rank requests by how often they come up?
Because volume follows the number of accounts, not their value. Here the most-asked request, bulk edit in Builder, came 86% from small accounts and ranks fifth by renewing ARR. SCIM provisioning was asked 36 times and has $1.5M renewing behind it.
Does a request from a renewing customer mean it will decide the renewal?
No. It means the request was raised by an account that renews soon, which makes it worth an answer before the renewal call. The page doesn't claim any request causes churn.
How are shipped, planned and not planned decided?
From Jira. Shipped is Done in the last 12 months. Planned is In Progress, or any status with a target quarter. Not planned is Backlog with no target quarter. Change a status in Jira and the next run moves the account to the right list.
What if requests aren't linked to Jira?
Then they can't be matched to a status, and they're reported as a count instead. Linking takes seconds in Intercom when the conversation is tagged; the rules sheet can also map tags to issues for teams that work that way.
Why two quarters and not one?
One quarter leaves product no time to act on what it learns. Two gives a roadmap meeting the chance to commit a date before the second quarter's renewals come up.
What should a CSM say about a request that isn't planned?
Something true and specific: that it's been logged, who else asked, and what the account can do today. The list gives each CSM the request and its status so that answer is ready before the call, not improvised during it.
How often should this run?
Monthly, before the roadmap meeting, on a schedule. The accounts whose request changed status since last month are the ones to update first.