Key Takeaways
- SAP Build is a suite of three low-code products — SAP Build Apps, SAP Build Process Automation, and SAP Build Work Zone — all delivered through SAP BTP
- SAP Build entitlements are included in RISE with SAP and GROW with SAP base packages, but only at starter capacity levels that most enterprise deployments will exceed quickly
- SAP Build licensing is BTP consumption-based: costs scale with application users, process automation runs, and workflow instances — creating unpredictable spend if not governed
- 70% of RISE customers hold BTP credits that never get fully consumed — but SAP Build capacity overruns are a separate charge that catches organisations by surprise
- Negotiating SAP Build entitlements, consumption caps, and overage protections before signing your BTP or RISE contract is essential — these terms are far harder to change post-signature
SAP Build is SAP's answer to the low-code revolution. Announced in 2022 and expanded significantly through 2024 and 2025, it consolidates SAP's citizen development tools — app creation, process automation, and digital workplace — into a unified suite. The marketing message is that non-technical employees can build business applications, automate workflows, and extend SAP systems without professional developers. The commercial reality is more complicated.
SAP Build licensing is delivered entirely through SAP BTP — the Business Technology Platform — and follows BTP's notoriously complex consumption-based model. Understanding what is included in your BTP entitlements, where consumption overruns occur, and how to negotiate SAP Build capacity before you sign is essential for any enterprise deploying RISE with SAP or buying BTP services directly. This guide covers all of it.
What Is SAP Build? The Three Products Explained
SAP Build is not a single product — it is a portfolio of three related tools, each with its own licensing model, consumption metrics, and cost drivers:
Want an Independent View of Your SAP Position?
Our advisors are former SAP insiders working exclusively for enterprise buyers. A free 30-minute discovery call will tell you whether independent advisory would materially change your commercial outcome.
Book a Free Consultation → Download Free SAP Audit Guide →Visual App Development
Drag-and-drop application builder for creating SAP-connected web and mobile apps without coding. Replaces SAP AppGyver. Licensed by active users per month and build minutes consumed.
Workflow & Robotic Automation
Combines SAP Workflow Management and SAP Intelligent RPA (Robotic Process Automation). Licensed by workflow instances, automation jobs, and bot runtime hours. Consumption can escalate rapidly in high-volume process environments.
Digital Workplace Hub
Unified portal for SAP applications, integrations, and employee-facing content. Two editions: Standard Edition (included in most BTP packages) and Advanced Edition (priced per user per month, significantly higher). See our dedicated SAP Work Zone licensing guide for details.
All three SAP Build products run on BTP infrastructure and consume BTP service plans. This means your SAP Build costs are inextricably linked to your overall BTP consumption model — and understanding the BTP credit and service plan structure is a prerequisite for managing SAP Build costs.
SAP Build Entitlements in RISE with SAP and GROW with SAP
SAP bundles starter-level SAP Build entitlements into RISE with SAP and GROW with SAP subscriptions. These are positioned as "included in your RISE contract" — which is technically accurate but commercially misleading. The included entitlements are sized for proof-of-concept deployment, not enterprise-scale production use.
What RISE with SAP Includes
A standard RISE with SAP Private Cloud Edition contract typically includes:
- SAP Build Apps: 25 active users per month at Standard plan capacity. Sufficient for a pilot with a small citizen developer group. Not sufficient for organisation-wide rollout.
- SAP Build Process Automation: A fixed number of workflow instances (typically 3,000–5,000 per month) and limited RPA bot runtime. Enterprises running high-volume AP, HR, or procurement automation will exceed this within months.
- SAP Build Work Zone (Standard Edition): Included at scale for all named users on your RISE subscription. The Advanced Edition — which includes personalisation, advanced analytics, and extended integration capabilities — is a separate purchase.
What GROW with SAP Includes
GROW with SAP (SAP S/4HANA Cloud Public Edition) includes a similar SAP Build starter package, often with slightly lower thresholds than RISE. The GROW model is designed for midmarket organisations that are less likely to pursue large-scale citizen development, so SAP's commercial team is less proactive about upsizing Build entitlements at the time of signing.
SAP Build Pricing: How the Consumption Model Works
Understanding SAP Build's pricing structure requires understanding BTP's dual commercial model: the subscription model (fixed entitlements per service plan) and the consumption-based model (pay-per-use via BTP credits).
SAP Build Apps Pricing
SAP Build Apps is priced on a per-active-user basis. SAP defines an "active user" as any individual who creates or modifies an application within a calendar month — not just people who use deployed applications. This distinction matters: in a citizen development programme, the count of active creators is smaller than the count of application consumers, but the consumer-side licensing depends on how applications are deployed and whether they are run on BTP or on SAP Fiori.
| Tier | Capacity | Typical Use Case | Commercial Note |
|---|---|---|---|
| Included in RISE | 25 active users/month | Pilot / PoC | Overage billed at BTP list |
| SAP Build Apps — Standard | 100 active users/month | Department deployment | Negotiable; benchmark against list |
| SAP Build Apps — Professional | Unlimited users | Enterprise-wide rollout | Significant discount available vs per-user |
SAP Build Process Automation Pricing
Process Automation is the most commercially complex of the three Build products. It has multiple consumption dimensions: workflow instances (each execution of a defined process), RPA job runs (each automated task execution), and active users who access the process automation cockpit. All three dimensions can generate costs independently.
The workflow instance model is particularly prone to overruns in organisations with high-transaction processes — purchase order approvals, invoice processing, or employee onboarding. A mid-size manufacturing company processing 500 purchase orders per day will consume 180,000 workflow instances per year before any RPA activity is factored in. At list price, this can represent €200K–€400K in annual BTP consumption beyond what RISE includes.
SAP Build Work Zone Advanced Edition Pricing
SAP Build Work Zone Standard Edition is included in most BTP and RISE subscriptions. The Advanced Edition, which adds personalisation engines, native mobile app capability, content federation, and advanced analytics, is priced per user per month. List pricing typically runs €15–€25 per user per month for large enterprises, with negotiated rates available. See our SAP Work Zone licensing guide for a full comparison of Standard versus Advanced Edition capabilities and costs.
SAP Build and BTP Credits: The Consumption Architecture
SAP Build services can be purchased via BTP Global Accounts using the consumption-based commercial model — meaning they draw down from your BTP credit balance. This has important implications for organisations that received BTP credits as part of their RISE contract.
SAP bundles BTP credits into RISE agreements as part of the transition incentive. These credits are designed to encourage BTP adoption but expire — typically within 12–24 months of the RISE go-live date. Our analysis of SAP BTP credit consumption found that 70% of RISE customers never fully use their allocated credits, while simultaneously accruing SAP Build overruns billed outside the credit mechanism.
This asymmetry exists because SAP Build overage is often billed through a separate commercial mechanism — a BTP Subscription agreement for the specific service plan, not through your general BTP credit balance. This means credits expire unused while Build overrun invoices arrive separately. Correcting this requires explicit contract language at the time of signing.
How to Negotiate SAP Build Licensing: The Enterprise Playbook
SAP Build is a relatively new commercial offering, which means SAP's pricing and deal structures are less standardised than for legacy products. This creates genuine negotiating room — but only for buyers who engage the commercial conversation before signing, not after deployment.
Model Your Actual Consumption Before Negotiating
Before approaching SAP on SAP Build pricing, build a realistic consumption model: how many citizen developers do you intend to enable, what processes will be automated, how many workflow instances per month, and what user population will access Build Work Zone Advanced Edition. Without this model, you cannot benchmark SAP's proposal or identify where the overrun risks sit.
Negotiate Capacity at RISE or BTP Contract Signature
SAP Build entitlements are most negotiable when they are part of a larger RISE, GROW, or BTP commercial discussion. Adding SAP Build capacity to a RISE negotiation — as part of the overall deal economics — typically produces 25–40% better pricing than purchasing SAP Build capacity as a standalone expansion after go-live.
Demand Overage Protections and Consumption Caps
Request contractual caps on SAP Build overage charges — either as a monthly monetary limit or as an automatic escalation to the next service tier when your consumption approaches threshold. SAP will resist hard caps but will often accept a "soft cap with 30-day notification" provision that gives you time to adjust before being billed for overruns. This single provision can prevent five- and six-figure surprise invoices.
Align BTP Credit Usage with SAP Build Costs
Negotiate explicit contract language that SAP Build consumption can be satisfied by your general BTP credit balance. This requires a specific amendment to the standard RISE or BTP Order Form — your account executive will say it is not standard, but deal desk will approve it for deals above a certain threshold.
Challenge the Standard Service Plan Structure
SAP's standard SAP Build service plans are designed for predictable, low-volume use. Large enterprises with complex process automation requirements should negotiate custom commercial terms — a blended rate across workflow instances, RPA runs, and user counts — rather than accepting the per-unit pricing in SAP's standard BTP price list.
Include SAP Build in Your Licence Optimisation Reviews
SAP Build consumption should be reviewed quarterly alongside your broader BTP usage. Unused Build Apps licences, dormant Process Automation configurations, and over-provisioned Work Zone Advanced users all represent costs that can be restructured mid-term. See our guidance on SAP licence optimisation for the framework.
SAP Build Is a BTP Licensing Problem in Disguise
Most SAP Build cost overruns are preventable with correct contract structuring at the point of signing your RISE or BTP agreement. Our RISE with SAP advisory team has reviewed over 50 RISE proposals and consistently identifies SAP Build as one of the top three sources of unexpected post-signature cost. Talk to us before you sign.
Get a RISE Contract ReviewSAP Build Governance: Controlling Citizen Development Costs
The commercial risk of SAP Build is not just in the contract — it is in the deployment model. Citizen development programmes, by design, distribute application creation to non-technical users across the organisation. Without governance controls, this distribution creates unpredictable BTP consumption that is extremely difficult to budget or forecast.
Best-practice SAP Build governance includes a number of controls that directly affect your licensing cost:
- Central BTP Global Account monitoring — real-time consumption dashboards that flag Build Apps, Process Automation, and Work Zone usage against your contracted thresholds. SAP's SAP for Me portal provides this data but requires active monitoring.
- Application retirement policies — SAP Build Apps licences are charged per active creator, but deployed applications continue to consume BTP infrastructure resources. Applications that are no longer actively used should be retired to reduce ongoing BTP consumption.
- Process Automation instance limits — configure maximum workflow instance limits per deployed process in your Process Automation configuration. This prevents a runaway automation process from generating thousands of billable instances before your monitoring detects it.
- Work Zone Advanced Edition right-sizing — audit your Work Zone Advanced user list quarterly. Users who have not accessed the platform in 90 days should be reviewed for licence removal or downgrade to Standard Edition.
The Five SAP Build Licensing Traps to Avoid
Trap 1: Assuming Your RISE Entitlements Are Sufficient
RISE with SAP Build entitlements are starter-level. Any enterprise planning a meaningful citizen development or process automation programme will exceed them. Build your consumption model before assuming your RISE contract covers your SAP Build plans.
Trap 2: Ignoring the Work Zone Advanced Edition Distinction
SAP Work Zone Standard is included — Work Zone Advanced is not. Many organisations discover this distinction only when they attempt to deploy features that require the Advanced Edition. The cost difference can be material across a large user population.
Trap 3: Treating SAP Build as a Free Citizen Development Platform
The "included in RISE" messaging creates an expectation that SAP Build is free. It is not — it is deferred cost in a consumption model that triggers charges the moment you exceed starter thresholds. Treating it as free leads to unbudgeted BTP invoices.
Trap 4: Buying SAP Build Capacity Post-Go-Live
SAP Build capacity purchased after your RISE or BTP contract has been signed is priced at less favourable rates than capacity negotiated as part of the original deal. The leverage you have during contract negotiation — the cloud booking, the TCV, the multi-year commitment — disappears after signature.
Trap 5: Not Modelling Process Automation Volumes
Process Automation is the highest-risk consumption component in SAP Build. Workflow instances and RPA job runs scale with business volume — not with your headcount or user count. A process that runs 1,000 times per day generates 365,000 billable instances per year. Model your automation volumes explicitly before your deployment begins.
Conclusion: SAP Build Is a Strategic Platform With Real Licensing Complexity
SAP Build is genuinely useful. For organisations that need to extend SAP S/4HANA with business-specific applications, automate high-volume processes, or create a unified digital workplace without large development teams, the three Build products deliver real value. The problem is not the technology — it is the licensing model.
SAP Build's BTP-based consumption pricing, its entanglement with RISE and GROW contract structures, and its tendency to generate overrun charges that fall outside standard contract governance frameworks create material financial risk for enterprises that do not engage the commercial conversation carefully before signing.
If you are evaluating RISE with SAP, approaching a BTP expansion, or currently running SAP Build and worried about consumption costs, our team can review your current position, model your exposure, and identify the negotiation levers available to you. The complete SAP BTP licensing guide provides additional context on the broader platform economics.