ERP Selection Criteria: 12 Questions Every Mid-Market CFO Should Answer First

ERP selection criteria are the diagnostic questions that determine platform fit before any vendor demo happens. There are twelve that matter for a mid-market ERP decision, and the pattern of your answers points toward NetSuite, Rillet, Campfire, or the honest conclusion that you should wait.

This is a guide for the Office of the CFO working through an ERP buying guide the right way: requirements first, vendor conversations second. Zanovoy is an Oracle NetSuite Alliance Partner and an implementation partner for both Rillet and Campfire. We deliver all three, which means we have a stake in this and also no reason to push any one of them. This guide works through each question in the order it should be asked. If you want the platform-by-platform comparison first, our guide on how to choose an ERP, covers how NetSuite, Rillet, and Campfire compare against each other. This one is about diagnosing your own business first, before that comparison matters.

Why Most ERP Selections Start in the Wrong Place

The usual sequence is backwards. A CFO books three demos, builds a feature comparison, and picks a winner. Requirements get written afterward, reverse-engineered from whichever platform impressed most. Real ERP requirements gathering happens before the first demo, not after it.

The cost of that sequence is documented. Gartner has found more than 70 percent of ERP implementations fail to meet their original objectives, and most fail because of how the system was set up rather than which system it was. Failed mid-market implementations routinely run $500,000 to $2 million once you count sunk vendor fees, consulting overruns, and the disruption of starting again. Panorama Consulting and Standish Group research puts the share of projects that blow budget, miss go-live, or miss their operational goals at 50 to 75 percent.

That is not an argument against ERP. It is an argument for answering these twelve ERP evaluation questions before anyone schedules a demo.

1. Operational Scope: Product Business or Pure SaaS?

This is the first knockout question because it eliminates entire categories. If you hold inventory, manufacture anything, or run field service, AI-native finance platforms are out. Rillet and Campfire are finance systems, not operations systems, and no amount of AI extends them into work they were not built to do.

Pure SaaS and services businesses have the opposite problem: buying a platform designed to run a warehouse means paying for modules that stay switched off for years.

2. Entity Structure and Consolidation Needs

Count your legal entities, then count your currencies. A single entity in one country keeps every option open. As entity count and currency complexity grow, consolidation capability starts separating platforms, and the real difference is localization depth, not whether a platform can technically add up more than one entity.

All three platforms handle multi-entity consolidation as a mechanical capability. Campfire supports consolidation across 180-plus currencies, and Rillet handles multi-entity consolidation too. But consolidating currencies is not the same thing as localization: local statutory reporting formats, in-country tax compliance, translated interfaces, and country-specific regulatory filing requirements. NetSuite OneWorld includes multi-language support and has built out two decades of local compliance depth across dozens of countries. Campfire and Rillet are newer platforms built primarily around the US and SaaS markets, and while their consolidation mechanics are genuinely capable, neither has the same documented breadth of country-specific localization that NetSuite has accumulated over 20-plus years.

For a business operating across a handful of English-speaking jurisdictions with straightforward tax requirements, that gap may not matter much. For a business with real international footprint, multiple statutory reporting regimes, or local-language requirements, it usually does. At the highest end of multi-entity complexity, intercompany eliminations, multi-subsidiary tax, and regulatory consolidation across dozens of jurisdictions, NetSuite OneWorld is usually the practical answer for that reason, not because the others can't consolidate at all.

3. Compliance: SOX and GxP Readiness

Regulated industries change the calculation, though not the way most vendors imply. NetSuite is SOC 1 Type II and SOC 2 Type II audited at the platform level, and it has a long track record of implementations across regulated verticals. But no ERP is compliant out of the box, regardless of which regulatory framework applies, and no platform should be evaluated on a vendor's compliance claims alone.

Archer Insights, a life sciences validation practice, puts it plainly: NetSuite has the features to support SOX-compliant controls, but none of it is on by default, and a system set up for speed leaves most of it switched off or configured too loosely. Validation is work performed on an implementation: risk assessment, protocols, testing, and documented evidence. That work costs the same whichever platform you validate, and it's the validation, not the vendor, that determines whether a specific system is actually compliant.

The real differentiator for regulated businesses is operational scope, not compliance marketing. Life sciences companies typically need inventory, batch records, and traceability alongside the ledger, and that requirement, not a compliance checkbox, is what points ERP for life sciences decisions toward NetSuite in 2026 and beyond.

