Which opportunities deserve a closer look?
A consulting pipeline can look healthy while important account context stays buried in notes. Use this field guide to evaluate CRM reporting that helps leaders ask better questions before the forecast meeting.
Explore the seven-step field guideNot a product view
- DiscoverInitial conversationRecord the client's business problem and source of interest.
- ShapeScope takes formConnect stakeholders, next steps and open questions.
- DecideProposal under reviewTrack the decision process, not just the expected close date.
- ContinueRelationship developsKeep the history available for the next account conversation.
A lifecycle is context, not a forecast by itself.
A number without its history is a weak signal
Consulting opportunities may involve several partners, changing scopes and long gaps between decisions. A dashboard should make those conditions visible enough to guide a conversation, rather than reduce them to a single pipeline total.
Seven checks
Build the dashboard around the decision.
When comparing CRM software, bring a real pipeline review scenario. Ask how each view is built, what data it needs and who will maintain that data.
-
01 /
Define a qualified opportunity
Agree on the evidence needed before work enters the pipeline, such as a named client need and an agreed next conversation. Evaluate: Can the team document and consistently apply those definitions? An inflated early-stage total is not the same as qualified demand.
-
02 /
Read the stage distribution
Review opportunity value and count by stage to see where work is concentrated. Evaluate: Can stages reflect your actual consulting sales process? A large proposal-stage balance may include very different levels of client commitment.
-
03 /
Inspect time in stage
Look for opportunities that have remained in one stage longer than expected, then ask the owner what changed. Evaluate: Can stage history be recorded and reviewed? A long interval can be normal for a complex engagement, not necessarily a sign of trouble.
-
04 /
Separate movement from activity
Compare changes in stage with the next meaningful client action. A meeting count alone says little about whether a buying decision has advanced. Evaluate: Can a review connect an opportunity to its next step, owner and relevant notes?
-
05 /
Test forecast assumptions
Examine expected close dates, values and any probability assumptions alongside the client’s decision process. Evaluate: Can leaders see how forecast views are calculated? A weighted value is an estimate, not a commitment from the client.
-
06 /
Read wins and losses in context
Review outcomes by service line or opportunity type, then compare the reasons recorded by the team. Evaluate: Can outcome reasons be captured consistently? Small groups and incomplete reasons can make a win-rate comparison misleading.
-
07 /
Protect the account narrative
Before a review, connect open opportunities to prior conversations, stakeholders and related work. Evaluate: Is that context easy for the right colleagues to find and update? A dashboard is only as useful as the records behind it.
Three lanes for a useful review.
Choose views for different decisions. Then agree on a follow-up, rather than treating every indicator as an instruction.
Pipeline review
Look atStage, time in stage and the next client action.
AskWhich opportunities need a decision or a clearer next step?
Follow upAsk the opportunity owner to confirm the client’s position.
Forecast review
Look atExpected close dates, values and underlying assumptions.
AskWhich estimates depend on an unresolved scope or approval?
Follow upDocument the uncertainty before discussing capacity.
Account review
Look atStakeholders, relationship history and open opportunities.
AskWhere does the team need more context or coordination?
Follow upAgree who will update the account record and speak with the client.
Bring your review to the evaluation.
Use a representative opportunity and walk through the questions your partners actually ask. Check whether the proposed CRM can show the underlying records, explain its calculations and fit the way your team maintains account context.
Agree on definitions and ownership before comparing visual polish. A clear view cannot compensate for inconsistent stage updates or missing next steps.
Return to the seven checks ↑