I like that SAP Build is easy to use and speeds up development with minimal coding. I appreciate the speed at which applications are developed. I also like the availability of prebuilt templates and components, which makes getting started much easier and makes the app easy for users. The initial setup is simple and fast to integrate. It helps solve the problem of slow and complex applications, and after using SAP Build, we are more efficient and can complete tasks faster. Review collected by and hosted on G2.com.

Customization for more complex applications is an area they need to improve. Basic changes are easy, but more advanced tasks are harder. Review collected by and hosted on G2.com.

we are using SAP build for our workzone - move of our portal to SAP Build. we will be using build for our Workflow, Fiori apps, and other RPA tools and other build products Review collected by and hosted on G2.com.

We are going live with SAP Build in 2027. so cant say there is something I do not like. once we go-live we will have idea of use of use. thing I am worried is in SAPPHIRE, I came to know that workzone may be absolete. this is something I need to look Review collected by and hosted on G2.com.

I primarily use SAP Build for rapid prototyping and developing internal administrative tools. It excels at allowing me to quickly spin up side-by-side extensions and handle repetitive backend workflows and data synchronization. I love the balance of low-code speed with pro-code extensibility, as the native SAP integrations and drag-and-drop UI handle the boilerplate effortlessly. When compliance requires complex data routing, I can still drop in custom logic, which makes it flexible. The tight integration with SAP BTP is a massive time-saver, especially for pulling data from SAP backends or third-party APIs. The pre-built connectors and destination routing handle authentication and middlewares securely, which is crucial for compliance. The biggest value I see is the sheer development velocity without sacrificing security, as it handles the boilerplate UI and secure data routing out of the box, allowing my engineering team to focus on the core architecture and complex features. Review collected by and hosted on G2.com.

The debugging experience can sometimes feel like a black box compared to traditional development environments. Also, while the drag-and-drop UI is great for speed, customizing it beyond the standard templates can be frustratingly rigid when we need a highly specific user interface. The initial setup definitely has an enterprise learning curve. Configuring the BTP subaccounts, entitlements, and secure cloud connectors is not exactly plug-and-play. Review collected by and hosted on G2.com.

What I like most about SAP Build is its low-code approach that allows teams to quickly build enterprise applications without heavy development effort. The drag-and-drop interface, integration with SAP services, and built-in automation capabilities make it easy to prototype and deploy solutions faster. It significantly reduces development time while still allowing customization when needed, which is very useful for organizations already working within the SAP ecosystem. Review collected by and hosted on G2.com.

One downside of SAP Build is that customization can become limited when you try to implement more complex or highly specific business logic. In some cases, you still need additional development or workarounds outside the platform. The learning curve can also be slightly steep for new users who are not familiar with SAP products, and debugging or troubleshooting workflows could be more intuitive. Review collected by and hosted on G2.com.

What stands out the most is how SAP Build bridges the gap between business users and IT. Non-developers on our team were able to spin up basic workflow apps without writing a single line of code — something that would've taken weeks of back-and-forth with the dev team before. The integration with S/4HANA is fairly seamless out of the box, which saves a lot of the usual connector headache. Frequency of use has gone up noticeably because the drag-and-drop interface is approachable enough that business analysts actually want to use it, rather than submitting tickets and waiting. For a consultant, that shift in ownership is genuinely valuable on any implementation. Review collected by and hosted on G2.com.

The learning curve is gentler than traditional SAP development, but the moment you need to go beyond the pre-built components, things get complicated fast. Advanced customizations often push you back into needing a developer anyway, which partially defeats the low-code promise. Customer support documentation is still catching up — a lot of edge cases aren't covered well, and community forums are thin compared to more mature platforms. Ease of implementation is fine for simple use cases, but multi-system integrations can get messy and require deeper BTP knowledge than most business-side users have. It's promising, but not fully there yet for complex enterprise needs. Review collected by and hosted on G2.com.

