CRM opportunities: stage evidence and next action
An advanced card does not prove negotiation or collection. Use stage criteria and tasks that preserve each decision's reason.
Test ten sales follow-up decisions
Record stage evidence, next action, closure and repetition. Observed results are reserved for your testing.
Each stage should describe a fact and a next action
A CRM supports follow-up when its stage explains what was verified, by whom and what should happen next. Proposal sent describes a sales action; negotiation needs evidence that the customer is reviewing or discussing terms. If everyone advances cards by intuition, the board stops distinguishing outstanding work from a deal close to completion.
ActiveCampaign documents pipelines with stages, opportunities linked to contacts and follow-up tasks. Microsoft describes Dynamics 365 Sales closure as won or lost, closure details and reopening. These are those products' features. Evidence required for each change should reflect your business process.
| Stage | Minimum evidence | Next action |
|---|---|---|
| Identified inquiry | Contact, initial need and owner | Confirm context and authority to continue |
| Confirmed need | Problem and scope discussed with a suitable contact | Resolve missing proposal data |
| Proposal sent | Version, scope, recipient and date | Confirm receipt and review |
| Terms under review | Customer question or requested change | Respond and revise proposal if needed |
| Won | Verifiable acceptance under business rule | Handover commitment to operations |
| Lost | Reason and closure decision | Keep history and permitted future follow-up |
Example: sending a proposal does not prove negotiation
Sales receives a request and schedules a conversation. It has not happened yet: the opportunity remains an identified inquiry with that next action. After discussing, sales confirms both sites and records the decision owner. If authority or required quoting access remains unknown, keep the missing detail visible instead of pretending scope is ready.
V1 for 18,000 is sent. OP-18 moves to proposal sent with a receipt-confirmation task. An automatic delivered message does not move it to terms under review. When the contact asks about an exclusion and requests a visit change, record the question; review evidence and a sales action with owner and date now exist.
V2 clarifies the change and preserves its relation to V1. The business receives V2 acceptance from the authorized contact and marks won with that evidence. Won means neither work performed nor money collected. Operational handover carries accepted scope, sites and outstanding access details, while collections keep their own state.
An overdue task needs a decision, not another automatic date
Each open opportunity should show a specific next action, owner and date with time zone. For example, confirm V1 receipt on October 12, 2026 at 11:00 Mexico City time. If the task expires, record outcome, reason and next decision. Moving the date without explaining what happened creates a list that always looks current.
| Situation | Expected outcome | Evidence |
|---|---|---|
| Same information request arrives through two channels | One opportunity with linked activities | Verified contact and need |
| Saved V2 acceptance recorded again | One won opportunity; one identified handover | Version and acceptance reference |
| No reply after a task | Pending or closed under an explicit rule | Attempt and decision; no invented loss |
| Customer selects another provider | Lost with verifiable reason | Response or recorded decision |
| Customer resumes the same scope | Reopen with history and new action under policy | Link to previous closure |
Two contacts at the same company may request different projects: do not merge them solely by company name. Define opportunity identity and correction authority. If another salesperson changes the stage while an old screen saves, the second action should check current state rather than erase a closure reason or replace current acceptance.
An open opportunity's value is a commercial possibility, not collected funds. If you use probabilities or forecasts, explain assignment rules and missing evidence; this guide supplies no invented percentages or sales projection. It also recommends no automatic messaging sequence without reviewing contact preferences and rules.
Evaluate a pipeline with insufficient and repeated evidence
- Try confirming need without minimum details. Show what is missing and its resolution owner.
- Send a proposal and an automatic receipt. Neither alone should prove negotiation or acceptance.
- Accept an identified version, repeat recording and check one operational handover without another opportunity.
- Close with a reason and test reopening. Keep history and next action rather than erase the previous outcome.
- Make changes from two salespeople and review an overdue task. Show current decisions and outstanding actions.
Prepare five anonymized opportunities, including an unanswered, lost and resumed one. Bring stage criteria, owners and a valid acceptance example. The worksheet compares that discipline in software without attributing unmeasured conversion improvement.
For general scope, review custom CRM; for changes before work, service quotes. A customer portal consultation can examine the transition between accepted proposal and information customers need to see.
Frequently asked questions
Not under this test rule. Record a customer question, review or requested change demonstrating that stage. Sending is the internal proposal-sent action.
No. Commercial closure evidence and payment confirmation are separate records. Define sufficient acceptance and what operations need before starting.
It depends on your business's closure rule. Preserve attempts and decision; do not invent rejection or move dates indefinitely to conceal missing follow-up.
If it concerns the same work under your rules, preserve history and a new action. A different project may need another linked opportunity and an explicit decision.
Sources
- Pipelines, stages, opportunities and tasksActiveCampaign
- Close and reopen opportunitiesMicrosoft Learn
Last updated: