SAP Build

Name: SAP Build
Brand: SAP
Rating: 4.3 (252 reviews)

Leader

We bring out the best in every business.

Est 1972|Valuation $254.5B|Raised $495.9M

LinkedIn 180K|Website|Web traffic 12.5M|FTEs 2,432|HQ Walldorf, Germany

MarketsBusiness Process Management (BPM)Workflow Automation Low-Code Development Platforms

Published Oct 15, 2026

01Common complaints

This section describes scenarios where SAP Build may not be the appropriate choice or where usage should be limited to narrow cases:

The organization is not an SAP shop: SAP Build’s primary differentiation is SAP-native context; if SAP is not central, alternatives may be less expensive and simpler.
Complex, highly customized UI is required: TrustRadius reviews advise caution for complex UI requirements.
The organization already has a scaled citizen-development platform (e.g., Power Platform) with governance, COE, and adoption: introducing SAP Build can create a second low-code ecosystem with duplicated patterns, training, and operations.
Best-of-breed RPA at scale is required: Dedicated RPA vendors often provide deeper desktop automation capabilities and more mature operational tooling.
The organization cannot invest in DevOps maturity: Peer review titles and community commentary indicate scaling adoption requires platform and operational maturity beyond simple drag-and-drop usage.

This section describes scenarios where SAP Build may not be the appropriate choice or where usage should be limited to narrow cases: - **The organization is not an SAP shop**: SAP Build’s primary differentiation is SAP-native context; if SAP is not central, alternatives may be less expensive and simpler. - **Complex, highly customized UI is required**: TrustRadius reviews advise caution for complex UI requirements. - **The organization already has a scaled citizen-development platform** (e.g., Power Platform) with governance, COE, and adoption: introducing SAP Build can create a second low-code ecosystem with duplicated patterns, training, and operations. - **Best-of-breed RPA at scale is required**: Dedicated RPA vendors often provide deeper desktop automation capabilities and more mature operational tooling. - **The organization cannot invest in DevOps maturity**: Peer review titles and community commentary indicate scaling adoption requires platform and operational maturity beyond simple drag-and-drop usage.

Deal disqualifiers (poor fit)

The organization mainly requires non-SAP app development with minimal SAP integration.
The organization needs heavy custom UI/front-end experiences beyond what reviews suggest Build handles comfortably.
The organization cannot support the platform engineering/governance overhead.

Limitations and recurring pain points (from reviews/discussions)

Cannot copy processes (reported by a TrustRadius reviewer)
Environment deployment problems (reported by reviewers)
Integration complexity and non-SAP integration friction (reported on multiple review platforms)
Limited customization (reported by reviewers)
Performance issues reported by some users (G2 and TrustRadius excerpts)

Roadmap / "AI agents" evolution (caution)

SAP’s messaging has evolved toward AI agents/Joule Studio and generative AI augmentation. Some public-facing claims about agent capabilities and out-of-the-box use cases appear in vendor-sponsored content.

Buyers should validate what is generally available vs roadmap, what is region/edition-dependent, and what requires additional AI credits/entitlements.

02Why they buy

Why customers chose SAP Build (recurring themes)

Across review platforms and discussions, common rationales include:

Native SAP integration and ability to extend SAP apps in context
Governance / clean-core narrative (upgrade-safe extensions)
Consolidating multiple needs (apps + workflows + workspace) under SAP tooling

03Field reports

Gartner Peer Insights (examples)

Gartner Peer Insights shows SAP Build with an above-average aggregate rating and a modest number of ratings at the time of capture, and provides qualitative review titles that highlight both adoption value and scaling caveats.

Examples of review headlines/snippets visible on the product page:

Positive: “Efficient SAP Integration Enables Rapid Prototyping With Minimal Development Work”
Mixed: “Business Enablement Enhanced Yet Large Scale Adoption Needs DevOps Maturity”

(Full review text is often gated behind interaction; the product page still indicates the themes and rating distribution.)

