SAP Build Reviews & Product Details

I use SAP Build daily as a CAP developer, mostly through Business Application Studio. The dev spaces come ready with the CDS tooling, so I can start a new CAP project in minutes without setting anything up locally. The CDS language support and the Fiori elements generators save a lot of time, and building and deploying the MTA to Cloud Foundry from the same place keeps the whole workflow in one to Review collected by and hosted on G2.com.

Dev spaces stop after some inactivity and take a while to start again, which breaks focus. The browser IDE can also feel slower than working locally in VS Code. The documentation is spread across SAP Help, the CAP docs and community blogs, so finding the right answer sometimes takes longer than it should. Entitlements and service setup on BTP can be confusing for newcomers. Review collected by and hosted on G2.com.

What I like most about SAP Build is how it brings application development and process automation together in one environment. The low-code approach makes building applications more accessible, while the visual interface helps organize workflows and understand how different components interact.

I particularly like the integration between applications and automation tools, as it makes it easier to connect different processes without developing everything from scratch. The platform offers useful features for improving productivity, although more complex projects still require technical knowledge.

In terms of performance, my experience has generally been positive, especially when working with smaller applications and automation workflows. The initial learning curve can be challenging, but the available documentation helps with getting started.

From a productivity perspective, the ability to reuse components and automate repetitive tasks can save development time. Overall, SAP Build offers a practical combination of application development and automation, with interesting possibilities for further AI-assisted functionality. Review collected by and hosted on G2.com.

One thing I think SAP Build could improve is its learning curve, especially when moving beyond basic applications and automation workflows. While the visual interface is useful, configuring more complex processes and integrations can become confusing, particularly for someone who is still getting familiar with the platform.

Another concern is pricing. Depending on the licensing model and the size of the project, the overall cost could be a challenge for smaller organizations or independent developers. More transparent pricing and accessible options would make the platform more attractive.

I also think the documentation could benefit from more practical, step-by-step examples covering real-world applications and automation scenarios. Some of the more advanced features, including AI-assisted functionality, could be explained more clearly to help users understand how to get the most out of them. Review collected by and hosted on G2.com.

What I like most about SAP Build is how seamlessly it combines low-code/no-code development with strong enterprise capabilities. It enables our team to quickly prototype and deploy applications, which has significantly improved our overall productivity. Review collected by and hosted on G2.com.

Honestly, there is very little to dislike since the platform performs exceptionally well. If anything, the initial learning curve for advanced features can be slightly steep, but the comprehensive documentation and overall value easily make up for it. Review collected by and hosted on G2.com.

I like how quickly I can go from an idea to a working solution. The visual workflow designer and drag-and-drop app builder make it easy to build and adjust processes without writing much code. I can map a process with the business team and see it working the same day, so we can get feedback early, and I can create a simple data entry app in a few hours. Native connections to SAP systems remove most integration work and let me focus on the process. Templates give me a solid starting point for common processes, and Joule helps me draft logic or fix steps quickly when I’m stuck. These features help me deliver more solutions with less effort and make automation accessible beyond developers. I also value turning manual, paper-based steps into faster, trackable digital workflows, reducing repetitive data entry and errors, and giving non-technical staff an easy way to view and update SAP data. SAP Build fit into our existing SAP landscape, and getting started was smoother than I expected: activating it and assigning roles took a few hours, and the Lobby made it easy to find templates and start our first project. I’d confidently recommend it to colleagues in the SAP space. Review collected by and hosted on G2.com.

I find debugging tricky because the logs aren’t always detailed enough to show why a workflow or bot failed, and tracking down the exact cause can take time. Bots can be slow with large Excel files or many records. The low-code tools work well for standard cases, but advanced customization quickly requires pro-code skills. Pricing and licensing are hard to understand, especially when I’m estimating costs for new projects, and I’d like more version control and testing features to manage changes safely across environments. Connecting to backend systems also took extra time: configuring the Cloud Connector, destinations, and authentication needed help from our Basis team, and setting up the Desktop Agent required IT approvals. Review collected by and hosted on G2.com.

I find SAP Build easy to use. The drag-and-drop tools and templates help me build things quickly, and it connects well with our SAP system. I value having workflows, decision tables, and bots in one place so I can automate approvals quickly and business users can update rules without IT. SAP Build Apps lets me build and prototype apps fast while connecting to SAP backends, and Joule speeds up development by generating code and logic from simple prompts. The process is faster, data goes directly into SAP, and we don’t always need to wait for IT. Having apps, workflows, and automation in one platform is convenient. The integration with S/4HANA and BTP saves time, and having workflows and bots together is much easier to manage with less maintenance across multiple tools. Once the basic setup was done, building our first app or workflow went quickly. Review collected by and hosted on G2.com.

Complex logic still needs developers, and SAP Build’s error messages aren’t always clear. Licensing is confusing, and I’d like more real-life examples and simple guides for beginners, including end-to-end sample projects and short walkthroughs. Connecting to our on-premise systems took some trial and error because of authentication and network settings, and assigning roles and permissions needed some care. Rebuilding older workflows during the switch also took some effort. Review collected by and hosted on G2.com.

I like how easy SAP Build is to use. With the drag-and-drop tools and ready-made templates, I can quickly create forms, simple apps, and workflows without much coding. The workflow automation sends approvals and tasks to the right people, and apps can update data directly in SAP, which saves our team manual work and time. I also like how well it connects with our SAP systems, and how it works with SAP Build Work Zone, Microsoft Teams, and Outlook so people can open apps and act on requests quickly. The built-in AI features help me get started faster, and the templates and guided tutorials made it easy to build my first small app and workflow within a few days. Review collected by and hosted on G2.com.

SAP Build is easy for simple apps and workflows, but it gets harder when I have more complex requirements. For advanced logic or custom designs, I still need help from developers. Sometimes performance is a bit slow, and error messages are not always clear, so finding the problem takes time. I also find the licensing and pricing confusing. The basic tutorials and learning journeys mostly cover simple examples, and it’s hard to find step-by-step guidance for real business cases. I’d like more real-life examples, short videos, and clear troubleshooting guides, with updated documentation in one place. Review collected by and hosted on G2.com.

I find SAP Build quite intuitive. It helps me accelerate the time to market for applications and workflows. I appreciate the simplicity of communicating with the SAP ecosystem: having an integrated environment on the BTP helps me not worry about the communication layer or authorizations. The initial setup was also quite simple. Review collected by and hosted on G2.com.

I find SAP Build quite intuitive, but the automation is very unstable: the Process Automation interface often freezes or is extremely slow. 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.

I appreciate the central entry point and the unified UI/UX for BTP-related developments. With BAS, I actively develop Fiori applications and perform on-premise deployments. The setup was very easy: authorize services, set up subscriptions, done. Review collected by and hosted on G2.com.

What bothers me the most is that I need permissions for each subscription and have to log in to SAP Build again when I grant permissions for the services. However, this results from the tool's architecture. Review collected by and hosted on G2.com.

I find SAP Build good and flexible. I like that I can build and adopt applications easily, and create applications and workflows with less code. The setup is simple in the cockpit when I have the needed subscription, access, and instance. Review collected by and hosted on G2.com.

Sometimes SAP Build loads slowly. After I build and deploy the code, it takes a lot of time to open. I also checked my network speed. Review collected by and hosted on G2.com.