ERP Consulting. Choose Before You Buy.
ERP consulting is the planning work that decides whether an ERP project succeeds: what your business needs, which products can meet it, where each one falls short and what the rollout should cost. We write that down in a scorecard, a gap analysis and a roadmap you own, so the licence decision is made on evidence and not on a demo.
What Is ERP Consulting?
ERP consulting is advice, written as a scorecard you can check, on choosing and planning an enterprise resource planning system. It sits in front of an implementation. A consultant interviews the people who run orders, stock, production, purchasing and the books, writes down what the system must do, and tests each candidate product against that list.
Companies usually come to us at one of four moments: spreadsheets and QuickBooks have stopped keeping up, a vendor quote arrived and nobody can tell if it is sound, an earlier ERP project stalled, or the business is about to add a warehouse, a plant or a second company. In each case the cheapest fix is to find the problem on paper.
We run ERP consulting for businesses in the United States as a remote team, through online workshops and shared documents. The table shows where consulting ends and implementation begins.
| ERP consulting | ERP implementation | |
|---|---|---|
| Question it answers | Which system, and what will it take? | How do we build and launch it? |
| Main output | Requirements, scorecard, gap analysis, roadmap, budget | A configured, tested system with your data in it |
| Who needs it | Teams with several options or unclear scope | Teams with a decision already made |
| Risk it removes | Buying the wrong product or underestimating scope | Launching late or with bad data |
| Where to read more | This page | Odoo implementation |
Not sure which of the two you need? Describe your situation and we will tell you plainly.
Book a CallERP Consulting Services
Each service stands alone, so you can buy only the part you need, from a requirements review to a full selection.
Requirements Mapping
We can interview each department and document how work really flows today: quotes to cash, purchase to payment, stock moves, month-end close and the approvals in between. Each requirement is written as a testable sentence and ranked as must-have, should-have or nice-to-have, so the scorecard has something firm to measure against.
MapERP Selection
A shortlist of products that fit your size and sector, scored against your weighted list.
SelectGap Analysis
Every requirement marked by how a product meets it, with the custom work sized.
GapsData and Integration Review
We look at the quality of your customer, item and ledger data and list every system the ERP must talk to: ecommerce store, CRM, shipping, payments, payroll or a bank feed. Messy data and unplanned integrations are two of the most common sources of late projects, and both are cheaper to find during planning than during a rollout.
DataRoadmap and Budget
A phased plan with owners, dependencies and a cost range for each phase.
PlanQuote and Partner Review
We can give a written second opinion on a vendor quote or a partner proposal you already hold.
ReviewFrom Messy Requirements
to a Written Roadmap.
Each step ends with a document you can read, challenge and keep. Nothing is held back for a later phase.
Kickoff and Scope
We agree which departments, entities and systems are in scope, who makes decisions and which questions you most need answered. The output is a one-page scope note and a workshop calendar.
Process Workshops
Short online sessions with the people who do the work, not only managers. We collect real documents: an invoice, a bill of materials, a pick list, a month-end checklist. Real documents expose exceptions that interviews miss.
Requirements and Weights
We turn the notes into a numbered requirements list and ask you to weight it. This is where internal disagreements surface, which is the reason to do it before a vendor is in the room.
Shortlist and Scoring
We choose candidates, read each vendor's documentation and pricing, request quotes where prices are not published, and score every product against the weighted list. Each score points to the page or document that supports it.
Gap Analysis and Cost Model
For the leading one or two products we classify each requirement and estimate the custom work, data migration and integrations. We then model licences and services over several years so the comparison is not only year one.
Roadmap and Handover
You receive the roadmap, the scorecard and the gap list in editable formats, plus a walkthrough call. If you choose to proceed with Devvista we continue from these documents. If you do not, you can hand them to any other partner.
What You Receive
The deliverables are the product. They are written to be reused by a vendor, a partner or your own staff, and they are handed over in editable form.
| Document | What it contains | Why it matters |
|---|---|---|
| Requirements register | Numbered, testable requirements with a priority and an owner | The yardstick for every vendor demo and quote |
| Weighted scorecard | Criteria, weights and a score per product with a source for each score | Lets you check our reasoning and reuse it |
| Gap analysis | Each requirement classified by how a product meets it, custom items sized | Shows where the budget difference between products comes from |
| Data readiness note | Quality issues in customers, items and ledger data, and a cleanup plan | Bad data is a common cause of late go-lives |
| Integration map | Every connected system, direction of data and method | Prevents integration work from appearing late in the project |
| Cost model | Licences, services and internal time over several years, with assumptions listed | Makes the comparison honest beyond year one |
| Roadmap | Phases, owners, dependencies, risks and a cost range per phase | What you hand to the implementer |
Comparing ERPs on Facts, Not Demos
Demos show the best path through a product. We prefer to compare what vendors publish and what a proposal says. Below is the kind of comparison we build, using two products whose pricing pages we opened on 9 November 2026. List prices change, so check the linked pages before you rely on a figure.
| What we check | Odoo | Microsoft Dynamics 365 Business Central |
|---|---|---|
| How pricing is shown | Per user per month on a public pricing page, with an entry plan limited to one app, then Standard and Custom plans for all apps | Per user per month on a public pricing page |
| Published tiers | One App entry plan, Standard, Custom and a Light User price | Essentials at $80, Premium at $110 and Team Members at $8 per user per month, billed yearly |
| What changes between tiers | Only the Custom plan lists external API access; Odoo.sh hosting costs and maintenance of custom code are not included in the listed price | Premium adds service management and manufacturing to Essentials; Team Members have limited access to read data, approve workflows and update selected records |
| What the page warns | Discount applies to initial users for the first 12 months | Prices are informational and may differ by currency, country and region |
| What to confirm in a quote | Hosting choice, custom modules and who maintains them, number of full and light users | Which users need Premium features, add-ons, partner services and regional pricing |
Reading list prices side by side is only the first step. Total cost also includes implementation services, data migration, integrations, training and the internal time your team gives up. A product with a higher licence price can be cheaper over five years if it fits your processes with fewer custom items, and the reverse is also true. That is why the gap analysis comes before the final recommendation.
We do not rank products in the abstract. A manufacturer, a distributor and a services firm will weigh the same criteria differently. If you are already comparing two named systems, our Odoo versus NetSuite guide and Odoo pricing guide give the background.
How We Classify a Gap
A gap is any requirement a product does not meet exactly as shipped. Counting gaps is not enough, because a missing report and a missing costing method are very different sizes. We sort every requirement into one of six groups and attach a rough size to each.
| Group | Meaning | Effect on budget |
|---|---|---|
| Fits as shipped | The standard feature does the job | No extra cost |
| Settings change | Configuration inside the product meets the need | Small, one-off consulting time |
| Light extension | A field, report or rule added without changing core logic | Small to medium, plus upgrade testing |
| Integration | Another system must supply or receive the data | Medium, and a recurring support item |
| Process change | Your process adapts to the product | No build cost, but needs staff buy-in and training |
| Custom build | New logic that the product does not offer | Largest cost, and a long-term maintenance duty |
The last group deserves caution. Every custom build must be tested again at each version upgrade and someone must own it. When two products are close on features, the one with fewer custom builds is usually the safer choice. We show the count and the estimate for each so you can see the trade-off.
Pricing ERP Consulting
After a short call we write the quote to your scope, and we ask what budget range you are working with so the proposal fits it. Scope, complexity, integrations and the seniority of the people involved are what shape the total. For consulting, a fixed price fits a defined scope such as one department or one shortlist. Hourly fits an open question or a vendor-quote review where the size of the problem is not known yet.
Your real figure depends on the level of consultant, the number of documents and the answers you need.
| Scope | Typical fit | Pricing model (typical placement in our estimates, scoped per project) |
|---|---|---|
| Requirements review for one department | One team leaving spreadsheets | Fixed price (typical placement in our estimates, scoped per project) |
| Vendor quote or proposal review | An offer in hand, doubts about scope | Hourly or a small fixed price |
| ERP selection for several departments | Two to four candidate products | Fixed price after a scoping call |
| Selection plus gap analysis and roadmap | Larger or multi-entity businesses | Fixed price in phases, hourly for open items |
When You Do Not Need ERP Consulting
Consulting is not always worth buying. Skip it, or keep it very short, in these cases:
We would rather tell you that on a first call than sell a planning phase you do not need.
- The decision is made and signed off, and the only open task is configuration and migration. Go to Odoo implementation.
- One department with simple processes is moving to a single app, and a trial can answer the question.
- Your needs are really a custom workflow, a portal or an integration that no ERP covers; see custom software development API development and integration between your ERP and other systems instead.
- The system is already live and the problem is a specific integration or report; see our guide for an API integration consultant.
Who Uses ERP Consulting
The projects that benefit most usually start from one of these situations. Each one has a guide on our site that goes deeper.
| Starting point | What consulting settles | Read next |
|---|---|---|
| QuickBooks or spreadsheets no longer cope | Whether to move now, and which modules to start with | QuickBooks Desktop to Odoo |
| A legacy ERP is reaching end of support | Replace, upgrade or move, and in what order | Dynamics GP end of life |
| A food business needs lot traceability | Which records and systems the ERP must hold | FSMA 204 traceability |
| A factory is outgrowing Excel | Which production features are must-haves | Manufacturing ERP |
| An online store needs stock and finance to agree | How the store and ERP exchange data | Shopify ERP integration |
Why Us for
ERP Planning?
These are things you can check on a first call, including the one that works against us.
Devvista builds Odoo systems for clients, so Odoo appears on many shortlists. We say that before the first workshop and we put the weighted scorecard in your hands so the result can be checked or sent to another vendor.
Every deliverable is handed over in editable form. If you choose another partner, they can start from our requirements and gap list instead of repeating the workshops.
Each score in the comparison links to a vendor page, a document or a proposal. A number with no source does not go in the scorecard.
We quote to scope after a short call, in writing, and we ask for your budget range so that what we propose fits it. Quote reviews can be billed by the hour so you only pay for what you need.
We can run process workshops and review sessions online, record decisions in shared documents and send regular written updates, so people in different locations can take part.
Related Services
Our Odoo implementations are covered by client NDAs, so we do not publish them as case studies. We can walk through anonymised examples on a call.
Odoo implementation: building and launching the chosen system Custom software development for needs no ERP covers API integration consultant: when you need one Hire Odoo developers for extensions and support Manufacturing ERP with OdooWhat We Checked
Facts on this page that depend on a vendor were read from the vendor's own pages on 9 November 2026. Prices change, so open the page before you decide.
- Odoo pricing: entry plan with one app, Standard and Custom plans per user per month, external API access listed on Custom, Odoo.sh costs and custom code maintenance not included
- Dynamics 365 Business Central pricing: Essentials $80, Premium $110 and Team Members $8 per user per month billed yearly, with a note that prices may differ by region
Straight
Answers.
The questions buyers ask us most, answered without a sales script.
Plan Your ERP Before You Buy.
Tell us what your team runs on today and what is breaking. We will reply with a scope, an estimate and the questions a scorecard would answer.
- 30-minute consultation
- NDA signed on request
- Reply within 24 hours
- Book a call30 minutes, no pitch. Tell us what you want to build.
- Get a straight answerHonest feedback on fit, scope and timeline.
- Decide with no pressureMove ahead only if it feels right. No commitment required.