4. Close-Cycle and Reporting Demands

How many business days does your close take, and where does it stall? Reconciliations and intercompany eliminations point to a consolidation problem. Revenue recognition points to contract complexity. Waiting on someone to build a report in Excel points to reporting architecture. Each diagnosis leads somewhere different, which is why close time alone tells you little. The stall point is the signal.

5. Implementation Budget: What Does it Actually Cost?

Software subscription is the smaller number. Scoping, integrations, data migration, configuration, training, and support are where the budget actually goes. First-year NetSuite cost typically runs $100,000 to $500,000 and up for a mid-market company. Rillet and Campfire typically cost less for in-scope use cases, though neither publishes pricing, and the actual number varies by entity count and transaction volume. An honest ERP implementation cost comparison has to include all of it, not just the license line, and the gap between platforms narrows across five years.

Watch the implementation-versus-installation distinction. Offers promising configuration in four to six weeks are usually installation: the platform gets switched on, documentation gets handed over, and chart of accounts design, revenue recognition, and consolidation structure become your team's problem. Those decisions determine what the system can do for a decade.

6. IPO or Acquisition Timeline

An exit clock changes the answer. Auditor familiarity, control maturity, and the ability to produce evidence quickly matter more than feature lists when diligence starts. NetSuite has the deepest audit-firm familiarity and powered 61 percent of US technology IPOs since 2011. Rillet is SOC 1 Type II. Campfire supports a public company but has a shorter track record.

IPO finance readiness is really an audit-readiness question wearing a different name. With an exit 18 to 24 months out, choose the audit you will face rather than the workflow you have now.

7. Internal Finance Bench

How many people are in finance, and what is their seniority? A one-to-three-person team benefits disproportionately from AI-native automation because the platform absorbs work nobody has capacity for. A larger team with specialists often values platform breadth more than automation.

This also predicts implementation success better than most criteria. Undisciplined scope creep and unclear decision rights are the two leading causes of failure at mid-sized companies, and both are bench problems rather than software problems.

8. Integration Map

List every system that must exchange data with the ledger: CRM, billing, payroll, expense, banking, and tax. That list is your finance technology stack, and the ERP is only one piece of it. Then mark which connections are real-time and which can run nightly.

NetSuite has 600-plus certified SuiteApps and the widest ecosystem. Rillet and Campfire ship native connectors to the modern finance stack, Stripe, Salesforce, Ramp, Brex, and Rippling among them. The question is not which has more integrations but whether the five you actually depend on exist and are maintained.

9. AI Tolerance

How much automation is your team prepared to trust, and what does your auditor accept? Rillet and Campfire were built finance-first with AI embedded in journal entries, revenue recognition, and flux analysis. NetSuite added AI capability as a layer on an existing platform.

Neither approach is automatically better. What matters is whether automated entries are explainable to an auditor and whether your controller is comfortable reviewing rather than preparing. Teams that need every entry built by hand will not get value from AI-native architecture, whatever it costs.

10. Vendor Independence

How much of your operating model would sit inside one vendor's ecosystem, and what would it take to leave? Deep single-vendor stacks reduce integration overhead and raise switching cost; best-of-breed stacks do the reverse. There is no correct answer, but there is a correct time to ask, because heavy customization quietly converts a reversible decision into an irreversible one and accumulates after go-live rather than during selection.

11. The Five-Year Scenario Test

Describe your business at three times current revenue. New entities? New countries? Physical product? An acquisition to integrate? Now ask which platform still fits that description and what the migration would cost if it does not.

A Censuswide survey of 4,295 global executives found 36 percent believe the traditional ERP model will become obsolete, replaced by modular API-driven architectures. Whether or not that proves right, today's selection is an architectural bet with a longer horizon than most buyers assume.

12. Should You Be Buying at All?

The twelfth question is the one no vendor asks. If your finance team is two people, revenue is under $5 million, and QuickBooks is working, the right answer is often to wait, hire a controller, and revisit in twelve months.

In our advisory work the pattern holds steady: roughly half the time NetSuite fits, roughly a third of the time Rillet or Campfire does, and in the remaining cases the recommendation is to do nothing yet. The most expensive ERP project is the one a company runs eighteen months too early.

How To Use Your Answers

