The ERP and CRM partner pipeline playbook

ERP and CRM implementation partners often segment prospects by company size, industry and platform. Those fields are useful, but they do not show whether a business has a workflow worth changing, the capacity to run an implementation or enough readiness to make a project credible.

A stronger pipeline starts with three linked views: workflow fit, implementation capacity and change readiness. The goal is not to predict a purchase from public data. It is to decide which accounts deserve careful discovery and which should wait.

1. Define the workflow you can improve

Choose one end-to-end process where the practice has approved expertise. Examples might include quote to cash, case management, project delivery or field service. Describe:

• the start and end of the process;
• teams involved;
• hand-offs and records created;
• platform capabilities required;
• integration boundaries;
• situations the practice will not support.

Microsoft’s Dynamics 365 guidance recommends using end-to-end business processes through definition, design, build, test and support. That makes workflow a useful basis for segmentation because it connects commercial discovery to implementation reality.

Avoid turning vendor terminology into a prospect claim. A company may describe a workflow publicly without revealing the system behind it.

2. Create three pipeline gates

Gate A: workflow fit

Find current evidence that the target process exists and has enough complexity to justify discovery. Useful sources include company service pages, operational documentation, relevant vacancies, public transformation notices and annual reports.

Record the observed fact separately from your interpretation. “Operates five service centres” may support a multi-site workflow hypothesis. It does not prove that the current CRM is fragmented.

Gate B: implementation capacity

A technically relevant account may still be unable to act. Look for what must be confirmed:

• accountable business owner;
• internal project lead;
• availability of subject-matter experts;
• integration and data owners;
• procurement path;
• realistic delivery window;
• partner delivery capacity.

Capacity is two-sided. Do not create more qualified demand than the consultancy can scope and deliver well.

Gate C: change readiness

Readiness concerns the organisation’s ability and willingness to change the process, not an invented maturity score. Test for an agreed problem, executive sponsorship, user involvement, decision criteria and a next discovery action.

Microsoft’s implementation-guide overview describes Strategize, Initiate, Implement, Prepare and Operate stages. Its Success by Design guidance uses Discover, Initiate, Implement, Prepare and Operate, and also stresses early attention to technical and project risk. A sales hand-off should therefore preserve the workflow, ownership and risk questions needed for discovery rather than reduce the account to a platform label.

3. Build a pipeline by state

Use states that describe evidence and action:

1. Observed: a sourced workflow or change signal exists.
2. Researched: fit, exclusions and likely ownership have been checked.
3. Verified: a responsible person has confirmed the workflow or priority.
4. Discovery agreed: scope and participants for a discovery step are known.
5. Qualified for solution work: the practice’s own criteria for need, authority, capacity and timing are met.

Do not call an account “Dynamics ready” or “CRM replacement” based on public clues. Platform and timing remain unknown until verified.

Fictional worked scenario

Harbour Services Group is fictional. Its website describes regional teams handling customer requests by phone and email, and a current vacancy mentions responsibility for standardising service reporting. The evidence supports a service-process discovery hypothesis. It does not identify the current CRM or prove a replacement project.

The partner records:

• workflow fit: plausible and sourced;
• implementation capacity: unknown;
• change readiness: a standardisation signal, still unconfirmed;
• exclusion check: no evidence of an unsupported regulated workflow;
• next action: identify the service owner and test whether reporting change is an active programme.

If the owner says the vacancy is routine backfill and no process change is planned, the account returns to monitoring. That is useful qualification, not failure.

4. Match activity to delivery capacity

Create a simple planning view by month:

Use your own delivery data. There is no universal conversion rate from researched account to implementation. Work backwards from the number and type of opportunities the practice can responsibly handle, then set research volume and qualification depth accordingly.

ERP and CRM pipeline worksheet

Quality check:

• [ ] One end-to-end workflow anchors the segment.
• [ ] Public facts and inferences are stored separately.
• [ ] Platform is unknown unless a current source confirms it.
• [ ] Delivery capacity is included in pipeline planning.
• [ ] Readiness is verified through discovery, not guessed from a score.
• [ ] Unsupported projects and sectors have explicit exclusions.
• [ ] Qualification states have owners and next actions.
• [ ] Personal data, channel and suppression checks are complete.

Companies House can help confirm company identity, status and filings, but its own guidance says the register is not comprehensive. Use it as one input, never as a complete view of operating change.

For the broader account-research model, read Hyper’s software sales lead generation guide. To discuss managed new-business support for an ERP or CRM implementation practice, see Hyper’s managed new-business service.

Discuss your growth priorities with Hyper