Gartner Peer Insights shows **SAP Build** with an above-average aggregate rating and a modest number of ratings at the time of capture, and provides qualitative review titles that highlight both adoption value and scaling caveats. Examples of review headlines/snippets visible on the product page: - **Positive**: “Efficient SAP Integration Enables Rapid Prototyping With Minimal Development Work” - **Mixed**: “Business Enablement Enhanced Yet Large Scale Adoption Needs DevOps Maturity” *(Full review text is often gated behind interaction; the product page still indicates the themes and rating distribution.)*

G2 reviews (examples)

G2’s SAP Build reviews contain both praise and criticism. Examples pulled from visible review excerpts:

Positive: A reviewer reports SAP Build enabled rapid prototyping and workflow/app building with templates and AI suggestions, and cited SAP integration as reliable.
Negative/mixed points in the same review: “Initial setup took more effort than expected… Customer support response times can be slow… linking non-SAP systems… required workarounds.”

G2 also places SAP Build as a “Contender” in its No-Code grid report, noting market presence but comparatively lower satisfaction versus leaders, and flags limited review volume that constrains validation of the ratings.

G2’s SAP Build reviews contain both praise and criticism. Examples pulled from visible review excerpts: - **Positive**: A reviewer reports SAP Build enabled rapid prototyping and workflow/app building with templates and AI suggestions, and cited SAP integration as reliable. - **Negative/mixed points in the same review**: “Initial setup took more effort than expected… Customer support response times can be slow… linking non-SAP systems… required workarounds.” G2 also places SAP Build as a **“Contender”** in its No-Code grid report, noting market presence but comparatively lower satisfaction versus leaders, and flags limited review volume that constrains validation of the ratings.

TrustRadius reviews (examples + concrete complaints)

TrustRadius reviews show strong scores in some entries but contain pointed “cons” that are useful for buyers:

Pros cited: process automation, workflow triggers from SAP apps, building apps/digital workspaces.
Cons cited (specific): “Environment deployment has some problems,” “Cannot copy Processes,” “performance issues,” “limited customizations,” and “complex integrations.”
One reviewer explicitly advises: “If you have a complex UI requirements then don't use SAP Build.”

TrustRadius reviews show strong scores in some entries but contain pointed “cons” that are useful for buyers: - **Pros cited**: process automation, workflow triggers from SAP apps, building apps/digital workspaces. - **Cons cited (specific)**: “Environment deployment has some problems,” “Cannot copy Processes,” “performance issues,” “limited customizations,” and “complex integrations.” - One reviewer explicitly advises: **“If you have a complex UI requirements then don't use SAP Build.”**

Community / Reddit / forums (examples)

Community discussion trends are more candid and often emphasize scaling realities:

In SAP-focused community threads, commenters describe success in narrow use cases (e.g., ticket reading + incident creation) but also warn that scaling beyond templates or making business users fully self-sufficient often still requires functional/technical support.
Other community threads express skepticism about the value added after training—suggesting perceived ROI varies and may depend on licensing/AI credits and maturity.

Community discussion trends are more candid and often emphasize scaling realities: - In SAP-focused community threads, commenters describe success in narrow use cases (e.g., ticket reading + incident creation) but also warn that scaling beyond templates or making business users fully self-sufficient often still requires functional/technical support. - Other community threads express skepticism about the value added after training—suggesting perceived ROI varies and may depend on licensing/AI credits and maturity.

Why some customers hesitate or leave (recurring themes)

Existing adoption of Microsoft Power Platform in many SAP shops (especially Azure-aligned enterprises) makes Build a second platform to justify.
Non-SAP integration complexity and limitations become friction points.
Operational maturity requirements (DevOps, transport, lifecycle management) can reduce the anticipated citizen-developer benefits.

Case Studies

SAP’s SAP Build product page highlights customer stories with quantified claims, for example:

very large reported gains in app development speed
notable reported increases in transaction volume
reported reductions in operating costs

Critical evaluation:

These metrics are vendor-published and often lack a disclosed methodology (baseline, sample size, time period, counterfactual). Buyers should request:
- before/after definitions
- measured time horizon
- what portion of gains is attributable to Build versus broader program changes (process redesign, data cleanup, training)

