Choosing an OCI consultancy is a different problem from choosing a partner for AWS or Azure, and most buyers do not adjust for the difference. The bigger hyperscaler ecosystems have thousands of partners, dense certification programs, and enough public references that a bad firm is hard to hide. The OCI ecosystem is younger and thinner. There are fewer firms, fewer genuinely experienced engineers, and far more generalist cloud shops who have added OCI to their website because a client asked for it. At the same time the stakes are usually higher, because the workloads that move to OCI tend to be the Oracle databases and the systems built on top of them, which is to say the systems the business actually runs on.
That combination, a thin market and tier one workloads, means the selection process deserves more rigor than a generic cloud procurement, not less. This article is part of our complete guide to hiring an OCI partner, and it gives you the evaluation checklist we believe every buyer should run before signing anything. The 12 points below cover technical depth, commercial structure, and the relationship mechanics that decide whether the engagement still feels like a good decision a year in.
A note on what this checklist is not. It is not a scoring spreadsheet that replaces judgement, and it is not a way to avoid talking to references. It is a structured set of questions, each of which has answers that signal strength and answers that signal risk. Your job in the evaluation is to ask all 12, listen carefully, and weight the answers against your own situation.
Why generic cloud credentials tell you very little
The first trap in OCI partner selection is accepting hyperscaler credentials as a proxy for OCI capability. A firm can be a superb AWS partner and still be a liability on OCI, because the things that make OCI projects succeed are not generic cloud skills. They are Oracle database skills applied in a cloud context. OCI's compartment and policy model, its network constructs, and above all its database platforms, Exadata Cloud, Base Database, Autonomous, behave differently enough from the equivalents elsewhere that experience does not transfer cleanly. The migration patterns that matter most on OCI, Data Guard switchovers, GoldenGate replication, RMAN based moves, ZDM orchestration, are database engineering disciplines that a generalist cloud team has usually never touched.
The second trap is accepting certifications as a proxy for delivery. OCI certifications are useful hygiene, and a firm with none of them should worry you, but exams are passed by individuals reading documentation, not by teams shipping production systems. What you actually want evidence of is delivery: named projects, on OCI specifically, of comparable shape to yours, with reference clients willing to take a call. Everything else is decoration. The checklist below is built around forcing that evidence into the open, and it pairs naturally with the warning signs we cover in OCI partner red flags, which is effectively the negative image of this article.
The 12 point checklist
Here is the full checklist. Each point is phrased as the thing you are trying to confirm, and the sections that follow expand on the points that buyers most often get wrong.
- Proven OCI delivery references. The firm can name real OCI projects of comparable scope, not generic cloud projects, and will connect you with at least two reference clients who will speak candidly about what went wrong as well as what went right.
- Oracle database depth. The team has hands on production experience with Exadata, Data Guard, GoldenGate, and RMAN, because OCI migrations are won and lost at the database layer, not the compute layer.
- Landing zone and IaC maturity. The firm builds landing zones as code, in Terraform or an equivalent, with compartment design, IAM policy, and network topology expressed in versioned modules you will own, not as console clicks documented in a slide deck.
- FinOps and cost track record. The firm can show measured cost outcomes on OCI, with before and after numbers, and treats cost as an engineering discipline rather than a quarterly report.
- Licensing independence. The firm is not an Oracle reseller and earns nothing from your licensing decisions, so its BYOL versus license included advice is clean, and it works comfortably alongside independent licensing counsel.
- Security and compliance capability. The firm can speak fluently about Cloud Guard, Security Zones, vault and key management, and the compliance frameworks that apply to your industry, and has implemented them, not just listed them.
- Named team, not a bench. The people in the sales meetings are the people who will do the work, named in the contract, with substitution requiring your approval rather than a notification.
- Pricing model transparency. The firm offers clear commercial structures, fixed fee for defined projects, a monthly retainer for ongoing operations, contingency pricing for optimization, and can explain exactly what is in and out of each.
- SLA substance. Service levels specify response and resolution by severity, with credits that have teeth, rather than a single response time and a promise of best efforts.
- Knowledge transfer commitment. Documentation, runbooks, and working sessions with your team are deliverables in the statement of work, with acceptance criteria, not a goodwill gesture at the end.
- Exit terms. The contract specifies handover obligations, artifact ownership, and a defined offboarding period, so leaving is a process rather than a fight.
- Cultural fit and communication cadence. The firm proposes a concrete rhythm of standups, reviews, and escalation paths, communicates in plain language, and feels like a team yours can work beside for years.
Strong versus weak answers, area by area
The checklist only works if you can tell a strong answer from a rehearsed one. The table below summarizes what each looks like in practice for the areas where the difference is most telling. A strong answer is specific, verifiable, and usually includes an admission of something that went wrong. A weak answer is general, unverifiable, and uniformly positive.
| Evaluation area | Strong answer | Weak answer |
|---|---|---|
| References | Named OCI clients, comparable workloads, contacts offered without being chased | Logos on a slide, generic cloud stories, references promised but never produced |
| Database depth | Engineers describe specific Data Guard or GoldenGate cutovers, including the one that needed a rollback | Talk stays at the level of services and consoles, no one in the room has run a production cutover |
| Landing zone | Shows real Terraform modules, explains compartment and policy design choices and their tradeoffs | Shows architecture diagrams only, vague on how the environment is actually built and rebuilt |
| Cost record | Before and after spend figures from named engagements, method explained, savings verified by the client | Claims of big percentages with no baseline, no method, and no client willing to confirm |
| Licensing | States plainly that it does not resell Oracle and welcomes independent licensing review | Evasive about reseller status, steers every conversation toward buying more from Oracle |
| SLAs | Severity matrix with response and resolution targets, credit mechanics, and reporting cadence in the contract | One response time for everything, credits absent or capped into irrelevance |
| Exit terms | Offboarding plan, artifact ownership, and transition support written into the agreement from day one | Exit is not in the draft contract at all, and raising it makes the room uncomfortable |
The four points buyers most often skip
In our experience across 500+ OCI engagements, on both sides of the table, four of the 12 points are routinely skipped in procurement, and they are the four that cause the most regret later.
Licensing independence
Oracle licensing is where the largest sums in an OCI program move, and it is also where incentives are most often hidden. A consultancy that resells Oracle licenses or Universal Credits earns margin on what you buy, which quietly shapes its advice on BYOL, on edition choices, and on the size of your commit. That does not make resellers dishonest, but it does make their advice structurally conflicted, and you should know which kind of firm you are talking to before you weigh anything it says about licensing. Ask directly: do you resell Oracle products, and do you earn anything from our Oracle spend? A firm with nothing to hide answers in one sentence. The broader comparison of conflicted versus independent advice is the subject of our companion piece on independent OCI partners versus Oracle Consulting.
Named team versus bench
Every consultancy sends strong people to the pitch. The question is who turns up in week three. Firms with thin OCI capability staff the sale with their two genuine experts and staff the delivery from a generalist bench, and the contract usually permits it. Insist on named individuals in the statement of work, review their actual OCI history, and require your written approval for substitutions. A firm confident in its bench strength will accept this without drama. A firm that resists is telling you something important.
Knowledge transfer
The cheapest engagement is rarely the one with the lowest day rate. It is the one that leaves your team able to operate what was built. Knowledge transfer fails when it is treated as a vibe rather than a deliverable, so make it a deliverable: documentation with named artifacts, runbooks for the operations your team will own, and scheduled working sessions, all with acceptance criteria. A partner that wants you dependent will resist this. A partner that expects to win your next project on merit will welcome it.
Exit terms
Nobody wants to negotiate the divorce at the wedding, which is exactly why you must. Exit terms, handover obligations, ownership of Terraform code and documentation, a defined transition period at agreed rates, are easiest to agree when nobody needs them. Agreed under pressure two years later, they are expensive. The headline is simple: a firm that makes leaving easy is a firm you will probably never want to leave.
Pricing models and what they reveal
Point eight on the checklist, pricing transparency, deserves expansion because the pricing model a firm leads with tells you a great deal about how it thinks. There are three structures that dominate serious OCI work. A fixed project fee suits defined scopes such as a landing zone build or a migration wave, and a firm willing to fix a price is a firm confident in its estimation, because it carries the overrun risk instead of you. A managed monthly retainer suits ongoing operations, where a flat fee covers a defined service catalog, monitoring, patching, incident response, and the firm is incentivized to automate because toil eats its own margin. A contingency model for optimization, where the fee is a percentage of verified savings and no savings means no fee, is the cleanest incentive alignment available in consulting, and it is only offered by firms that consistently find savings, which on OCI estates that have never had a structured review average around 40% of spend in our experience.
What should worry you is a firm that only offers open ended time and materials for everything, because that structure transfers all delivery risk to you and rewards the firm for slowness. Time and materials has legitimate uses for genuinely undefined exploratory work, but as the default for a defined migration it is a signal of either weak estimation ability or a deliberate commercial posture. For current market numbers on what each structure costs, see OCI consulting rates in 2026, and for the recurring side see how managed retainers are typically scoped and priced.
How to run the evaluation
The checklist works best inside a lightweight but structured process. Resist the temptation to run a 200 question RFP, because the firms best at answering giant RFPs are procurement specialists, not engineers, and you will select for the wrong skill. A focused request built around these 12 points, with space for specific evidence, gets you better signal in a quarter of the pages. We publish a ready made structure in our OCI RFP template guide if you want a starting point.
Three practical rules improve almost every evaluation. First, put engineers in the room on both sides. Your database lead will learn more in 20 minutes of technical conversation with the proposed delivery team than procurement will learn from any written response, and the simple request to meet the actual engineers filters out bench staffing on its own. Second, call the references and ask about failure. Every real project has a moment where something broke, and how the firm behaved in that moment, communication, ownership, speed of recovery, is the single most predictive piece of evidence you can gather. A reference who cannot name anything that went wrong has been coached. Third, score independently before you discuss. Have each evaluator rate the 12 points alone, then compare. The divergences are where the real conversation is, and they surface concerns that group discussion politely buries.
Weight the points to your situation rather than treating all 12 equally. If you are migrating a heavily customized E Business Suite estate, database depth and references dominate. If you are handing over steady state operations, SLA substance, knowledge transfer, and exit terms matter most. If cost is the driver, the FinOps track record and the willingness to price on verified savings should lead. The checklist is a lens, not a formula.
Where this leaves you
The OCI consulting market rewards buyers who ask sharp questions, because the gap between firms is wide and the marketing is uniform. Run the 12 points, demand evidence rather than assurance, weight for your situation, and pay particular attention to the four points everyone skips: licensing independence, named teams, knowledge transfer, and exit terms. A firm that answers all 12 well is rare, and worth paying properly for, because over 20+ years of combined Oracle experience we have watched the cheap choice become the expensive one more times than we can count. If you want a structured second opinion on a shortlist, or a partner to evaluate against this checklist directly, our OCI consulting practice is happy to be held to every point on it.
Free white paper
Go deeper on this topic with The OCI Cost Optimization Framework, how to find, verify, and lock in OCI savings. An independent analyst style report with comparison tables and recommendations, free with a work email. Prefer a monthly summary instead? The OCI Brief delivers one practical OCI briefing a month.
Moving Oracle workloads to OCI, or already running on OCI and not sure the architecture or the spend is right? Most teams bring in a specialist before they commit to a region, a shape, or a Universal Credits number. OCISpecialists.com plans the landing zone, runs the migration, and manages the estate after go live, on a fixed project fee, a managed monthly retainer, or a cost optimization fee paid only on verified savings.