Gain share engagements depend on rigorous success metrics. The advisor charges a percentage of savings, the buyer pays only if savings materialize, and the construction of "savings" determines whether the engagement creates aligned incentives or recurring disputes. Most failed gain share engagements fail at the metrics layer — not at the negotiation, not at the contract, but at the question of what counts as savings and how savings are measured.
This piece walks through the metrics architecture for gain share engagements: baseline construction, savings categorization, measurement methodology, verification protocol, and dispute resolution. The architecture matters because the metrics directly determine the cash flow between advisor and buyer.
Baseline is the foundation of every gain share measurement. The baseline is the cost the organization would have incurred without the advisory engagement.
For renewal negotiations, the baseline is typically the renewal proposal received from Workday. The renewal proposal establishes what cost the organization would have paid absent advisory.
For optimization engagements, the baseline is typically current-state Workday spend annualized. Current-state spend establishes the cost being optimized against.
For new-purchase engagements, baseline construction is harder — there is no current-state cost. Hypothetical baseline typically uses Workday's initial proposal or industry-benchmark pricing.
Baseline should be locked at engagement start. Baseline that floats during the engagement produces disputes and incentive distortions.
Savings categorize into several types, each requiring different measurement.
Direct reduction in license cost versus baseline. Easiest category to measure — the new contract specifies the license cost, and the delta versus baseline is the savings.
Savings from reduced future price escalation. Multi-year savings should be measured against the contractual escalation, not just first-year pricing.
Savings from eliminating or downgrading modules. Measured as the cost of the eliminated modules in the baseline contract.
Savings from reduced implementation scope, partner pricing, or implementation methodology. Measured against baseline implementation proposals.
Savings from negotiated true-up mechanics, overage caps, and similar contract structure improvements. Measured against baseline contract default terms.
Savings from avoided unnecessary purchases — module additions Workday proposed that were not pursued. Measured against the proposed but avoided cost.
The most common gain share dispute is "what counts as savings." Pre-defining savings categories in the engagement contract eliminates 80% of post-engagement disputes. Vague categorization — "all cost reductions" — produces persistent dispute.
Methodology should be specified for each savings category.
For license cost savings and module rationalization, direct measurement is straightforward — final contract cost compared to baseline contract cost in the same scope.
For multi-year contracts with non-uniform escalation, net present value measurement normalizes savings across years. NPV calculation should specify discount rate.
For avoided cost savings, comparison-based measurement uses the documented proposed cost as the avoided benchmark.
Like baseline, methodology should be locked at engagement start. Methodology changes during measurement produce disputes.
Verification protocol determines how savings are confirmed.
Contract documents (baseline proposal, final executed contract) provide direct verification for most savings categories. The documents are unambiguous evidence.
Some engagements include independent verification by a third party. Independent verification adds cost but resolves dispute risk.
Buyer-side verification by procurement, finance, or legal teams is standard. Buyer-side verification authority should be clear.
Final savings calculation should require mutual sign-off by advisor and buyer. Mutual sign-off creates closure.
Savings horizon affects measurement.
First-year savings are typically the simplest measurement — the difference between baseline first-year cost and contracted first-year cost.
Multi-year savings require term-length measurement. A 3-year contract produces 3-year savings; a 5-year contract produces 5-year savings.
Some engagements measure lifetime savings including expected renewal trajectories. Lifetime measurement is harder to verify but produces more accurate value representation.
Most gain share engagements use first-year savings or contract-term savings as the measurement basis. Lifetime measurement is reserved for sophisticated engagements with strong verification.
Several metric failures recur across failed gain share engagements.
Baseline that changes during the engagement — Workday updates the proposal, the organization changes scope, escalation assumptions shift. Floating baseline destroys measurement clarity.
Engagement scope that expands without baseline adjustment. Expanded scope produces additional savings that arguably should be measured but are difficult to allocate to advisory contribution.
"All cost reductions count" categorization produces dispute. Specific categorization — license, escalation, module, implementation, true-up — produces clarity.
Methodology that shifts during measurement — first-year versus multi-year, NPV versus nominal. Methodology lock prevents drift.
Verification protocol that is unclear or one-sided. Mutual sign-off protocol prevents ambiguity.
Strong gain share engagements include explicit metric language in the contract.
Baseline definition. The contract should state the baseline cost, the source document, and the lock date.
Savings categories. The contract should list categories with specific definitions and measurement methodology for each.
Time horizon. The contract should specify the measurement horizon — first-year, contract-term, or lifetime.
Verification protocol. The contract should specify verification authority, documents required, and sign-off process.
Dispute resolution. The contract should specify dispute resolution mechanics for unresolved measurement disputes.
Reporting cadence affects gain share trust.
Engagement-end reporting summarizes savings against baseline. Standard for most gain share engagements.
For ongoing engagements, quarterly reporting provides interim visibility. Quarterly cadence supports relationship maintenance.
For multi-year savings, annual reporting tracks savings realization against forecast.
Each report should include audit trail to source documents. Audit trail enables verification independent of the report itself.
Who defines the baseline? Baseline should be jointly defined by advisor and buyer with source documents specified. Unilateral baseline definition produces dispute.
What if Workday changes the proposal mid-engagement? Proposal changes should be documented and baseline updated through formal change control. The change control mechanism should be specified in the engagement contract.
How are multi-year savings measured? Either nominal sum across years, NPV with specified discount rate, or contract-term-equivalent. The choice should be specified in the engagement contract.
What if scope expands? Scope expansion should trigger baseline expansion through formal change control. Expanded scope without expanded baseline produces dispute.
Can we audit the savings calculation? Yes, and audit rights should be specified in the engagement contract. Mutual sign-off protocols typically include audit access.
Independent Workday-only advisory. 500+ engagements, $28M+ saved, 34% average reduction across 14 modules. Two engagement models — choose whichever fits your risk posture.
Scoped advisory with a known price. Benchmarks, contract redlines, and on-call negotiation support through signature.
Zero upfront cost. Our fee is a percentage of verified savings against your baseline. If we don't save you money, you don't pay.
Predictable scope or pay-only-on-savings. Whichever model fits your risk posture.
Compare →Benchmarks, tactics, and contract language for Workday buyers.
Fixed fee or gain share — strategy memo within 48 hours.
Contact Us →One email per week. Benchmarks, contract language, and tactics.