Writing an OCI Services RFP: Template and Scoring Guide

An RFP for OCI services has one job: to make competing proposals comparable, so the decision can be made on evidence rather than on who presented best. Most RFPs fail at that job. They describe the current environment vaguely, prescribe the solution in detail, ask for information nobody will read, and then score the responses on instinct dressed up as process. The result is predictable. The bid with the most polished writing and the lowest headline number wins, the gaps surface three months into delivery, and the change orders begin. Writing a good RFP is not about length or formality. It is about giving bidders enough truth to price honestly, asking questions whose answers actually differentiate, and committing to a scoring model before the first response lands.

This article is part of our complete guide to hiring an OCI partner, which covers the full selection journey from defining the need through to contract signature. Here we focus on the RFP itself: the document, the process around it, and the scoring.

Why most OCI RFPs select the wrong partner

The failure mode is almost always the same. The buyer does not know OCI deeply, which is exactly why they are hiring, so they copy an RFP template written for a different kind of procurement, fill it with generic questions about company history and quality certifications, and leave the genuinely discriminating questions unasked. Every serious bidder can describe their methodology in confident prose. Very few can name the three OCI database migration paths they would consider for your specific estate and explain why they would rule two of them out. The first kind of question produces identical answers. The second kind separates firms that have done this 500+ times from firms that will be learning on your invoice.

The second failure is scoring after the fact. If the evaluation criteria and their weightings are decided after the bids arrive, they will be reverse engineered, consciously or not, to justify the response the committee already likes. Publishing the criteria in the RFP and locking the weightings before opening a single response is the cheapest integrity mechanism available, and it also improves the bids, because bidders who know that delivery references carry twice the weight of the rate card will lead with evidence instead of discounts.

What an OCI services RFP must include

Whether you are buying a migration, a greenfield implementation, or ongoing managed services, the structure below holds. Adjust the depth to the size of the engagement, but do not skip sections.

Current estate summary

Bidders cannot price what they cannot see. Give them an honest inventory: database versions and editions, total data volume, application platforms, operating systems, current hosting, known performance constraints, and the interfaces that connect everything. Include the unflattering parts. The database that is two versions behind support, the application with no documentation, the batch window that already overruns. A bidder who prices against a sanitised estate will reprice against the real one later, on their terms rather than yours. If sharing detail openly is a concern, summarise in the public document and provide the full inventory under a confidentiality agreement to shortlisted firms.

Target outcomes and scope boundaries

State what success looks like in business terms: workloads running in OCI by a date, a disaster recovery posture achieved, a monthly run cost ceiling, an operations handover completed. Then draw the scope boundary explicitly. Say what is in scope, what is out of scope, and, most usefully, what is undecided. An honest "we have not yet decided whether the reporting databases move in phase one" invites bidders to price options rather than guess. Vague scope produces padded bids from careful firms and underpriced bids from careless ones, and the underpriced bid usually wins.

Technical requirements

Cover the constraints that genuinely bind: required OCI regions and any data residency rules, compliance frameworks the architecture must satisfy, database versions and options in use, availability and recovery targets, network connectivity to existing sites, and identity integration requirements. Resist the temptation to specify the solution. Requiring "Exadata Cloud Service for all production databases" in the RFP converts your bidders from advisors into order takers and forecloses cheaper options before anyone with current platform knowledge has examined the workloads. State the requirement, not the answer, and let the proposals show you who actually understands the platform.

The commercial structure you want to see

Tell bidders how you want the work priced, because unstructured commercial responses are impossible to compare. For defined delivery work such as a migration or landing zone build, ask for a fixed project fee against a defined scope with named assumptions. For ongoing operations, ask for a managed monthly retainer with the service tiers, coverage hours, and SLA targets stated. For cost reduction work, ask whether the firm will work on a percentage of verified savings, with no fee if no savings are found. The answers are revealing in themselves. Firms confident in their estimating accept fixed fees. Firms confident in their optimization practice accept contingent fees. Firms that insist on open ended time and materials for everything are asking you to carry all of the delivery risk, a pattern we examine in OCI consulting rates in 2026.

Evaluation criteria, references, and team

