RTRoutetrack Tech
Guides › Implementation

Are You Ready to Buy an ERP? A 22-Step Readiness Assessment Before You Sign

Most ERP overruns are locked in before the contract is signed. These 22 checks on process ownership, data quality, contingency and backfill help you find the gaps while you still have negotiating leverage.

Routetrack Tech editorial team · November 2026 · 8 min read

Find Your Gaps Before the Statement of Work Finds Them

You've narrowed the field to two vendors. The implementation partner wants a signature by quarter end, and the discount depends on it. Before you sign, you need to know one thing: does your organization have what this project assumes it has? An ERP readiness assessment answers that. It tells you whether to sign now, sign with conditions, or wait 60 to 90 days.

Most change orders trace back to things the buyer could have found out beforehand. Processes nobody documented. An item master full of duplicates. Key users who were never given time off their day jobs. Integrators price their work on assumptions, and every assumption that turns out wrong becomes a billable change.

Advertisement

Here's how to score it. Rate each of the 22 steps below 0 (not started), 1 (partial) or 2 (done, with evidence). The maximum is 44. The evidence rule is strict: "done" means there's a document you could hand to the integrator today. A meeting where people agreed doesn't count. Give it three to six weeks with a small group: the CFO or COO, your IT lead, and two senior operations people. Treat it as the core of your ERP project preparation, not an extra.

Steps 1–4: Lock the Business Case and Decide Who Can Say Yes

  1. Write an ERP business case with measurable outcomes. Pick three to five targets and record today's baseline for each. Examples: cut the month-end close from 12 days to 6, raise inventory accuracy from 92% to 98%, or reduce days sales outstanding by 5. Without a baseline you can't prove value later, and scope drifts toward whatever the loudest department wants.
  2. Name an executive sponsor who controls budget. This person settles disputes between finance and operations and should expect to give the project a meaningful share of their week, often 10–15% at peak. A sponsor who hands the job to IT is a red flag.
  3. Set up a steering committee with written decision rights. Decide who can approve scope changes and up to what amount. For example, your project manager approves changes up to $10,000 and anything larger goes to the committee.
  4. Get formal executive sign-off on scope, total budget including contingency, and the target go-live window. Where your governance requires it, that means the board, not just the leadership team.

Steps 5–8: Assign Process Owners and Map What Actually Happens

  1. Name a business owner for each end-to-end process: order-to-cash, procure-to-pay, record-to-report, plan-to-produce and warehouse execution. The owner makes design decisions and signs off on testing. IT supports but doesn't own the process.
  2. Do current-state ERP process mapping for your top 8–12 processes. Swimlane diagrams are enough; skip the 200-page binder. What matters is the exceptions: returns, backorders, intercompany transfers, consignment stock, drop-ships and credit holds. That's where implementation estimates go wrong.
  3. Agree on future-state principles. The default should be "adopt the vendor's standard process unless it erodes a genuine competitive advantage." Write down the short list of deviations that are truly non-negotiable.
  4. Build and rank a gap list. Sort each gap into configure, extend, work around, or drop. Then run scripted demos built from your own maps and make each vendor classify every gap against its standard product. Each extension adds build cost and upgrade-testing work, so the length of this list is a major cost driver.

Steps 9–12: Sample Your Data Before You Promise a Migration Date

  1. Inventory every data source: the legacy ERP, spreadsheets, WMS, TMS, CRM, e-commerce platforms and any local systems at subsidiaries.
  2. Sample each master data domain. Pull 100–200 random records each for customers, suppliers, items, bills of materials and locations. Check for duplicates, missing units of measure, invalid tax IDs, wrong addresses and obsolete items. Record the error rate for each domain.
  3. Assign data owners and a cleansing plan, and start cleansing before the contract, not during the build. If any domain's error rate is above roughly 10%, treat cleansing as a funded workstream.
  4. Decide how much history to migrate. Moving open transactions plus balances is cheap. Moving years of line-level history isn't. Most companies are better off archiving old data in a read-only store.

Hypothetical worked example: say a distributor has 40,000 active SKUs. It samples 200, and 34 have problems, a 17% error rate. That suggests roughly 6,800 items need fixing. At 3–5 minutes per record, that's about 340–570 hours of skilled work. If nobody has budgeted for it, it comes back later as a change order.

Steps 13–16: Build a Five-Year Budget and Set ERP Budget Contingency

  1. Model five-year total cost of ownership. Include subscription, implementation, integrations, data migration, training, internal staff time and post-go-live support.
  2. Check the services-to-subscription ratio. For mid-market cloud ERP, first-year implementation services often run one to two-and-a-half times the annual subscription, though this varies widely. A quote far below your comparable bids usually means work has been quietly left out of scope.
  3. Set ERP budget contingency at 15–25% of services and internal costs. Go higher, toward 30%, if you're rolling out to several countries, customizing heavily, or found high error rates in step 10. The steering committee should hold the contingency. Don't add it to the vendor's purchase order.
  4. Fund internal costs explicitly: backfill, travel, extra sandbox environments, test automation tools and super-user training.
