Lead generation for ERP and IT consulting starts with a business problem that a buyer has a reason to address. To find opportunities before a project goes to tender, identify accounts with relevant signs of change, reach the people who own the problem and ask how they are handling it. A visible trigger is a reason to investigate, not proof of buying intent.
An implementation partner can have a strong delivery team and still struggle with pipeline. Current projects keep the consultants occupied. Vendor referrals produce work some months and very little in others. The founder handles business development between delivery issues, and the next quarter remains uncertain.
Waiting for a formal request for proposal can leave you entering the conversation after much of the thinking has happened. The organisation may already have discussed its options, spoken with providers and formed a view about scope. Earlier conversations can help you understand the actual challenge while the buyer is still deciding what to do.
That does not mean bypassing procurement or trying to shape a tender unfairly. It means finding a useful commercial conversation when the buyer is willing to have one, and respecting the organisation’s process when a formal procurement exercise begins.
Why a list of companies using an ERP is not enough
Knowing which platform a company uses can help with targeting. It does not tell you whether the company needs help, who owns the issue or whether it is prepared to consider a project.
Two businesses on the same system may have completely different situations. One is comfortable with its setup. Another has acquired a company, is running finance across separate entities and is struggling to produce reliable reporting. A third has already selected an implementation partner.
The useful account definition combines platform fit with the kind of business situation your team can address. For example, an ERP consultancy may choose multi-entity businesses facing integration problems. A specialist IT firm may target organisations whose growth has exposed a support, security or data-management gap.
Choose a manageable segment where your expertise is credible. Our broader IT services lead generation guide explains how account selection connects to technical and commercial buyer roles.
Which changes can create a reason to talk?
The following examples are illustrative. A new acquisition, job advertisement or leadership appointment does not automatically mean the company needs a project. The first conversation tests whether the signal connects to a real problem.
| Situation | Possible owner | Useful first question |
|---|---|---|
| Growth or an acquisition creates separate systems | CFO, COO, business systems leader | How are you bringing reporting and processes together across the businesses? |
| Manual reporting or slow month-end close | CFO, finance controller | Which part of the reporting process is creating the most extra work? |
| An implementation has stalled | Project sponsor, CIO, programme owner | What is preventing the project from moving into the next stage? |
| Operational work depends on spreadsheets and re-entry | COO, operations manager, system owner | Where are people working around the system to get the job done? |
| A platform review or integration initiative is planned | CIO, enterprise applications leader | What prompted the review, and who needs to be involved in the decision? |
Those questions are more useful than asking whether someone wants an ERP demonstration before understanding the situation. They give the buyer room to describe the problem, correct your assumption or tell you that the timing is wrong.
Who should you call first?
The person with the most senior technology title is not always the best starting point. A CFO may own the reporting problem. An operations leader may be dealing with stock visibility or manual scheduling. A business systems manager may understand the platform limitations but need executive support for a change.
Map three roles: who experiences the problem, who can sponsor the work and who controls the decision process. One person may cover more than one role in a smaller organisation. A larger business may have finance, operations, technology and procurement involved.
The aim of the first call is to find that path. If the contact has useful context but is not responsible for the issue, ask who owns it. If they cannot or do not want to help, respect that. A job title on a contact list is not enough to establish influence.
What can an early cold call sound like?
Here is an illustrative opening for a finance-systems conversation. The premise should only be used when the caller has actually researched the account and the service fits.
Hi Alex, it’s Rahul from Leadscaler, calling on behalf of an ERP consultancy. I’m calling because your business appears to be operating across several entities. Is bringing finance reporting together something your team is working on, or is that already running well?
A useful response might be that reporting is fine, the problem belongs to someone else or the organisation is already reviewing its systems. Each answer changes the next step. The caller should follow the buyer’s explanation rather than push every answer towards a meeting.
If there is a problem, explore what happens now. What takes extra time? Who is affected? Has the business tried to fix it? Is there a reason to act this quarter, or is it a longer-term concern? A first call can establish useful context without trying to scope the implementation.
How do you qualify an opportunity before there is a project brief?
Early opportunities often have incomplete information. The buyer may know the problem but have no approved budget or final scope. That does not automatically make the conversation useless. It changes what you should expect from the next meeting.
Record the business impact, ownership, status and next decision. A finance team spending time reconciling multiple systems is different from someone casually exploring new software. A platform review planned for next year is different from an implementation that needs help now.
A practical handover might look like this:
- Account fit: A multi-entity Australian business that matches the consultancy’s delivery experience.
- Buyer role: Finance systems owner, with the CFO involved in approving a project.
- Active challenge: Reporting requires manual consolidation between systems.
- Timing: An internal review is planned; no implementation date has been approved.
- Unknowns: Budget, preferred solution and procurement approach are still open.
- Agreed next step: A discovery conversation about the current process and possible options.
This is an illustrative handover, not a customer result. It gives the expert team something specific to prepare for. The qualification criteria should reflect what your firm can use at that stage of the buying process.
What if the buyer is interested but not ready?
Do not turn a distant review into an urgent project in your notes. Capture what would change the timing and agree whether follow-up is welcome. A useful future action might be checking in after an internal review or sending a relevant example the buyer has requested.
Keep sales opportunities separate from longer-term market conversations. That makes pipeline reporting more honest and prevents the delivery team from planning around work that has not progressed.
Use the calls to improve your offer
The market may describe the problem differently from your service page. Your team might talk about integration architecture while buyers talk about duplicate entry, unreliable reports or a project that nobody owns.
Record those patterns across conversations. If several relevant buyers describe the same difficulty, review whether the service offer and account selection reflect it. If the assumed trigger rarely creates urgency, change the targeting before increasing activity.
Our article on cold calling as market intelligence covers how to separate useful patterns from a few isolated responses.
What should you measure?
Track conversations with relevant decision makers, the challenges discussed, accepted next steps, meetings attended and opportunities your team agrees are worth progressing. Record why accounts are excluded as well. That feedback helps improve the next account list.
Keep pipeline value and closed revenue separate. A conversation may reveal a possible implementation, but it is not a signed contract. When an opportunity enters pipeline, give it an honest value, stage and timing.
The Leadscaler campaign examples show the distinction between calls, decision makers reached, attended meetings, proposals and pipeline. For an ERP or IT consultancy, the purpose of outbound is to build a reliable way to find these conversations alongside vendor referrals and existing relationships.
Start with a specific segment, a credible business challenge and a clear standard for what reaches your team. You can review our research-led Australian B2B calling process or talk through your target accounts to decide how that would work for your market.
