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.
Author
A clear explanation leaves room for what remains uncertain. Subject: CRM software and sales operations. Noah Smith is the editorial byline assigned to this area. Background, definitions and the interpretation of available information belong to this editorial remit. Related coverage: Pipeline Design. This is an editorial pen name used by the publication, not a claim of an independently verified personal identity.
Pipeline Design
Choose which old opportunities leave active work, check the CRM's archive behaviour and verify that useful history remains findable.
Permissions
Define account-routing priorities, protect existing owners and give ambiguous records a review path before enabling automated assignment.
Contact Data
Reconcile imported records, values, links and errors against the source population, then correct and recheck affected customer records.
Contact Data
Choose CRM identifiers for contacts, accounts and opportunities, and set matching rules for imports and other systems.
Automation
Compare field sales mobile CRM needs with documented offline functions, plan limits and visit tasks.
Replacement
Define the failing customer task, compare repair and replacement on one scope, and account for dependencies and continuing effort.
Contact Data
Design a website-to-CRM hand-off that preserves each enquiry, matches contacts carefully and exposes rejected or missing submissions.
Adoption
Build CRM habits around customer handovers, useful records, constructive pipeline reviews and fixes for workflow friction.
Contact Data
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.
Automation
Plan CRM integrations around clear hand-offs, field ownership, privacy boundaries and confirmed outcomes.
Replacement
Review recurring CRM problems, preserve useful history and decide whether to repair the system or assess a controlled replacement.
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
Set up a CRM sales pipeline with clear deal boundaries, meaningful stages, next actions and a practical review routine.
Replacement
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
Turn a real sales process into checkable CRM requirements using events, roles, information needs, exceptions and acceptance results.
Pipeline Design
Write stage entry rules based on observable sales progress, resolve awkward cases and check that colleagues classify deals consistently.
Contact Data
Review likely duplicate contacts: assess identity evidence, handle uncertain pairs and inspect the effects of a planned merge.
Adoption
Diagnose low CRM usage by following a customer task, separating rule, access, screen, skill and handover problems, then checking a fix.
Contact Data
Triage missing CRM information by the work it affects, assign unresolved gaps and avoid guessed values that make a record misleading.
Pipeline Design
Separate service obligations from sales deals while sharing the customer context each team needs.
Adoption
Define eligible customer work, check whether records support a handover and interpret CRM activity without mistaking logins for adoption.
Pipeline Design
Represent a long or paused sales cycle with a justified stage, waiting reason and review point.
Pipeline Design
Record each person's role in a particular CRM opportunity, distinguish confirmed decision-makers from assumptions and handle role changes.
Automation
Find failed and missing CRM integration updates with run history, reconciliation, owned exceptions and safe replay checks.
Pipeline Design
Define when a won deal is ready for operations, send an identifiable request and handle acknowledgement, retries and later changes.
Pipeline Design
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
Set team and territory boundaries for CRM records, check overlapping grants and related data, and test access after account transfers.
Permissions
Check CRM uptime wording, support hours, response terms, exclusions and remedies against the proposed contract.
Permissions
Inventory CRM administrators, compare grants with current duties, inspect audit history and record decisions when privileged access changes.
Contact Data
Check a CRM field's purpose, values and dependencies before hiding, changing or deleting it, including product recovery limits.
Contact Data
Set a company naming rule, preserve useful alternate names and resolve account ownership without obscuring customer work.
Adoption
Test mobile CRM forms through customer lookup, visit updates, follow-up actions and difficult field cases.
Automation
Define an actionable stale-deal signal, choose the right time trigger and avoid repeated CRM alerts that lack a clear resolution.
Contact Data
Record an offline customer visit, verify the later CRM sync and hand off the next action.