Finance & Accounting

ERP buyers, mid-evaluation.

ERP is the longest and most committee-heavy purchase in the finance stack. Buyers arrive on our pages already in trouble — outgrowing the system they have, or forced off it — and they compare a shortlist for months before anyone takes a call.

Part of a 500k–1M deliverable finance and accounting audience

What starts it

Nobody evaluates ERP for fun.

Outgrowing entry-level accounting

A company on QuickBooks or Xero hits multi-entity, multi-currency or revenue recognition and cannot stay. The shortlist is formed in weeks, and the first vendor to explain the migration usually stays on it.

A failed or painful audit

Controls and audit trail move to the top of the requirement list. Compliance language beats feature breadth in this moment.

A merger or a new entity

Consolidation across entities becomes the requirement overnight, and the incumbent is often ruled out on that one point.

End of life or a forced upgrade

An on-premise install going unsupported turns a deferred decision into a dated one. These buyers compare hardest, because they did not choose to be here.

Private equity ownership

A PE-backed group standardises systems across its acquisitions. The decision is made above the operating company, on a timetable set by the sponsor.

Who is in the room

The room grows every month this runs.

CFO or VP FinanceTotal cost over five years and whether the business can survive the implementation.

ControllerClose speed, audit trail and whether the month-end process actually improves.

Head of Financial SystemsData migration, integrations, and who owns the system afterwards.

IT and securityHosting, access control and the integration surface. Often holds a veto rather than a preference.

OperationsWhether inventory, projects or manufacturing survive the move intact.

Business unit or divisional leadsWhether their own process survives standardisation. In a multi-entity group this is where the project meets resistance.

Weighed against, by name

Three shortlists wearing one label.

NetSuiteMicrosoft Dynamics 365Sage IntacctAcumaticaOdooEpicorInforSAP

Seven or eight names, but they are not one shortlist — they are three. A mid-market finance team compares NetSuite, Sage Intacct and Acumatica; a manufacturer compares Epicor and Infor against the same two; an enterprise already running Microsoft compares Dynamics against SAP and nothing else. A vendor who treats this as one pool is pitching against the wrong half of it.

Every lead we deliver carries the vendors that person put side by side on the page, by name and with a timestamp — so your rep knows which of these they are actually up against before the first call.

How size changes it

The same category is bought three different ways.

Under 200 staffThe real competitor is staying on QuickBooks or Xero for another year. The evaluation is led by a controller with no implementation experience, and the thing that decides it is whether the first year of cost is survivable, not feature coverage.

200 to 1,000 staffThe implementation partner matters more than the software. Buyers at this size have usually heard an ERP horror story from a peer and are shopping for a safe pair of hands as much as a system. Reference calls carry disproportionate weight.

1,000 staff and aboveIT and procurement are now running it, the timeline stretches past a year, and the question shifts to what the existing Microsoft or SAP estate forces. Finance is a stakeholder rather than the buyer.

Why the deal stalls

Most ERP evaluations die in the middle, not at the end.

Scope grows past the budget

Every department that hears about the project adds a requirement. The business case that justified the project stops matching the quote, and the whole thing goes back for re-approval.

The partner question arrives late

Buyers compare software for months and only then discover the implementation partner is a separate choice, separately priced, and often the bigger risk.

Data migration gets inspected

Someone finally opens the legacy chart of accounts. The cleanup effort is larger than anyone scoped, and the go-live date moves.

A champion changes job

These evaluations run long enough that the controller driving it can leave before it closes. The deal does not die loudly; it goes quiet.

What they read

What a long evaluation needs feeding.

Implementation and migration guides

The real fear is not the licence, it is the project. Content that treats the migration honestly gets read to the end.

Total cost of ownership breakdowns

Published pricing is rare in ERP, so anything that models five-year cost gets downloaded and forwarded to the CFO.

Requirements and RFP templates

The committee needs a shared document. Supplying it puts a vendor inside the buyer's own process.

Head-to-head comparisons

NetSuite against Dynamics, Intacct against the incumbent. This is what they came to the page to read.

How a program runs

ERP suits content syndication with a long nurture behind it, because the gap between first read and first call is measured in months rather than weeks. Leads carry the consideration set, so a vendor can see which of NetSuite, Dynamics or Intacct they were weighed against on the page, and brief sales accordingly rather than guessing.

Runs on FinanceOpsClub, Spotsaas · Typical spec: Standard — from $45

Also covered

Other categories we publish in.

Accounts Payable AutomationTriggers, committee and consideration set →

Before you ask

What vendors get wrong about ERP buyers.

How long does an ERP evaluation actually run?

Long enough that most vendors mistake a quiet period for a loss. The buyer is usually still inside the process, held up by scope, the implementation partner question or data migration rather than by a competitor.

Who really decides an ERP purchase?

It depends on size. Below a few hundred staff the controller decides and finance owns the budget. Above a thousand, IT and procurement run the process and finance becomes one stakeholder among several.

Is the incumbent the main competitor?

Often, yes. In the smaller half of this market the thing a vendor loses to is the buyer deciding to stay on entry-level accounting for another year, not to a rival ERP.

Is the implementation partner chosen separately?

Usually, and buyers often discover it late. The software decision and the partner decision are separately priced and separately risky, and the partner is the one more likely to determine whether the project succeeds.