Analytics Legends The knowledge platform for SAP Analytics
Guide

SAP BTP Extension Development Services: Who Delivers Them and How

As of 2026-08-17

SAP BTP extension development services cover the delivery side of the clean-core pattern: the teams that design, build and support side-by-side applications, workflows and integrations on SAP Business Technology Platform rather than modifying S/4HANA's standard code. The work sits across three distinct disciplines, and a single provider rarely covers all three at senior depth. Buying this as one undifferentiated line item is the most common scoping mistake a buyer makes.

What the phrase actually buys

BTP Extension Suite's three pillars are application development (Build Code or Build, Java, Node or Python on Cloud Foundry or Kyma, or the CAP framework), process automation (SAP Build Process Automation), and integration (SAP Integration Suite). A development service can be scoped against any one of the three, or across all of them, and the skill sets barely overlap: an application developer building a Fiori-based side-by-side app is not the same person who wires an integration flow between S/4HANA and a third-party procurement tool.

Ask which pillar the requirement actually sits in before asking who can deliver it. A vendor pitching "BTP extension development" as a single capability is usually strongest in one pillar and generalist in the other two.

Why this is a services question, not a product one

Clean core is the governance discipline behind the whole category: nothing a customer builds should modify SAP-delivered objects, so anything custom has to live in a separate extension layer that SAP's release process cannot touch. That single rule is what turned in-system ABAP work into an external delivery stream. The requirement to build custom functionality did not shrink when clean core arrived — it moved off the ABAP stack and onto BTP, and someone still has to staff it.

For a buyer used to commissioning ABAP enhancements from an internal team or a classic SI, this is the mental shift: extension development is now sourced the way a web or integration project would be, not the way an in-system modification used to be.

Cloud Foundry or Kyma — the question a scope document often skips

Cloud Foundry is the more managed runtime — buildpacks, less container-level configuration, a gentler ramp for teams new to BTP. Kyma is Kubernetes-native and gives more control at the cost of more operational overhead. A developer fluent in one is not automatically fluent in the other, and the two runtimes are not interchangeable mid-project.

Before agreeing a statement of work, confirm which runtime the target landscape actually uses, or is migrating towards, and ask the provider directly which one their delivery team has shipped a production go-live on — not which one is on their capability slide.

What the live market shows

Filtering our tracked SAP contract corpus on BTP, extension, side-by-side and Integration Suite terms currently returns around 21 open postings — a modest, extension-specific slice of the wider SAP contract market the corpus tracks, not a saturated skill category. That matters for sourcing strategy: a crowded skill like SAP BW or SAC lets a buyer run a competitive tender across many bidders; a thin one like BTP extension delivery rewards a steady relationship with a system integrator or a boutique BTP shop over a spot-market tender.

How to scope the engagement, not just the skill

Four questions do more work than a generic RFP: which of the three pillars is actually in scope; which runtime, and has the bidder shipped a production go-live on it; has the team delivered under S/4HANA Cloud's stricter extensibility model; and who owns the extension after go-live, because a clean-core extension nobody maintains degrades exactly like the in-system customisations it replaced.

Frequently asked

Is BTP extension development the same as ABAP development?

No. ABAP development modifies or extends the system in place; BTP extension development builds a separate, side-by-side application or integration that talks to S/4HANA through stable APIs, so the core system stays untouched and upgradeable. Clean core is the rule that makes the second approach the default for new work.

Do I need a Cloud Foundry specialist or a Kyma specialist?

It depends on the runtime the target landscape uses or is standardising on. The two are not interchangeable skill sets — confirm the runtime first, then ask the bidder for a production go-live reference on that specific runtime, not a generic BTP capability statement.

How large is the market for this specific service?

Our tracked SAP contract corpus currently shows around 21 open postings matching BTP, extension, side-by-side or Integration Suite terms — a real but modest slice of the wider SAP contract market. It rewards a steady delivery relationship more than it does a competitive spot tender.

Is this the same as buying an SAP BTP Extension Suite licence?

No. The licence covers the platform components — the application runtime, process automation and integration tooling. This service is the delivery capability that actually builds and maintains something on top of that licence; buying the licence does not staff the build.

What this page is built on

Read next