What I like most about SAP Build is how well it supports rapid application development while remaining tightly integrated with the SAP ecosystem. Its low-code and no-code approach makes it easier for both developers and functional consultants to design, build, and deploy applications without spending too much time on boilerplate code. As a result, delivery is accelerated and teams can focus more on business logic instead of getting bogged down in technical complexity.

Another key strength is the seamless integration with SAP systems such as S/4HANA, SAP BTP, and other SAP services. The availability of prebuilt connectors, APIs, and templates reduces the overall integration effort and helps maintain data consistency across enterprise systems. In addition, SAP Build Apps and SAP Build Process Automation enable organizations to automate workflows and repetitive tasks, which can improve operational efficiency.

The user-friendly interface, drag-and-drop components, and guided development experience also make SAP Build approachable for non-technical users. This helps business users and IT teams collaborate more smoothly, since business requirements can be translated into working applications quickly. Built-in governance, security, and compliance aligned with SAP standards are also important advantages, especially in enterprise environments.

Overall, SAP Build stands out as a strong platform for innovation, rapid prototyping, and scalable enterprise application development within SAP landscapes. Review collected by and hosted on G2.com.

SAP Build can have a learning curve, especially for users new to SAP BTP and its ecosystem. Customization options are sometimes limited for complex or highly specialized use cases, making advanced scenarios harder to implement. Licensing and overall cost can also be high for small teams or organizations. Additionally, debugging and error messages are not always clear, which can slow down troubleshooting and development. Review collected by and hosted on G2.com.

SAP Build offers an enhanced level of security by ensuring that users can only access the Fiori tiles assigned to them, without granting access to the backend system. I find this security feature particularly valuable, as in the backend system, users would need to enter transaction codes to open any business application. With SAP Build, however, users can simply view the Fiori tiles on their dashboard, making access more controlled and secure.

There No code approach is really useful. Review collected by and hosted on G2.com.

The support provided by SAP Consultants for any issue is quite slow, and at times I have to wait more than three to four weeks just to receive a response. Additionally, the documentation for SAP Build, when using SAP S/4HANA Public Cloud as the backend system, contains inaccuracies, which makes the experience even worse. Review collected by and hosted on G2.com.

What I like most about SAP Build is that it supports rapid application development with minimal coding, which makes it accessible to both developers and business users. The seamless integration with SAP systems and services also makes it easier to build enterprise-ready solutions without a lot of extra effort. I find the drag-and-drop interface especially helpful because it speeds up development while still offering the flexibility needed for more complex use cases. Overall, SAP Build helps me turn ideas into functional apps much faster. Review collected by and hosted on G2.com.

One drawback of SAP Build is that it can feel limiting for highly complex or heavily customized use cases when compared with full-code development. Performance tuning and more advanced configurations can also be less transparent, which makes it harder to understand what’s happening under the hood. The learning curve may be steep as well, especially when you need to integrate with multiple SAP services. In addition, licensing and overall cost considerations can be a concern for smaller teams. Review collected by and hosted on G2.com.

What I like most is how quickly I can build and deploy applications without needing to write complex backend code. The visual development interface makes it easy to design screens, connect data, and test workflows in one place. It also integrates well with SAP systems, which saves a lot of time when working with existing enterprise data and processes. Instead of building everything from scratch, I can extend what’s already there. Another plus is that it combines app development, process automation, and workspace features in a single platform. That makes it easier to create complete business solutions rather than disconnected tools. Review collected by and hosted on G2.com.

The learning curve can be a bit steep at first, especially when working with advanced logic or integrations. Some configurations aren’t always intuitive, and debugging can take time. Customization can also feel limited in certain scenarios compared to full-code development. If you need very specific UI behavior or complex backend logic, it may require workarounds. Performance optimization and handling large-scale use cases can sometimes be challenging without deeper technical adjustments. Review collected by and hosted on G2.com.

