Verified User
G
Verified User
Small-Business (50 or fewer emp.)
"Strategic Tool for Seamless Intranet Access & Automation"
3.5/5
What do you like best about SAP Build?

I like SAP Build for its ease of use and process automation capabilities. It allows end user access to our intranet SAP system without needing a VPN, which helps us scale the app across the organization. It's a strategic tool from SAP's perspective, combining all the build capabilities for extension. This makes it our go-to tool for our developers. We are in the process of automating our audit documentation, which further highlights its utility. Review collected by and hosted on G2.com.

What do you dislike about SAP Build?

I think there's too much repackaging like different instance types. The licensing model confuses the customers. Review collected by and hosted on G2.com.

Ravindra N.
RN
Ravindra N.
SDET - 2
Oil & Energy
Enterprise (> 1000 emp.)
"Rapid Test Automation & SAP Integration, But Debugging and Collaboration Need Work"
4.5/5
What do you like best about SAP Build?

Rapid test tooling without waiting on backend teams. With Build Apps I can drag-drop a small UI, bind it to an OData/REST service, and ship a functional “test harness” in an afternoon. Our “Return Order Generator” for QA came from this, zero boilerplate, just data variables and logic canvas.

Process Automation that stitches end-to-end flows. Timers, webhooks, approvals, and RPA steps let me seed data, kick off background jobs, and verify statuses before CI starts UI runs.

Reusable artifacts & clean promotion. Pages, data models, and automations are reusable across projects, and promoting between dev -> test -> prod via transports keeps things consistent.

Governance that doesn’t get in my way. Role-based access, change history, and environment-scoped credentials make audits easy while still letting me iterate quickly.

Observability when something breaks. Run logs, input/output traces, and retry queues make it straightforward to pinpoint flaky integrations during test setup.

Tight fit with SAP ecosystems. OData bindings and BTP integration reduce glue code, which means fewer failure points in test scaffolding. Review collected by and hosted on G2.com.

What do you dislike about SAP Build?

Debugging complex flows can feel opaque. Step-through is limited, errors sometimes read like “node X failed” without enough context.

Versioning & reviews aren’t as natural as Git. Collaborating and doing code-style PRs is clunkier in a low-code canvas.

Custom code escape hatches exist, but feel bolted on. Great for 90% cases; the last 10% needs more ergonomic extensibility. Review collected by and hosted on G2.com.

Konjengbam  M.
KM
Konjengbam M.
BDR
Financial Services
Mid-Market (51-1000 emp.)
"Empowers No-Code App Building, But Watch Out for Connector Costs"
4.5/5
What do you like best about SAP Build?

The best part about this platform is the ability to build an app without much or no knowledge of coding. It enables individuals to implement their smart ideas into a running application. This greatly improves the quality of work and individuals. Like all SAP products , its robust SAP ecosystem promotes the overall functionality and security of this platform. The integration issues faced from 3rd party platform is solved with its vast resources. The realization of objectives is faster and productivity increases by using this platform. The automation created through the application created by this platform allows optimum allocation of resources for better efficiency and productivity. The platform allows monitoring of the workflow very easy which is another plus point of this platform. Review collected by and hosted on G2.com.

What do you dislike about SAP Build?

The cost of building powerful application comes with a cost. Though I love most part of this platform, I felt that the cost of building an application may spiral out of the budget with its connector costs. Frankly speaking the user also needs a clear thought out process to build an application. The user should develop a knowledge of each potential integration platform and its applications to enable users to be more effective in using this platform. Since the platform is mostly focused and build around SAP ecosystem, SAP needs to do a continuous update to compete equally with various other individual platform which does its best in their own individual field. Review collected by and hosted on G2.com.

MB
Mousumi B.
Enterprise (> 1000 emp.)
"Strong Low-Code Layer for BTP & Datasphere, with Some Integration Concerns"
3.5/5
What do you like best about SAP Build?

It’s a low-code/no-code development layer that can be integrated with BTP, and it also integrates with Datasphere. From an AI and data landscape perspective, it’s a really nice capability to have. Review collected by and hosted on G2.com.

What do you dislike about SAP Build?

I don’t have enough experience yet to highlight anything I dislike. That said, the integration with BTP and Datasphere concerns me a bit. Cost is a factor too. Review collected by and hosted on G2.com.

Harsh K.
HK
Harsh K.
Platform Engineer II
Enterprise (> 1000 emp.)
"Low-Code SAP Build That Speeds Development and Integrates Seamlessly"
4/5
What do you like best about SAP Build?

