Share-of-savings vendors · ZopDev University

Outcome

By the end of this lesson, you will be able to decide whether a share-of-savings commitment vendor fits your org, evaluate vendor proposals against the in-house alternative, and audit vendor performance once engaged.


Prerequisites	M5.7.L1-L4 (commitment fundamentals)
Time	9 minutes

1. Concept

Some vendors will manage your commitments for you and take a cut of what they save, rather than a fee.

ProsperOps and Spot Eco (both now owned by Flexera) are names you will hear. The pitch is that you pay nothing unless you save.

Whether it is a good deal depends on your size, how complicated your estate is, and whether you have somebody who could do it instead.

SHARE-OF-SAVINGS MODEL:
  Vendor manages your RI/SP/CUD portfolio
  Buys, exchanges and manages commitments in your cloud account on your behalf
  Continuously optimizes: exchanges, expirations, new purchases
  Charges a percentage of realized savings
  Rates are negotiated and vary by vendor and spend; this module
  uses 25% as an illustrative figure
  Vendor takes the operational + judgment overhead

ALTERNATIVE: IN-HOUSE:
  You manage commitments yourself (FinOps team)
  You pay your own commitments + admin overhead
  Full transparency on every decision
  Headcount cost: ~$180K-$250K per FinOps engineer

GOOD FIT for vendor:
  Org lacks dedicated FinOps headcount (or part-time only)
  Cloud spend is significant ($5M+ annually)
  Commitment management is complex
    (multi-cloud, multi-instrument, frequent workload changes)
  Want a hands-off approach
  Team's time is better spent on other FinOps work
  In-house team can't realistically achieve >30% effective discount

When in-house is better

GOOD FIT for in-house:
  Dedicated FinOps team already in place
  Smaller cloud spend (<$2M annually)
  Predictable workloads (low churn in instance types)
  Want full transparency on every commitment decision
  Team has commitment management skills already
  In-house can realistically achieve 30%+ effective discount

The decision math

EXAMPLE: $10M annual cloud spend at 30% in-house discount:

VENDOR-MANAGED:
  Vendor achieves 35% effective discount (5pp improvement)
  Additional savings: $500K/year
  Vendor fee (illustrative 25%): 25% × $500K = $125K
  Net additional savings: $375K/year

IN-HOUSE (with dedicated headcount):
  Achievable with FinOps engineer: 35%
  FinOps headcount cost: $200K/year
  Net additional savings: $500K - $200K = $300K

WINNER (this scenario): vendor by $75K

EXAMPLE: $2M annual cloud spend at 30% in-house discount:

VENDOR-MANAGED:
  Vendor achieves 35% effective discount
  Additional savings: $100K/year
  Vendor fee (illustrative 25%): 25% × $100K = $25K
  Net additional savings: $75K/year

IN-HOUSE (part-time):
  Achievable with part-time effort: 32%
  Marginal savings (no extra headcount): $40K/year
  Net: $40K

WINNER: vendor by $35K, but tighter at this scale

EXAMPLE: $500K annual cloud spend:
  Either approach yields small absolute savings
  Vendor fee may eat most of the marginal benefit
  In-house effort minimal (1-2 days per quarter)
  LIKELY WINNER: in-house at this scale

The math turns on absolute spend. Small spend → in-house; large spend → vendor often wins.

Variations on the model

VARIATION 1: Performance tiers
  Lower fee % for less-optimized starting portfolios
  Higher fee % for already-optimized portfolios
  Levels the field for various customer starting points

VARIATION 2: Hybrid
  Vendor handles RI/SP/CUD optimization
  Customer handles Spot directly (often Spot needs deeper
  workload knowledge)

VARIATION 3: Caps
  Maximum vendor fee per period
  Useful if savings exceed expectations (vendor doesn't get
  windfall)

VARIATION 4: Multi-vendor
  Multiple share-of-savings vendors competing
  Best for very large customers ($50M+ spend)

