Harbour Clinic
Review non-clinical brief
Jamie1 day
121 CRM guide · Sales handover
The useful outcome is a repeatable decision with an owner, evidence and an exception route. This guide helps a small team turn sales handover into a specific, testable way of working rather than a vague intention. It uses a bounded customer journey, clear ownership and evidence people can review, keeping sales handover grounded in real work rather than treating it as another abstract CRM ambition.
Fictional working example
This code-built sales handover illustration shows how the decision could appear inside a working CRM, demonstrating information and responsibility rather than a fixed account configuration.
Northstar Joinery
FictionalKnow what needs to happen next
See each opportunity's stage, owner and next action in one view.
Harbour Clinic
Review non-clinical brief
Field & Form
Assign an owner
Bramble Studio
Call · Thu 11:30
Oakfield Homes
Site visit · Fri
Marlow Works
Decision due Friday
Hill & Co
Reason recorded
CRM building blocks
These are the practical tools behind the guide, with enough context to decide where they can help and where people still need to take responsibility.
Represents a potential sale or deal linked to a contact, value, owner and pipeline position.
Defines an ordered sales process through which opportunities can be reviewed and moved.
Uses configured stages plus open, won, lost and abandoned statuses to describe the state of a deal.
Creates assigned, dated and optionally recurring actions against contacts or opportunities.
Combines supported widgets and filters into an operational view for ongoing monitoring.
Start with the decision
The useful aim is to make commercial work visible without pretending that a stage or forecast guarantees an outcome. For sales handover, define what needs to change, who owns the choice and how the team will recognise a better customer or staff outcome.
Write this pipeline method as a question an owner can answer. Here, the practical task is to turn sales handover into a specific, testable way of working rather than a vague intention. Name the customer stage and the later action this pipeline method should inform.
Collect stage definitions, entry and exit rules, owner checks, ageing records and recorded outcome reasons. Use a small current sample to test this pipeline method, including one example that did not follow the expected path.
The main risk is that stage movement can create false confidence when evidence, ownership or the next customer action is missing. State the stop, escalation or approval point for this pipeline method in ordinary language and give it to a named person.
A practical method
Try this method on a representative slice of this pipeline method before changing every team or record. Each part of the sales handover trial should leave evidence that another person can inspect, challenge and repeat.
Describe the event or evidence that makes an opportunity enter and leave each stage; avoid stages that merely express optimism; keep the practical aim in view: turn sales handover into a specific, testable way of working rather than a vague intention.
Record who is acting, what will happen and when. A future date without an action or owner should not count as healthy progress; keep the practical aim in view: turn sales handover into a specific, testable way of working rather than a vague intention.
Separate a valid wait from neglected work using stage-specific expectations, customer context and an explicit exception reason; keep the practical aim in view: turn sales handover into a specific, testable way of working rather than a vague intention.
Record won, lost, paused and disqualified reasons consistently, then review patterns without treating correlation as proof of cause; keep the practical aim in view: turn sales handover into a specific, testable way of working rather than a vague intention.
Review the method
Use the second view to inspect ownership, exceptions and the evidence the team should review before extending this pipeline method.
Book discovery
October · illustrative availability
Appointment sequence
Booked
Calendar entry created
1 day before
Reminder scheduled
Exception
Owner reviews a reply
Journey summary
New
24
Illustrative
Owned
21
Illustrative
Due
4
Illustrative
Worked example
Marlow Studio is a small design consultancy. The team tests sales handover on one bounded customer journey, using fictional data and the existing working practice as its comparison point.
Marlow Studio needs to turn sales handover into a specific, testable way of working rather than a vague intention. The customer context needed for this pipeline method exists today, but it is spread across records and individual knowledge, so another colleague cannot consistently explain the next decision.
The team selects ten recent examples, applies the four-part method to this pipeline method and records every exception. It changes only the minimum fields, ownership rules and prompts needed for this pipeline method; one person can halt the trial if customer context is lost.
The owner checks whether active opportunities meet their stage rules and carry a credible next action. Staff compare the new route for this pipeline method with the earlier practice, identify avoidable administration and show which awkward case still needs a person rather than another rule.
The examples use evidenced CRM building blocks without claiming that every block is active for every customer or free of separate provider charges for this sales handover trial. The trial can show whether the method is clearer for Marlow Studio; it cannot promise revenue, growth or a universal result.
Limits and review
The sales handover design needs another look when opportunities sit without next actions, stage rules are bypassed, forecasts swing without explanation or outcome reasons become vague. Give this pipeline method both a calendar review and an event-driven trigger so a once-useful configuration does not quietly become misleading.
If staff keep a private list, retype the same value or move this pipeline method into chat, ask what the agreed method failed to represent. Fix that problem before layering another automated action over this pipeline method.
The CRM shows captured events under chosen definitions. Before drawing a conclusion from this pipeline method, check missing activity, timing, duplicated records and whether the population still matches the decision.
The examples use evidenced CRM building blocks without claiming that every block is active for every customer or free of separate provider charges for sales handover. Recheck the providers, permissions, retention and communication rules supporting this pipeline method when the scope changes.
The accountable owner must be able to pause this pipeline method, correct the record and explain why an exception was handled differently. Responsibility for this pipeline method cannot be delegated to a status or score.
Questions about this page
Start with the question that changes a customer action or handover: how will the team turn sales handover into a specific, testable way of working rather than a vague intention? Give this pipeline method an owner and test it against a few current examples before choosing more configuration.
Bring stage definitions, entry and exit rules, owner checks, ageing records and recorded outcome reasons. Include a normal case, a missing-information case and an exception so the review of this pipeline method does not describe only the ideal journey.
Stop where context, consent, fairness, professional responsibility or an unusual customer need changes the appropriate action for this pipeline method. A person should own that point in this pipeline method and be able to explain the decision.
Review this pipeline method when opportunities sit without next actions, stage rules are bypassed, forecasts swing without explanation or outcome reasons become vague. Also set a proportionate review date for this pipeline method so quiet drift is found even when nobody raises an incident.
Continue the journey
Delegate the work. Keep the human.
Subscribe through the approved secure checkout, or review pricing and responsibilities before you decide.
121 CRM
Your customers. Your conversations. Your business. Organised around clear ownership and human decisions.