
Driving Adoption and Reducing Operational Risk in SAP’s Enterprise Subscription Billing Platform
Led UX strategy for SAP’s enterprise subscription billing suite, aligning six global teams around a unified interaction model that reduced errors, improved efficiency, and scaled across multiple products.

Benedikt Breitschopf
UX Design Lead
Shaping complex B2B systems into clear, scalable experiences through rigorous research, coherent design, and cross-team alignment.
Context & Business Problem
SAP’s subscription billing ecosystem consisted of multiple loosely connected applications used by enterprise finance teams. Inconsistent interaction patterns, fragmented navigation, and legacy workflows increased onboarding time, user errors, and operational risk.
Business Risk • High error rates in billing setup • Long time-to-proficiency for new users • Inconsistent UX across products slowed adoption

Timeline
March 2018 – April 2022
UX Architect
• Owned UX strategy across 6 global development teams • Defined cross-product interaction standards • Acted as primary UX counterpart to Product and Engineering leadership
Key Decisions & Trade-offs
Key UX Decisions • Standardized object-page and navigation models across products to reduce cognitive switching • Prioritized consistency over local optimization, even when individual teams preferred custom solutions
Trade-offs • Accepted less customization in early iterations to accelerate adoption • Postponed niche workflows to protect a coherent core experience
Research
Evidence & Insights • 30+ qualitative interviews and 200+ survey responses across global users • Identified mismatches between system structure and user mental models • Validated accessibility and error-handling gaps impacting enterprise adoption Insights directly informed: • Navigation architecture • Error prevention models • Cross-app interaction patterns
Results & Impact
Measured Outcomes • +22% improvement in time-on-task efficiency • +18% increase in SUS scores Business Impact • Faster onboarding for enterprise customers • UX model acts as a reference for future products
Reflection
What I’d Do Differently Earlier alignment with engineering leadership on technical constraints would have reduced iteration cycles and accelerated rollout on specific topics.
