SAP Fieldglass review

SAP Fieldglass is difficult to assess from the published official material: SAP’s homepage text does not mention Fieldglass, so it does not establish what the product does or which capabilities belong to it. The pricing notes name four offerings—Contingent Workforce Management, Services Procurement, Worker Profile Management and Assignment Management—but do not describe what each includes.

That leaves a gap between the product name and a usable scope. SAP’s broader spend-management area is described as covering sourcing, procurement, contracts and payments, but those are not verified here as Fieldglass capabilities. We would not treat the broader SAP description as a feature list for this product.

The clearest user-side clue comes from a recruiting discussion, where participants refer to Fieldglass as a VMS and describe managers, recruiters, suppliers and MSP coordinators interacting with it. That is useful context, not a substitute for product documentation. Confirm the workflows and roles you need with SAP before treating Fieldglass as a fit.

The published sources do not verify a Fieldglass feature set, so its strengths are hard to establish. The pricing notes do identify four workforce-related categories:

• Contingent Workforce Management
• Services Procurement
• Worker Profile Management
• Assignment Management

Those labels suggest SAP packages Fieldglass around distinct workforce and procurement needs. They can help structure a sales conversation, but the notes list no included features, and they do not show how the categories differ in practice.

A Reddit discussion offers a limited operational signal. One staffing-side commenter said they received notifications when candidates were shortlisted and could check candidate status in the system. Another commenter suggested that missing visibility might depend on client settings or configuration, and said they believed reviewed status could also be visible. These are individual reports, and the discussion does not settle which permissions, alerts or status details are available in a typical setup.

SAP’s broader spend-management page also mentions sourcing, procurement, contracts and payments, plus a customer story about assistants simplifying procurement workflows and streamlining HR tasks. Those may be relevant to SAP’s wider portfolio, but the published material does not tie them to Fieldglass.

The main drawback in the published material is limited price and product transparency. Pricing is described as custom and quote-based, with monthly and annual rates not published. The notes list four plan names but no prices or included features. They mark the free-plan field as false, while a free-trial offer is not published. The pricing data is marked low confidence, so confirm every quote and inclusion directly with SAP. No numeric usage caps or plan limits are provided; that is missing information, not evidence that limits do not exist.

User reports also point to a possible visibility problem, though experiences conflict. One agency-side poster said they could not tell whether candidates had been viewed or how managers searched and shortlisted them. A commenter said their staffing-side setup provided shortlist notifications and status checks, and suggested configuration could explain the difference. That disagreement makes permissions, client setup and supplier access important questions to resolve before buying. Ask SAP to demonstrate the specific hiring and status workflows your team needs, and get those details written into the quote.

The published pricing notes describe SAP Fieldglass as custom-priced and quote-based; they do not give a starting price or monthly or annual rates. They list four offerings: Contingent Workforce Management, Services Procurement, Worker Profile Management and Assignment Management. Prices for all four are unpublished, so there is no verifiable jump between offerings—and no public rate card to compare against another vendor’s quote.

The notes list no add-ons, but that does not confirm they are unavailable or included. They also do not specify billing frequency, contract length, implementation fees or what drives the quote. Ask SAP to itemize those costs and state which capabilities, users and services the quote covers. The notes are marked low confidence, so treat them as a prompt to request current written pricing, not as a final quote. If predictable public pricing is a requirement, Fieldglass is difficult to assess from the published information alone.

The published sources do not establish Fieldglass’s migration tools, data-export options, implementation effort or contract terms. They also do not include Reddit reports about why customers leave, so we can’t verify common switching complaints. Don’t assume export formats, integrations or migration support: ask SAP and any replacement vendor to confirm them in writing.

Before committing, map the worker, assignment and services-procurement records you need to move, and confirm which fields, history and attachments can be exported. Request a migration plan, ownership of the work, costs, and a clear answer on access to your data during and after a contract. If you are moving from Fieldglass, test a representative export before setting a cutover date. If you are moving to it, confirm how your current systems and workflows will connect. The vendor's homepage discusses SAP’s broader spend-management areas, not Fieldglass-specific capabilities, so verify the exact configuration and scope with SAP before treating those descriptions as product commitments.