Enterprise resource planning (ERP) lead generation is a search for a business decision. A company can have an old platform and no reason to replace it. Another can have a modern system and still need help with a new entity, a broken handoff or a stalled rollout. Your campaign must tell those situations apart.
This playbook is for ERP software vendors, resellers and implementation partners building an outbound pipeline. It covers account selection through the first sales meeting. For exact opening language, use the linked ERP scripts; for a detailed financial argument, use the separate business-case guide.
Decide which ERP opportunity you want to create
A campaign for first-time ERP adoption needs different evidence from a competitive replacement campaign. Write one offer statement before anyone buys data or starts calling.
| Sales motion | Account condition to investigate | Useful first meeting |
|---|---|---|
| First ERP adoption | Accounting tools and manual processes struggle with a growing business | Review one process and the requirements for a larger system |
| ERP replacement | A known limitation matters enough to consider disruption | Examine the limitation, alternatives and change constraints |
| Subsidiary or site rollout | An acquisition or expansion requires an agreed operating model | Map entities, local needs and the parent system |
| Implementation or recovery services | A defined project needs delivery capacity or specialist help | Review scope, ownership and the work still open |
| Integration and ongoing support | The platform stays but a connection or support task needs attention | Assess the bounded service requirement |
Choose the supported platforms, industries, countries, business sizes and project types. Exclude work your implementation team cannot deliver. A large account is not a good lead when its requirements sit outside your capabilities.
Build an account list around processes and capacity
Use company size as a starting filter, then examine entities, locations, product complexity and operating model. Employee count alone says little about whether a firm needs manufacturing planning, multi-entity consolidation or more reliable inventory records.
Record the evidence source and date. An acquisition announcement is a fact. A need to consolidate financial systems is a hypothesis until someone confirms it. Avoid presenting guessed technology stacks, contract dates or implementation problems as known information.
In Microsoft's implementation guidance, the starting point is the business value expected from the project. Apply that principle to prospecting: ask what the business needs to do differently before discussing the product. Microsoft implementation guide.
Find the owner of the process before assembling the committee
For a finance-led campaign, ask the Controller about reporting, reconciliation or consolidation. For an operations-led campaign, ask about orders, inventory or production. IT can explain the systems environment, but may not own the business case for changing it.
Build the committee from confirmed responsibilities. Finance assesses the investment and controls. Operations explains what must keep working. IT evaluates architecture, access and integrations. Procurement manages commercial requirements. An executive sponsor resolves priorities when the project crosses departments.
The buying committee guide explains the full mapping method. The first call only needs to establish who can help answer the next useful question.
Open an ERP cold call with one testable question
Use a relevant fact and leave room for correction. Here is an illustrative opener for a business that has publicly announced a new entity:
“Hi [Name], [Caller] with [Company]. I saw the announcement about [entity]. Does bringing its reporting into the group create extra work for Finance, or is that already handled in the current setup?”
If reporting is handled, accept the answer. If it creates work, ask where that work happens and who owns it. Do not jump from “we use spreadsheets” to “you need a new ERP.” Spreadsheets can support a sensible process as well as conceal an expensive one.
For a complete call flow, use the ERP modernization script for CFOs. Keep the opener short enough that the buyer has time to explain the real situation.
Qualify an evaluation without pretending to run technical discovery
An appointment setter needs enough information to make the meeting useful. They do not need to design the solution on a cold call.
- What system and process are involved?
- What work becomes harder, slower or less reliable?
- Who owns that consequence inside the business?
- Is the account considering replacement, an addition or specialist support?
- Which integrations, data sources or local requirements cannot be ignored?
- Does the team have time and ownership for an evaluation?
- What question should the first meeting answer, and who needs to be there?
Record unknowns openly. Ask an ERP specialist to resolve product fit, migration effort and technical commitments. An honest unknown gives the next team a discovery task; a guessed answer can damage the opportunity.
Handle incumbent systems and timing with respect
“We already have an ERP” establishes context. It does not establish satisfaction or dissatisfaction. Ask whether the proposed topic falls inside the current platform, outside it or nowhere on the agenda. Use the incumbent ERP guide when a real replacement review exists.
If the concern is disruption, clarify the specific constraint: peak trading, close, a warehouse launch, a lack of internal capacity or a project already in progress. Record a buyer-approved review point when appropriate. Do not invent urgency from the age of the software.
Disqualify accounts with no relevant requirement, no service fit or no willingness to explore. Separate an interested researcher from an authorized evaluation. Both can be useful contacts, but they belong in different pipeline stages.
Design a first meeting that earns a second one
Send a short agenda tied to the confirmed process. For example: review how the new entity reports today, identify the systems involved and decide whether an integration discussion is warranted. That is more useful than “ERP introduction.”
The handoff should include the trigger source, current environment, buyer corrections, business consequence, known stakeholders, constraints and open questions. Confirm the attendees and time zone. Use the qualified appointment standard to agree what sales will accept before the campaign begins.
After the meeting, record whether it happened, whether sales accepted the account and which next step the buyer agreed. A booked meeting, a held meeting and an active ERP opportunity are different outcomes.
Run follow-up around the buyer's decision
Follow up with the promised process map, relevant example or discovery agenda. A repeated product brochure adds little when the unresolved question is implementation capacity. If the buyer agrees to revisit after a planning event, record that event rather than placing the contact in an indefinite chase sequence.
For US and Canadian accounts, match working hours and the seller's supported market. Calling, email, recording and data rules require separate campaign checks. Use the global calling compliance guide as the starting point for that review.
Measure results by sales motion. First ERP adoption and implementation recovery should not be pooled into one conversion claim. Track held meetings, accepted evaluations, rejection reasons and progression using the campaign quality metrics guide. This shows whether research and conversations are producing work the sales team can advance.