SAP Build Reviews & Product Details

Honestly, what I like best is how everything is connected under one roof. Like, I'm not jumping between five different tools ,I can build an app in Build Apps, hook it into a workflow in Process Automation, and surface it in Work Zone, all within the same ecosystem. That tight integration with SAP backend systems is something you really can't replicate easily outside of SAP.

But if I had to pick one thing it's Joule Studio. The fact that you can build actual AI agents, not just simple bots, is a big deal. We built an operator scheduling agent and an adaptive line scheduling agent, and the way it reasons through constraints and adapts and that's not something I expected from a low-code platform honestly.

For a professional developer, it also doesn't feel limiting. Build Code gives you enough room to write real logic when you need to, and the AI assistance genuinely speeds things up. It's not just autocomplete, it understands SAP context which saves a lot of back and forth with documentation.

So yeah the integration, the AI agent capability through Joule, and the fact that it scales from simple drag-and-drop to actual serious development. That combination is what keeps me using it. Review collected by and hosted on G2.com.

Joule Studio is exciting but it still feels a bit early. Some features are there but not fully mature yet, and you do hit walls occasionally where you're like ,okay this should be possible but I can't figure out how to do it right now. Licensing and pricing can also get complicated when you start combining multiple Build components. It's not always clear what's included and what's an add-on.he learning curve is steeper than they make it look in the marketing. Like, the drag-and-drop stuff is fine, but once you get into anything complex,custom logic, integrations, building agents in Joule Studio myou really need to dig into documentation and SAP community forums a lot. It's not as intuitive as you'd hope.

The performance can also be a bit sluggish at times, especially in Build Apps when your project starts getting larger. Nothing that's a dealbreaker, but you notice it. Review collected by and hosted on G2.com.

I like most about SAP Build is how it combines low-code speed with pro-code extensibility.

I have worked on React and UI5 both however, working with UI5 on BTP, it lets me build applications quickly, integrate with services and workflows, and still add custom logic when needed.

Overall, it helps reduce development time while keeping the solution enterprise-ready and aligned with Fiori UX standards.

Also it's UI is cleaner and more responsive. It gives direct drag and drop feature many places which makes user's job very easy while giving response through UI. Review collected by and hosted on G2.com.

Myself from starting of my career I am using this. But in some case it lags a bit.

I have found slightly limiting in SAP Build is the reduced flexibility for highly complex or custom logic compared to pro-code development.

In scenarios where deep debugging, performance tuning, or advanced UI behavior is required, I still prefer using SAP UI5. However, for rapid development and business-driven applications, SAP Build is extremely effective and significantly accelerates delivery. 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.

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.

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.