Questions one through three are knockouts that eliminate options. Four through eleven rank whatever survives. Twelve is the sanity check nobody runs. Read the pattern rather than any single answer, since almost every company has one criterion pulling against the others.

Write your answers down before the first demo. Turn your twelve answers into an ERP RFP template instead of a blank page, and the vendor conversation changes, a conversation held against documented requirements produces different answers than one held against a feature list a salesperson hands you.

If you want the full platform-by-platform comparison once your answers are in hand, How to Choose the Right ERP in 2026 walks through how NetSuite, Rillet, and Campfire actually compare

Quick Reference: What Your Answers Point Toward

Question	If your answer is	Direction
1. Operational scope	You hold inventory, manufacture anything, or run field service	NetSuite. Rillet and Campfire are out
1. Operational scope	Pure SaaS or services, no physical operations	Rillet or Campfire stay in play
2. Entity structure	Single entity, one country	All three remain open
2. Entity structure	Many jurisdictions, local statutory reporting, translated interfaces needed	NetSuite OneWorld, on localization depth, not consolidation mechanics alone
3. Compliance	Regulated industry needing inventory, batch records, and traceability	NetSuite, on operational scope; no platform is compliant out of the box
5. Budget	Roughly $100,000 or less available in year one	Rillet or Campfire more likely to fit
6. Exit timeline	IPO or acquisition inside 18 to 24 months	Weight audit familiarity heavily; NetSuite has the deepest track record
12. Buying at all	Finance team of two, revenue under $5 million, QuickBooks still working	Wait twelve months and hire a controller first

Turn These Answers Into a Real Evaluation

Twelve answers on their own are a self-assessment. Scored and weighted against your specific operational profile, they become a defensible recommendation, the kind you can hand to a board or an investor, not just a personal read. The ERP Selection Scorecard does that scoring: the same categories covered above, weighted for your entity structure, compliance footprint, and stage, ending in a ranked recommendation across NetSuite, Rillet, and Campfire instead of a gut call.

Take the ERP Selection Scorecard: NetSuite vs. Rillet vs. Campfire.

Score your twelve answers against a weighted framework built for the Office of the CFO. Independent of which platform, if any, Zanovoy ends up implementing.

Frequently Asked Questions

Twelve criteria matter: operational scope, entity structure, compliance footprint, close-cycle demands, implementation budget, exit timeline, finance bench, integration requirements, AI tolerance, vendor independence, a five-year scenario test, and whether to buy at all. The first three are knockouts that eliminate platforms outright; the rest rank whichever options survive.

Gartner has found more than 70 percent of ERP implementations fail to meet their original objectives, and most fail because of how the system was configured rather than which system was chosen. At mid-sized companies the two leading causes are undisciplined scope creep and unclear decision rights, both organizational problems rather than technical ones.

No ERP is compliant out of the box, regardless of the regulatory framework. NetSuite is SOC 1 Type II and SOC 2 Type II audited at the platform level and has a long track record in regulated verticals, but whether a specific implementation is compliant depends entirely on the validation work done on it: risk assessment, protocols, testing, and documented evidence.

First-year NetSuite costs typically run $100,000 to $500,000 or more. Rillet and Campfire typically cost less for in-scope use cases, though neither publishes pricing and the actual figure varies by entity count and transaction volume. The gap narrows over five years. Failed mid-market implementations routinely cost $500,000 to $2 million once sunk fees, consulting overruns, and restart disruption are counted.

Yes, as a consolidation mechanic. Campfire supports multi-entity consolidation across more than 180 currencies, and Rillet handles multi-entity consolidation as well, so the capability is not exclusive to NetSuite. The real differentiator is localization depth, local statutory reporting, translated interfaces, and country-specific tax compliance, where NetSuite OneWorld's two decades of built-out coverage still outpaces newer platforms, not whether a platform can add up more than one entity.

When the current system still works and the finance team lacks capacity to run an implementation. If finance is two people, revenue is under $5 million, and QuickBooks is functioning, waiting twelve months and hiring a controller first is often the better decision. The most expensive ERP project is one run eighteen months too early.

The same twelve categories used to diagnose fit: operational scope, entity structure, compliance requirements, close-cycle demands, budget, exit timeline, internal bench, integration map, AI tolerance, vendor independence, a growth scenario, and a documented reason for buying now rather than later. An RFP built from those answers gets more honest vendor responses than one built from a generic template.