SAP Build is the low-code, process-automation and developer-tooling surface on Business Technology Platform. The Admodum read on the three products, the credit basket, the seat-and-credit hybrid model and the buyer-side commitment discipline.
SAP Build is the BTP umbrella for the low-code, process-automation and developer-tooling surface. The umbrella organises three products under a shared commercial structure and a shared design-time experience: Build Apps, Build Process Automation and Build Code.
Build Apps is the low-code application builder, the successor to the AppGyver acquisition. Build Process Automation is the workflow-orchestration and RPA engine, the successor to the SAP Workflow Management service and the SAP Intelligent RPA service. Build Code is the BTP-resident developer environment that runs ABAP Cloud and Java development against the clean-core extensibility model.
Build Apps is the visual-builder low-code product that produces web and mobile applications. The application is composed from a library of components and bound to a BTP-resident data model or an external API source. The output is a deployable application that runs on the BTP runtime and consumes BTP runtime credits.
The commercial model is a seat-priced subscription: a developer seat for the application builder and an end-user seat for the deployed application audience. The end-user seat is the silent renewal-cycle driver at scale: an application that reaches an enterprise audience drives the end-user-seat count well above the developer-seat count.
Build Process Automation is the workflow-orchestration and bot-execution product. The product replaces and consolidates two predecessor services: the SAP Workflow Management service and the SAP Intelligent RPA service. The consolidation is a transition-period read for customers with active entitlement against either predecessor.
The commercial model is seat-priced on the developer and end-user counts. The runtime consumption (the workflow runs, the bot executions, the trigger evaluations) is metered against the BTP credit pool. The buyer-side artefact is the workflow-run-rate forecast against the deployed workflow inventory.
Build Code is the BTP-resident developer environment. The environment supports ABAP Cloud development against the clean-core extensibility model and Java development against the BTP runtime. The product replaces the predecessor Business Application Studio entitlement that ships with the BTP free tier.
The commercial model is seat-priced on the developer count. The runtime consumption (the build minutes, the test environments, the deployed-application runtime) is metered against the BTP credit pool. The buyer-side read is the named-developer roster against the seat count: a developer seat is reassignable but tied to a named individual at any one time.
The Build commercial model is a seat-and-credit hybrid. The seat tier is the predictable, capacity-based commitment; the credit tier is the variable, consumption-based commitment. The two interact at the renewal cycle: a seat count that is sized against the predictable workload and a credit pool that absorbs the variable workload.
The buyer-side discipline is the workload-by-workload forecast. The developer-seat forecast is the named-developer roster; the end-user-seat forecast is the deployed-application audience; the credit-pool forecast is the application-execution rate, the workflow-run cadence, the build-minute volume against the actual deployed workload.
The renewal posture is driven by the application-portfolio audit. The audit inventories the deployed Build applications, the active developer seats, the actual runtime consumption, the predecessor-entitlement transition status (the Workflow Management and Intelligent RPA carryover where applicable) and the BTP credit-pool drawdown against the Build workloads specifically.
The buyer-side artefact is the renewal evidence pack: the developer seat list, the application audience size, the runtime-credit consumption rate, the predecessor-entitlement transition map, the BTP credit-pool drawdown. The senior-advisor read aligns the renewal-cycle commitment to the actual deployed workload rather than the SAP account-team forecast.
The credit basket that absorbs Build runtime, workflow runs and build minutes.
The architectural pattern that Build Code targets for ABAP Cloud extensions.
A senior Admodum SAP advisor will read your Build subscription, your BTP credit consumption and your renewal posture on a private call. Active renewal moments route to Renewal Programme.