ERP sales objections, questions and competitors

When they push back.

The objections ERP buyers raise most, what to say in the next ten seconds, and what not to promise.

"This is too expensive."

Expensive compared to what: your current costs, another quote, or the budget you had in mind?

Do not discount before you understand the comparison. Do not cut implementation scope just to lower the number.

"Migrating off our current system is too big a risk."

What worries you most about the move: the data, the downtime, or people adopting the new way of working?

Do not say migration is easy. Do not promise zero downtime.

"We built most of this ourselves."

What does your team spend its time on today: running the business logic or keeping the custom system alive?

Do not insult the team that built it. They may be in the room and may be your future champion.

"Now is not a good time."

Makes sense. What would need to happen for this to become a priority, and when is that likely?

Do not invent urgency. Do not pressure with fake deadlines.

"Security and IT need to approve where our financial data lives."

What does your security team need to see first, and who should I connect them with?

Do not answer security questions from memory. Route them to people who can answer accurately.

"We already run SAP (or Oracle, or Microsoft) and it's the standard here."

What works well with it today, and where do teams work around it?

Do not attack the incumbent or the people who chose it. Do not claim you replace everything they do.

Every one of these is a deal that slips a quarter if you fumble it. Ghost puts the answer on your screen while the buyer is still talking.

Download for Windows Download for Mac

When they name a competitor.

Give them credit, then ask whether that vendor's strength matters to this buyer.

SAP

SAP is the standard for many large global companies. How much of that breadth do you need, and how much change can your team absorb?

Oracle Fusion Cloud ERP

Oracle Fusion is a strong cloud ERP for large finance teams. Which of your processes need that level of depth?

Oracle NetSuite

NetSuite is popular with fast-growing companies moving off basic accounting. What do you expect to need in a few years that you don't need today?

Microsoft Dynamics 365

Dynamics fits well if you are deep in Microsoft already. How important is that tie-in compared to fit for your operations?

Infor

Infor builds industry-specific suites. How close is their industry version to how you actually run?

Epicor

Epicor is well known with manufacturers and distributors. Which of your plant-floor processes matter most in this decision?

Workday

Workday is strong when HR and finance want one platform. How much of your project is about people data versus operations?

Sage Intacct

Sage Intacct is a favorite of many finance teams. Is this a finance project, or do operations need to be in the same system?

IFS

IFS is known for asset-heavy and service-heavy businesses. How central are field service and maintenance to your decision?

Acumatica

Acumatica is popular in the mid-market for its flexible licensing. How fast do you expect user counts and complexity to grow?

Questions that qualify the deal.

Ask these on the first call. Then dig into the pain when they say it out loud.

Qualify

Which system is your source of truth for the books today, and what lives in spreadsheets around it?
What does close look like today, step by step, and where does it stall?
If nothing changes over the next year, what does that cost you, and who notices first?
Is there a date driving this, like end of support, an audit, a new entity, or a fiscal year start?
Who sits on the steering committee, and who has the final say if finance and operations disagree?
Has budget been approved for software and implementation, or is that part of what this evaluation decides?

Dig into the pain

"Our systems don't talk to each other." Where do people re-key data today, and what goes wrong when they do?
"We've outgrown our accounting software." What can't it do today that the business now needs, like entities, inventory, projects, or revenue rules?
"We have no real visibility into inventory and margin." If I asked for margin by product or customer right now, how would you get it and how long would it take?
"Our last ERP project went badly." What went wrong last time, and what would have to be different for you to try again?

Know who is in the room.

ERP (enterprise resource planning) is the system of record for how a company makes, buys, sells and accounts for things. It ties the general ledger to procurement, inventory, manufacturing, projects and order-to-cash, so finance and operations work from the same numbers. Most companies replace an ERP rarely, and the project touches almost every department.

Who buys and who signs

Economic buyer: Usually the CFO. In manufacturing and distribution, the COO often co-signs. The CEO and board get involved on large replacements.
Champion: The Controller, VP Finance, or a director of operations who lives with the pain of the current system every month-end.
Users: Accounting, AP and AR clerks, FP&A, buyers, planners, warehouse staff, plant managers, project managers.
Blockers: IT (integration, data migration, support load), security (access controls, audit trail, data residency), procurement and legal (contract terms, exit rights), and external auditors who want controls they can test. Department heads who run their own spreadsheets or point tools can quietly resist.

Signs the deal isn't real

No named executive sponsor, or the CFO has not heard of the project.
No trigger: the current system works and nobody can say what happens if they wait.
"We're just looking" with no budget cycle, steering committee or target go-live.
The consultant running the selection has already picked a vendor.
They want pricing before they can describe their processes.
IT is driving alone and finance or operations is not in the room.
An implementation partner is not part of the conversation at any stage.
They keep asking to see features unrelated to their business, a sign you are a benchmark for someone else.

15 words ERP buyers use

GL: General ledger, the core accounting record.
Close: The month-end or year-end process of finalizing the books.
Order-to-cash (O2C): From customer order through invoicing and collection.
Procure-to-pay (P2P): From purchase request through paying the supplier.
Intercompany: Transactions between legal entities of the same group, and the eliminations that follow.
Consolidation: Rolling up multiple entities into group financials.
MRP: Material requirements planning, working out what to buy or make and when.
BOM: Bill of materials, the parts list for a product.
Chart of accounts (COA): The list of accounts the ledger uses.
Fit-gap: Comparing requirements to standard features to find what needs configuration or custom work.
Customization vs configuration: Code changes versus settings; buyers want the second.
Two-tier ERP: A corporate ERP at headquarters with a lighter ERP at subsidiaries.
Go-live / cutover: The switch from the old system to the new one.
SI (systems integrator): The implementation partner.
Clean core: Keeping the ERP close to standard so upgrades stay simple.

Selling ERP: questions

What objections come up when selling ERP?

The most common are: "This is too expensive", "Migrating off our current system is too big a risk", "We built most of this ourselves", "Now is not a good time", "Security and IT need to approve where our financial data lives" and "We already run SAP (or Oracle, or Microsoft) and it's the standard here". Each one above has a line to say back and what to avoid.

What discovery questions should I ask a ERP buyer?

Start with: Which system is your source of truth for the books today, and what lives in spreadsheets around it? What does close look like today, step by step, and where does it stall? If nothing changes over the next year, what does that cost you, and who notices first? Is there a date driving this, like end of support, an audit, a new entity, or a fiscal year start?

Who are the main competitors in ERP?

Buyers most often compare SAP, Oracle Fusion Cloud ERP, Oracle NetSuite, Microsoft Dynamics 365, Infor, Epicor, Workday, Sage Intacct, IFS and Acumatica.

Who buys ERP?

Economic buyer: usually the CFO. In manufacturing and distribution, the COO often co-signs. The CEO and board get involved on large replacements.

How does Ghost help on ERP calls?

Pick the ERP market pack in Ghost's setup and every card on this page loads into Ghost. When a buyer raises one of these objections or names one of these competitors on a live call, Ghost shows you what to say on your screen, hidden from screen shares and recordings.

Other markets

CRM Cybersecurity Cloud infrastructure Data and databases DevOps and developer tools Observability Collaboration HCM and payroll Analytics and BI ITSM and IT operations Supply chain Marketing automation Contact center and CX Finance and spend Ecommerce PLM and CAD Healthcare EHR Payments and POS Applicant tracking

ERP: what buyers say on the call, and what to say back.