What I like best about SAP Build is how easy it makes application development and process automation, even for people who don’t have deep coding expertise. The low-code/no-code approach really helps turn ideas into working solutions quickly, which saves a lot of time and effort.

The most helpful aspect of SAP Build is how well it integrates with other SAP systems. This makes it much easier to build apps, automate workflows, and design business processes without worrying too much about compatibility or complex setups.

One of the biggest upsides of using SAP Build is the boost in productivity. Teams can collaborate better, deliver solutions faster, and adapt to changing business needs more easily. It also reduces dependency on heavy custom development, making it a practical and efficient choice for many organizations. Review collected by and hosted on G2.com.

What I dislike about SAP Build is that it can feel a bit overwhelming at first, especially for new users. The learning curve can be steep, and it takes some time to fully understand all the features and how they fit together.

The least helpful aspect is the limited flexibility in certain scenarios. For more complex or highly customized requirements, SAP Build can feel restrictive compared to traditional development approaches.

One of the main downsides of using SAP Build is performance and cost considerations. As applications grow in complexity, performance tuning options can be limited, and licensing costs may be higher for smaller teams or organizations. Additionally, debugging and troubleshooting can sometimes be less transparent than in full-code environments. Review collected by and hosted on G2.com.

I use SAP Build for building my web applications, and I find it saves a lot of time, as it's quicker to integrate. What I like most is the ease of use and effectiveness, particularly because of the visual aspect. It's much easier to see and build something you can visually observe. The live preview feature is good, as it shows updates in real-time, making my updates come to life. The initial setup was also very easy, which was a nice surprise. Review collected by and hosted on G2.com.

I guess it's alright for small tasks, but struggles when building larger systems. The integrations between multiple different systems. Review collected by and hosted on G2.com.

What I like most about SAP Build is its low-code simplicity: it enables rapid app development, integrates seamlessly with SAP, and helps me automate workflows efficiently. Review collected by and hosted on G2.com.

One drawback of SAP Build is that advanced customizations can be limiting compared to traditional development platforms, and complex scenarios may still require technical expertise. Review collected by and hosted on G2.com.

SAP Build is extremely helpful for rapidly developing internal prototypes and workflow mock-ups without the need for developer involvement. From an EUDR perspective, it enables us to visualize incremental process improvements, outline internal approval workflows, and experiment with how specific compliance steps might appear before they are actually implemented in SAP or other platforms. The intuitive drag-and-drop interface simplifies the creation of basic dashboards and forms, making it easier for teams to track data movement and understand the flow of due-diligence tasks. This not only saves time but also enhances communication between business users and IT, particularly when we need to confirm new requirements for EUDR processes. Review collected by and hosted on G2.com.

Some components remain limited and often necessitate workarounds when constructing more complex scenarios. Integration with other SAP modules is not always smooth, so projects that go beyond basic prototypes typically still need IT support. Performance can fluctuate based on the project's size, and some features could use greater flexibility or more customization options. While it is a robust tool for rapid iterations, it does not serve as a substitute for fully developed SAP applications. Review collected by and hosted on G2.com.

SAP build is a great tool for creating applications in a very short time frame. The integration of several key automated systems and Ai allows users to create new apps with very little to no coding at all and it allows high performance with minimal input from the users. Review collected by and hosted on G2.com.

The primary concern I have with SAP is that it is best utilized within a SAP heavy environment, meaning there are potential issues with wider integration of the system depending on the users environment. Additionally, the software is expensive, limited in the overall customization of the apps themselves, and there is a steep learning curve, not helped by in my opinion on very clunky user interface. Review collected by and hosted on G2.com.

I think that using SAP Build is pretty easy from an SAP standpoint. It is great for extending and building upon in the ecosystem. It can be pretty easy to implement if you're familiar with BTP. Review collected by and hosted on G2.com.

The extensibility and ease of use outside the SAP Ecosystem. If you are not familiar with BTP the learning curve can be steep. So that is what can make it challenging. Review collected by and hosted on G2.com.