Record the starting point
Decide which inquiries enter the funnel and which do not. A duplicate or an unsolicited vendor message may need a different path.
A CRM field guide for growing startups
A conversion rate starts with a definition.
When everyone moves opportunities differently, a funnel report can look precise while hiding the real story. Define the handoffs first, then decide what your CRM needs to measure.
Explore CRM workflows
The handoff map
Illustrative example
Demand
InterestRequest received
QualifiedCriteria agreed
Sales
AcceptedOwner confirms
OpportunityNext step recorded
The arrow is part of the measurement. Agree on what crosses it and who confirms the move.
01 / Follow the journey
Make each stage a decision, not a label.
Early teams often inherit stages from a template. Before adding a chart, walk through a real prospect journey and decide what evidence earns each move.
Agree on the threshold
Write down the evidence required for a qualified record, such as a confirmed use case and a relevant contact. Keep the rule short enough to use.
Separate sent from accepted
A record passed to sales is not necessarily one sales has reviewed. Define who accepts it and how a rejected handoff is recorded.
Inspect the exceptions
Reopened, stalled, and disqualified records can change the story. Agree on their treatment before comparing periods.
02 / Assign the decisions
Reports inherit the habits of their owners.
At a startup, one person may wear several hats. The important distinction is between the decisions, not the job titles.
Keep the rules legible
Maintain a short stage dictionary with entry criteria, exclusions, and examples. Review changes with the people who use it.
Capture the move
Confirm who updates the record at each handoff and what should be noted when an opportunity is declined or sent back.
Question the denominator
Document which records are counted, the period being measured, and whether the report follows a cohort or counts activity in a period.
Metric sketch / illustrative example
Qualified-to-accepted conversion
Define the cohort first
Qualified records from a chosen period that were later accepted
÷
All qualified records from that same period
÷
All qualified records from that same period
Choose a follow-up window for acceptance and apply it consistently. Recent cohorts may need more time to mature. State how duplicates, rejected records, and records still awaiting review are treated.
03 / The CRM evaluation
Can the system preserve the story behind the number?
A dashboard alone cannot tell you whether a stage was applied consistently. When comparing CRM software, use a sample journey and ask to see how the following would be handled.
- Stage definitions and fieldsCan you configure stages and capture the evidence your team needs without making every update burdensome?
- Handoff historyCan you examine when a record entered a stage, who owned it, and whether it was returned or reopened?
- Cohort reportingCan you group records by the date they qualified and follow that same group to acceptance, rather than mixing unrelated monthly totals?
- Data inspectionCan you see the individual records behind a rate, filter exceptions, and export the data for further analysis if needed?
Test with a few messy cases as well as the ideal path. The useful question is not just whether a report can be built, but whether its inputs and limitations are understandable.
A practical next step
Take one handoff into your next evaluation.
Bring your stage dictionary, an example of a returned record, and the conversion question you want answered. Use them to compare the workflow and reporting tradeoffs in each CRM you consider.
See what to evaluate