10 Red Flags When Evaluating OCI Service Providers

Every failed OCI engagement we have been called in to rescue had warning signs visible during selection. Not in hindsight, visible at the time, sitting in the proposal or hanging in the air during the presales calls, waiting for someone to ask one more question. The buyers were not careless. They were busy, the provider was persuasive, and the procurement clock was running. The pattern repeats often enough to be worth cataloguing, because almost every flag can be surfaced with a single direct question asked before signature, while you still have leverage.

This article is part of our complete guide to hiring an OCI partner. The ten flags below come from what we have observed across 500+ OCI engagements, including the ones where we arrived after another provider had left a mess. For each flag we describe what it looks like in the wild, why it predicts trouble, and the probing question that makes it show itself. None of the questions are hostile, and a good provider answers all ten easily.

Red flag 1: an unnamed delivery team behind a star presales architect

The presales meetings feature a genuinely impressive principal architect who answers every question with depth and confidence. The proposal, read carefully, commits that person to nothing. The delivery team is described as appropriately skilled resources, with no names, no certifications attached to individuals, and no stated allocation. After kickoff the star vanishes and a rotating cast of juniors you never evaluated does the work.

This is the single most common bait and switch in cloud services, and it is entirely preventable. The question that exposes it: name the people who will deliver this engagement, state the percentage of their time committed, and agree in writing that substitutions need my approval. Watch the reaction. A confident provider names people on the spot. A hedging provider has just told you the proposal team and the delivery team are different teams.

Red flag 2: no OCI specific references

The provider has an impressive client list and a thick case study deck, and on close reading every project is AWS or Azure. Cloud experience is presented as transferable, but OCI is not a reskinned AWS. Compartments, dynamic groups, Universal Credits, Exadata Cloud, Data Guard on OCI, BYOL mechanics, none of these map cleanly from another cloud, and a team learning the differences on your estate learns them at your expense and on your timeline.

The question that exposes it: give me two referenceable customers running production workloads on OCI today, with a similar database footprint to ours, and let me speak to them without you on the call. A provider with real OCI depth has these names ready. A provider without them will offer you a logo slide instead of a phone number. How to run those reference calls properly, and what to ask when you get them, is covered in our guide to choosing an OCI consultancy.

Red flag 3: reseller economics hidden in the engagement

Some providers resell Oracle cloud services or earn rebates and margin tied to your consumption. There is nothing illegal about it, but understand what it does to advice: a firm that earns a percentage of your OCI spend makes more money when your bill grows and less when it shrinks. Rightsizing, decommissioning, and aggressive commitment negotiation all cut directly into their revenue, and that conflict quietly shapes a thousand small recommendations, all leaning the same direction.

The question that exposes it: do you, or any affiliated entity, earn margin, rebates, or incentives based on our Oracle consumption, and will you state your independence in the contract? We are independent by design, not affiliated with Oracle and not a reseller, because cost advice is only worth taking from someone who earns nothing when your bill goes up. It is also why an Optimization fee charged as a percentage of verified savings, no savings, no fee, is a model only an independent firm can credibly offer.

Red flag 4: time and materials only, with no appetite for outcome pricing

Hourly billing has legitimate uses, genuinely undefined advisory work among them. But a provider who will only sell open ended time and materials, and visibly stiffens when you raise a fixed Project fee, a Managed Monthly retainer, or any fee tied to outcomes, is telling you where they want the delivery risk to sit: entirely with you. A firm confident in its estimates will cap or fix them; one that refuses every structure except the running meter is asking you to fund its own uncertainty.

The question that exposes it: which parts of this scope will you deliver for a fixed fee, and what would you need from us to fix the rest? The answer tells you how well they understand the work.

Red flag 5: no runbooks and no documentation culture

Ask to see a sanitised sample of their operational documentation, a runbook, an architecture decision record, a handover pack from a finished engagement. Providers who run estates seriously produce these as a matter of course and will show you one within a day. Providers who operate from memory and heroics will explain that documentation is tailored to each client, which is another way of saying it does not exist. Undocumented estates are hostage estates: every renewal negotiation happens with the knowledge locked in their heads.

The question that exposes it: show me a sample runbook and tell me, contractually, what documentation we own and when we receive it.

Red flag 6: lowball estimates built on thin discovery

One bid arrives 40 percent below the field, and the temptation to take it is enormous. Look at what the estimate is built on. If the provider scoped a database migration without asking about data volumes, integrations, downtime tolerance, or licensing, the low number is not efficiency, it is ignorance or strategy. Either they do not understand the work, or they understand it perfectly and intend to recover the margin through change orders once you are committed and switching is expensive. Both versions cost you more than the honest bid.

