implementation partner
before signing
Most partner evaluation processes come down to price and the demo. Neither tells you anything about what happens after you sign. Use this as your interview script for every partner call.
“We did our research. We spoke to three partners. They all sounded good.” That is the most common thing a founder says six months into a struggling Odoo implementation. They did speak to multiple partners. They did get proposals. They did compare pricing. What they did not have was a way to distinguish between partners who would deliver and partners who would overpromise.
India has 500+ Odoo partners ranging from solo freelancers to large system integrators. Odoo’s official partner tiers (Ready, Silver, Gold) tell you something about certification and revenue volume — but nothing about whether the delivery team is senior enough for your project, whether their methodology will suit your business, or whether they will still be responsive six months after go-live. Two recurring failure patterns: the low-cost partner who compresses discovery and delivers a technically functional but operationally misaligned system, and the large partner who wins the deal with senior people and delivers it with juniors. Both are avoidable with the right questions asked before signing.
Partner project counts on the Odoo website are self-reported but independently visible. A partner claiming 200 implementations whose odoo.com profile shows 12 has a credibility problem immediately.
This is the most revealing single question in any partner evaluation. A strong partner can answer immediately with a number. A weak one deflects with “every project is unique.”
Generic case studies mean nothing. Industry-specific ones with named outcomes show the partner has solved problems similar to yours.
References from three years ago describe a different team and a different version of Odoo. A partner who cannot offer recent references either does not have them or is protecting unhappy clients from your call.
This reveals whether the partner has depth to recognise and fix implementation debt, and shows what failure patterns they have seen up close.
Large firms win deals with senior people in the room and deliver with juniors on the keyboard. Asking for names before signing creates accountability. If the partner cannot name the team, the team has not been allocated.
The people who built the system understand its design decisions. A handover to a support team not involved in implementation means every issue requires re-explanation of context.
Partners with a real methodology can describe it in five minutes without hesitation. Partners without one use words like “agile” without being able to say what that means in practice.
Partners who say “we will accommodate changes as they come” are partners who will charge you later for everything not explicitly written in the original scope.
Implementations that fail often do so because the client team was not available for UAT, data validation, or decisions. A serious partner quantifies client commitment upfront.
The exclusions list tells you more about total cost than the quoted number. Common exclusions: data migration, custom reports, training, post-go-live support, integrations, GST configuration.
Many proposals include a fixed number of customisation hours. Once exhausted, every additional requirement is billed separately. Partners who don’t track this create budget surprises at the worst possible time — typically during UAT when you have the least leverage.
AMC terms offered during the sales process are often more generous than what is available post-go-live. Understand the year-two cost before signing.
Partners who do not address this in their contract are leaving cost allocation to whoever has more leverage when the overrun happens.
This is a technical question with a specific correct answer. Any competent Indian Odoo partner should describe the intrastate and interstate fiscal position setup, how GSTIN-based state code detection works, and how it maps to CGST/SGST versus IGST on invoices.
E-invoicing configuration is specific and procedural. Partners who have done it before describe it fluently. Partners who haven’t use vague language about “integration with the government portal.”
TDS in Odoo requires section code mapping at the chart of accounts level, threshold alert configuration, and understanding that TDS is calculated on taxable value — not the GST-inclusive total.
The first 90 days after go-live are the highest-risk period. Partners who define hypercare clearly with daily check-ins, issue SLAs, and adoption metrics are partners who plan for success.
Odoo releases a major version annually. How the partner designs the system today determines how expensive the next upgrade will be. Partners who write upgrade-safe code create manageable upgrades. Partners who write fragile custom code create upgrade crises.
Adoption failure is the most common ERP outcome that nobody talks about in case studies. The system works technically but the team has reverted to Excel, WhatsApp, and manual processes.
“The single most important data point from any partner evaluation is not the answer to any one question. It is how the partner responds when a question makes them uncomfortable.”
Discomfort handled with honesty indicates a partner worth trusting. Discomfort handled with deflection or overselling indicates a partner worth avoiding.
Ask these questions of ochre.digital too. We wrote them because we have seen what happens when they are not asked. We have built our practice around being able to answer all twenty of them clearly, with evidence. If you are evaluating partners and would like to put these questions to us, book a session. We will answer every one of them before asking anything about your budget.
Evaluate ochre.digital against all 20 questions
Book a 30-minute session. Bring this list. We answer first, then ask about your business.