Skip to main content
Have a project in mind? Let's talk
Book a call Tell us about your project Book a Call
ERP
  ERP Consulting

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.

ScorecardWeighted With You
WrittenQuote to scope
RoadmapYours to Keep
Requirements MappingERP SelectionGap AnalysisData AssessmentIntegration PlanningBudget and RoadmapQuote ReviewOdoo and Other ERPsRequirements MappingERP SelectionGap AnalysisData AssessmentIntegration PlanningBudget and RoadmapQuote ReviewOdoo and Other ERPs

What Is ERP Consulting?

A good ERP decision is mostly made before anyone opens the software.

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 consultingERP implementation
Question it answersWhich system, and what will it take?How do we build and launch it?
Main outputRequirements, scorecard, gap analysis, roadmap, budgetA configured, tested system with your data in it
Who needs itTeams with several options or unclear scopeTeams with a decision already made
Risk it removesBuying the wrong product or underestimating scopeLaunching late or with bad data
Where to read moreThis pageOdoo implementation

Not sure which of the two you need? Describe your situation and we will tell you plainly.

Book a Call

ERP Consulting Services

Each service stands alone, so you can buy only the part you need, from a requirements review to a full selection.

01

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.

Map
02

ERP Selection

A shortlist of products that fit your size and sector, scored against your weighted list.

Select
03

Gap Analysis

Every requirement marked by how a product meets it, with the custom work sized.

Gaps
04

Data 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.

Data
05

Roadmap and Budget

A phased plan with owners, dependencies and a cost range for each phase.

Plan
06

Quote and Partner Review

We can give a written second opinion on a vendor quote or a partner proposal you already hold.

Review

From 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.

01
Step One

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.

02
Step Two

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.

03
Step Three

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.

04
Step Four

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.

05
Step Five

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.

06
Step Six

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.

DocumentWhat it containsWhy it matters
Requirements registerNumbered, testable requirements with a priority and an ownerThe yardstick for every vendor demo and quote
Weighted scorecardCriteria, weights and a score per product with a source for each scoreLets you check our reasoning and reuse it
Gap analysisEach requirement classified by how a product meets it, custom items sizedShows where the budget difference between products comes from
Data readiness noteQuality issues in customers, items and ledger data, and a cleanup planBad data is a common cause of late go-lives
Integration mapEvery connected system, direction of data and methodPrevents integration work from appearing late in the project
Cost modelLicences, services and internal time over several years, with assumptions listedMakes the comparison honest beyond year one
RoadmapPhases, owners, dependencies, risks and a cost range per phaseWhat 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 checkOdooMicrosoft Dynamics 365 Business Central
How pricing is shownPer user per month on a public pricing page, with an entry plan limited to one app, then Standard and Custom plans for all appsPer user per month on a public pricing page
Published tiersOne App entry plan, Standard, Custom and a Light User priceEssentials at $80, Premium at $110 and Team Members at $8 per user per month, billed yearly
What changes between tiersOnly the Custom plan lists external API access; Odoo.sh hosting costs and maintenance of custom code are not included in the listed pricePremium adds service management and manufacturing to Essentials; Team Members have limited access to read data, approve workflows and update selected records
What the page warnsDiscount applies to initial users for the first 12 monthsPrices are informational and may differ by currency, country and region
What to confirm in a quoteHosting choice, custom modules and who maintains them, number of full and light usersWhich 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.

GroupMeaningEffect on budget
Fits as shippedThe standard feature does the jobNo extra cost
Settings changeConfiguration inside the product meets the needSmall, one-off consulting time
Light extensionA field, report or rule added without changing core logicSmall to medium, plus upgrade testing
IntegrationAnother system must supply or receive the dataMedium, and a recurring support item
Process changeYour process adapts to the productNo build cost, but needs staff buy-in and training
Custom buildNew logic that the product does not offerLargest 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.

ScopeTypical fitPricing model (typical placement in our estimates, scoped per project)
Requirements review for one departmentOne team leaving spreadsheetsFixed price (typical placement in our estimates, scoped per project)
Vendor quote or proposal reviewAn offer in hand, doubts about scopeHourly or a small fixed price
ERP selection for several departmentsTwo to four candidate productsFixed price after a scoping call
Selection plus gap analysis and roadmapLarger or multi-entity businessesFixed 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.

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 pointWhat consulting settlesRead next
QuickBooks or spreadsheets no longer copeWhether to move now, and which modules to start withQuickBooks Desktop to Odoo
A legacy ERP is reaching end of supportReplace, upgrade or move, and in what orderDynamics GP end of life
A food business needs lot traceabilityWhich records and systems the ERP must holdFSMA 204 traceability
A factory is outgrowing ExcelWhich production features are must-havesManufacturing ERP
An online store needs stock and finance to agreeHow the store and ERP exchange dataShopify ERP integration

Why Us for
ERP Planning?

These are things you can check on a first call, including the one that works against us.

01
We Tell You About Our Bias

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.

02
Documents You Can Reuse

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.

03
Sources Behind Every Score

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.

04
Prices Stated Up Front

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.

05
A Remote Team Used to Online Workshops

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.

Straight
Answers.

The questions buyers ask us most, answered without a sales script.

Still have a question?Send it over and we will answer personally.Send a Message

ERP consulting covers the decisions that come before and around a rollout: mapping your requirements, building a shortlist, scoring the options, finding the gaps between each option and your processes, and writing a costed roadmap. You get documents you can use with any vendor or partner, not a commitment to one.

After a short call we write the quote to your scope, and we ask for the budget range you have in mind so we can propose what fits. What moves the cost is the scope, the number of integrations, who does the work and how settled the requirements are. A single-department requirements review is a smaller job than a multi-department selection with a gap analysis, and every project is scoped separately. We give a written estimate after a first call.

Not always. If one department is moving off spreadsheets and the choice is already made, you can go straight to implementation. Consulting pays off when several departments are involved, when you have two or more serious options, when a vendor quote surprised you, or when an earlier ERP project stalled.

No, and we say so up front. Devvista is a software development company that builds Odoo systems for clients, so Odoo is on many of our shortlists. The scorecard is written down and weighted with you before any product is scored, so you can check the result and send the same scorecard to other vendors.

We compare the products that fit your size and sector, using each vendor's own documentation and proposal. On this page we show Odoo and Microsoft Dynamics 365 Business Central because both publish list pricing. For vendors that do not, we work from the quote you obtain.

A gap analysis lists each requirement and marks how a candidate ERP meets it: as shipped, by changing settings, by a light extension, through an integration, by changing your process, or by custom development. The count and size of the custom items drive most of the budget difference between products.

It depends on how many departments and systems are involved. A single-department review is short. A selection across finance, inventory, sales and production takes longer because each area needs workshops and sample data. We set the schedule in the estimate and send regular written updates against it.

Yes, we can. Send the quote and your requirements list. We check what is included, what is left out, which items are custom work, how licences scale with users, and what you would pay at year three. You get a written review that you can use when you negotiate.

Only if you want it to. The roadmap is written so that any competent partner could follow it. If the answer is Odoo, our Odoo implementation team can take over with the gap analysis already done, which saves repeated workshops.

Yes. We sign a mutual NDA on request before you share process documents, sample data or vendor quotes. Sample data can also be masked before it leaves your systems.
Let's talk

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
  1. Book a call30 minutes, no pitch. Tell us what you want to build.
  2. Get a straight answerHonest feedback on fit, scope and timeline.
  3. Decide with no pressureMove ahead only if it feels right. No commitment required.
Chat on WhatsApp