RISK                              MITIGATION
──────────────────────────────────────────────────────────────────
VENDOR LOCK-IN                     Negotiate exit clauses upfront;
(transition costs if changing      typical 90-day notice with
vendors are high)                  knowledge transfer

CONTRACT TERMS                     Typically 1-3 year contracts;
(long-term commitment to           verify mid-term exit option;
vendor itself)                     terminate clauses for under-performance

INFLATED BASELINE                  Vendor measures savings against
(vendor sets the "baseline"        their stated baseline; insist on
they're improving from)            independent baseline measurement
                                  (your starting point, not theirs)

SAVINGS DEFINITION                 Define "savings" precisely in
(disputes about what's saved)      contract; include calculation
                                  methodology

EXIT CLAUSE                        Always negotiate; the worst case
                                  is being unable to exit when
                                  vendor underperforms

Auditing vendor performance

Once engaged, the vendor’s performance must be audited regularly:

QUARTERLY AUDIT:
  Cross-check vendor's reported savings against your own analysis
  Verify commitment portfolio decisions match the strategy
  Compare to in-house projection (what would we have achieved?)
  Track effective discount over time
  Identify any underperforming periods

ANNUAL REVIEW:
  Review fee + value calculation
  Reconsider in-house vs vendor decision
  Negotiate renewal or shop alternatives
  Document the year's learnings

SPECIFIC RED FLAGS:
  Effective discount declining
  Commitment portfolio decisions you wouldn't have made
  Lack of transparency on decisions
  Fees increasing without performance increases

Comparison shopping

If considering multiple share-of-savings vendors:

COMPARE:
  Fee structure (flat percentage? tiered? capped?)
  Track record (case studies, references, customer count)
  Tools provided (audit, transparency, real-time dashboards)
  Exit terms (notice period, transition support, knowledge
    handoff)
  Multi-cloud support (AWS, GCP, Azure parity)
  Specific instruments covered (RI, SP, CUD, Spot?)
  Contract length (1-year, 3-year, longer?)
  Performance guarantees (refunds if savings miss?)

A 6-8 week evaluation cycle is typical for enterprise customers. Don’t pick a vendor based on a single pitch.

Common evaluation mistakes

MISTAKE                                   FIX
──────────────────────────────────────────────────────────────────
Choosing vendor by lowest fee %            Lowest fee on smaller
                                          savings can be more
                                          expensive than higher fee
                                          on larger savings

Not measuring baseline rigorously          Independent baseline
                                          assessment before signing

Long contract without exit clauses         Negotiate mid-term exit;
                                          performance-tied milestones

Ignoring multi-cloud capability             If you might add Azure
                                          later, verify vendor supports
                                          it now

Not auditing actual savings                Schedule quarterly audit
                                          from day 1

Doubling down on under-performing vendor   Switch sooner; vendor
                                          retention bias is real

2. Demo

A complete vendor vs in-house evaluation for a $4M cloud spend customer:

COMPANY: $4M annual cloud spend (mostly AWS)
CURRENT: 30% effective discount, no dedicated FinOps headcount
DECISION needed: hire FinOps engineer OR engage share-of-savings vendor

ASSUMPTIONS:
  In-house FinOps engineer cost: $180K/year (fully loaded)
  Expected in-house improvement: 30% → 32% (small but real)
  Expected vendor improvement: 30% → 38% (larger; vendor is specialized)
  Vendor fee: 25% of additional savings (illustrative; real rates vary)

CALCULATIONS:

  CURRENT savings (no change):
    30% × $4M = $1.2M/year

  IN-HOUSE (with new FinOps hire):
    Achievable: 32%
    New savings: 32% × $4M = $1.28M (additional $80K)
    Cost: $180K (FinOps headcount)
    Net additional benefit: $80K - $180K = -$100K
    (FinOps headcount has other value beyond commitments: see note)

  VENDOR:
    Achievable: 38%
    New savings: 38% × $4M = $1.52M (additional $320K)
    Cost: 25% × ($320K) = $80K
    Net additional benefit: $320K - $80K = $240K

DECISION: Vendor wins by $340K

NOTE on FinOps headcount:
  $180K headcount for ONLY commitment management is not justified
  at this scale. But FinOps does other work (tagging, scheduling,
  optimization, reporting) where vendor doesn't help. Reconsider:
  hire FinOps for the broader work + vendor for commitments
  specifically. The "either/or" framing is sometimes wrong.

REVISED DECISION:
  Hire FinOps engineer ($180K) for breadth of work
  Engage vendor for commitments specifically ($80K)
  Total cost: $260K
  Total savings improvement: 30% → 40% (10pp; FinOps work elsewhere
  amplifies vendor's commitment work)
  Annual savings: 40% × $4M = $1.6M (additional $400K)
  Net benefit: $400K - $260K = $140K

  Better than either alone. Hybrid model.

LOCKED-IN: vendor with quarterly audits and 90-day exit clause.

3. Hands-on (5 min)

For your org, evaluate vendor vs in-house:

CURRENT ANNUAL CLOUD SPEND:    $______
CURRENT EFFECTIVE DISCOUNT:    ____%

IN-HOUSE OPTION:
  Achievable discount with current setup: ____%
  Achievable with new FinOps headcount:    ____%
  Headcount cost:                          $______/yr
  Net annual additional savings:            $______

VENDOR OPTION:
  Estimated achievable discount:            ____%
  Estimated annual additional savings:      $______
  Vendor fee (your quoted rate):            $______
  Net annual additional savings:            $______

DECISION:
  □ In-house (better at this scale)
  □ Vendor (better at this scale)
  □ Hybrid (FinOps for breadth + vendor for commitments)
  □ Defer (not yet ready)

IF VENDOR/HYBRID:
  Evaluation process:
    □ Multi-vendor comparison
    □ Reference checks
    □ Pilot or 6-month trial
    □ Contract review (exit clauses!)
    □ Quarterly audit plan

Don’t sign a multi-year contract without going through this analysis.

4. Knowledge check

Q1

Share-of-savings vendor at an illustrative 25% fee, $500K savings vs baseline:

A. Bad math: vendor took too much
B. $125K net to customer
C. $375K net to customer
D. Too expensive

Show answer

Correct: C. Reasonable if customer would not have achieved that savings in-house. The vendor takes 25% in exchange for taking the operational + judgment overhead. Compare against the alternative (in-house cost) before judging.

Q2

For a $500K annual cloud spend, with part-time in-house effort already at a 30% effective discount:

A. Consider in-house
B. Always use vendor at this scale
C. Hire a dedicated FinOps engineer just for commitments
D. Vendor only, since 30% is unreachable

Show answer

Correct: A. At this spend each extra point of discount is worth only $5K a year, so the absolute gain is small and in-house effort of a day or two per quarter usually wins, as in the lesson’s $500K example. At $2M the lesson’s example already tips to the vendor, so always run the math for your org.

Q3

A multi-year contract with a share-of-savings vendor:

A. Always good: locks in lower fees
B. Cheaper per year than an annual deal
C. Lock-in risk
D. Required to get the lowest fee rate

Show answer

Correct: C. Negotiate exit clauses; don’t sign without an escape mechanism. Lock-in compounded over years can cost more than the savings if the vendor under-performs or the org’s needs change.

5. Apply

Evaluate vendor vs in-house annually. Don’t auto-renew without comparison. Pull the inputs from your provider’s coverage and utilization reports; ZopNight’s commitment coverage card and Cost Flow’s Purchase layout show the current portfolio mix.

For new vendor evaluations: 6-8 weeks of analysis, multi-vendor comparison, reference checks, contract review.

Module quiz

Complete M5.7 → 10-question module quiz.

Outcome

1. Concept

When share-of-savings makes sense

When in-house is better

The decision math

Variations on the model

Risks of share-of-savings

Auditing vendor performance

Comparison shopping

Common evaluation mistakes

2. Demo

3. Hands-on (5 min)

4. Knowledge check

Q1

Q2

Q3

5. Apply

Related lessons

Module quiz

Start with the bill.