Skip to content
FinOps workspace
COST LEDGER / DECISION GUIDE

Cloud cost optimization RFP: compare proposals side by side

Updated: 10 November 2026

Get a quote for my project

Proposals for cloud cost work are hard to compare because each bidder scopes a different job. A request for proposals fixes that by describing your situation once, naming the deliverables and scoring everyone on the same grid. The sections below follow the order of the document.

Illustrative rows of server racks in a pale hall lit with mint light
Infrastructure illustration, unrelated to any customer account.
On this page
  1. The brief every bidder receives
  2. Name deliverables by FinOps capability
  3. A scoring grid fixed before proposals arrive
  4. Commercial models side by side
  5. Conflicts of interest to ask about
  6. Questions for the clarification round
  7. A short exercise for shortlisted bidders
  8. Official sources
  9. RFP questions from buyers

For FinOps consulting in South Africa, ask each proposal to distinguish team location, cloud regions, invoice currency and reporting currency. Compare the same delivery scope and make any on-site work or travel charges explicit.

Before distributing the RFP, verify candidates using the FinOps consulting shortlist checklist.

For a brief described as FinOps Beratung or advisory work, confirm workshop and handover language along with delivery scope. For an AI assignment, use the AI FinOps consulting acceptance checklist to ask each candidate for comparable evidence.

Use the FinOps consulting and support scope to separate the initial assessment from implementation assistance and recurring reviews. Require an acceptance owner for each work package.

The brief every bidder receives

Keep it to two pages and include:

  • The clouds in use and the contractual route for each: direct contract, reseller, marketplace, Enterprise Agreement, Microsoft Customer Agreement or partner billing. The route decides which billing data you can export yourself.
  • The size of the estate in ranges (accounts, subscriptions, projects) and the main platforms: Kubernetes, data platforms, AI workloads.
  • The objectives, ranked: allocation, forecasting, commitment purchases, anomaly response, usage cleanup.
  • Your dates: budget cycle, expiring commitments, audit or board deadlines.
  • Who in your team is available, and for how many days, for workshops and validation.
  • Constraints on data location, access model and confidentiality.
  • What is out of scope, typically implementation in production and purchases of commitments.

Leave out credentials, raw exports and customer names. Share data only with the shortlisted provider, under an agreement.

Name deliverables by FinOps capability

Capability (Framework 2026 names)Deliverable to requestAcceptance evidence
AllocationAllocation policy, owner mapping, unallocated-cost reportShare of cost attributed to owners, reconciled to the invoice
Reporting & AnalyticsDashboards and the export pipeline behind themQueries your team can rerun on new data
ForecastingDriver-based model and revision logBridge from budget to actual with residual shown
Anomaly ManagementAlert rules and a response runbookNamed recipients and a test alert
Usage OptimizationFindings register with owner, action and rollbackEach item confirmed by the resource owner
Rate OptimizationCommitment coverage and utilization analysis with a downside casePurchase left as your decision, assumptions listed

Tie each deliverable to an acceptance evidence before you compare prices. A bidder that cannot state its acceptance evidence has not defined the deliverable.

A scoring grid fixed before proposals arrive

Set the criteria and weights yourself, in writing, before the first proposal is opened, then use the same grid for every bidder:

  • Clarity of method: steps, inputs needed, outputs, and what happens when data is missing.
  • Named team and roles. The FinOps Foundation runs individual certifications such as FinOps Certified Practitioner, so ask which staff hold them. It also certifies organizations as FinOps Certified Service Provider, a program that asks for public service descriptions or statements of work aligned to Framework capabilities. Treat certification as one signal and read the proposal itself.
  • Data handling: access tiers, storage location, deletion at the end.
  • Handover: formats, editable files, training session.
  • Commercial clarity: what is excluded, how change requests are priced, what your team must supply.
  • Comparable work described by context and method, without client names you cannot verify.
Illustrative server rack in the foreground with a row of cabinets behind it
Illustration only: proposals are compared on the same grid, not on appearance.

Commercial models side by side

ModelSuitsWatch for
Fixed-fee assessmentA bounded review with a report and workshopsExclusions, number of workshops, what counts as acceptance
Time and materialsOpen-ended discoveryA cap, weekly reporting, who can approve extra days
Success feeWork where savings are directly measurableBaseline, eligible actions and reversal terms, see the dedicated guide
Managed serviceContinuous operation after the first reviewExit terms, handover, who owns queries and dashboards

For the success fee row, the success fee guide lists the clauses to settle before work starts.

Conflicts of interest to ask about

  • Does the bidder resell cloud capacity or earn partner or marketplace incentives on your spend? If yes, ask for a written statement of how that is separated from its advice.
  • Would commitments be bought through the bidder? Ask whether the price is the same as buying direct.
  • Does the proposal depend on a tool the bidder licenses? Ask who pays after the engagement and who owns the collected data.

Questions for the clarification round

  1. Which data do you need in the first week, and in what format?
  2. How many hours do you expect from our finance and engineering staff?
  3. What do you do if billing data arrives late or is incomplete?
  4. Who owns the queries, models and dashboards at the end?
  5. What is your process for removing access and deleting copies?
  6. Which parts of this brief would you change, and why?

A short exercise for shortlisted bidders

Give each shortlisted bidder the same redacted one-month summary for a single account and ask for a one-page reading: the questions it would ask, the top three places it would look, and what it would not conclude from that data. The answers show how each team reasons, which a slide deck does not.

Need help turning this brief into a request for your own estate? Get support on my project.

Official sources

Official documentation used for this page.

RFP questions from buyers

Should we ask every bidder for a savings percentage?

Ask for the method and explicit assumptions instead. A percentage given before the bidder has seen your data and scope cannot be compared.

Can a cheap assessment create high internal cost?

Yes. Export setup, approvals, testing and implementation may stay with your team. Put those tasks and the hours they take in the comparison.

Is FinOps certification required to bid?

No. It is a signal you can weigh in your grid. The FinOps Foundation certifies individuals and, separately, certification for service organizations.

For the billing-data workstream, use the cloud RFP checklist for exports and FOCUS acceptance (French) to specify source coverage, reconciliation and handover. Ask each bid to price those deliverables on the same assumptions.

Before sending the brief, agree how to choose a FinOps consulting firm using delivery roles and acceptance evidence. For a French-language consultation, the consultant FinOps mission checklist helps define the initial scope.

Continue your review

Launch my project

Share the decision you need to make and get a quote scoped to it.

Launch my project
Get my FinOps quote