Number of Seats/Users: SAP Build offers discounts based on the number of users or seats. A higher volume typically leads to a better discount structure, especially for enterprise-level usage.

Commitment to a Long-Term Contract: Discounts are often provided to companies that commit to using the service for a longer period (e.g., 1-year or 3-year contracts). A longer commitment shows SAP Build that the company is serious and willing to invest in the platform long-term.

No Active Discounts: Companies that are not already receiving other active discounts may have a better chance of qualifying for additional discounts from SAP Build. SAP Build reserves discounts for new customers or those not currently under promotional pricing.

Volume or Usage Commitment: SAP Build offers discounts if you agree to a minimum amount of usage or transaction volume. This could be based on data storage, transactions, or other metrics tied to how much you will use the platform.

Enterprise-Level Negotiation: Companies that qualify as “enterprise” due to their size or complexity (e.g., having large teams, multiple departments, or geographical presence) may be eligible for additional discounts from SAP Build. Such companies are often in a position to negotiate for better pricing.

Early Renewal or Prepayment: SAP Build often offers discounts if you renew early or prepay for the entire contract period. This is a common approach to securing a lower price.

Here at Spendbase our internal data shows that SAP Build is generally seen as a strong, cost-effective low‑code platform, especially for teams already invested in the SAP ecosystem.

From what Spendbase clients share, the main strengths are:

• Ease of use and speed
• Drag-and-drop interface and “no-code” feel make it possible to build apps and automations fast.
• Prebuilt templates and a rich control library reduce build time and dev effort.

• Many clients mention using it daily for core work, which signals high adoption.

• Business impact

• Helps simplify workloads and automate repetitive tasks.
• Supports cross‑platform app development (desktop and mobile).

• Good fit for co-development across multiple teams, improving collaboration.

• Perceived value for money

• Clients frequently associate SAP Build with “value for money” and faster deployment, which is key for ROI.

At the same time, our internal feedback surfaces several friction points that matter for budgeting and adoption:

• Pricing and program limits
• Non‑SAP customers especially find pricing and thresholds confusing.
• There is uncertainty about when usage will exceed free or included tiers, which can create surprise costs.

• This is exactly where a structured discount and usage optimization strategy can save money.

• Product and experience gaps

• Occasional freezes, forced sign-outs, and cloud function errors.
• Confusing password reset experience.
• Challenges exporting apps to mobile platforms.
• Documentation and community support are perceived as weaker than ideal.
• Learning curve exists, particularly for non-technical end users.
• Change management for multi-team setups can be complex without clear governance.

From a Spendbase discount and optimization standpoint, our takeaway is:

• SAP Build is a good candidate for:
• Negotiating clearer pricing tiers and volume or commitment discounts.
• Actively monitoring usage to avoid crossing free/limited thresholds unintentionally.
• Structuring licenses and environments by team (dev vs business users) to reduce waste.

In short, SAP Build delivers strong functional value, but to keep the TCO in check, you want tight control over pricing structure, usage, and support expectations—areas where we typically help our clients save.