The OCI procurement toolkit for Oracle Cloud buyers. Five artifacts to build before you sign.

An OCI purchase is decided by five documents built before signature. Commit at your own floor, write every term into the order document, and move the signature date before you give up a clause.

An OCI deal is decided before signature, by the documents your team brings to the table. Five belong there: a requirements matrix, a commitment model, reference checks, an order document clause list and an evaluation scorecard. This guide defines each one, who builds it and the decision rule it enforces.

It covers the buying event only. Running OCI after signature is a separate discipline with its own page, our OCI FinOps operating model. Three related guides carry the detail this one leaves out:

• Licensing rules. The OCI licensing reference covers BYOL rules and OCPU counting.
• Savings after go live. The OCI cost optimization page covers what you can cut once workloads are running.
• Database licensing inside the deal. Our BYOL versus license included comparison covers that decision.

What belongs on the table before you sign an OCI order?

Five artifacts, each answering a question that Oracle's paperwork will not ask on your behalf. Build them in the sequence below, scorecard first, and every pricing call after week 8 runs against your own documents.

The sequence matters. A scorecard signed in week 2 decides what the other four artifacts have to prove, and it cannot be bent to fit a quote that does not exist yet. The clause list and the references land together in week 8 because both feed the order markup.

How do OCI deals usually close?

In our files they close in one of three ways, and only one of them protects the years after the first.

• Signed clean. Oracle's first quote, accepted with no benchmark and no markup. This is the most common pattern and the most expensive.
• Discount memory. Last cycle's rate plus a small concession, negotiated from what Oracle remembers you accepted the last time.
• Artifacts on the table. Benchmarked, scoped and papered. It is the only pattern that protects the multi year picture, and it is what this toolkit produces.

Why plan a 12 week runway?

Twelve weeks from kickoff to signature is the timeline that holds for a material commitment. Weeks 1 to 8 build the artifacts and weeks 9 to 12 are for negotiating on your own paper. Oracle's fiscal year ends on May 31, so its quarters close at the end of August, November, February and May.

Quarter end pressure helps a buyer whose file is complete and hurts one whose clause list is still open. If the timeline slips, push the signature date back and keep every artifact, because a deal that has to close inside Oracle's quarter is priced on Oracle's assumptions.

What have we seen in recent OCI negotiations?

Most OCI deals we were brought into arrived as a quote and a slide deck, with none of the five artifacts built. That was true across the 15 to 25 OCI purchase and renewal negotiations I supported in 2024 and 2025, and the same three patterns kept coming back.

The first pattern is where overcommitment starts. A seller's migration plan assumes every wave goes live on schedule, and the credits are sized to that assumption. The second pattern shows up a term later, when a rollover or rate cap agreed on a call has no force against the renewal quote.

What goes into the OCI requirements matrix?

Every workload, region, compliance constraint and exit requirement, each written as a testable line that Oracle's response can be scored against. "High availability" is an adjective. "Autonomous Database in Frankfurt with a standby in Amsterdam" is a requirement Oracle can confirm or fail.

Which sections does the matrix need?

• Workload inventory. Databases including any Exadata dependency, middleware and application servers, compute, storage and network profiles, each with sizing evidence.
• Service by region availability. The OCI catalog differs from region to region. Check each required service in each target region against the published region documentation. Oracle charges the same price for a service in every region, including government regions, so the region decision is about service availability and the rate is the same wherever you land.
• Sovereignty and compliance. Data residency, government or sovereign region needs, and any regulator specific attestation, each tied to a named workload.
• Deployment model. Public region, dedicated region or Cloud at Customer. Our Cloud at Customer versus OCI comparison sets out that choice.
• Migration dependencies. What happens to your middleware changes both cloud sizing and license need. The middleware migration business case covers the economics.

Which lines do buyers forget?

• Exit assistance. Data egress support and a defined wind down period, priced at signature instead of at departure.
• SLA claims process. The SLA percentage matters less than the mechanics of claiming against the published Oracle Cloud SLAs: who files, within what window, and with what evidence.
• Support model. Severity response expectations and escalation paths, tested with reference customers before you rely on them.
• Disaster recovery pairing. The second region, its service coverage, and the cross region traffic the design generates.

A requirement missing from the matrix cannot be scored, so it will not be priced, and it returns later as a change order. Writing it now costs an afternoon. Adding it after signature means paying for it twice, once in the change order and once in the bargaining position you gave up.

How should the OCI commitment model be built for the negotiation?

Build it yourself as a three scenario consumption model: floor, expected and stretch, month by month and service by service. The floor is the number you commit to. The sizing logic and the expiry arithmetic are on our Universal Credits sizing page, and the model itself needs five tabs.

What are the five tabs of the model?

1. Workload inventory with owners and go live dates, tied line by line to the requirements matrix.
2. Monthly consumption curve by service, priced from the published price list before any discount conversation. Oracle's online Cost Estimator is a useful cross check.
3. BYOL offsets, each backed by an entitlement record and never by an assumption.
4. Scenario switches for floor, expected and stretch, driven by migration dates that can slip.
5. Sensitivity showing what each 90 day slip does to year one consumption, because at least one slip usually happens.

