Pipeline Design
Archiving old opportunities without losing history
Choose which old opportunities leave active work, check the CRM's archive behaviour and verify that useful history remains findable.
Section
Pipeline Design
Pipeline Design
Avoiding activity logs that obscure the customer history
A busy CRM timeline can hide the very event someone needs: a changed requirement, a missed commitment or an unresolved objection. The cure is a clearer recording …
Pipeline Design
Checking report filters before presenting results
Use a record-level checklist to verify CRM report dates, stages, owners, exclusions, visibility and totals before sharing a result.
Pipeline Design
Comparing pipeline value with expected revenue
Compare full pipeline value, weighted deal value and a period forecast using the same deals, dates and currency.
Pipeline Design
CRM activity management
A customer record should answer two questions quickly: what happened, and who will do what next? A long timeline is not necessarily a useful one. Activity …
Pipeline Design
CRM for relationship-led businesses
Organise lasting customer relationships alongside distinct sales, service and follow-up work in a CRM.
Pipeline Design
CRM mobile use
Plan mobile CRM work around customer visits, offline updates, device data and usable hand-offs.
Pipeline Design
CRM reporting
Learn how to define CRM sales reports, choose the right deal population and calculation, and check figures before sharing them.
Pipeline Design
CRM sales pipelines
Set up a CRM sales pipeline with clear deal boundaries, meaningful stages, next actions and a practical review routine.
Pipeline Design
Defining a CRM sales forecast
Define a CRM sales forecast by period, deal population, amount basis and owner, then make assumptions and adjustments reviewable.
Pipeline Design
Defining CRM requirements from the sales process
Turn a real sales process into checkable CRM requirements using events, roles, information needs, exceptions and acceptance results.
Pipeline Design
Defining pipeline stages from observable progress
Write stage entry rules based on observable sales progress, resolve awkward cases and check that colleagues classify deals consistently.
Pipeline Design
Defining what must be recorded after a customer conversation
Set a post-conversation recording rule for changed decisions, uncertainty, commitments and the next owner.
Pipeline Design
Keeping service relationships separate from new-business deals
Separate service obligations from sales deals while sharing the customer context each team needs.
Pipeline Design
Modelling long sales cycles without artificial stages
Represent a long or paused sales cycle with a justified stage, waiting reason and review point.
Pipeline Design
Modelling several decision-makers in one account
Record each person's role in a particular CRM opportunity, distinguish confirmed decision-makers from assumptions and handle role changes.
Pipeline Design
Passing closed deals to operational systems
Define when a won deal is ready for operations, send an identifiable request and handle acknowledgement, retries and later changes.
Pipeline Design
Recording useful conversation context
A useful CRM note preserves the information a colleague needs for the next decision. It need not be a transcript. Write it soon after the conversation, while the …
Pipeline Design
Reviewing pipeline quality without public shaming
Run a pipeline review that settles deal questions, assigns record corrections and keeps individual coaching private.
Pipeline Design
Separating completed activity from scheduled follow-up
A completed call and a planned follow-up describe different states. Keeping them separate lets a colleague see both the customer history and the work still owed.
Pipeline Design
Setting required information at a deal stage
Decide which deal details a stage truly needs, choose prompts or blocking fields, and check exceptions and integration paths.
Pipeline Design
Tracking a next step with an owner and date
“Follow up” is a prompt, not an action. A CRM task becomes useful when someone can tell what completion looks like, who owns it and when it is due.
Pipeline Design
Tracking several opportunities within one customer account
Decide when one customer needs separate opportunities and keep each deal’s scope, people and outcome distinct.