From my perspective as a test engineer working with motor systems, the biggest advantage of SAP Build is how quickly 1 can put together small internal tools and workflows without having to wait for a developer. It lets me build forms, dashboards, and simple automations that make my daily testing work easier. I also appreciate how well it connects to the rest of our SAP environment - things like material data, equipment information, or production orders are all accessible without needing complicated setup.

Another strong point is visualization. It's quite useful for creating dashboards that show test results, statistics, and overall traceability in a clean way. Review collected by and hosted on G2.com.

SAP Build can feel slow at times, especially when working with larger datasets or more complicated screens.

Some of the "low-code" logic is also limiting there are situations where I would prefer more flexibility to implement custom logic that fits my testing workflows better. Integrations outside the SAP ecosystem (for example, with test benches or measurement equipment) usually require extra help from IT, which slows things down. The tool is also not as intuitive as it looks at first; it takes some time to understand how data models, flows, and Ul pieces work Review collected by and hosted on G2.com.

SAP saves me a lot of time because I can get everything in one place. With its AI features, it’s also very convenient for handling daily business tasks, as well as development and automation. Review collected by and hosted on G2.com.

Although it’s an amazing tool, I do feel that it offers limited flexibility for complex logic. Debugging can be cumbersome, and the performance-tuning options feel restricted compared to full-code solutions. Review collected by and hosted on G2.com.

In my first company, our CRM was backed by SAP. I did not like the UI as such but towards rhe end of 2019, there was complete revamp and new version did have good UI. But it always got the job done, we maximum times used it for bulk service ticket upload via excels to facilitate records and service visits. Review collected by and hosted on G2.com.

Old ui was not good and while bulk uploading, even if we enter everything as expected, some fields are always black not sure why. Though, UI problem was fixed end of 2019. Review collected by and hosted on G2.com.

What I love most about SAP Build is how it turns the "business user" into a creator, significantly improving ease of implementation. By removing the traditional IT bottleneck with intuitive, drag-and-drop tools, you can bypass the month-long wait for custom code. Instead, you can build functional apps and automate repetitive tasks in days, moving from a conceptual idea to a live, enterprise-grade tool with minimal friction.

This accessibility naturally leads to a high frequency of use, as teams begin to solve their own minor daily frustrations rather than just waiting for massive, high-priority projects. It is particularly effective for customer support teams, who can rapidly build custom dashboards or automate ticket routing to respond to client needs faster. Because it’s natively wired into your SAP data, you aren’t fighting complex APIs; you’re simply empowering your staff to innovate as a standard part of their workday. Review collected by and hosted on G2.com.

One major hurdle is the ease of integration with non-SAP systems. While it’s seamless within its own family, connecting to third-party tools often requires tedious manual configuration that feels anything but "low-code." When things break, the debugging tools are often too vague to be helpful, turning a "quick fix" into a frustrating scavenger hunt through the BTP.

Additionally, customer support documentation often lags behind the platform’s rapid updates, leaving you to rely on community forums for answers. While the frequency of use is high for simple tasks, the premium licensing costs are a tough pill to swallow. It’s a high-cost commitment that makes sense only if you’re already "all-in" on the SAP ecosystem, which can feel less like a flexible tool and more like an expensive constraint for smaller teams. Review collected by and hosted on G2.com.

Best thing about it is that it provides a unified low-code environment to create applications, design and automate workflows- tightly integrated with SAP systems. The drag-and-drop UI, prebuilt components and native connectors to SAP services (like S/4H and BTP) significantly reduce development effort and speeds up delivery. I mainly like how business users and developers can collaborate in the same platform helping to accelerate prototyping and process automation without high level coding Review collected by and hosted on G2.com.

Dislikes:

1. The learning curve can still be steep mainly for users without prior SAP BTP experience.

2. Many advanced customizations and debugging require technical knowledge which then again reduces the “citizen developer” simplicity in complex scenarios.

3. Performance and responsiveness of the design environment does occasionally lag

4. Licensing/Pricing is still a concern for smaller teams.

5. Documentation has been improving but still I have to look at fragmented docs across different SAP portals and comm posts. Review collected by and hosted on G2.com.