Odoo services · Odoo Consulting Services
Odoo consulting that starts with your process, not the software.
Most failed ERP projects were decided before a single module was configured. They failed at scoping, when nobody asked how the business actually runs. Our consulting engagement exists to answer that question properly, with a written recommendation you can act on whether or not you hire us to build it.
—— Where it hurts
The problems this work actually solves.
Companies rarely call a consultant because the software is broken. They call because the way of working has stopped scaling, and nobody can say with confidence what an ERP should fix first.
The business runs on spreadsheets
Orders, stock and costing live in files that only one or two people truly understand. Every month-end is a manual assembly job, and a single mistyped cell can misprice a quote. Nobody planned this — it grew.
How we handle itWe document what each file actually does before proposing anything, so the roadmap replaces the spreadsheets' function, not just their format.
Three quotes, three different projects
You asked three partners to quote Odoo and the numbers are far enough apart that they cannot be describing the same project. Each proposal assumes a different scope, so comparing them is guesswork. The cheapest one usually assumes the least.
How we handle itAn independent scope document puts every bidder on the same baseline. Quotes become comparable, and the gaps become visible before you sign.
No one can name the total cost
Licences, hosting, implementation, training and future changes blur into one number that keeps moving. Budget approval stalls because finance cannot see what is one-off and what recurs every year.
How we handle itThe costed roadmap separates licence, build and run. Community is $0 and we say so; Enterprise is billed by Odoo directly, so the software line stays transparent.
The last ERP attempt failed
The company already paid for a system that never got adopted, and the team remembers. Any new proposal meets scepticism before it meets analysis. Repeating the same approach will produce the same result.
How we handle itWe start with a post-mortem of the failed attempt — where scope, data or adoption broke — and design the roadmap around that specific failure, not a generic template.
Growth outran the tools
Order volume doubled but the process did not change, so people work late to feed the old workflow. Hiring more admin staff treats the symptom and raises the payroll.
How we handle itWe find the single bottleneck that costs the most hours and sequence it into phase one, so the first go-live pays back while the rest is still being planned.
—— Learn from other projects
Mistakes we see, and how to avoid them.
Rebuilding the old system inside Odoo
Teams ask Odoo to mimic the legacy system screen for screen, including workarounds that only existed because the old software was limited. Every replicated quirk becomes custom code that costs again at every upgrade. We separate what the business needs from what the old system trained people to do, and default to standard Odoo.
Scoping with managers only
Requirements gathered in a boardroom describe how work is supposed to happen, not how it happens. The gap surfaces at go-live, when the warehouse team meets a workflow that skips half their reality. Our discovery interviews the people who ship, invoice and count stock — before a single requirement is written down.
Leaving data quality until migration
Duplicate customers, dead SKUs and inconsistent units sit quietly until migration week, then become the emergency that delays go-live. Cleaning data late is the most expensive time to do it. Our study audits master data in week one and puts the clean-up into the roadmap as a costed line item.
Deciding by committee
When every department has a veto and nobody has the final word, scoping drags for months and the loudest voice wins. ERP decisions need one accountable owner. We ask you to name that person at kick-off, and we frame every recommendation as a decision they can actually make.
Shopping for a day rate
A lower daily rate with an open-ended estimate routinely costs more than a higher rate with a fixed scope. Hourly billing also rewards slow work. We quote consulting as a fixed fee against a written scope, so our incentive is to finish, not to linger.
—— Ways to engage
Three ways to start with us.
Fit and feasibility study
A fixed-fee engagement of two to four weeks that answers one question: should you run your business on Odoo, and if so, how. The deliverable is a written roadmap you own outright.
- Process map of your order-to-cash, purchase-to-pay and stock flows
- Community-versus-Enterprise verdict with the licence maths shown
- Phased roadmap with effort estimates and a data clean-up plan
Second-opinion review
You already have a proposal from another partner, or a project stalled mid-scope. We review it line by line and tell you what is sound, what is padded and what is missing.
- Line-by-line review of the proposed scope, estimates and assumptions
- Flags on over-customisation that will cost again at every upgrade
- A question list you can put to the bidder before signing
Ongoing advisory retainer
For companies already running Odoo, or mid-project with another builder. A senior consultant stays involved month to month, so decisions get challenged before they get expensive.
- Monthly working session with the same consultant every time
- Review of change requests and quotes before you approve them
- Version and upgrade planning so you are never stranded on an old release
Your implementation partner
A partner, not a licence reseller.
We are not chasing licence volume — we design, build and stay accountable for systems that companies run their operations on. The consultant who scopes your project stays through go-live and the support that follows, and everything we commit to is written into a fixed scope per phase.
—— What done looks like
Outcomes you can verify yourself.
A roadmap anyone can execute
You finish with a written document listing phases, modules, effort estimates and sequence. It is specific enough that your internal team or a different partner could build from it without calling us.
A budget finance can defend
Licence, build and run costs are separated, with one-off and recurring lines clearly marked. Approval conversations get shorter when every number has a name.
A clear configure-versus-build line
The report lists which requirements standard Odoo meets, which need configuration and which genuinely need code. That list is your defence against any future quote that pads the third column.
A team that has already agreed
The people who do the work were interviewed and saw their processes documented. Disagreements surface on paper during the study, not in the warehouse at go-live.
—— How we work
What the engagement looks like.
Process discovery
We sit with the people who do the work — not only management — and document how orders, stock, invoices and approvals actually move today.
Gap analysis
Where standard Odoo covers your process, where it needs configuration, and where it genuinely needs custom development. Most partners overstate the third category.
Module and edition recommendation
Which modules you need on day one, which can wait, and whether Community is enough or Enterprise earns its licence cost for your case.
Costed roadmap
A phased plan with effort estimates per phase, so you can start small and expand rather than committing to everything at once.
—— Why us
What you get that you would not elsewhere.
A recommendation you own
The written analysis is yours. Take it to another partner, or bring it in-house. We are not holding your roadmap hostage to win the build.
We will say no
If your operation is better served by a lighter tool, or by fixing a process before automating it, that is what the report will say.
Local compliance built in
Thai e-Tax invoicing and Revenue Department formats, US multi-state sales tax, Indian GST — factored into scope from the first session, not discovered at go-live.
Not sure where to start? A short call sorts it.
Talk to an Odoo specialist ➜—— Why us
What working with us is actually like.
Partner access, independent advice
We are an Official Odoo Partner through the India programme, which gives us direct access to Odoo's release plans and support channels. But licences are billed by Odoo directly and never marked up, so recommending fewer users — or the $0 Community edition — costs us nothing.
The same consultant, first call to go-live
The person who runs your discovery workshops is the person who writes your roadmap and, if you build with us, stays through go-live. Nothing is lost in a handover because there is no handover.
Workshops in the language people think in
Discovery only works when people describe their work comfortably. We deliver natively in Thai and English, so a Bangkok warehouse supervisor and a New York controller both get interviewed properly, not through a translator.
Three offices, three regulatory systems
Bangkok, New York and Delhi NCR are working offices, not sales addresses. Thai e-Tax invoicing, US multi-state sales tax and Indian GST are requirements we scope routinely, so cross-border needs do not surprise the roadmap.
We put the $0 option on the table
Odoo Community costs nothing to licence, and our reports say so plainly when it covers your case. Many businesses never need Enterprise at all, and hearing that from a partner is rarer than it should be.
A fixed fee you see before we start
Consulting is quoted as one written fixed fee once the scope is known. No hourly meter running during workshops, no discovery that mysteriously extends itself.
Estimates from people who build
Our consultants configure and deliver Odoo as well as scope it. Effort estimates in the roadmap come from delivery experience, not a sales spreadsheet, which is why they hold up when the build starts.
A deliverable built to travel
The roadmap is written in plain language, with no proprietary formats and no dependence on us to interpret it. If we are the right builder, good. If not, the document works just as hard for whoever is.
—— Partner tiers, explained
What an Odoo partner tier does and does not tell you.
Odoo ranks partners by certifications held and licence volume sold. A tier signals commitment to the programme — it does not tell you who will actually staff your project. Ask that question of any partner, including us.
Learning Partner
New to the programme, building their first certified consultants and reference projects. Not a red flag — everyone starts here — but ask for hands-on proof.
Official Partner
Certified consultants and active delivery. This is where we sit, enrolled through the India programme, delivering from Thailand, the USA and India.
Silver & Gold
Higher tiers earned mainly through licence sales volume and headcount of certified staff. A strong signal of scale — not automatically of fit for your project.
—— Who this is for
Built for your size, not resized for it.
Growing companies (5–100 people)
Most of our consulting clients are companies of five to a hundred people making their first ERP decision. The study is short, the fee is fixed, and sometimes the answer is 'not yet' — which is cheaper to hear now.
- You run on spreadsheets or standalone accounting software and can feel the ceiling.
- The owner or MD can make the decision without a committee.
- Odoo Community at $0 licence cost is a genuine option at your size.
- You need a plan you can phase as cash flow allows.
Mid-market (100–500 people)
Companies of one hundred to five hundred people usually come to us with multiple entities, a legacy ERP, and departments that disagree about what the problem is. The study is bigger because the organisation is.
- You are replacing or consolidating an existing ERP, not starting from blank.
- Multi-company, multi-currency or cross-border structures are in scope from day one.
- Department heads need a documented scope they have each signed off.
- The board wants licence, build and run costs on separate lines before approving.
—— Risks
What usually goes wrong — and how we prevent it.
Licences bought before scoping
A licence count fixed before process mapping locks your budget to a guess. We scope first, so the order matches what the rollout actually needs.
The polished-demo trap
Demos hide the hard parts. We test your edge cases — partial deliveries, credit notes, multi-currency — before writing any recommendation.
Advice bent by the next sale
A consultant paid only on implementation will recommend implementation. Our report is priced standalone, so "not yet" stays a possible answer.
—— Pricing
What this costs.
Consulting is quoted as a fixed fee once we know how many processes and entities are in scope. No hourly billing, no open-ended discovery.
—— Editions & hosting
Community, Enterprise, and where it runs.
The licence and the hosting are separate decisions, and both are yours — we implement either edition and hand over whichever infrastructure you choose.
$0 licence
Odoo Community
Open source and free to license. Covers sales, purchasing, inventory, invoicing, manufacturing and more. You pay for implementation, not rent.
Per user, billed by Odoo
Odoo Enterprise
Adds studio, advanced accounting and localisations, mobile apps and official support. Billed by Odoo directly — never marked up by us.
Odoo.sh · VPS · on-premise
Your server or the cloud
Odoo.sh, a VPS we manage, or your own hardware. We recommend based on your compliance and budget, then document the choice so it stays portable.
—— The toolkit
What this service usually touches.
—— Related
Explore what else we do.
—— FAQ
Questions teams ask about this service.
How long does a consulting engagement take?
Two to four weeks for most companies. Larger or multi-entity operations run longer because there are simply more processes to document. You get the written roadmap at the end, not a verbal summary.
Do we have to use you for the implementation?
No. Consulting is a standalone engagement with its own deliverable. A meaningful share of clients take the roadmap and build with their internal team, and we would rather that than a badly matched project.
What do you need from us to start?
Access to the people who run each process, and samples of what you produce today — a few sales orders, an invoice, a stock report, whatever spreadsheets are holding things together. Messy is fine. Messy is the point.
Can you review a proposal we already have from another partner?
Yes — that is our second-opinion review. We go through the scope, estimates and assumptions line by line and give you a written view of what is sound, what is padded and what is missing. The other partner never needs to know, though in our experience the review works best in the open.
We already run Odoo. Is consulting still relevant?
Often more so. A running system accumulates customisations, workarounds and modules nobody opens, and a structured review tells you what to simplify before the next upgrade. We map how the system is actually used against how it was configured — the gap between the two is usually where the money is.
Do you earn anything on the licences you recommend?
No. Odoo Community is $0 to licence, and Enterprise is billed by Odoo directly to you at Odoo's own price — we never mark it up. Our income is the fixed consulting fee, which is why the licence recommendation in the report has no thumb on the scale.
Is the work on-site or remote?
Both, depending on where you are. In Thailand we run discovery workshops on-site from our Bangkok office; for US and India clients, our New York and Delhi NCR offices cover the same ground. Warehouse and shop-floor walks are worth doing in person, so we push for at least one site visit wherever practical.
Who actually does the work — will we be handed to a junior?
The consultant on your first call is the consultant who runs the workshops, writes the roadmap and, if you build with us, stays through go-live. We do not run a model where a senior sells and a junior delivers. Continuity is the point of the engagement.
Let's find out whether Odoo actually fits your business.
A short call, an honest answer. If it isn't the right system for you, we'll say so.