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.
Desk
Desk Sales Operations
Covers pipeline stages, activity capture and the reporting sales managers rely on each month.
Permissions
Assigning account ownership with clear rules
Define account-routing priorities, protect existing owners and give ambiguous records a review path before enabling automated assignment.
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.
Adoption
Choosing a pilot team for CRM adoption
Select CRM pilot users by role, workflow and exception, then give their feedback a clear route into the rollout decision.
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 …
Adoption
CRM adoption and operating routines
Build CRM habits around customer handovers, useful records, constructive pipeline reviews and fixes for workflow friction.
Automation
CRM automation
Plan CRM automation around clear triggers, ownership, repeat behaviour and observable outcomes. Learn where to start and how to check a rule.
Pipeline Design
CRM for relationship-led businesses
Organise lasting customer relationships alongside distinct sales, service and follow-up work in a CRM.
Automation
CRM integrations
Plan CRM integrations around clear hand-offs, field ownership, privacy boundaries and confirmed outcomes.
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.
Adoption
Finding workflow friction behind low CRM usage
Diagnose low CRM usage by following a customer task, separating rule, access, screen, skill and handover problems, then checking a fix.
Pipeline Design
Keeping service relationships separate from new-business deals
Separate service obligations from sales deals while sharing the customer context each team needs.
Adoption
Measuring adoption through useful records rather than logins
Define eligible customer work, check whether records support a handover and interpret CRM activity without mistaking logins for adoption.
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.
Automation
Monitoring failed CRM updates
Find failed and missing CRM integration updates with run history, reconciliation, owned exceptions and safe replay checks.
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.
Automation
Syncing email activity without exposing unrelated messages
Set email logging and sharing rules before connecting a mailbox to CRM, then check exclusions, linked records and what colleagues can see.
Adoption
Testing mobile forms with real sales tasks
Test mobile CRM forms through customer lookup, visit updates, follow-up actions and difficult field cases.
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.
Adoption
Training users on the minimum reliable record
Teach CRM users to leave a customer record the next colleague can act on, including ownership, current position, next action and uncertainty.
Automation
Triggering alerts for stale opportunities
Define an actionable stale-deal signal, choose the right time trigger and avoid repeated CRM alerts that lack a clear resolution.