Becoming a Software Vendor (SAP Add-ons)
As of 2026-10-10
Becoming an SAP add-on vendor is a capital-allocation decision, not a technical one: you trade unbillable R&D months now for licence revenue later, and the trade only pays off if you avoid cost-plus pricing. One Stuttgart boutique embedded its S/4HANA finance-close validation logic into an ABAP add-on and grew recurring licence revenue to 30% of turnover within 18 months without hiring a consultant — that is the ceiling this module targets. Getting there requires an SAP PartnerEdge Build membership, an IP and EULA position resolved in writing, and value-anchored pricing from day one, because a licence sold too cheap is nearly impossible to reprice at renewal. Consultants who can show a real installed base and a renewal rate command 15–25% higher day rates than peers with identical technical skills — the product becomes proof of depth, not a side business.
What you will learn
- Identify the three packaging routes (custom widget, transport add-on, Datasphere data product) and select the right one for your IP
- Navigate SAP PartnerEdge Build requirements including certification, fees, and the realistic path to higher co-marketing tiers
- Structure R&D budgeting, IP ownership, EULA terms, and value-anchored pricing to avoid the most common first-product failures
- Reposition your day rate and client conversation once a verifiable installed base and renewal track record exist
From Consulting Hours to Recurring Revenue
The fundamental shift in becoming an SAP add-on vendor is not technical — it is economic. A consulting practice sells time; a software vendor sells usage. When a boutique SAP analytics firm in Stuttgart embedded its data-validation logic for S/4HANA finance closes into a reusable ABAP add-on in 2022, it kept selling the original consulting work AND charged a €3,000/year per-system licence. Within 18 months, recurring licence revenue represented 30 % of total turnover without adding a single billable consultant. That is the model. The hard part is getting there honestly, because most consultancies underestimate what a product business actually requires.
Prerequisites
- Intermediate hands-on experience on SAP analytics projects
- Review core concepts first: C087, C083, C067
Outcomes
- Work through a realistic scenario: A 12-person SAP analytics boutique with a proven S/4HANA finance-close data-validation script decides to package it as a licensed ABAP add-on instead of continuing to re-sell.
- Recognize and avoid the anti-pattern: Building an add-on around a feature SAP will ship natively within 12 months — The licence becomes worthless the day the roadmap feature ships — read SAP's roadmap blog.
- Apply the module's core decision: Which packaging route for your IP — choose Default to a Custom Widget on SAC for speed to market.
- Track mastery with the KPI: Recurring licence revenue mix (target: ≥25–30% of total turnover within 18 months of the first paid licence; red flag: Licence revenue stalls below 10% after 18 months).
Full module available to members. The full module adds: the decision framework · the end-to-end scenario walkthrough · the KPI scorecard · the anti-patterns · the knowledge check · the diagrams.