A pipeline becomes difficult to trust when one salesperson moves a deal after a conversation and another waits for a written brief. The software should make the agreed distinction clear without demanding information the team cannot yet know.
Related service: CRM, ERP and web application development- 01Define the commercial milestone.
- 02Identify evidence needed at that point.
- 03Validate the transition.
- 04Record the old and new stage.
- 05Handle reopening without rewriting history.
SECTION 01
Write the milestone before adding required fields
Describe what a colleague should be able to verify. Qualified might mean the buyer's problem and decision contact are known; proposal sent might mean a particular quote version was delivered. Avoid several stages that differ only in how optimistic the owner feels. Keep probability estimates separate from observable milestones.
Choose whether a missing item blocks the transition or creates a visible exception. A mandatory budget field can encourage made-up numbers when the buyer has not shared a budget. A reasoned exception with a manager review may be more useful. The W3C form guidance supports clear correction messages; the business still decides which evidence matters.
SECTION 02
Illustrative example: a proposal returned for revision
Imagine a service opportunity moves to proposal sent after a scoped document is issued. The buyer asks for another location, so the team creates a revised proposal. The CRM should not count this as a new opportunity merely to get it back into the drafting queue. This example describes a possible workflow, not delivered client work.
Keep the current stage and the revision task visible together. If the opportunity really returns to discovery, record that transition with its reason and preserve the earlier proposal event. A monthly conversion report can then explain both the current pipeline and genuine transitions rather than treating every backwards move as data corruption.
SECTION 03
Test the difficult transitions, not just the board
Begin with one sales process. Configure an existing pipeline where its stage rules and history are adequate; do not build a new CRM for a preferred board color. A custom workflow should address a meaningful gap such as separate commercial and technical approvals.
Ask the agency to demonstrate skipped stages, reopened opportunities, changed owners and imports with old stage values. Confirm who may override a blocked transition and whether the reason is recorded. Reports should identify their date basis: created date, stage-entry date and close date answer different questions. Retain the approved definitions with the handoff so later administrators do not silently change the meaning of established reports.
SECTION 04
Frequently asked questions
Should every stage require more fields?
Only where the information is needed for that decision. Too many early requirements can create guessed values and encourage staff to bypass the process.
Can we skip a stage?
If the business permits it, define the conditions and record the exception. Do not let unrestricted dragging silently bypass an approval.
Why preserve old stage changes?
They explain cycle time, reopening and historical conversion. A current stage alone cannot reconstruct the path an opportunity followed.
PRIMARY REFERENCES
Sources and further reading
These references cover the standards, platforms, or published prices discussed in the guide. Worked examples and checklists are our editorial guidance.
- Accessible form validationW3C WAI
- Application logging guidanceOWASP Foundation
EDITORIAL METHOD
About this guide
We use AI to assist with drafting and editing. Catapult AI Work is responsible for the published content. Examples illustrate possible approaches; they are not client case studies unless identified as such.
Budget examples are not Catapult package prices. Check linked provider pages for current fees and plan limits before making a purchase.
Read the editorial policy