The question that exposes it: walk me through the assumptions behind this estimate, line by line, and tell me which discoveries would change the price. Thin assumptions mean a thin estimate. A provider who did real discovery can defend every line.

Red flag 7: certification badges without engagement depth

OCI certifications matter, but they are an entry ticket, not a track record. Some firms industrialise certification to earn partner tier logos while their actual OCI delivery history is shallow. A wall of badges with no named practitioners behind them, and no count of completed OCI engagements, is marketing wearing the costume of evidence.

The question that exposes it: how many OCI engagements has this firm completed, and how many has the team proposed for us personally delivered? Numbers, not logos. A team with 20+ years of combined Oracle experience and a real engagement history will answer in specifics; a badge farm will answer in adjectives.

Red flag 8: no escalation path and no named accountability for incidents

Ask what happens when production goes down at 2am on a Sunday, and listen for structure. A serious operations provider answers with a mechanism: 24/7/365 monitoring, defined severity levels, response targets, a named incident manager, and an escalation chain that ends at a human being whose job depends on your uptime. A weak provider answers with reassurance: we are very responsive, you will have my mobile number. Reassurance is not a mechanism.

The question that exposes it: show me the escalation path for a severity one incident, with names, response times, and what happens if the first responder fails to respond. If you are buying ongoing operations rather than a project, this flag alone should be disqualifying when it appears.

Red flag 9: lock in by design

Some providers engineer dependency deliberately: proprietary monitoring and automation tooling you cannot take with you, tenancy credentials held in their vault rather than yours, documentation withheld as intellectual property, contracts with no exit clause, no handover obligation, and renewal terms that auto extend. Each element is presented as convenience. Together they are a wall around your own estate, and you discover its height the first time you ask about leaving.

The question that exposes it: if we give notice tomorrow, describe the exit. Who owns the tooling and the documentation, how do credentials transfer, what handover support is included, and what does it cost? A provider who retains clients through service answers happily. A provider who retains clients through friction changes the subject.

Red flag 10: the provider never says no in presales

Every requirement is no problem. Every deadline is achievable. Every assumption you float is validated. It feels wonderful, and it is the most reliable predictor of a painful engagement on this list. OCI work involves genuine constraints, licensing realities, regional service availability, downtime windows, and a provider who has done the work surfaces them early. Unbroken agreement in presales means either inexperience or a sales process that books revenue first and lets delivery renegotiate later, through change orders and missed dates.

The question that exposes it: tell me three things in our stated requirements that worry you, and describe an engagement where you told a client they were wrong. A provider with nothing to push back on has not thought about your estate, or is not planning to start until after signature. This dynamic is one reason buyers comparing an independent firm against Oracle's own consulting arm should study incentives as closely as skills, a comparison we draw in full in OCI partner vs Oracle Consulting.

The flags side by side

The table condenses six of the most damaging flags into a form you can take into an evaluation meeting.

The ten question quick screen

If you only have one meeting to pressure test a shortlisted provider, run this sequence. Each question maps to one flag, and a provider who clears all ten is, in our experience, very unlikely to be a regret.

Process beats vigilance

Reading a list of red flags arms you for the meetings, but the durable defence is process, because process makes the flags surface whether or not anyone is feeling vigilant that day. A written RFP forces every bidder to answer the same questions in writing, which makes hedged answers visible the moment you lay the responses side by side; our guide to writing an OCI services RFP includes the sections that pull each of these flags into the open. Independent reference calls, done without the provider listening, surface the gap between the case study and the experience. And a simple weighted scorecard, agreed before proposals arrive, stops the best presenter from beating the best provider, which is otherwise the default outcome of every evaluation run on impressions.

It is fair to ask how we answer our own questions. Our OCI consulting practice names its people in proposals, works on a fixed Project fee, a Managed Monthly retainer, or an Optimization fee charged only as a percentage of verified savings, hands over documentation as a contractual deliverable, and runs 24/7/365 monitoring behind the managed tier. Across our optimization work the average verified reduction in OCI spend is 40 percent, a number that is only credible because the fee collapses if the savings do not survive verification. None of that is heroic. It is simply what the absence of these ten flags looks like, and it is what you should demand from every firm on your shortlist, including us.

No provider is perfect, and a single yellow flag with a good explanation is not a reason to walk away. Two flags are a pattern. Three are a decision. The engagements that go wrong are almost never the ones where the buyer asked too many hard questions in presales. They are the ones where the questions were never asked at all.