Turning Invoicing into a Scalable Growth Platform
Role
Design Lead @ Temper EU
Industry
Human Resources
Skills
Product Design
User Research
UX Engineering
Workshop Facilitation
Temper’s invoicing system became a growth blocker. It was neither reliable, nor compliant, and unable to support enterprise needs. I co-led a migration to revamp invoicing as a flexible micro-service for retention and new business verticals.
impact
99.99%
Invoice success rate improved from 71%
100%
compliance across invoicing flows
+27%
conversion among finance users
+€12,1m
projected ARR from new businesses unlocked
Disclaimer: Confidential information has been omitted or obfuscated. This case reflects my own perspective and does not necessarily represent the views of Temper.
CONTEXT
Invoicing was everywhere, but no one trusted it
Temper’s invoicing system was critical to how clients, freelancers, and internal teams operated. Over time, it became increasingly difficult to use, trust, and scale.
Compliance issues, high error rates, and rigid logic made invoicing fragile, especially as enterprise usage grew. While everyone depended on it, everyone understood it differently, and used it differently.
This created risk in the most sensitive part of the business.
Project kickoff and initial analysis
GAP
Scale exposed what the system couldn’t handle
As usage scaled, the system started blocking growth rather than supporting it:
Millions in MRR at stake, with a projected 8% YoY decline linked to invoicing
71% invoice success rate, with error rates reaching 90% for enterprise clients
Limited access to key business verticals due to inflexible invoicing logic
Mapping, Data deep-diver, and Workshop
MOVE
We stopped fixing invoices and redesigned what invoicing meant
Together with Isaac Huijink (PM), I led a migration strategy focused on reducing risk while rebuilding trust.
Our approach was guided by three principles:
Ship in small, lean releases to minimize disruption
Maintain transparency for teams and clients throughout the migration
Align stakeholders around a shared understanding of what invoicing is and isn’t
Equally important was what we avoided:
Big-bang rewrites
Client-specific fixes that wouldn’t scale
Optimizing for one vertical at the expense of blocking others
Change management was as critical as the platform work. Every team, client, and freelancer spoke a different invoicing language.
Initial UI explorations
SYSTEM
One structure that could support every business model
We rebuilt invoicing to support multiple business models within a single, coherent structure. The system was organized around four pillars:
Billing Profiles
An opt-in model defining when invoices are generated, who receives them, and what they contain.Financial Overview
A redesigned overview focused on clarity and education, giving clients visibility into spend and behavior.Invoice Management
Scalable tools for finance users to manage references, notes, and compliance needs.Credit Management
Centralized handling of credits across enterprise companies and branches.
This structure supported diverse verticals, from events to construction and frontline work, without branching into custom logic per client.
Validated migration strategy
Validated Financial Overview Screens
IMPACT
Growth returned once trust was established
The results validated the approach:
Invoice success rate improved from 71% to 99.90%
100% compliance achieved across invoicing flows
27% increase in conversion among finance users
+€12.1M projected MRR, driven by retention and access to new enterprise verticals
Invoicing stopped being a blocker for growth and opened Temper to new business verticals, with Events presenting the largest opportunity.
—
In revenue-critical systems, design impact is measured as much by risk reduced as by features shipped. Designing for trust, flexibility, and scale often means resisting short-term fixes in favor of structures that hold under pressure.
This mindset continues to guide how I approach complex systems where failure has real business consequences.