SumUp

Building Subscription Infrastructure at Scale

Final fiscalisation UI showing plan selection, checkout, and subscription management

In 2020, SumUp was transforming from transaction fees to recurring revenue - a fundamental business model shift. I was the designer for fiscalisation, the first product on their new subscription platform. The stakes were high: prove this infrastructure could work at scale while making German tax compliance invisible to merchants.

Outcomes

0.0

NPS score achieved during usability tests.

0

+

Foundation product for 5 more subscription services.

Role:
Senior Product Designer

Key responsibilities

  • Designed unified subscription experience coordinating two product teams

  • Created production-ready UI integrated across dashboard and marketing website

  • Built systematic Figma structure enabling multi-stakeholder independent review

  • Conducted user research validation achieving NPS 8.5 for ease of use

  • Developed technical integration approach balancing platform constraints with merchant needs

30 Second Story

Challenge: Design SumUp's first subscription product on new platform infrastructure
Discovery: Two teams, German tax law, 4M merchants, zero-support requirement
Action: Embedded with two teams, created systematic approach, validated quality
Impact: NPS 8.5, minimal support tickets, foundation for future subscription products

01.

The Challenge: First Product on New Infrastructure

High-Stakes Execution
SumUp was evolving from transaction fees (2.75% per sale) to recurring revenue through subscription products. They built a comprehensive "Billing & Subscription" platform to support this transformation across three business entities and multiple future products.

Fiscalisation was the first real-world test of this entire infrastructure.

The challenge wasn't just designing a tax compliance subscription - it was proving the platform worked, establishing patterns for future products, and doing it all for 4 million merchants where support tickets don't scale.

Key Constraints:

  • German tax compliance requirements (TSE certification, device management)

  • New technical platform with untested integration points

  • Two separate teams: Billing API + Product team

  • Self-service only: with 4M merchants, human support doesn't scale

  • First product sets patterns for 5+ future subscriptions

Key Constraints:

  • German tax compliance requirements (TSE certification, device management)

  • New technical platform with untested integration points

  • Two separate teams: Billing API + Product team

  • Self-service only: with 4M merchants, human support doesn't scale

  • First product sets patterns for 5+ future subscriptions

02.

Respecting Complexity Without Being Overwhelmed

Coordinating Between Two Technical Teams
Designing the subscription service meant working at the intersection of two teams: one building the payment processing and billing infrastructure, the other creating the fiscalisation product merchants would subscribe to.

My Approach
To ensure I understood the requirements of both teams, I embedded myself in both, working with product owners and developers to understand the needs of each platform.

Being involved in mapping both the platform and the product allowed me to understand the details and create a unified design experience that worked for both technical systems and merchant understanding.

Going from early ideas, through technical understanding, through subscription details

This coordination work revealed key decisions:

  • Subscription management separated from individual products (platform decision I supported with UX validation)

  • Checkout remains in-product for coherent experience

  • Billing details widget integrated, but feeling native

  • Progressive disclosure for complex tax requirements

This coordination work revealed key decisions:

  • Subscription management separated from individual products (platform decision I supported with UX validation)

  • Checkout remains in-product for coherent experience

  • Billing details widget integrated, but feeling native

  • Progressive disclosure for complex tax requirements

03.

Systematic Organisation for Multi-Stakeholder Clarity

Creating Structure for Complex Work

Part of solving the design problem was creating clarity for stakeholders on why and how things would work. With two technical teams, multiple product managers, and curious stakeholders all needing to understand the flows, I needed a system that enabled independent review.


The Figma Solution:

I created a Figma template that follows the main user journey from top to bottom, showing variations of screens from left to right. Each row starts with a card describing:

  • Main user needs addressed

  • Research questions identified during design

  • Design decisions and rationale

This organisation allowed developers, product managers, and stakeholders to review screens independently without requiring my constant presence for explanation.

Creating Structure for Complex Work

Part of solving the design problem was creating clarity for stakeholders on why and how things would work. With two technical teams, multiple product managers, and curious stakeholders all needing to understand the flows, I needed a system that enabled independent review.


The Figma Solution:

I created a Figma template that follows the main user journey from top to bottom, showing variations of screens from left to right. Each row starts with a card describing:

  • Main user needs addressed

  • Research questions identified during design

  • Design decisions and rationale

This organisation allowed developers, product managers, and stakeholders to review screens independently without requiring my constant presence for explanation.

Figma Organisation for Scale

I structured our design files to enable parallel work streams and maintain consistency:

Figma Organisation for Scale

I structured our design files to enable parallel work streams and maintain consistency:

From site structure to Figma organisation to file organisation to screens.

The Value of Systematic Thinking:

