How to analyze revenue by product from CRM data
Group won deals by product, then compare revenue, win rate and cycle length. Judge by revenue per opportunity, not total revenue, with a worked example.
Short answer
Product-level revenue analysis means grouping your won deals by product in your CRM and reading three numbers together: revenue, win rate and sales cycle length. Judge products by revenue per opportunity, not total revenue. Your best-selling product is rarely the one that deserves the budget.
What is product-level revenue analysis?
Product-level revenue analysis means taking the deals closed in a given period, grouping them by product or product family, and reading three numbers side by side for each one: total revenue, win rate and average days to close.
The analysis really asks three questions at once: what you have (which product brought in what), what you spent (how many opportunities and days it took), and what you will get (where the same money returns the most next quarter).
Total revenue on its own misleads. A product can bring in a lot of money while consuming three times the opportunities and twice the calendar, which means it is eating your team instead of feeding it.
What CRM data do you need for this?
Four fields are enough. Most companies have the first three and are missing the fourth.
- Product or product family: what the deal was opened for.
- Amount: the value of the deal.
- Outcome: won, lost or still open.
- Open and close dates: so you can measure cycle length.
If those fields are empty in your CRM or your ERP, the analysis cannot run. You have to produce the data first, and the way to do that is not more forms for your reps, it is pulling the data out of the sales conversation itself.
How do you calculate revenue by product?
Three steps:
- List every deal closed in the last 12 months, grouped by product.
- Sum the won amounts per product, then divide won deals by total deals to get the win rate.
- Divide won revenue by the total number of opportunities, not just the won ones. That is revenue per opportunity, and it is the number you decide on.
A worked example. A company with three products, last 12 months:
- Product A: 40 opportunities, 12 won (30%), average 120,000. Revenue 1,440,000. Revenue per opportunity 36,000. Cycle 30 days.
- Product B: 25 opportunities, 10 won (40%), average 60,000. Revenue 600,000. Revenue per opportunity 24,000. Cycle 20 days.
- Product C: 60 opportunities, 9 won (15%), average 200,000. Revenue 1,800,000. Revenue per opportunity 30,000. Cycle 75 days.
By total revenue, Product C wins. By revenue per opportunity, Product A wins, and it does it in less than half the time.
Which product should get the marketing budget?
The budget goes to the product with high revenue per opportunity and a short cycle. The reason is simple: marketing does not produce revenue, it produces opportunities. The sales process converts them. Buying opportunities without knowing what one is worth is like ordering something without asking the price.
A marketing manager usually has one real decision each quarter: which product's demand to grow. That decision should come from revenue per opportunity, not from a product manager's enthusiasm or last year's habit.
In the example above, spending a budget worth 100 new opportunities on Product A gives you an expected 3,600,000; on Product C it gives 3,000,000, and the cash arrives two and a half times later. Same money, different outcome.
Why is the best-selling product not always the most profitable?
Because revenue does not show the full cost. A long cycle, heavy discounting, repeated technical meetings and the hours spent on deals you lost never appear on the revenue line. At a 15% win rate, every win carries the effort of roughly six opportunities.
That is why you track discounting alongside this analysis. We covered how discounting erodes your margin in a separate post.
What if the product data is missing in your CRM?
Start with three moves:
- Make the product field short rather than mandatory. Offer five product families instead of fifty SKUs.
- Tag the last 12 months of closed deals retroactively; invoices make this fast.
- For new deals, capture the product from the conversation. Your rep already says which product they pitched; the problem is that nobody writes it down.
The same data also tells you which customers actually make you money. We walked through customer profitability from CRM data here.
How often should you repeat the analysis?
Once a quarter is enough. Repeat it as well whenever your product range changes or you update the price list; in both cases the old numbers go stale overnight.
Use the same period length every time you run it. Comparing one quarter against twelve months will crown the wrong winner whenever a product is seasonal.
Most companies allocate marketing budget quarterly, so the analysis should sit on that rhythm. Monthly creates noise; annually sends the budget to the wrong place for a full year.
FAQ
How many opportunities do you need per product?
At least 20 to 25 closed deals per product. With less than that, the win rate measures coincidence.
Should I track product families or individual products?
Product families. Splitting by SKU thins the data and makes the decision harder, not clearer.
Should open deals be included?
No. Use closed deals only; open ones have not produced an outcome yet and including them makes every win rate look worse than it is.
Is revenue per opportunity the same as average deal size?
No. Average deal size counts only the wins; revenue per opportunity also carries the cost of the losses.
Can I run this from ERP data instead?
Yes for the revenue side, since invoices are accurate. What is missing there is the lost deals, so you still need your CRM for the win rate.
Closync AI is an AI layer that turns sales conversations into high-quality CRM/ERP data and that data into sales decisions.
Last updated: 23 October 2026
