Your SAP Fieldglass renewal is not a seat count. SAP prices Fieldglass on usage metrics written into your Order Form — Spend processed through the service and Resources (also called Worker Profiles) managed in it — and the renewal quote usually assumes you re-commit at last term's level or higher. Most of the money in a Fieldglass renewal is decided by three things: whether your committed usage still matches what actually flows through the system, who funds the fees (you, your suppliers, or both), and whether a managed service provider's fee is quietly sitting on top of the platform.
This guide walks the shape of an SAP Fieldglass renewal from the buyer's side. It comes from Fortune 500 sourcing experience and thousands of renewals worth of pattern recognition — not from SAP, and not from a reseller or MSP taking a referral fee. It teaches you where the cost really comes from and the levers that move it.
SAP does not publish a Fieldglass rate card, and the third-party percentages that circulate disagree with each other, so the table below describes how each cost line is metered rather than quoting a price. Contract terms cited here come from SAP's publicly posted Fieldglass cloud services supplement and SAP training material; your own Order Form governs. Treat everything as directional leverage, not a rate you should expect to hit.
Directional and estimated guidance from public SAP documentation and aggregated renewal experience — not any organization's confidential terms, and not a promise of savings. Normalize your own order form to the same basis before comparing.
| Cost line | Typical unit | Directional range |
|---|---|---|
| Contingent Workforce Management | Spend processed and/or Resources (Worker Profiles), per Order Form | No public rate card; quote-based — model from your own 12–24 months of usage |
| Services Procurement (SOW) | Spend on SOW / payment-term invoices, per Order Form | No public rate card; contract-specific |
| Worker Profile Management | Resources (Worker Profiles), monthly allotment unless the Order Form says otherwise | No public rate card; contract-specific |
| Analytics add-on / sandboxes | Separate subscription lines | Quote-based; carry only if used |
| Supplier-funded fees | Agreed percentage short-paid to suppliers | Contract-specific; public third-party estimates conflict — don't anchor on one |
| MSP fee | Markup or discount on bill rates, under the MSP's contract | Set by the MSP, not SAP; separate it from the platform fee |
| Renewal increase | Annual % increase | Assume an increase unless capped in writing |
How SAP Fieldglass pricing drives your renewal cost
SAP's current Fieldglass cloud services supplement defines two usage metrics. Spend is the total expenditures processed through the service. Resource is a people-based metric, also referred to as Worker Profile, counted as a monthly allotment unless your Order Form says otherwise. Earlier versions of the supplement used different definitions — for example “Monitored Individuals,” and a Spend definition split between time-sheet spend and statement-of-work invoice spend — so the version your Order Form references matters.
The modules are separate lines. Contingent Workforce Management covers contingent labor from job posting through invoice. Services Procurement covers SOW-based services providers from project requisition through invoicing. Worker Profile Management tracks non-traditional workers who have no time sheet and no job posting or SOW. An analytics add-on and non-production sandboxes are sold separately. Fieldglass integrates with SAP S/4HANA, SAP Ariba and SAP SuccessFactors — which is real value, and also real switching cost that the renewal price assumes.
Then there is the funding model. SAP's own training material describes buyer-funded, supplier-funded and hybrid programs. In a supplier-funded program the buyer short-pays suppliers an agreed percentage that is used to pay SAP Fieldglass — and SAP's material itself notes that suppliers may build that fee into their rates.
Where the money hides: the traps in an SAP Fieldglass renewal
The renewal quote is built to look like continuity. The cost usually hides in five places:
- A stale usage commitment. SAP's supplement says there is no refund or credit for an unused aggregated commitment, and that on a 12-month renewal the limit is annualized unless otherwise agreed in writing. A commitment sized for a peak year carries forward unless you re-baseline it.
- Meter-definition drift. If the renewal references a different supplement version, what counts as Spend or as a Resource can change — and so can your bill. Excess use is governed by your Order Form.
- Supplier-funded fees that aren't free. A supplier-funded program can look cost-neutral while the fee migrates into bill rates you pay.
- Platform cost buried in the MSP invoice. When an MSP runs the program, its fee — buyer- or supplier-funded, by markup or discount — sits under a separate contract and can blur together with the platform cost.
- Shelfware, scope and the bundle. Services Procurement, Worker Profile Management or analytics licensed but lightly used; affiliates and countries out of date; and Fieldglass folded into a broader RISE with SAP conversation where its price disappears.
The levers that actually work
A handful of moves do most of the work in an SAP Fieldglass renewal:
- Rebuild the baseline from evidence. Collect the Order Form, every amendment and the referenced supplement version, then pull 12–24 months of actual Spend and Resource counts by module and compare them with your committed limits.
- Re-baseline the commitment. Ask for the renewal to be built on real usage rather than an annualized prior limit, with a pre-agreed excess-use rate and a true-down right at defined points.
- Fix the meter in writing. Name the usage-metric definitions and the supplement version that govern the renewal term, so the count can't drift underneath you.
- Map and separate the fee flows. Document the funding model, mirror any supplier-funded percentage in your supplier agreements, check bill rates for creep, and separate the platform fee from the MSP fee.
- Keep Fieldglass priced on its own and cap the increase. Hold Fieldglass outside any larger SAP bundle, cost a credible alternative VMS at a high level, and get a renewal price cap across the term.
Timing and leverage: when to start
Leverage is a function of time, evidence and alternatives. Start 6 to 9 months before the renewal date — before the notice window closes and before the renewal quote is built from SAP's usage snapshot. Start earlier if a RISE with SAP or S/4HANA conversation is underway, because that is when adjacent products get pulled into a bigger, longer commitment.
Use the window to reconcile usage against commitment, trace who pays which fee, review the MSP contract alongside the Fieldglass Order Form, and confirm your affiliate and country scope. A buyer who shows up two weeks before the notice date with no usage analysis has no leverage. The team that walks in with 12–24 months of evidence, a fee-flow map and a costed alternative sets the terms of the conversation.
Gather these three things before a triage call
- Your executed order form(s), amendments and the Fieldglass supplement version they reference
- The latest invoice or renewal quote, including how the fee is funded (buyer, supplier or hybrid)
- 12–24 months of spend under management and active worker / Worker Profile counts by module
With those in hand, a 15-minute call can tell you where your leverage is. Nothing needs to be shared before the call.
Walk into your SAP Fieldglass renewal prepared
This guide is the shape of the problem. For a second set of independent, buyer-side eyes on your specific renewal — where the leverage is, before your notice deadline — book a free 15-minute triage, or grab the free checklist and the free SAP Fieldglass renewal playbook.
Book a free 15-min renewal triage → Get the free 15-point renewal checklist → Get the free SAP Fieldglass renewal playbook →Frequently asked questions
How is SAP Fieldglass priced?
Through usage metrics written into your Order Form, not seats. SAP's published Fieldglass supplement defines Spend (the total expenditures processed through the service) and Resource (individuals managed or monitored in the service, also called Worker Profile, counted as a monthly allotment unless the Order Form says otherwise). Which metric applies, and exactly how it is counted, depends on the module and on the supplement version your Order Form references. SAP does not publish a rate card, so pricing is quote-based and contract-specific.
What is a supplier-funded VMS model, and does SAP Fieldglass use it?
SAP's own training material describes three funding models for Fieldglass: supplier-funded, where the buyer short-pays suppliers an agreed percentage into a holding account that pays SAP Fieldglass; buyer-funded, where the buyer pays implementation, subscription and transaction fees; and hybrid, where costs are split. SAP's material also notes that suppliers may build the fee into their rates, so a supplier-funded program is not automatically free to the buyer. Map the fee flow and check bill rates before you renew.
How is the MSP fee different from the Fieldglass fee?
A managed service provider (MSP) runs your contingent workforce program and is paid under its own contract; Fieldglass is the software platform licensed from SAP. In Fieldglass, the MSP fee can be configured as buyer-funded or supplier-funded and calculated as a markup or a discount on bill rates. At renewal, ask for the platform fee, the MSP fee and the funding model as separate lines so neither hides inside the other.
What evidence should I gather before an SAP Fieldglass renewal?
Your Order Form, every amendment, and the supplement version they reference; 12 to 24 months of actual Spend and Resource counts by module compared with your committed limits; supplier-funded fee flows and the supplier agreements that set them; your MSP contract; your notice window; and the affiliates and countries in scope. That evidence is what lets you re-baseline the commitment instead of accepting last term's number.
When should I start negotiating my SAP Fieldglass renewal?
Start 6 to 9 months out, before the notice window and before the renewal quote is built from SAP's usage snapshot. Start earlier if a RISE with SAP or S/4HANA conversation is underway, so Fieldglass stays visible and separately priced rather than folded into a larger bundle. SAP's supplement also says an aggregated usage commitment is annualized on a 12-month renewal unless otherwise agreed in writing, so the time to re-size it is before you sign.
Key takeaways
- Fieldglass is priced on usage metrics in your Order Form — Spend and Resource (Worker Profile) — not seats; confirm which metric each module uses and which supplement version defines it.
- Re-baseline the commitment to 12–24 months of actual usage: SAP's supplement gives no refund for unused aggregated commitments and annualizes them on a 12-month renewal unless otherwise agreed.
- Map who funds the program — buyer, suppliers, or both — and check bill rates, because supplier-funded fees can migrate into what you pay.
- Separate the Fieldglass platform fee from any MSP fee, and match affiliate and country scope to your current entity structure.
- Start 6–9 months out, keep Fieldglass priced on its own outside any RISE with SAP bundle, and get the meter definitions, an excess-use rate, a true-down right and a renewal cap in writing.