This wasn't just organisation for its own sake - it solved real collaboration problems:

  • Developers could understand flows without designer handholding

  • Product managers could review independently across time zones

  • Stakeholders could explore without blocking the team

  • Research questions were visible, inviting validation

This systematic approach became my contribution to the team's working method.

The Value of Systematic Thinking:

This wasn't just organisation for its own sake - it solved real collaboration problems:

  • Developers could understand flows without designer handholding

  • Product managers could review independently across time zones

  • Stakeholders could explore without blocking the team

  • Research questions were visible, inviting validation

This systematic approach became my contribution to the team's working method.

04.

Validation Through User Testing

Ensuring Quality Before Launch

I collaborated with a user researcher to create scenarios and questions that would validate our core design decisions. We tested with existing merchants to ensure the experience worked for real users in real contexts.


What We Learned

Merchants successfully completed all scenarios, validating our core flows:

  • Central subscription management in "Account" made sense

  • Everyone could easily cancel the subscription

  • Payment confirmation and summary were clear


Key User Quotes
"I think it's good. Simple and uncomplicated."
"Compliment! You just solved it. The fact that you can cancel something so easily - you rarely experience that."


Areas for Improvement

Merchants struggled understanding how and if tax regulation applied to them - this wasn't a design problem but revealed the need for clearer educational content about German fiscalisation requirements.

Ensuring Quality Before Launch

I collaborated with a user researcher to create scenarios and questions that would validate our core design decisions. We tested with existing merchants to ensure the experience worked for real users in real contexts.


What We Learned

Merchants successfully completed all scenarios, validating our core flows:

  • Central subscription management in "Account" made sense

  • Everyone could easily cancel the subscription

  • Payment confirmation and summary were clear


Key User Quotes
"I think it's good. Simple and uncomplicated."
"Compliment! You just solved it. The fact that you can cancel something so easily - you rarely experience that."


Areas for Improvement

Merchants struggled understanding how and if tax regulation applied to them - this wasn't a design problem but revealed the need for clearer educational content about German fiscalisation requirements.

For original design through competitor and inspiration, through testing to final design

The Impact
This iterative process didn't just deliver a better calculator - it established our design principles for the entire platform. We learned that users don't need less complexity; they need complexity revealed progressively, with clear value at each step. This insight shaped every subsequent feature we built.

05.

The Outcome: Deceptively Simple Execution

When Design Succeeds, You Don't Notice It

A design is successful when people using it barely notice the design choices. After release, fiscalisation was successfully used from day one with few questions raised to customer support.

When Design Succeeds, You Don't Notice It

A design is successful when people using it barely notice the design choices. After release, fiscalisation was successfully used from day one with few questions raised to customer support.

Some of the core screens

The Business Validation:

Beyond user satisfaction, the project proved the subscription platform could work:

  • Infrastructure validated for future products

  • Self-service model confirmed as viable

  • Pattern established for subscription management

  • Integration approach validated across teams


What This Project Demonstrated:

  • Execution at scale: Designing for 4M+ merchants across European markets

  • Cross-functional coordination: Bridging two technical teams with different requirements

  • Systematic approaches: Creating structure that enabled team efficiency

  • Quality craft: Delivering NPS 8.5 on high-stakes first product

  • Platform thinking: Designing for both immediate needs and future products

Recommendation

"I had the pleasure of working with Sjors on designing a new subscription experience at SumUp. Together, we went through the entire process of exploring and defining the problem space, conducting competitor research, creating prototypes, validating designs with users, and seeing them go live with customers. A strong sense of ownership, critical thinking, and attention to detail are just three of the qualities that come to mind when thinking back to working together."

— Stefan Jannsen, Senior Product Manager at SumUp

Let's talk

Ready to discuss complex product challenges? Let's connect.

Book a Call

info@sjorstimmer.eu

Let's talk

Ready to discuss complex product challenges? Let's connect.

Book a Call

info@sjorstimmer.eu

Let's talk

Ready to discuss complex product challenges? Let's connect.

Book a Call

info@sjorstimmer.eu

Let's talk

Ready to discuss complex product challenges? Let's connect.

Book a Call

info@sjorstimmer.eu

Let's talk

Ready to discuss complex product challenges? Let's connect.

Book a Call

info@sjorstimmer.eu

Berlin, 2025

This is the end of the page, book a coffee call ☕, always happy to chat.

Berlin, 2025

This is the end of the page, book a coffee call ☕, always happy to chat.

Berlin, 2025

This is the end of the page, book a coffee call ☕, always happy to chat.

Berlin, 2025

This is the end of the page, book a coffee call ☕, always happy to chat.

Berlin, 2025

This is the end of the page, book a coffee call ☕, always happy to chat.