GROW pricing tiers — the band structure

SAP GROW is sold in pricing bands rather than as a single linear price. Each band defines an entry FUE quantity, an included module scope, a BTP-credit allocation, and a per-FUE rate that varies modestly across bands. The band structure is presented as a simplification benefit. For most mid-market buyers it is a simplification with consequences: the band thresholds create economic step-changes at specific user counts, and the renewal trajectory across bands can be substantially less favourable than the buyer assumed at sign. This article sets out the band structure, the threshold economics, and the bracket-creep problem that recurs at renewal. It is one of the engagement patterns inside our contract negotiation service for GROW buyers.

The band structure

GROW pricing is organised into bands by FUE quantity. The exact band boundaries vary across SAP’s pricing generations and regions, but the typical pattern includes an entry band (covering the smaller mid-market entrants), one or two intermediate bands (the bulk of the mid-market base), and an upper band (where GROW starts to overlap with RISE). Each band has its own per-FUE list price and its own minimum subscription.

The intent of the band structure is operational: SAP can sell GROW at a low marginal cost to the entry-band buyers (where the support and account-management cost per buyer is lowest) and at a higher marginal cost to upper-band buyers. The implication for the buyer is that the per-FUE rate is not constant across the population; landing in the right band is itself a commercial decision. The GROW topic page sets out the broader architectural detail.

What changes between bands

Three elements vary materially across GROW bands. First, the per-FUE rate, which steps up across bands. Second, the included module scope, with the entry band typically excluding certain operational areas (advanced analytics, certain integration-suite features, some industry-specific add-ons) and the higher bands including them. Third, the BTP-credit allocation, which scales with the band but not always linearly.

The buyer-side discipline is to read each band’s inclusion list against the buyer’s actual operational requirement. An entry-band signing where the operational requirement extends to upper-band-included content forces additional purchases (which exceed the cost saving of the lower band) or operational compromise. The GROW package contents article sets out the inclusion list in detail.

The included-modules gap

Buyers in the entry band typically find one or two modules excluded that they expected to be included. Common cases include advanced inventory management features, advanced production planning, and certain analytics capabilities. The exclusion is documented in the SAP-supplied band literature but is easy to miss in the deal-stage review. The pre-sign exercise should include a line-by-line review of the band-included list against the buyer’s process inventory.

The threshold economics

The pricing step at the band threshold can be material. A buyer at FUE 240 in the entry band signs at a per-FUE rate of (for example) X; a buyer at FUE 260 in the next band signs at a per-FUE rate of approximately 1.15X. The differential applies across the entire FUE quantity, not just the marginal FUE above the threshold. The economic implication is that landing just below a band threshold is materially better than landing just above.

The buyer-side preparation is the population review applied at the deal-sign stage, with the goal of placing the contracted FUE quantity just below a band threshold if the operational requirement permits. Where the operational requirement places the buyer above the threshold, the band-rate negotiation becomes the focus, with the buyer-side leverage drawn from the comparable-deal benchmarks in the same band. The FUE in GROW article covers the FUE quantity construct.

The bracket-creep problem

The bracket-creep problem is the renewal-stage version of the threshold problem. A buyer who entered GROW at FUE 240 (entry band) and who has grown organically across the contract term to FUE 280 will, at renewal, sit in the intermediate band. The renewal pricing applies the intermediate band rate to the new FUE quantity. The total renewal price increase is the sum of the FUE growth and the band step.

Buyers anticipate the FUE-growth component but rarely anticipate the band-step component. The renewal therefore arrives with a larger increase than the buyer modelled. The mitigation is the contractual provision (negotiated at initial sign) that holds the entry-band rate across a defined FUE growth range at renewal. The provision is non-standard but achievable in serious negotiations. The GROW renewal mechanics article covers the renewal-stage provisions in detail.

The cross-band migration

Buyers whose growth takes them clearly into an upper band face a structural decision at renewal: continue in the higher band (and accept the rate) or migrate to RISE (which becomes the rational route in the upper-band region where the two products overlap). The migration option is real but the migration cost is substantial: the GROW-to-RISE conversion is technically an environmental migration, not a contractual reclassification, and the buyer rebuilds the implementation.

The migration option therefore exists as leverage rather than as a likely action. The buyer’s ability to credibly threaten the migration influences the renewal price negotiation; the actual exercise of the option is uncommon. The GROW versus RISE comparison covers the route-selection decision frame.

The BTP-credit dimension

BTP credit allocation in GROW varies by band. The allocation is non-trivial in the upper bands (sometimes a key part of the band’s economics) and modest in the entry band. The credit allocation is itself a negotiable element within the band: the buyer can sometimes negotiate a higher credit allocation as part of the deal in exchange for term commitments or for accepting other terms.

The credit-usage forecast is the buyer-side input. A buyer with a clear extensibility-build pipeline should size the credit allocation to the pipeline; a buyer with no immediate extensibility need should minimise the allocation. The GROW extensibility article covers the credit-usage frame.

The list-versus-net question

The band rates SAP discloses are list rates. The negotiated rates are typically discounted from list by a meaningful margin (the discount depends on the band, the term commitment, the regional pricing context, and the specific deal). The buyer-side leverage on the discount comes from the comparable-deal evidence, from the credible threat of alternative routes, and from the term-and-scope commitments the buyer is prepared to make.

Each band is a separate negotiation. The discount achievable in the entry band is not the same as in the upper band, because the SAP-side economics differ. The negotiation should therefore be band-specific rather than generic, with the discount target informed by comparable-deal evidence in the same band. The GROW pricing benchmarks white paper sets out the comparable-deal frame, and the mid-market GROW case file documents the negotiated outcome in practice.

Where to start

Map the buyer’s actual position against the band thresholds before signing. Sit just below the next-band threshold rather than just above; the price differential across the boundary is material. The contract negotiation service brief covers the GROW-route specifics.