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.
Archive
October 2026
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.
Contact Data
Auditing data quality after a bulk import
Reconcile imported records, values, links and errors against the source population, then correct and recheck affected customer records.
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 …
Permissions
Checking data export before contract signature
Specify CRM export scope, relationships, permissions and timing, then inspect a sample before signing.
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.
Contact Data
Choosing a unique identifier for customer records
Choose CRM identifiers for contacts, accounts and opportunities, and set matching rules for imports and other systems.
Replacement
Choosing CRM software for a sales team
Choose a sales CRM from your team's workflow and required outcomes. Compare relevant HubSpot, Pipedrive and Zoho CRM plan limits before buying.
Automation
Choosing mobile CRM features for field sales
Compare field sales mobile CRM needs with documented offline functions, plan limits and visit tasks.
Replacement
Comparing per-user plans and feature restrictions
Map CRM seats and editions to user tasks, then compare feature limits, add-ons and billing terms.
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.
Replacement
Comparing reconfiguration with replacing the CRM
Define the failing customer task, compare repair and replacement on one scope, and account for dependencies and continuing effort.
Contact Data
Connecting website enquiries to CRM records
Design a website-to-CRM hand-off that preserves each enquiry, matches contacts carefully and exposes rejected or missing submissions.
Automation
Creating follow-up tasks without duplicates
Set task-worthy triggers, define equivalent open work and check repeat entry before automating CRM follow-up tasks.
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.
Contact Data
CRM contacts and account structure
Structure CRM contacts, customer accounts and opportunities so sales teams can find the right people and potential sales without duplicating records.
Replacement
CRM costs and vendor selection
Compare workable CRM editions, seats, implementation work, support and exit terms using the same buying brief.
Contact Data
CRM data quality
Define useful CRM data quality checks, find the causes of errors and set a review routine around the customer work your team needs to complete.
Pipeline Design
CRM for relationship-led businesses
Organise lasting customer relationships alongside distinct sales, service and follow-up work in a CRM.
Replacement
CRM implementation
Plan a CRM implementation around usable sales work, prepared records, representative users and a clear go-live decision.
Automation
CRM integrations
Plan CRM integrations around clear hand-offs, field ownership, privacy boundaries and confirmed outcomes.
Replacement
CRM maintenance and replacement
Review recurring CRM problems, preserve useful history and decide whether to repair the system or assess a controlled replacement.
Pipeline Design
CRM mobile use
Plan mobile CRM work around customer visits, offline updates, device data and usable hand-offs.
Permissions
CRM permissions
Plan CRM permissions by role, record, action and field. Test team access, limit partner and admin rights, and review access when responsibilities change.
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.
Replacement
CRM versus a spreadsheet customer register
Decide when a shared customer spreadsheet is enough and when sales work calls for a CRM, using ownership, follow-up and hand-offs as the tests.
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.
Replacement
Estimating CRM implementation and support costs
Scope CRM migration, configuration, training and support, then separate first-year and recurring costs.
Contact Data
Finding duplicate contacts without merging different people
Review likely duplicate contacts: assess identity evidence, handle uncertain pairs and inspect the effects of a planned merge.
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.
Permissions
Giving an external partner limited account access
Define the accounts, actions and time period an external CRM partner needs. Test related data exposure and remove access when the work ends.
Contact Data
Handling incomplete customer records
Triage missing CRM information by the work it affects, assign unresolved gaps and avoid guessed values that make a record misleading.
Pipeline Design
Keeping service relationships separate from new-business deals
Separate service obligations from sales deals while sharing the customer context each team needs.
Permissions
Limiting sensitive CRM data stored on mobile devices
Identify and reduce customer information held on phones, including offline data, notifications and exports.
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.
Replacement
Planning a CRM switch with record relationships intact
Map account, contact, opportunity and history links before a CRM switch, then reconcile IDs and relationships before cutover.
Contact Data
Preparing a clean CRM migration file
Prepare CRM import rows, identifiers, field values and relationships, then check a small import before moving the agreed data.
Contact Data
Recording referral sources accurately
Record who introduced an opportunity without confusing a personal referral with web traffic or CRM creation source.
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 …
Permissions
Removing former users without orphaning customer records
Revoke a former user's CRM access, transfer active accounts and tasks, check automations, and preserve useful customer history.
Permissions
Restricting access by team and territory: design and test
Set team and territory boundaries for CRM records, check overlapping grants and related data, and test access after account transfers.
Permissions
Reviewing a CRM vendor's service commitments
Check CRM uptime wording, support hours, response terms, exclusions and remedies against the proposed contract.
Permissions
Reviewing administrator permissions
Inventory CRM administrators, compare grants with current duties, inspect audit history and record decisions when privileged access changes.
Pipeline Design
Reviewing pipeline quality without public shaming
Run a pipeline review that settles deal questions, assigns record corrections and keeps individual coaching private.
Contact Data
Reviewing unused fields and customisations
Check a CRM field's purpose, values and dependencies before hiding, changing or deleting it, including product recovery limits.
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.
Contact Data
Separating contacts, companies and opportunities
Decide whether CRM information belongs to a person, customer account or separate sales opportunity, using a practical example.
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.
Contact Data
Standardising company names and account ownership
Set a company naming rule, preserve useful alternate names and resolve account ownership without obscuring customer work.
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.
Automation
Testing a CRM rule before enabling it for all users
Use qualifying, excluded and repeat cases to check a CRM rule, understand what vendor previews show and inspect outcomes before wider rollout.
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.
Contact Data
Steps for updating an account after an offline visit
Record an offline customer visit, verify the later CRM sync and hand off the next action.