Finding the companies whose systems were falling behind their operations
An ERP conversation rarely starts with a company asking for a new system. It starts with something the current setup makes difficult: reconciling stock across warehouses, planning production in spreadsheets, or pulling reports from several systems.
The campaign totals above cover 3,187 target companies, 922 decision-maker conversations and 67 booked meetings. The sections below explain an approach to ERP conversations with manufacturers and wholesale distributors.
Start with the processes the provider can actually support
Before calling, work through the provider’s fit criteria: manufacturing and distribution workflows, supported integrations, implementation requirements and the situations its sales team wants to discuss.
Company websites, business profiles, location pages and public expansion announcements help identify useful reasons to call. A second warehouse, a new production facility or additional operating locations can be useful clues. Each clue is a question to verify on the call.
Keep manufacturers and distributors in separate calling lists. For manufacturers, ask about production planning, materials and shop-floor reporting. For distributors, focus on inventory visibility, purchasing and orders moving between locations.
Depending on the company, the first useful contact may be a CFO, operations leader, IT director or owner. Record who would need to join a later ERP evaluation.
Keep the conversation close to their daily work
Call during the prospect’s local business hours. If the person is unavailable, record a callback time or ask who owns the relevant process. Send requested information by email with a short recap of the conversation.
Once you reach the right person, useful questions include:
- Which system handles finance, inventory and production today?
- Where does the team still use spreadsheets or enter the same information twice?
- Can people see reliable stock and order information across locations?
- Has growth created work the current system struggles to handle?
- Is a review planned, and who would be involved?
A company satisfied with its setup and without a planned change has no immediate reason to meet. A specific issue can keep the conversation open, even if a full ERP replacement is still some way off.
Refine the questions as you learn
1. Make the opening question useful. Asking which ERP a company uses may produce a product name and little else. A process question gives the contact more to work with: “How are you handling production planning outside the ERP today?” For distributors, ask about stock across locations. Record the existing system after understanding the workflow.
2. Reach the owner of the problem. IT contacts may know the software while finance or operations owns the reporting or inventory issue. Record the referral so the next call has a specific person and reason to ask for.
3. Separate a problem from a project. A spreadsheet workaround alone does not qualify a meeting. Ask about its effect on the business, whether anyone is reviewing it and what the prospect wants from a first discussion.
4. Give follow-up a date and a reason. Link a callback to the relevant planning cycle or internal review. Use the previous notes to reopen the conversation.
Review call notes and handoff feedback with the provider’s sales team. Questions about deployment, migration and integrations belong with its specialists; the caller establishes enough context for that discussion.
How to handle the usual objections
“We already have an ERP.” Ask which processes still happen outside it and whether that arrangement causes any problems. If the answer is no, there is no reason to push a meeting.
“Replacing it would be a huge project.” Acknowledge the work involved and check whether the company is considering a review at all. A first meeting can establish requirements and timing without committing the prospect to a migration.
“Send something over.” Ask what would be useful: information about manufacturing workflows, integrations or implementation. An email request on its own does not establish a qualified opportunity.
Give each meeting a clear purpose
Before booking, check that the account fits the provider’s customer profile, has a specific issue or planned review, and includes someone who owns or can influence the project. Agree on a defined next conversation and a time.
Budget, implementation scope and purchase authority may still need confirmation. Make those gaps visible in the handoff.
Example meeting brief
- Account: Example account 014
- Business: Manufacturer with approximately 180 employees and two operating locations
- Contact: Director of Operations
- Current setup: On-premise ERP, with production scheduling and some inventory reconciliation handled in spreadsheets
- Reason for interest: A second location has made it harder to keep production plans and inventory information aligned
- Purpose of the meeting: Review the workflow and discuss whether the provider can support production planning and multi-location inventory
- Other stakeholders: Finance and IT would need to join a later evaluation
- Still to confirm: Budget, integration requirements, project owner and implementation timing
- Status: Booked — attendance pending
40 accounts interested in a later next step
The totals include 40 separate accounts interested in further contact without a booked meeting. Follow-up can make sense around a later budgeting cycle, an internal systems review or a decision to involve another stakeholder.
Each follow-up record should include the issue, the person to contact and the agreed next step. A general request for a brochure alone does not establish a qualified opportunity.
Across the campaign, 67 bookings and 40 follow-up accounts add up to 107 positive responses. A useful handoff gives the sales team a starting point: the current setup, the operational issue and what the prospect wants to discuss.