In 2026, BTP ships with every SAP bundle. RISE with SAP includes it as credits. GROW with SAP depends on it for clean core extensions. The result: every CIO planning an S/4HANA project sits through a BTP presentation without necessarily understanding what they are buying or what they will actually consume. This guide explains what BTP concretely is, the five components mid-market companies genuinely use, and what you will pay depending on your profile.
What SAP BTP Is in 2026 (and What It Is Not)
The Common Confusion with S/4HANA
BTP is not S/4HANA. That is the most widespread misconception. S/4HANA is your core ERP (financial data, procurement processes, logistics). BTP is the platform layer that connects to that ERP to integrate third-party systems, extend processes without touching the core, analyse data, and run AI workloads.
The confusion stems from how tightly the two are bundled commercially. A RISE with SAP contract includes BTP credits. A GROW with SAP contract mandates BTP for clean core extensions. SAP often presents both together, as if BTP were automatically necessary the moment you run S/4HANA. That is not wrong, but the intensity of use varies enormously: you can run a perfectly operational S/4HANA with minimal BTP usage, or you can allocate 30 to 40 percent of your annual SAP budget to it.
SAP positions BTP as “the enterprise digital transformation platform,” but in practice for mid-market companies (500 to 5,000 employees), BTP is primarily an integration and extension tool — not a transformation programme.
The Four BTP Service Families
SAP BTP organises its services into four broad families (Redress Compliance, 2026):
| Family | Primary Use | Key Services |
|---|---|---|
| Integration | Connect S/4HANA to third-party SaaS | SAP Integration Suite |
| Extension | Build apps and workflows | SAP Build (Apps, Process Automation, Work Zone) |
| Data & Analytics | Governance, modelling, reporting | SAP Datasphere, SAP Analytics Cloud, HANA Cloud |
| AI & Automation | Generative AI, agents, automation | SAP AI Core, Joule |
You do not need to activate all four families. Most mid-market companies starting an S/4HANA project begin with Integration Suite and only activate additional families for specific requirements. In 2026, over 80 BTP services are eligible for CPEA consumption (SAP Licensing Experts, 2026), but a standard mid-market deployment typically uses three to five of them.
The 5 Components CIOs Actually Use
SAP Integration Suite: Connecting S/4HANA to Third-Party SaaS
This is the most widely deployed BTP component in practice. Integration Suite is the successor to SAP Cloud Platform Integration (CPI), itself the successor to SAP HCI. It moves data between S/4HANA and any third-party system via iFlows (configurable integration flows) and managed APIs.
Why CIOs choose it: the native integration between Integration Suite and S/4HANA events (Business Events) is difficult to replicate with a generic iPaaS. For a mid-market manufacturer whose WMS needs real-time production orders from S/4HANA, this native event-driven integration delivers genuine value. One documented analysis compared Integration Suite at $85,000/year within a $180,000 annual BTP engagement against a Boomi alternative at $48,000/year for the same company. Integration Suite was chosen for its native event capabilities that Boomi could not cover without custom development (Automation Atlas, 2026).
Indicative pricing: $2,500/tenant/month on the base plan (5 million messages included), $5,000/tenant/month on the premium plan (15 million messages). These are pre-CPEA negotiation figures (Atonement Licensing, 2026).
SAP Build Apps (No-Code/Low-Code)
SAP Build groups three distinct tools that are frequently conflated in commercial presentations:
- SAP Build Apps: creation of web and mobile applications without code, connected to S/4HANA and BTP (formerly AppGyver, acquired by SAP in 2022).
- SAP Build Process Automation: automation of business workflows and repetitive tasks (RPA + workflow management).
- SAP Build Work Zone: a collaborative portal that consolidates apps, tasks, and content in a unified launchpad interface.
All three are marketed under the “Build Suite” label but purchased separately. Conflating them on a quote is a common source of pricing errors.
Typical mid-market use case: a finance team wanting a budget approval process connected to S/4HANA without custom ABAP development. SAP Build Process Automation is often faster to deploy than traditional development for this type of structured workflow.
Indicative pricing: Build Apps at $15/user/month (citizen developer) or $30/user/month (professional). Build Code (for developers): $59 to $89/developer/month (Atonement Licensing, 2026).
SAP Analytics Cloud vs SAP Datasphere
These two products serve different purposes and are often incorrectly presented as a single offering:
- SAP Analytics Cloud (SAC): a BI and planning tool, the presentation and analysis layer for business users. It progressively replaces SAP BW/4HANA for reporting.
- SAP Datasphere: a data governance and virtualisation layer, the successor to SAP Data Warehouse Cloud. It connects heterogeneous sources (S/4HANA, Salesforce, third-party data lakes) into a shared semantic layer.
SAC without Datasphere is often sufficient for a mid-market company doing primarily S/4HANA-based reporting. Datasphere becomes relevant when you need to consolidate multiple data sources with fine-grained governance.
Indicative pricing: SAC between $28 and $108/user/month depending on activated modules (BI, planning, predictive) (Atonement Licensing, 2026).
SAP CAP: For Clean Core Custom Development
The SAP Cloud Application Programming Model (CAP) is SAP’s official framework (Node.js or Java) for building extensions on BTP that comply with the “clean core” strategy. The principle: any custom logic previously coded in ABAP inside the S/4HANA core must be externalised into an autonomous BTP extension, built with CAP and connected to the core via official APIs published in the SAP Business Accelerator Hub.
Why this matters: a CAP extension on BTP survives S/4HANA upgrades without retesting and revalidation. A direct modification to the ABAP core creates technical debt that burdens every migration. SAP formalised the clean core strategy in 2023 and reinforced it at SAP Sapphire 2026 with an official certification programme for BTP extensions (SAP Community).
This decoupling logic fits within the broader trend toward composable architectures analysed in our guide to monolithic vs. microservices vs. composable ERP architecture.
Who uses it: primarily SAP developer teams (former ABAP developers transitioning to cloud, or Node.js/Java profiles). This is not a citizen developer tool.
SAP Work Zone: Unified Collaborative Portal
SAP Work Zone (formerly SAP Launchpad Service) consolidates all SAP and non-SAP applications into a unified interface. End users access their S/4HANA tasks, SAP Build applications, active workflows, and content within a single portal.
Practical usage: for a mid-market company with a single central ERP and a dozen key SAP users, Work Zone adds little differential value. It becomes relevant from 100+ active users with access to multiple different BTP applications.
When BTP Is Essential, When It Is Overhead
The 3 Scenarios Where BTP Becomes Unavoidable
1. Event-driven integration between S/4HANA and critical SaaS. If your Order-to-Cash process or logistics flows require real-time integration between S/4HANA and third-party tools (WMS, CRM, e-commerce), and you need centralised monitoring of those flows, Integration Suite is hard to compete with on native SAP ground.
2. Clean core extensions replacing ABAP development. If you have a migration roadmap to S/4HANA Cloud (GROW or RISE), your integrator will ask you to migrate your Z-developments into BTP extensions. CAP then becomes your structuring framework.
3. Consolidated multi-entity reporting and planning on S/4HANA. A mid-market group with four subsidiaries on S/4HANA that wants to consolidate budget and forecast in a single SAP tool needs SAP Analytics Cloud with its financial planning modules natively integrated with S/4HANA data.
The 5 Situations Where Cheaper Alternatives Are Enough
1. Few integrations (fewer than five simple flows). For three or four basic integrations (order export to Salesforce, invoice import from an HR tool), a Make connector or a low-code iPaaS costs a fraction of what Integration Suite does.
2. You are not running S/4HANA. BTP is designed and optimised for the SAP ecosystem. On another ERP (Sage, Access Group, Odoo, Microsoft), the publisher’s native connectors or a generic iPaaS are more appropriate.
3. Your custom development footprint is small. If you have a single custom business form to maintain, a CAP extension on BTP is oversized infrastructure. SAP Fiori Elements or a lightweight extension is sufficient.
4. Your BI is already on Power BI or Tableau. If your teams are satisfied with Power BI connected directly to HANA Cloud, moving to SAC creates a double dependency with no tangible near-term gain.
5. You are on GROW with standard extensions. GROW with SAP on S/4HANA Public Edition enforces strict clean core constraints, but SAP Store-certified extensions often cover standard requirements without additional custom BTP development.
Licensing Model and Real Costs in 2026
The CPEA Model (Cloud Platform Enterprise Agreement)
BTP is not priced at a fixed licence. You purchase cloud credits via a CPEA that services consume as they are used. Each service has a credit rate, and each month your balance is debited by actual consumption (Redress Compliance, 2026).
What makes CPEA hard to forecast:
- Unused credits at year-end are lost (no rollover by default under standard terms)
- PAYG (pay-as-you-go), triggered outside the CPEA, costs 2 to 3 times more per unit (SAP Licensing Experts, 2026)
- On average, 18% of CPEA credits are wasted on over-provisioned or inactive services (Atonement Licensing, 2026)
Negotiation: ask for “commit-to-actual reset” clauses (credit adjustment to actual consumption at year-end) and overage caps. Between 30 and 40% of buyers obtain these clauses through direct negotiation.
Usage-Based vs Fixed Subscription
Some BTP services are available as a fixed monthly subscription rather than variable credits. For predictable workloads (Integration Suite with a stable message volume), a fixed subscription removes credit uncertainty. For variable workloads (generative AI, exploratory analytics), CPEA credits are more appropriate.
The negotiated CPEA discount varies by annual commitment (Atonement Licensing, 2026):
| Annual Commitment | Negotiable Discount | Typical Duration |
|---|---|---|
| $50,000–$150,000/year | 12% | 1–3 years |
| $500,000–$1.5M/year | 18–22% | 2–3 years |
| $5M+/year | 26–28% | 3–5 years |
Budget Ranges by Mid-Market Profile (3 Case Types)
| Company Profile | Typical BTP Scope | Indicative Annual Budget (pre-discount) |
|---|---|---|
| 500–1,000 employees, 1 S/4HANA ERP, 5–10 integrations | Integration Suite base + Build Apps | $60,000–$100,000/year |
| 1,000–3,000 employees, multi-entity, complex integrations | Integration Suite premium + Build Suite + SAC | $120,000–$180,000/year |
| 3,000–5,000 employees, hybrid IT landscape, advanced BI | Integration Suite + Datasphere + SAC + AI Core | $200,000–$350,000/year |
These ranges are before applying negotiated CPEA discounts (12% to 28% depending on commitment). A three-year engagement mechanically places you in the higher discount bracket.
SAP BTP Outside S/4HANA: Myth or Reality?
Can You Use BTP Without Being an SAP Customer?
Technically, yes. SAP sells standalone BTP services (Integration Suite, Build Apps, Datasphere). In practice, use cases outside the SAP ecosystem remain a minority in 2026. BTP is built for S/4HANA: its API catalogue in the Business Accelerator Hub, its S/4HANA Business Events management, its pre-configured connectors — all of this carries significant value only if you run S/4HANA.
Notable exception: multi-vendor organisations (SAP + Oracle + Salesforce) sometimes use Integration Suite as a central integration hub. But MuleSoft or Boomi are generally more relevant in that context, as they are publisher-neutral and more flexible on complex non-SAP topologies. Our ERP iPaaS integration architectures comparison details this make-or-buy decision framework.
How to Start: The First Four Weeks
Before any BTP deployment, four steps help you avoid the classic onboarding mistakes.
Week 1: audit of existing integrations. List all integration flows that touch S/4HANA (data imports/exports, SaaS connections, batch jobs). Assess each one for frequency, volume, criticality, and complexity. This takes 3 to 5 days but determines every aspect of your CPEA design.
Week 2: CPEA sizing. Do not start with a “broad platform” CPEA. Start from the real use cases identified in Week 1 and calculate monthly credit consumption by service. Ask your SAP integrator for precise figures, not indicative ranges. The rule: better to start with a modest CPEA and expand it than to burn credits on unused services.
Week 3: Integration Suite vs alternative iPaaS comparison. If your ERP is not S/4HANA, or if your integrations are few and simple, compare Integration Suite to a third-party iPaaS before signing. The cost difference is substantial ($48,000 vs $85,000/year in the documented case cited above).
Week 4: extension governance definition. If you have ABAP developments to migrate, start the clean core conversation with your integrator now. Every month of custom ABAP code added to an S/4HANA that will migrate to GROW or Public Edition is debt that must be repaid at migration time.
The 3 launch mistakes to avoid:
- Buying the entire BTP catalogue because it is “included” in the RISE bundle
- Mistaking the Free Tier (100 messages/day, 4 GB RAM) for a viable production environment
- Failing to negotiate a credit reset clause before signing a multi-year CPEA
Going Further
To understand how BTP credits fit into the RISE vs GROW choice, read our complete RISE with SAP vs GROW with SAP decision guide 2026, which details the bundles included in each programme and the constraints of each model.
Download our ERP evaluation grid — 30 criteria scored out of 100 to compare 3 vendors side by side, including a dedicated section on platform and extension capabilities for each solution.
