— Odoo / Consulting
Strategy before code. Advice before SOW.
Pre-purchase advisory, architecture review, partner-takeover audits and second-opinion reviews — from a UAE-based partner that holds both Odoo Partner status and ERPNext Gold Partner status, and has walked away from Odoo deals in favour of the better fit.
In one paragraph
Independent advice. We will tell you not to pick Odoo if that is the right answer.
We run both Odoo and ERPNext. Cross-platform comparison comes from real delivery, not slideware.
Fixed-fee, scoped to the question. Not T&M.
Output is a written advisory document. Yours to act on with us — or not.
What it includes
Six engagement shapes.
Consulting comes in distinct shapes — each with its own time-box, its own deliverable and its own price. Pick the one that matches your question.
Pre-purchase advisory
Should you pick Odoo at all? Which edition? Which modules? Which hosting model? An honest answer from a partner who runs both Odoo and ERPNext.
Architecture review
Does the proposed module mix, integration topology and customization plan actually solve the problem? Reviewed before you commit budget.
Partner-takeover audit
Code quality, customization quality, data quality, upgrade-readiness on an existing Odoo system. Output: written remediation plan or rebuild recommendation.
License and hosting advisory
Community vs Enterprise. Odoo Online vs Odoo.sh vs self-hosted. Modelled over 3 to 5 years with data residency and FTA / ZATCA considerations.
Second-opinion review
You have an SOW from another partner. We review the scope, the timeline, the customization assumptions and the price. Three days, written verdict.
Process design workshops
Pre-implementation process design — getting your team aligned on the to-be process before the configuration phase begins.
Process
Frame, investigate, decide, document.
Most consulting engagements run 1 to 3 weeks end-to-end. Architecture reviews and partner-takeover audits trend longer; second-opinion reviews trend shorter.
- Phase 01
Frame
Surface the question. Pre-purchase advisory? Architecture review? Partner-takeover audit? License decision? Each has a different shape.
- Phase 02
Investigate
Process walk with the operating team, review of legacy systems, code audit if relevant, document the current and target states.
- Phase 03
Decide
Working session with leadership. Trade-offs surfaced, recommendation drafted, edge cases stress-tested.
- Phase 04
Document
Written advisory document with recommendation, rationale, alternatives considered, rough budget and a phased plan if applicable.
- Phase 05
Hand over
Document handover and a debrief session. Yours to act on with us, with another partner, or not at all.
Who this is for
Buyers who want a clean answer first.
Operators and CFOs in the UAE and the GCC who are about to commit serious budget to Odoo (or to a partner already proposing Odoo) and want an independent perspective before they sign.
Three patterns we see. The first: a CFO at a mid-market group evaluating ERP options, wants Odoo vs ERPNext vs Microsoft vs SAP B1 honestly compared against their actual operating reality before going to RFP. The second: a CEO who has received a USD 100K Odoo SOW from another partner and wants a 3-day second-opinion review before signing. The third: an IT director who inherited an Odoo system from a previous administration, suspects it is fragile, and wants an audit before committing to another year of operating cost.
Bad fit: clients who have already decided what they want and are looking for someone to validate the decision rather than test it. We will challenge the decision, not endorse it.
Pricing approach
Fixed-fee, scoped to the question.
Every consulting engagement is fixed-fee with a defined deliverable. We do not run consulting on T&M because the incentive is wrong — value is in a clean answer, not in extending the engagement.
Pricing scales with the depth of the question. A 3-day second-opinion review on someone else\'s SOW is the smallest engagement we run. A 2-to-3-week partner-takeover audit is the largest. We are happy to discuss comparable ranges on the discovery call.
What success looks like
A decision you can defend.
A successful consulting engagement ends with a decision the buyer can defend in front of their board, with a written rationale, and without buyer\'s remorse 12 months later.
Sometimes that decision is to proceed with Odoo, with us. Sometimes it is to proceed with Odoo, with a different partner. Sometimes it is to proceed with ERPNext instead. Sometimes it is not to proceed at all. All four are wins for the buyer — and that is the only metric we care about on a consulting engagement.
FAQ
Consulting questions, answered.
What does Odoo consulting actually cover? +
Pre-purchase advisory (should you pick Odoo at all, and if so which edition), architecture review (does the proposed module mix and integration topology actually solve your problem), license advisory (Community vs Enterprise, user count, hosting model), partner-takeover audits (you have an existing Odoo system you no longer trust), and second-opinion engagements (you have a quote from another partner and want a sanity check). What it does not cover: implementation work — that has its own engagement.
Will you tell us not to pick Odoo if that is the right answer? +
Yes. We hold both ERPNext Gold Partner status and Odoo Partner status, and we have walked away from Odoo deals in favour of recommending ERPNext when ERPNext was the better fit. We have also recommended that clients stay on their existing system when neither Odoo nor ERPNext would have produced enough lift to justify a migration. The consulting fee covers our advice, not a sales pitch.
How is consulting different from your Discovery week? +
Discovery is the first paid week of an implementation engagement — its purpose is to produce an SOW with a fixed price and date for a project we have already broadly agreed to take on. Consulting is upstream of that: it answers the question of whether you should embark on a project at all, or which of several possible projects is the right one. Some consulting engagements lead to a Discovery week with us; some lead to a recommendation that the client should not proceed at all.
Do you do partner-takeover audits? +
Yes — and roughly a fifth of our consulting work falls into this category. You have an Odoo system that another partner built. It is fragile, undocumented, slow, or you can no longer upgrade it. We run a written audit: code quality, customization quality, integration quality, data quality, upgrade-readiness, support readiness. The output is a remediation plan with priorities and rough budgets — and an honest answer to whether the system is salvageable or whether a fresh implementation is cheaper.
Can you advise on Odoo licensing and hosting? +
Yes. License advisory covers Community vs Enterprise, user count modelling over a 3-year horizon, partner-channel pricing vs direct, and whether Studio is worth the upgrade for your specific use case. Hosting advisory covers Odoo Online vs Odoo.sh vs self-hosted on AWS me-central-1 vs your own data centre — with explicit attention to data residency, FTA / ZATCA implications, and total cost over 3 to 5 years.
How is it priced? +
Fixed-fee, scoped to the question. A 1-week pre-purchase advisory engagement has one price. A 2-week partner-takeover audit has another. A 3-day second-opinion review on someone else's SOW has a third. We do not run consulting on T&M because the incentive is wrong — the value is in a clean answer, not in extending the engagement.
— Ready when you are
Talk to a real ERP consultant.
A 30-minute call is the fastest way to know if we're a fit. No slides.