Drag a card from “Contacted” to “Proposal sent.” If the team cannot explain what must have happened before that move, the CRM board may be little more than attractive colors. Configuring sales stages starts with the evidence permitting a transition, followed by testing whether the system helps staff apply it and shows the correct result to a supervisor.
You do not need numerous stages to make the process look professional. Staff need to recognize the same situation consistently and find the next step without guessing. Test meanings in an acceptance session before rolling out the configuration, rather than discovering differences when management requests a report of opportunities close to closing.
Write a definition a new colleague can use
In a fictional event-services company, “Proposal sent” means an identified proposal version reached the relevant person, with a follow-up date and owner. Merely starting to draft it is insufficient. Another company may use a different definition; its process owner must document it, and everyone should understand how occurrence is evidenced.
For each stage, state entry and exit conditions, important fields and editing authority. Separate an activity such as a call from a result such as a requirement accepted for discussion. Calls may recur across stages, so every activity need not become a separate column that multiplies card movements without adding meaning.
An acceptance session with three synthetic opportunities
- Incomplete information: Prepare a proposal lacking a recipient or follow-up date. Try moving it to the requested stage and inspect the agreed warning, restriction or exception route.
- A lost opportunity: Record the customer's decision not to proceed and an agreed reason. Check where the record appears and how it leaves open opportunities without losing its history.
- A returning customer: Handle a customer reopening discussions after closure. Should the opportunity be restored or a new one created? Inspect the effect on history, ownership and reporting under company policy.
These original test cases belong to the example; they are neither project results nor guaranteed settings in every product. Write each expected result before the session. If testing needs a sales-manager decision, the supplier should not invent company policy simply to complete the interface.
Test what winning and losing mean
HubSpot documentation stresses defining won and lost stages for correct deal reporting and describes conditional stage properties during manual transitions. A required field appearing in the interface does not establish that imports or external integrations automatically follow the same rule. Ask about and test the channels through which your records arrive.
Define winning for your business: documented approval, signing or another event the organization accepts. “Won” should not automatically prove money has been collected. If reporting needs invoices or collection data, that requires another definition, data source and scope to review with the appropriate specialist.
Odoo documentation explains lost reasons and restoring opportunities, while stating that reason and closing-note fields are optional in the documented workflow. If your policy requires a reason, request evidence of its enforcement in the chosen solution. A feature appearing in documentation is not equivalent to configuring it for your needs.
Backward transitions also need agreement
A customer may renegotiate, or a supervisor may need to correct a mistakenly chosen stage. Define who can make corrections, the required explanation and what the record shows afterward. Do not forbid every backward move merely to tidy the diagram, or allow edits that make the sequence unreadable when traceability is required.
Review records from different channels, ownership changes and stalled opportunities that have not yet been lost. Ask whether a separate stage is needed or a tag and follow-up date would suffice. Rules preventing accumulation should remain usable, rather than encouraging arbitrary entries just to pass a required field.
Open the report after testing
Ask the supervisor to identify open and closed opportunities in the sample and drill from totals to records. Review the chosen date, stage, owner and lost reasons against the approved definitions. A weighted amount using stage probabilities is not a measured forecast merely because the system displays a default percentage.
Receive the stage definitions, test cases, exception decisions and authority to change them after the session. The CRM implementation scope covers other implementation work, while lead routing rules address assignment. Include session results when discussing CRM configuration with Nextwave so the requested behavior can be reviewed.
Session references
The HubSpot pipeline guide and Odoo lost opportunities guide were reviewed on 4 November 2026. Scenarios are editorial material without customer data or promises of increased sales. AI assisted preparation, with information and translation review.