Worked example: how a ramp protects the floor

Suppose Oracle's migration plan implies $1.8 million of year one consumption. The floor case, counting only workloads with signed off migration dates, supports $1.1 million. Oracle proposes a flat $1.8 million commitment against its plan.

To see what a slip does, give the $700,000 gap a shape with two hypothetical migration waves:

• Wave 1. Goes live in month 4 at $50,000 a month, so $450,000 in year one on plan. After a 90 day slip it runs six months for $300,000.
• Wave 2. Goes live in month 9 at $62,500 a month, so $250,000 on plan. After the same slip it runs one month for $62,500.

With both waves late, year one consumption lands at $1,462,500 instead of $1.8 million.

If both waves go live on plan, all three structures cost the same $1.8 million at one contracted rate. The difference appears only when the plan misses, and migrations slip more often than they accelerate. That asymmetry is why the floor plus a written overage rate comes out ahead in every slip scenario.

Is a deeper discount on a bigger commitment worth it?

Oracle will usually offer a better rate for the bigger number, so price that offer against the forfeiture it creates. Here each extra point of discount is worth about $18,000, and only in a year when consumption reaches $1.8 million.

One 90 day slip forfeits the value of close to 19 points. In that year the full commitment is billed whatever the rate.

Where does BYOL enter the model?

BYOL lines change the rate and the compliance risk at the same time. Attach the entitlement evidence to every flagged workload, meaning the ordering document and the current support contract, because the flag will outlive the spreadsheet and surface in an audit.

Pay As You Go is the control case. Compare every commitment scenario with simply paying list and committing nothing, the baseline the account team will not show you. Credit the committed scenarios with Oracle Support Rewards and leave them out of the control case, since Pay As You Go customers are not eligible for the program.

Share the floor, negotiate at the floor, and keep the stretch case in your own file. Oracle sizes the deal to what you show it.

How does the toolkit change for a first purchase and for a renewal?

The five artifacts stay the same while the evidence behind them changes. On a first purchase the commitment model is an estimate, so the floor has to be conservative and the ramp does most of the protecting. At renewal you have a year or more of real consumption data, and Oracle has the same data.

What is different on a first OCI purchase?

• Price from list. Build the curve from the price list and Oracle's Cost Estimator before any rate is discussed, so the discount is measured against a number you produced.
• Keep year one small. You have no record yet of how fast your own team delivers on OCI, which makes the floor case the only number you can stand behind.
• Consider a short Pay As You Go start. Running the first workloads uncommitted for a few months produces real consumption data, at the cost of list rates and no Support Rewards in that period.
• Name the migration help. Oracle includes access to Cloud Lift Services with an OCI tenancy at no additional cost, subject to its workload eligibility rules. Write the scope into the order and do not accept it as a concession traded against rate.

What is different at an OCI renewal?

• Oracle knows your burn. Assume the account team has seen your monthly consumption and your forfeiture exposure before the first call.
• Forfeited credits are your evidence. Any credits lost in the current term are the strongest case for rollover language in the next one.
• Rerun the scorecard. Score OCI again with real consumption, real support cases and real SLA history, against the same weights.

Where does the renewal evidence sit in the OCI Console?

Billing and Cost Management holds most of it. Pull these before Oracle sends a renewal quote:

• Subscriptions. Usage against the commitment and the rate card Oracle is billing. Check those rates against the order document line by line.
• Cost Analysis and Cost Reports. Spend by service, region and compartment, with downloadable CSV files that feed the consumption curve directly.
• Support Rewards. Rewards accrued and redeemed, which tells you whether the rate you were promised is the rate being applied.
• My Oracle Support and your ordering documents. The entitlement record behind every BYOL flag, including whether support is current.

How do you run the hyperscaler benchmark and the reference checks?

Benchmark on your own workload numbers and normalize compute units before comparing anything. The per workload comparison is in OCI versus AWS for Oracle workloads, and our Benchmark Program supplies evidence from closed deals.

References are the second evidence artifact and the cheaper one. Ask for three production customers of comparable scale, and source at least one yourself through a user group or a peer so the list is not entirely Oracle's selection.

How do you normalize the benchmark file?

• Compute units. OCI bills x86 compute in OCPUs, and each x86 OCPU carries two vCPUs. Since January 2026 Oracle's web pages show prices per OCPU and per vCPU, but the price list, metering and invoices are unchanged. Convert before comparing any hourly rate.
• Like for like shapes. Match processor generation and memory ratio as well as core count.
• Storage assumptions. State the IOPS and throughput profile per workload. Storage tiers do not map one to one across clouds.
• Traffic profile. Model each workload's egress and cross region pattern. OCI includes 10 TB of outbound data transfer free each month, and a design with heavy replication or regular data exports can pass that, so check the allowance against your numbers.

What should you ask a reference customer?