Publish your scoring criteria and weightings in the RFP itself. Then ask for the evidence that feeds them: at least three references from OCI engagements of comparable scope within the last two years, with permission to contact them directly, and CVs for the named individuals who will actually deliver the work, not a gallery of the firm's best people who will never touch your account. Ask each bidder to state what percentage of the proposed team is employed rather than subcontracted, and to commit to the named individuals for a defined period. The gap between the bid team and the delivery team is one of the most common sources of regret, and it is covered in more depth in our guide to OCI partner red flags.

SLA expectations and timeline

For managed services, state the response and resolution expectations by severity, the coverage window you need, which for production estates usually means 24/7/365, and the reporting cadence you expect. You do not need to draft the full SLA in the RFP, but you should signal the floor, because it forces bidders to price real coverage rather than a help desk with good intentions. The detail of what to demand and what to concede belongs to the negotiation phase, which we cover in negotiating OCI SLAs. Finally, publish the procurement timeline: question deadline, response deadline, shortlist date, presentation dates, and target award date, and then keep to it. Firms triage their best people toward buyers who run disciplined processes.

A scoring model that survives real bids

The scoring model below works for most OCI services procurements. The exact weights can shift with context, a managed services deal might move five points from technical capability to contract terms, but the shape should hold: capability and evidence together should outweigh price, and price should never exceed a quarter of the total.

Three rules make the model work in practice. First, score independently before discussing. Each evaluator completes their scores alone, and the committee then examines divergence, because the arguments that resolve a three point gap between two evaluators are where the real evaluation happens. Second, require written justification for any score above eight or below three out of ten, which suppresses both halo effects and grudges. Third, call the references before finalising the delivery score, not after the decision. A reference call is twenty minutes, and one pointed question, "would you hire them again for the same work, and what would you change?", is worth more than any case study PDF.

The RFP process from draft to award

The document is half the work. The process around it determines whether the document achieves anything. The sequence below assumes a meaningful engagement, a migration or a managed services contract, and takes eight to twelve weeks end to end.

Common RFP mistakes

Over specifying the solution. The most frequent and most costly error. If the RFP dictates the architecture, the shapes, and the migration method, you have hired hands rather than minds, and you have anchored the whole procurement to whatever level of OCI knowledge existed internally on the day the document was written. Specify outcomes and constraints. Score bidders on the quality of the solutions they propose.

Headcount theatre. Evaluating bids by the size of the proposed team rewards exactly the wrong behaviour. A firm that proposes twelve people for work that needs five is not offering generosity, it is offering you their bench costs. Score the named individuals and the outcome commitments, not the bodies. The distinction between buying outcomes and renting people runs through the whole market, and it deserves its own scoring question in any managed services RFP.

Choosing on rate card alone. A day rate tells you what an hour costs, not what the engagement costs, and certainly not what the outcome costs. A firm at a higher rate that fixes the price, finishes in twelve weeks, and leaves run books behind is cheaper than a discount team that bills for nine months. This is also why commercial weight in the scoring model is capped: across 500+ OCI engagements we have seen far more money lost to weak delivery than to strong day rates, and an average 40% reduction in OCI spend from optimization work dwarfs any rate card difference.

Ignoring independence. Ask every bidder to disclose resale arrangements and referral incentives. A partner compensated on your Oracle consumption has a quiet reason to size everything generously. An independent firm that is not Oracle and not a reseller has no such conflict, which is the position our own OCI consulting practice takes deliberately, and it changes the advice you receive about shapes, credits, and commitments.

Treating the RFP as the relationship. The document gets you to a good shortlist and a defensible decision. It does not deliver the project. Budget energy for the contract, the SLA, the exit provisions, and the kickoff, because the firms that look identical in writing diverge fast once the work starts.

Bringing it together

A good OCI services RFP is short on prescription and long on truth. It describes the estate honestly, states outcomes and constraints rather than solutions, asks for fixed project fees, managed monthly retainers, or savings contingent pricing so that bids can be compared on risk as well as price, and publishes a weighted scoring model before anyone responds. Run the process on a published timeline, score independently, call the references, and keep two firms in play until terms are agreed. Teams with 20+ years of combined Oracle experience on the evaluation side run this loop instinctively. If you do not have that experience in house, borrowing it for the two weeks it takes to shape the RFP and the scoring model is one of the highest leverage purchases in the whole engagement.