So i like SAP build for its low code approach and seamless integration with SAP ecosystem.It enables faster app development, improves collaboration, and reduces dependency on heavy custom coding. Review collected by and hosted on G2.com.

What do you dislike about SAP Build?

While SAP Build is powerful, but first the learning curve will be steep for new users. Some advanced customizations feel limited compared to full-code development, and performance can vary with complex workflows. Clearer documentation and more flexibility would help improve the experience. Review collected by and hosted on G2.com.

Verified User in Human Resources
UH
Verified User in Human Resources
Enterprise (> 1000 emp.)
"Fast Low-Code SAP App Building"
3.5/5
What do you like best about SAP Build?

The low-code approach makes development more accessible. It integrates well with the SAP ecosystem and helps speed up the creation of simple apps. The UI components and templates are solid, making it easier to get started and build quickly. Review collected by and hosted on G2.com.

What do you dislike about SAP Build?

Limited flexibility for more complex use cases. Performance can feel slow at times, and debugging isn’t very intuitive. The documentation can also be unclear or incomplete, which makes it harder to troubleshoot issues. On top of that, licensing and pricing can be confusing to understand. Review collected by and hosted on G2.com.

Adeeshwar I.
AI
Adeeshwar I.
Senior Tableau Developer
Mid-Market (51-1000 emp.)
"Fast Low-Code Prototyping with Strong Automation and Smooth SAP Integration"
4.5/5
What do you like best about SAP Build?

Fast development and rapid prototyping, with an easy-to-use low-code/no-code approach. It has strong automation capabilities and integrates well with SAP system. The user interface is also good, which makes the overall experience smoother. Review collected by and hosted on G2.com.

What do you dislike about SAP Build?

SAP Build can struggle when the requirements involve complex logic or true enterprise-scale needs. I’ve also faced challenges integrating it with non-SAP systems. On top of that, there are issues with bugs, documentation quality, and updates. If we need deeper customisations, it becomes difficult compared to doing full coding. Review collected by and hosted on G2.com.

Verified User in Consumer Goods
CC
Verified User in Consumer Goods
Small-Business (50 or fewer emp.)
"Great No-Code Workflows, but Integrations and Custom Flows Need Work"
3/5
What do you like best about SAP Build?

I like the no code approach and workflow style development. Adding scenarios and implementing flows via drag and drop. I also appreciate the UI generation and connectivity selection. Review collected by and hosted on G2.com.

What do you dislike about SAP Build?

Its hard to connect to existing systems and also the custom flows are hard to implement. We don't use it much since it cannot support much of the custom flows. Its like we need to hack our way around workflow to implement it so in the end custom development is the way. Review collected by and hosted on G2.com.

Anthony P.
AP
Anthony P.
Finance Manager
Small-Business (50 or fewer emp.)
"Lots of training available on the web!"
1.5/5
What do you like best about SAP Build?

It's a big name brand trusted by big corporate clients of ours. So we have reassurance of it.

We have been using over 6 years now.

It seems very secure with 2FA and the forget password is easy to use. Review collected by and hosted on G2.com.

What do you dislike about SAP Build?

It's not user friendly nor intuitive at all.

Also when starting on work. There isn't a save "draft" option. Meaning in the middle of work. You could potentially lose work due to the Cloud based. This can be frustrating and stressful. Review collected by and hosted on G2.com.

Hirdesh P.
HP
Hirdesh P.
Mid-Market (51-1000 emp.)
"Good Low-Code Platform for Business and IT Collaboration"
3.5/5
What do you like best about SAP Build?

What I appreciate most about SAP Build is its ability to accelerate application development with minimal coding required. It empowers both technical and business users to create applications, automate processes, and design workflows without the need to start from the ground up. This capability greatly shortens development timelines and enables teams to adapt swiftly to evolving business demands.

Another significant benefit is its seamless integration with SAP systems and SAP Business Technology Platform (BTP). This integration facilitates the extension of existing SAP solutions in a secure and controlled manner, ensuring alignment with standard SAP architecture. In summary, SAP Build effectively connects business requirements with IT delivery. Review collected by and hosted on G2.com.

What do you dislike about SAP Build?

One of the primary limitations of SAP Build is its flexibility. Although it is effective for simple to moderately complex use cases, it may seem limiting for advanced scenarios that demand extensive customization or intricate logic. As applications expand, maintaining performance and design consistency can become increasingly difficult. Additionally, there is a learning curve for users unfamiliar with low-code concepts, and licensing costs could pose a challenge for smaller teams or projects. Review collected by and hosted on G2.com.