Cost lineTypical 2026 market range (50–500 users)Notes
Cloud ERP subscription$70–$250 per user per monthDynamics 365 Business Central sits near the low end. Dynamics 365 Finance and SCM, NetSuite with add-ons, SAP S/4HANA Cloud and Oracle Fusion sit higher. Acumatica prices by resources, not users
Implementation services$75,000–$1M+Partner rates of roughly $50–$250/hour, lower in India and Eastern Europe
Integrations$10,000–$60,000 eachWMS, TMS, EDI, banks, e-commerce
Data migration and cleansing10–20% of servicesHigher when sample error rates are high
Training and change management5–10% of project costOften the first line cut, and usually a mistake

These are typical ranges that vary by contract, region and negotiation. Confirm with each vendor and partner.

Steps 17–19: Free Up Your People and Pay for Backfill

  1. Commit core-team time in writing. Process owners typically need 30–50% of their time during design and testing. Above about 100 users, plan for a full-time project manager on your side as well as the integrator's.
  2. Budget for staff backfill. Use temporary staff, contractors or paid overtime to cover key users' day jobs. Hypothetical: three key users at 50% for eight months is roughly one full-time role for a year. Depending on the country, contractor cover for that can run from the low tens of thousands of dollars to well over $100,000. Skip it and your best people end up testing on weekends while quality drops.
  3. Plan change management and role-based training. Appoint super users, write a communication plan, and check local employment rules. In Germany, for example, works councils generally have co-determination rights over systems that can monitor employee performance, and other European countries have their own consultation requirements. Ask employment counsel early, because consultation can add weeks.

Steps 20–22: Check Integrations, Local Compliance and Contract Terms

  1. List every integration: the system, the direction of data flow, how often it runs, its volume and who owns it. Don't forget carrier APIs, EDI partners, bank connections and payroll.
  2. Confirm localization and compliance country by country. E-invoicing mandates differ widely and keep changing. Examples include India's GST e-invoicing, Mexico's CFDI, Saudi Arabia's ZATCA requirements, Poland's KSeF and Malaysia's MyInvois, with further EU reforms in progress. Data-protection and residency rules also vary, including GDPR, India's DPDP Act and Saudi Arabia's PDPL. For each country, ask whether compliance is built into the product or supplied by a third-party add-on, and who updates it when the rules change. Your tax advisor should confirm current requirements.
  3. Review the statement of work and how change orders are handled. Look for a clear list of assumptions, defined deliverables, acceptance criteria, a fixed rate card for changes, a named owner for data migration, data-export rights on exit and caps on renewal price increases. Have a contract lawyer review it before you sign.

Reading Your Score: Sign, Sign With Conditions, or Wait

ScoreWhat it meansDecision
36–44Ready, with minor gapsSign, and keep the full contingency
26–35Workable, but specific risks remainSign with conditions: close the named gaps before design starts
16–25The integrator's assumptions won't holdDelay 60–90 days or run a paid discovery phase
0–15Not readyGo back to the business case before talking to vendors

One rule overrides the total. A zero on step 2 (sponsor), step 10 (data sample), step 15 (contingency) or step 18 (backfill) means don't sign, whatever the overall score. Any one of those gaps can push the timeline back by a quarter or more.

Next step: book a 90-minute workshop this week and score your ERP readiness assessment honestly. Then send the gap list to both shortlisted vendors and ask each to price closing those gaps. How they respond will tell you which partner to choose.

Quick answers

How long does an ERP readiness assessment take?

For a mid-market company, three to six weeks is typical. Most of that time goes on process mapping and data sampling. If it runs past two months, unclear ownership is usually the cause, which is itself a readiness gap.

Should we pay for a discovery phase before signing the full contract?

If you score below 26, yes. A paid discovery phase commonly runs a few weeks to a couple of months and, as a typical 2026 range, costs roughly $15,000–$75,000 depending on scope and region. Confirm with vendors. It turns the integrator's assumptions into verified facts and makes the main estimate far more reliable.

How much ERP budget contingency is realistic?

Set 15–25% of services and internal costs as the baseline. Raise it toward 30% for multi-country rollouts, heavy customization or poor data quality. Keep it under steering-committee control so it isn't spent automatically.

Can the ERP vendor or partner run the readiness assessment for us?

They can help, but they want the contract signed, so they have a conflict of interest. Use their input on data and integrations, but have your own team or an independent advisor do the scoring. Never let the vendor grade your readiness alone.

What if our data sampling shows very high error rates?

Start cleansing right away and don't commit to a migration date until error rates in critical domains fall to roughly 10% or below. Migrate less history to cut volume. Treat cleansing as a funded workstream with named owners, not a task for spare time.

Do we need to map every process before signing?

No. Map the top 8–12 end-to-end processes and their main exceptions. That's enough for credible estimates and scripted demos. Detailed design comes after signature, during implementation.

Written by the Routetrack Tech editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.