1. How accurate has billing been, and how were disputes resolved?
2. Have you claimed against an SLA, and what did the process require?
3. What did a severity one support case look like in practice?
4. Where did the migration diverge from the plan Oracle presented?
5. How did the account team behave at your first renewal?
6. Which ancillary charges surprised you in the first year?
7. How long did the first production workload take from signature?
8. What would you negotiate differently with what you know now?

Give question 5 the most weight. Behavior on day one is part of the sale, and behavior at the first renewal is what you will live with for the next term.

Which clauses must be in the OCI order document?

Ten, and each one gets the same test: if the order document is silent, what happens? The terms sit inside Oracle's cloud services contract set, and silence almost always resolves in Oracle's favor. Which document binds, and how the pieces stack, is covered in our cloud contracts briefing for CIOs.

Which clause will Oracle not raise?

Unused credit treatment. The default is forfeiture at period end, the account team knows it, and the subject will not come up until you raise it. Raise it in writing in the first markup, while you still have a signature to trade.

One rule covers all ten clauses. Anything agreed on a call and missing from the order document was never agreed, so accept no side letters and no emails as amendments.

What wording should you ask for?

Counsel will adapt the language to your paper. The drafts below show the level of precision to aim for, with each commitment written as a sentence that contains its own number.

• Rollover. "Universal Credits unused at the end of the Services Period carry forward to a renewal order of equal or greater value placed before that date." It turns forfeiture into a reason to renew on your terms.
• Ramp. "The annual commitment is $A in year one and $B in year two." The commitment then follows the migration curve, and a late first year stops being a shortfall.
• Rate hold. "The unit prices in the attached rate card apply for the full term to all listed services, including consumption above the commitment." It covers the overage rate and the catalog risk in one sentence.
• Renewal cap. "Unit prices on renewal will not exceed the prices in this order by more than N percent." Without a number the protection is a promise to talk.
• Exit. "On expiry or termination, Oracle will provide continued access for data export for a stated period at the contracted rates." Requested at departure instead, the same export window is priced when you have nothing left to trade.

How do you run the markup itself?

• Send the clause list before the first draft arrives, so Oracle writes its paper knowing what will be checked.
• Track every clause in a simple grid: requested, countered, agreed, with the draft version where each one landed.
• Trade clauses against signature timing and never against each other. Offer flexibility on the signing date and keep the clause list whole.

What will the Oracle account team say, and how should you answer?

Expect the same handful of lines in most OCI negotiations. Each has a reply that keeps the discussion on your documents.

How does the evaluation scorecard keep the decision honest?

By existing before the first quote arrives, with weights the sponsor has signed. A scorecard filled in after the quote is a rationalization of a decision already made on rate.

Which decision rules survive an audit committee?

• Terms floor. If commercial terms score below an agreed minimum, there is no signature, whatever the rate says.
• No pending evidence. A reference that cannot be produced scores zero, and "to follow" earns nothing.
• Failed requirements go somewhere. Each one is carried into the clause list or into the price, and none is left to hope.
• Two scorers. Two people score independently, and the sponsor settles disagreements in writing.

What happens to the toolkit after signature?

It becomes the operating baseline and the renewal file. The commitment model turns into the burn plan for the weekly review, the clause list feeds the contract calendar, and the scorecard is rerun before renewal with real consumption data.

• Commitment model passes to the FinOps operating model as the pro rata burn plan.
• Clause list becomes the contract calendar: notice dates, ramp steps and review points, owned by procurement.
• Scorecard and references become the renewal baseline inside our Renewal Program.

Why chasing the deepest OCI rate costs more

The usual advice treats OCI as the aggressive price challenger: do the technical validation, push for the deepest rate and sign. We disagree. The rate is the least durable part of an OCI deal, because the other nine clauses decide what it is worth.

A deep rate on credits forfeited at period end, with no ramp, renewal protection or exit assistance, costs more than a modest rate inside a well written order. In the negotiations we supported, the savings came from the clause list and the commitment curve, and buyers who chased the headline rate signed the most expensive deals by year two.

How Redress supports an OCI purchase

We run the buying event with your team: the five artifacts, the benchmark evidence and the order document markup, through the Benchmark Program and the Software Spend Assessment. Vendor Shield keeps the file current between buying events, and our benchmarking work supplies the evidence for the rate discussion.

For the wider negotiation with Oracle across cloud products, see our guide to Oracle cloud negotiations. We take no money from Oracle. Read about us, meet the management team, see our locations, or contact us.

What to do next

1. Set the signature date 12 weeks out. Put the five artifacts on that calendar with named owners, and check where the date falls against Oracle's quarter end.
2. Write the scorecard first. Get the sponsor's signature on the weights before any quote exists.
3. Build the requirements matrix. Do the region and service availability check line by line.
4. Model the commitment yourself. Run all three scenarios, and let Oracle see only the floor.
5. Book three reference calls. Source at least one outside Oracle's list, and score the answers.
6. Mark up the order document against the ten clauses. Start with unused credit treatment.
7. Refuse the quarter end squeeze. If the clause list is not closed, the signature date slips and the terms stay.
8. Hand the file to operations on day one. The renewal negotiation then starts with two years of evidence.

Frequently asked questions