Revenue on a request shows the customer revenue associated with its voters. MRR means monthly recurring revenue. LTV is the lifetime value supplied for that customer or company.
Keep revenue on your customer records using manual updates, imports, the API or a connection such as Stripe. Open Users & companies to check the people and companies before relying on their totals.
The request's revenue is calculated from its voters. It is not an amount you assign directly to the feature.
Open a request to inspect its customer context, or show revenue columns in the posts table.
For example, if three people from one company vote and the company has $100 MRR, that company's contribution is $100, not $300. This is an illustrative example, not a forecast of revenue from the request.
A request supported by a large customer may deserve attention, but the total does not tell you why they need it or whether they will leave without it. Read the discussion, open customer profiles, and compare segments before using revenue in prioritization.
For a company account:
Use company import to update many accounts at once. You do not need a Stripe subscription record to supply company revenue.
Check these in order:
For a ranking of one company's requests, use Top requested on its company page. The revenue total on a post measures support across its voters, not the needs of only one company.