Community evidence of mixed results is mostly anecdotal:

Community discussions indicate some teams can implement useful automations, but scaling citizen-owned automations without dedicated support is often difficult.

SAP’s SAP Build product page highlights customer stories with quantified claims, for example: - very large reported gains in app development speed - notable reported increases in transaction volume - reported reductions in operating costs **Critical evaluation:** - These metrics are vendor-published and often lack a disclosed methodology (baseline, sample size, time period, counterfactual). Buyers should request: - before/after definitions - measured time horizon - what portion of gains is attributable to Build versus broader program changes (process redesign, data cleanup, training) Community evidence of mixed results is mostly anecdotal: - Community discussions indicate some teams can implement useful automations, but scaling citizen-owned automations without dedicated support is often difficult.

04Best fit

Company size

Most credible fit: mid-market to large enterprise (typically upper mid-market to enterprise organizations with a significant SAP footprint).

Industries

Commonly relevant in SAP-heavy verticals: manufacturing, transportation/logistics, utilities, CPG, pharma, and shared services—particularly where SAP is the system of record.

Roles/personas

Decision makers: CIO/IT leadership, SAP CoE leads, enterprise architects, BTP platform owners
Champions: SAP solution architects, automation leads (RPA/DPA), process owners
End users: citizen developers in business ops, power users in finance/procurement/HR; workflow participants/approvers

Pain points SAP Build addresses

High volume of manual SAP-adjacent processes (email approvals, spreadsheet tracking)
Need for faster extension delivery without modifying S/4HANA core
Requirement for governance and standardized extension patterns across teams

Qualification criteria (good fit)

The organization already licenses or is adopting SAP BTP and can staff platform governance.
Use cases are primarily SAP-workflow-centric and can leverage prebuilt SAP content.
The organization can invest in DevOps/transport discipline if aiming for enterprise-scale citizen development.

05The pitch

What the product does (objective value proposition)

Low-/no-code: SAP Build Apps, SAP Build Process Automation, SAP Build Work Zone
Pro-code & AI-assisted development: SAP Build Code (and related SAP BTP dev tooling)
Agent development: Joule Studio within SAP Build (positioning has evolved toward "AI agents")

SAP indicates outcomes such as faster delivery and reduced effort via prebuilt content, templates, and AI assistance. SAP's materials also emphasize governance and upgrade-safe extension patterns ("clean core alignment").

SAP Build is SAP’s unified extension and automation product family for creating apps, workflows/automations (including RPA-style UI automation), and digital workspaces—primarily for SAP-centric enterprises that intend to extend SAP applications while maintaining "clean core" principles. SAP presents Build as a suite spanning: - **Low-/no-code**: SAP Build Apps, SAP Build Process Automation, SAP Build Work Zone - **Pro-code & AI-assisted development**: SAP Build Code (and related SAP BTP dev tooling) - **Agent development**: Joule Studio within SAP Build (positioning has evolved toward "AI agents") SAP indicates outcomes such as faster delivery and reduced effort via prebuilt content, templates, and AI assistance. SAP's materials also emphasize governance and upgrade-safe extension patterns ("clean core alignment").

Target market and market positioning

Primary target: Existing SAP customers (ECC/S/4HANA, SuccessFactors, Ariba, etc.) adopting SAP BTP for extensions.
Secondary target: "Fusion teams" (IT + business) and citizen developers, though multiple observers and community comments indicate that complexity increases beyond simple workflows and may require IT/DevOps maturity.
Positioning: Enterprise low-code platform + process automation + digital workplace, with SAP-native integration and governance as distinguishing characteristics.

- **Primary target**: Existing SAP customers (ECC/S/4HANA, SuccessFactors, Ariba, etc.) adopting SAP BTP for extensions. - **Secondary target**: "Fusion teams" (IT + business) and citizen developers, though multiple observers and community comments indicate that complexity increases beyond simple workflows and may require IT/DevOps maturity. - **Positioning**: Enterprise low-code platform + process automation + digital workplace, with SAP-native integration and governance as distinguishing characteristics.

Get a comprehensive analysis of SAP Build including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →