Why stage definitions matter
“Lead” can mean a name in a database, a form submission, a person who replied or someone the sales team has accepted. When teams use one word for different states, a dashboard can look busy while leaving founders unsure what actually progressed.
Write a shared definition for every stage before building charts. Include the event that moves a record forward, who is responsible and what evidence is required. Keep the definition visible beside the metric.
A practical set of pipeline stages
These definitions create a useful starting point for B2B reporting. Adapt them to the company’s sales process and record any exclusions.
- Target account: a company that meets the agreed ideal customer criteria.
- Lead or contact: a person connected to a target account, with enough source and role detail to assess fit.
- Interested reply: a response that signals relevant interest or asks for a next step; exclude opt-outs, automated replies and polite declines.
- Sales-accepted conversation: sales confirms the person and request are relevant and owns the follow-up.
- Opportunity: sales creates or accepts an opportunity in the CRM under the company’s defined rules.
- Revenue: closed-won value recorded in the CRM or finance system, with the attribution caveats stated.
Show volume and conversion without implying causation
A weekly or monthly view can show the count at each stage, the movement from one stage to the next, and the time period used. Add segments such as source, campaign, market or account type only when the underlying data is consistent enough to support the comparison.
Keep activity metrics—contacts researched, emails sent, LinkedIn touches—separate from outcomes. A response rate is not an opportunity rate, and an opportunity is not booked revenue. If the sales cycle is long, show cohorts by the month they entered the process rather than comparing unrelated time windows.
Make the reporting source clear
Identify where each field comes from: outreach platform, CRM, analytics tag or spreadsheet. State whether counts are unique people, unique accounts or events. Add a last-updated date and note missing fields or tracking changes that affect interpretation.
When the CRM does not reliably contain opportunity or closed-won data, report the gap. Do not fill it with an estimate presented as actual performance. A smaller dashboard with dependable definitions is more useful than a polished report that hides uncertainty.
Use the report to choose the next test
A good pipeline report should lead to a question the team can act on: Are the target accounts a fit? Are replies reaching sales quickly? Do particular signals produce more relevant conversations? Is a source adding usable data at a reasonable cost?
Agree on the next adjustment, its owner and its review date. That turns reporting into an operating loop—observe, learn, change one thing and measure again—rather than a monthly recap that nobody uses.