I recently tried SAP Build and what I like most is how quickly you can build apps and automate simple workflows using drag-and-drop features. It reduces a lot of manual coding and makes development faster and easier to understand. As someone who is still learning and exploring the platform, I found it very helpful for understanding how real business applications are structured and connected. The prebuilt components and SAP integration also save time and make the whole process more smooth and practical for quick prototyping. Review collected by and hosted on G2.com.

SAP Build when working on more complex logic, it can feel a bit limited compared to full coding. Some advanced customizations are not very straightforward, so extra time is needed to understand how to achieve them properly. Also, as a learner, the documentation and deeper features take time to explore, so the learning curve becomes slightly steep after the basic level. It works really well for simple apps and workflows, but for very advanced use cases, it still needs improvement in flexibility. Review collected by and hosted on G2.com.

What I like best about SAP Build is how quickly it helps turn a business process into something usable without needing a full development project. The most valuable part for me is SAP Build Process Automation—being able to create approval workflows with forms, business rules, email notifications, and task routing in a visual way is very practical. Review collected by and hosted on G2.com.

What I dislike about SAP Build is that it can feel less intuitive once you move beyond simple workflows. The drag-and-drop setup is helpful, but debugging failed automations or understanding error messages is not always straightforward, especially when integrating with S/4HANA, APIs, or destination services in SAP BTP. Some templates also need more customization than expected, so “low-code” can still require technical support. Better error guidance, clearer setup documentation, and more real-world examples would make the experience smoother. Review collected by and hosted on G2.com.

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.

SAP Build is trying to simplify software and application development to the level of key users with maintaining the possibility of coding and scripting at the same time. It tries to create an environment which helps you to do all tasks around application development, but it is not really a help for hard core developers. Review collected by and hosted on G2.com.

The missing tools and all possibilities that a developer is used to by standard IDEs like Eclipse and VS Code are completely missing. The web based surface is too much easing that it cannot even do basic things that the older WebIDE could do. Maybe it evolved in the meanwhile but seeing SAP refering to Eclipse and VS Code as the tools for development, it remains a nice try to enable PowerUsers with the illusion of being a developer. 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.

The things I like most about SAP Build are its low-code and no-code features. They help me build solutions for problems in a time-efficient way, and because of the low-code/no-code approach, even complex tasks become easier to handle. Integrations with SAP systems are also straightforward with this.

On top of that, the UI/UX feels easier to work with thanks to the pre-built templates. With the AI assistance, performance and efficiency improve as well. When I compare the pricing, I feel the returns are good. Support is also good, especially for onboarding new organizations. Review collected by and hosted on G2.com.

Since this is a low-code/no-code platform, more complex problems can be difficult to solve. When I’m about to implement complicated features, it can feel a bit uncomfortable, and the learning curve is also somewhat difficult for a fresher. Review collected by and hosted on G2.com.

I like how SAP Build helps with reusability, which allows me to focus more on business logic while handling the UI through the table component. The drag and drop approach makes it easy to build schemes and workloads, especially when creating internal tools or prototypes quickly. I find the integration with SAP services really helpful as it saves a lot of effort when working with the SAP ecosystem, eliminating the need to build from scratch. This feature is time-saving for development and demos. I think SAP Build is a good option for teams looking to speed up development without a heavy investment in frontend components. It works best for enterprise usage, particularly for large-scale delivery and integration use cases. Also, the initial setup and development process is quite easy. Review collected by and hosted on G2.com.

There are some limitations when you need to customize more complex logic. As a developer, sometimes you want more control over behavior and UI, which can be slightly restrictive. Debugging could also be improved to make issue tracking easier. It works for me, but it could be improved in terms of complexities and debugging. Review collected by and hosted on G2.com.

I like how SAP Build lets me work on any idea or task quickly and create a prototype. The drag-and-drop UIs and prebuilt components make the setup time very short. It helps in creating simple dashboards and utilities quickly, reducing the time and effort required. The platform also reduces the need for dedicated frontend or backend professionals. The integration of components directly to the data store without needing code creates a lot of value, and it contains everything needed. The documentation and guides are good, covering everything needed for the setup. Review collected by and hosted on G2.com.

Something can be done around debugging, like integrating an AI chatbot inside the prototype workflow that has knowledge about it and can help to debug, help in making use cases. Review collected by and hosted on G2.com.

I like SAP Build's good diagnostic tools, which are essential for developing personalized health platforms at scale. Extending apps and healthcare solutions to meet unique needs is really beneficial. I find the patient engagement features, like care portals and booking systems, to be particularly effective. The software offers good remote access to medical records, which is crucial. I also appreciate the integration with health data services that provides a quick overview of patient data and medication history. The automation for tasks such as insurance claims is very useful, especially since we recently merged with a claims company. Additionally, the initial setup of SAP Build was quick and easy. Review collected by and hosted on G2.com.

There could be compliance challenges and workflow configuration limitations. Specifically, with more than 2,000 beds reporting that the rules engine and workflow configuration within SAP Build are not as robust as needed. Compliance can also be a challenge with low-code tools since they require rigorous validation. Review collected by and hosted on G2.com.

I really like SAP Build for its fast development with low-code tools. It makes delivery faster and more flexible. Also, the initial setup was relatively straightforward. Review collected by and hosted on G2.com.

There’s a learning curve when it comes to the advanced features. Basic usage is straightforward, but mastering the more advanced capabilities—such as integrations, automation, or extensions with SAP S/4HANA—can still be quite complex and often requires SAP-specific knowledge. Review collected by and hosted on G2.com.