Prioritizing Requests using customer and company data

Review the Requesters, companies, revenue, and CRM opportunities behind a Request to judge its demand.

Written By Markus Palm

Last updated 38 minutes ago

Overview

Customer and company data helps you see who needs a Request and why it matters to them. Look beyond the number of Requesters to understand the companies represented, their feedback, and the commercial context.

Connect customer and company data

Keep customer profiles and company information current through user identification and data syncing. This can include the customer's company, monthly spend, and other custom attributes your team uses to group customers.

For connected CRM data, use the relevant integration guide. Opportunities are available from supported HubSpot and Salesforce integrations, subject to your access permissions.

Review the customers behind a Request

Open the Request's Requesters list. Review the people and companies associated with it, their feedback, and the latest activity. Expand a company to see its contacts.

Several contacts from one company can support the same Request. Each adds context, but together they count as one company. Managing Requesters explains how to add people, correct associations, and export this list.

Company revenue

Use Revenue to compare the monthly spend associated with Requests. The request-level revenue total counts each associated company once, even when several people from that company are Requesters. Teammates who are Requesters do not add revenue.

Note: Revenue shows the existing customer relationship. It does not measure revenue that building the Request will create or retain.

Linked opportunities

Where CRM opportunity data is available, use the link control in the Requesters list to link a deal or opportunity to the Request, then review the linked deals alongside the original feedback.

Compare demand across customer groups

Use filters and saved views to focus on the customer groups relevant to your decision. You can then order Requests by Requesters, Revenue, or Opportunity, where available.

For each promising Request, check:

  • Breadth: How many different customers or companies share the need?

  • Evidence: What problem are they trying to solve?

  • Importance: How strongly do customers need it, and how often?

  • Context: Does the Request matter to your target customers or an active opportunity?

Review the linked Insights for the original context and the Impact score for customer ratings collected through Impact questions.

Tip: Use these signals to inform your team's value and effort scores.

FAQs