SAP Fieldglass is licensed primarily on spend under management - a percentage of the contingent-workforce and services spend that flows through the platform - rather than on named users, which means your bill scales with how much external-workforce spend you process, not with how many people log in. That model rewards accurate baselining and punishes loose forecasting. This guide explains how Fieldglass is priced, what actually drives the number, and the levers a buyer has at renewal. It sits within our broader SAP licensing guide and our pillar on the SAP estate and ECC exit.
What Fieldglass is
SAP Fieldglass is a cloud-based vendor management system (VMS) for the external workforce: contingent labour, statement-of-work services, and other non-payroll talent. Organisations use it to source, engage, manage, and pay contractors and services suppliers, and to gain visibility and control over a category of spend that is otherwise fragmented across business units. Because it is a SaaS application, it is licensed as a subscription rather than as on-premise software.
The spend-under-management model
The defining feature of Fieldglass pricing is that it is tied to the volume of spend transacted through the system. Commercials are typically structured as a percentage applied to the contingent-workforce and services spend that flows through Fieldglass over the contract period, often with a committed minimum. The logic is that the platform's value scales with the spend it governs, so the fee scales with it too. This is fundamentally different from per-user SaaS pricing and requires a different diligence approach.
| Element | What it represents | Buyer consideration |
|---|---|---|
| Spend under management | Services / contingent spend processed | The primary cost base - baseline it carefully |
| Percentage rate | Fee applied to that spend | Negotiable; benchmark against volume |
| Committed minimum | Floor regardless of actual volume | Avoid committing above realistic spend |
| Subscription term | Multi-year cloud agreement | Align term and ramp to adoption curve |
What drives the cost
Three things move a Fieldglass bill. The first is the volume of spend you route through the platform - the more categories and business units you onboard, the larger the base. The second is the percentage rate, which is where negotiation concentrates and which should reflect the scale of spend you bring. The third is the committed minimum: if you commit to a spend level you do not reach, you pay for governance you did not use. Because the model is spend-based, an over-optimistic forecast at signing translates directly into overpayment.
Baseline before you commit. The most common Fieldglass commercial mistake is committing to a spend-under-management level based on aspiration rather than measured reality. Spend-based pricing means a minimum commitment above your actual processed spend is money paid for nothing. Establish a defensible baseline of contingent and services spend, model the realistic adoption ramp, and size the commitment to the conservative case - you can grow into more, but you cannot easily claw back an over-commitment.
Indirect access and integration
Fieldglass rarely stands alone. It integrates with the core SAP estate - procurement, finance, and HR - and with third-party systems. Those integrations raise the same indirect- and digital-access questions that apply across SAP. Where Fieldglass data flows into or out of SAP ERP through documents and APIs, you should understand whether that interaction is already covered by your agreements or whether it implicates SAP's digital-access licensing. We cover the mechanics in our guides to the SAP Digital Access Adoption Program and SAP API and indirect-access changes; both are worth reading before you finalise a Fieldglass integration architecture.
The renewal levers
A Fieldglass renewal is a cloud-contract negotiation, and the levers are the ones common to SaaS deals, sharpened by the spend-based model. Re-baseline your actual processed spend before the conversation, so the percentage and minimum reflect current reality rather than the assumptions from the original deal. Benchmark the rate against the volume you bring. Scrutinise the committed minimum and any uplift mechanics. Align the term length and any ramp to your real adoption curve. And treat module additions and premium features as separate negotiable items rather than accepting a bundled uplift. The disciplines are covered in our cloud contract negotiation service.
A buyer-side checklist
Before renewing Fieldglass, confirm four things. What is your true spend under management, measured rather than forecast? Is your committed minimum at or below that measured level? Does the percentage rate reflect the scale of spend you process, benchmarked externally? And have you accounted for the indirect-access implications of every integration into and out of SAP? Answering these turns a spend-based renewal from an open-ended liability into a controlled, defensible commitment.
Fieldglass in the wider VMS and SAP context
Two contextual points help frame a Fieldglass commercial. First, Fieldglass competes in a vendor-management-system market with other established platforms, which means you have genuine benchmark reference points and, at renewal, real alternatives that strengthen your negotiating position even if you intend to stay. Knowing where the market sits on rate and structure is leverage. Second, Fieldglass is part of SAP's intelligent-spend and business-network portfolio, so SAP may present it bundled with adjacent procurement and network products. Bundling can deliver value, but it can also obscure the standalone economics of each component. Insist on seeing Fieldglass priced on its own spend-based terms before evaluating any bundle, so you can tell whether the bundle is a discount or a way to grow total commitment. The same discipline applies to any premium modules or analytics add-ons layered onto the core platform.
For the wider SAP picture, see the SAP third-party support and ECC exit pillar and the complete SAP licensing guide. For an engagement on your Fieldglass or broader SAP cloud commercials, see our SAP licensing experts service and the SAP vendor hub.