Selling ERP systems means finding the few people who sign a software decision that cuts across several departments. You reach them in the month something changed in their business, and you earn a first meeting before a long evaluation begins.
For outbound, the work runs in this order:
- Name the person who signs, using the title their company really uses.
- Check a public signal that says the account is moving now.
- Send a short message on email and LinkedIn that asks for a call and nothing more.
My team books meetings for B2B sellers through cold email and LinkedIn. What happens from the first meeting onward is your own team's work, so most of this guide sits before that meeting.
What does selling ERP systems actually involve today?
Mostly, as with other technology sales, it involves a buyer who has already looked you up. When Gartner asked 632 B2B buyers in August and September 2024 how they like to buy, 61% said they would rather skip the sales rep (Gartner, June 2025).
The next round, 646 buyers in August and September 2025, put the rep-free share at 67% (Gartner, March 2026).
Both surveys cover B2B buying in general, so read them as a direction for ERP. Either way, the sale starts before anyone talks. The Finance Director reads your message, opens your LinkedIn page and website, and decides on the spot whether you are worth 15 minutes. Nobody buys from an email. First they audit you, and only then do they buy.
Our own campaign data points the same way. Two senders used identical copy. One of them saw a 2% reply rate. The other got 7.5%. The copy did not change. What changed was what buyers found when they looked up each sender.
That is also why one channel is rarely enough. For a UK firm selling software development and IT consulting (a different product, but the same kind of committee sale), we ran cold email and LinkedIn in parallel from 17 April to 17 May 2023:
| Result in that month | Cold email | |
|---|---|---|
| Positive replies | 41 | 62 |
| Sales meetings booked | 13 | 18 |
| Sales | 2 | 3 |
LinkedIn brought more replies, meetings and sales. Email still won 2 sales on its own, which is why I run the two channels as one sequence. Pick one and you lose part of the pipeline.
One signature, many people behind it. Gartner's May 2025 sales survey reports buying groups of 5 to 16 people drawn from as many as 4 functions. It also found that 74% of buyer teams show unhealthy conflict during the decision. A couple of messages will not move that group.
Who sits on an ERP buying committee and who actually signs?
An ERP buying committee is the group of people inside the buyer who each have to agree before the contract gets signed. Names change from company to company. This table lists the roles that usually matter in an ERP decision.
| Role | Real titles to search | What they need from message one |
|---|---|---|
| Economic signer (often finance) | CFO, Finance Director, Group Financial Controller | A problem they already own, such as a slow month-end close |
| Finance owner | Head of Finance Operations, Controller | A sign you have moved a finance team their size without breaking the close |
| IT owner | CIO, IT Director, Head of Business Systems | A hint that you understand their current systems and integrations |
| Operations owner | COO, Supply Chain Director, Plant Manager | Stock visibility and orders across sites |
| End-user lead | Financial Controller, Operations Manager | Proof that daily work gets easier |
| Procurement (larger companies) | Procurement Manager | Little in message one, but expect them in the cycle early |
The table gives you titles to search. It cannot tell you who signs at your kind of customer. For that, I go back through a client's past and current projects and find out who really approved each one.
Plan for a committee of approvers. Deloitte's ERP selection article, citing a Gartner study, says technology-buying teams had 12 to 14 participants. So map several names per account.
Forrester's State of Business Buying 2026 found that procurement is a decision-maker in 53% of buying cycles and is involved from the start.
If your ERP buyers are hospitals, the approval path changes again; it resembles the one described for US hospital suppliers.
Once I know who approved past deals, I search with the titles that niche uses. I also remove the plain labels: Assistant, Associate and a bare Manager pull in people who cannot approve a budget. A specific title such as Operations Manager stays, because it tells you what the person runs.
With the finance signer, start from a problem they already carry: a month-end close that drags, or stock they cannot see across sites. A list of modules makes them translate your product into their problem, and few will bother.
If your past deals show that finance holds the budget, write to the finance signer first. Bring the IT owner in when finance agrees the problem is real. Keep the pitch out of the first message too. The Sandler selling system explains why an opening message should only start a conversation.
Which trigger events show an account is ready for a new ERP?
A trigger event is a change that makes the current system hurt. The useful ones leave a public trace you can check in five minutes.
| Trigger | Public signal to check | Why it opens a conversation |
|---|---|---|
| New CFO or COO | LinkedIn job change, press release | A new decision-maker you can introduce yourself to early |
| Acquisition or merger | News, company announcements | Two sets of books now have to become one |
| New country or site | Press coverage, job posts in a new location | Stock, currency and tax across more than one place |
| ERP administrator or finance systems analyst hire | Careers page, job boards | Someone is being hired to run or fix a system |
| Fast headcount growth | LinkedIn headcount trend | More users and transactions than the current setup was built for |
| Entry-level accounting software at a growing size | Tools named in their own job posts | The classic first ERP move |
Look hardest at the last row. Software Path, an ERP selection platform, analyzed buyer projects in its 2022 ERP report. The most common move it found was from QuickBooks to a first ERP. Over 30% of companies implemented to support growth, while companies with over 500 employees most often did it to replace outdated legacy systems (Software Path).
That report is four years old and comes from one platform's buyers, so use it to shape questions only. With companies above 500 employees, ask about the legacy system they want to replace. With smaller ones, ask what growth is straining.
NetSuite's ERP statistics roundup lists the top 3 reasons as replacing legacy systems, consolidating applications and updating technology.
Intent data has a place, but only in a big market. Picture a territory of about 2,000 target companies where signals show up on about 10 of them. In that case my team skips intent data and writes an offer that speaks to every company on the list.
How do you build a list of ERP prospects that reaches the inbox?
For a reseller or implementation partner, the best list starts in your own CRM. Build it in this order:
- Export your current and past clients with industry, headcount and the system each one left behind.
- Find lookalike companies that match that profile in the same regions.
- Add the real titles from the committee table and drop the generic ones.
- Verify every address. My team does not send while the bounce rate sits above 0.5%.
- Set up SPF, DKIM and DMARC on every sending domain.
- Send only to the verified list, and check the spam rate every week.
Mail to Gmail accounts has its own rules. Google's sender guidelines require SPF, DKIM and DMARC from anyone sending more than 5,000 messages a day to Gmail (Google Workspace Admin Help). Gmail also tells senders to keep the spam rate in Postmaster Tools below 0.10% and to avoid ever reaching 0.30% (Gmail Help).
The same guidance says to email only people who want to get messages from you. I read that as a firm no to a bought list of "manufacturing CFOs", however tempting it looks. Our deliverability and infrastructure FAQ covers domains, warmup and monitoring in more detail.
What should the first email and LinkedIn note to an ERP buyer say?
In message one I ask for a short call and leave the product out. Pitching an ERP to a stranger in the first email is the quickest way I know to be ignored.
Here is a made-up example, including the company, the names and the proof line. An ERP partner in Manchester is writing to the Finance Director of a UK distributor that just opened a second warehouse and is hiring a finance systems analyst.
Subject: Leeds warehouse
Hi Claire,
I saw Northfield opened the Leeds warehouse this spring and is hiring a finance systems analyst.
When distributors your size add a second site, month-end close can get harder, because stock now sits in two places and the accounting software may only see one.
Two write-ups on our site show how we handled the same switch for Yorkshire wholesalers.
Would a 15-minute call next week help, to compare notes before you scope anything?
Tom
What each line does:
- Line one names the trigger, so Claire knows why the email reached her.
- Line two states a problem in her own language: the close.
- Line three gives one piece of proof she can check on Tom's website.
- Line four asks for 15 minutes and nothing else.
Cut these from a typical first draft of that email:
- A paragraph listing finance, inventory, CRM and payroll modules. She cannot weigh modules from her inbox.
- Two sentences of company history. Her opinion of Tom forms on the profile and website she will open anyway.
- A brochure attachment and a demo link. Both ask for a decision she has no basis to make yet.
Run that delete pass on your own first draft before you send anything.
The LinkedIn connection note is shorter still:
Hi Claire, I work with finance teams at UK distributors that are adding sites. Saw the Leeds news and would be glad to connect.
It has no link and no question to answer. Its only job is to put Tom's face and profile in front of Claire. Even a plain note works when the profile behind it is strong. An unknown sender gets ignored, however polished the wording. I like the email to arrive after a LinkedIn touch, so by then the sender is someone she has already looked up. For more wording options, see what a connection request note should say.
That first touch does more work than it looks. One German software development client is a good example. We sent 84 connection requests. 52 people accepted. 40 of those replied. Across the full 6-month campaign, that client booked 488 sales meetings. That was a software sale, so take it as the pattern to aim for with ERP buyers, without expecting the same count.
How many touches does it take before a busy finance or IT lead replies?
Usually more than most teams send. A Finance Director in quarter-end week can miss your first two messages without ever deciding against you.
I plan 5 to 6 touches per person. Spread them over LinkedIn and email. In our campaigns, the third follow-up usually books the meeting. That only works with real gaps between messages. Give every touch its own job: the trigger, a peer problem, one short proof, a question about where their selection stands.
The number I ask teams to track is conversations started each month. Conversations come first. Meetings grow out of them, and clients grow out of meetings. I would rather a team aim at 50 or more new conversations a month than at a fixed number of booked meetings.
Step by step, that is how LinkedIn and email run as one sequence.
What are the stages of an ERP sale and who joins each one?
Six stages, and outbound owns only the first.
| Stage | Who joins from the buyer side | Who owns it on the seller side |
|---|---|---|
| 1. First reply and discovery call | Finance or operations owner | Outbound books it; your account executive runs it |
| 2. Requirements and fit review | IT owner, end-user leads | Your solution consultant |
| 3. Demo | Wider committee | Your presales team |
| 4. Proposal and business case | CFO, procurement | Your account executive |
| 5. References and negotiation | CFO, legal | Your account executive, with client references |
| 6. Signature and implementation planning | Signer, IT owner | Your account executive and implementation lead |
Filling a calendar and turning meetings into signed ERP contracts are two separate jobs. Stages two to six are where your team wins or loses the deal, much as in any manufacturing sales process.
That makes one check worth doing before you add volume. If your team closes few of the meetings it already gets, more meetings will push that ratio lower, because volume does nothing about whatever is losing deals today.
Pull last year's discovery calls and count how many reached a signature. If that number disappoints you, fix stages two to six first. If it holds up, outbound has one job: put the right signer in stage one, in the month their business changed. Fix the funnel first. Then scale.
If you sell ERP and want to sanity-check who should hear from you first, bring your last five signed deals to a call and I will map the roles.
Questions ERP sellers ask about outbound
What is ERP selling?
ERP selling is the work of getting a company to replace or adopt the system that runs its finance, stock and operations data, and then signing that contract. For an outbound team, it starts much earlier than the demo: name the signer, confirm a public signal, then send one short ask for a call.
How long do companies spend choosing an ERP system?
In Software Path's 2022 report, a typical selection took 17 weeks, and bigger companies needed longer. Over 55% searched for cloud only, and about 3% searched only for on-premise (Software Path). In a first meeting, ask how many weeks the buyer has already spent, and whether cloud is settled.
How much does an ERP system cost the buyer?
The same Software Path report put the average budget at about $9,000 per user, up from $8,295 in 2021 (Software Path). Use it as a rough anchor for the business case conversation, not as a quote, because scope and user count move it a lot.
What reply rate should an ERP outbound campaign expect?
Across our campaigns the typical reply rate is about 1%, dropping toward 0.5% once daily volume reaches the thousands. Instantly's 2026 benchmark, built from its own platform data, reports a 3.43% average and 5.5% for the top quartile (Instantly, 2026). It is vendor data, so plan with the range that fits your own volume.
Should ERP sellers cold call prospects?
My team works mostly through cold email and LinkedIn and never runs pure cold calling or a dialing floor. Warm calls are an optional add-on for us, and only to people who already replied, engaged or opted in. For an ERP seller, the phone fits best after a Finance Director has answered in writing and asked to talk.
Can I cold email ERP buyers in Germany, Austria or the Czech Republic?
My team does not send cold email to those countries without a compliant basis, and uses LinkedIn outreach there instead. If your ERP territory includes them, settle the legal basis with your own adviser before you load a list, and keep exclusion lists and opt-out requests honored on every channel you run.
