JimdoPay, Built from Scratch
Sellers issued 780 invoices with JimdoPay in October 2026, up from 11 in April, on a product I designed in code from day one

In short
Invoices issued in a month
780
October 2026, 337 sellers since April
from 11 in AprilBefore vs after
Invoiced through JimdoPay
€703k
2 Apr to 13 Sep 2026
from €0 before JimdoPayBefore vs after
Usability (UMUX-Lite)
79.8
round 2; Jimdo's bar is 75
from 66.3 in round 1Before vs after
Before vs after: no A/B test isolates the design, and the product was new and growing. Sources: Mixpanel, April to October 2026; JimdoPay invoicing review, September 2026; Maze, rounds of 28 Jan and 10 Feb 2026 (different participants).
- Jimdo's small businesses could get found and booked on their websites, but they had no simple way to get paid online.
- I designed JimdoPay in code: one live prototype on Jimdo's design system, tested twice with users, that engineers built production from.
- Invoicing grew from April to October, but it stayed below plan. That gap started my next case.
Context
Jimdo wanted to help small businesses get found, get booked and get paid. The last part didn't exist as a product. We started in December 2025 and launched publicly in May 2026.
We designed for yoga teachers, photographers and coaches: one person doing sales, delivery and accounting, often from a phone. On day one I went through Stripe's and Adyen's dashboards screen by screen and marked what that person never touches.
One live prototype
I built the prototype in code, on Jimdo's design system, and deployed every change. There was always one current link to review, and engineers built production from the same code.
Later I took the approach into the production repo: interface components that engineers connect to real data. Money logic stays with engineering, after a code review flagged a change I made to invoice totals.
One creation flow
Payment links, invoices and quotes share one creation flow: list, editor, send and details. Only the fields and the preview change, so a seller learns it once.
Flow
Flow
Flow
Flow
On the other side, the customer pays on one page: by card, Klarna, bank or PayPal.
Two test rounds
I ran two unmoderated rounds in Maze, inside the prototype. In round one a task broke: the quote it asked for was missing from the prototype, and about half the participants got stuck.
For round two I fixed the content, froze the version and added a popup that confirms each finished task. Then I wrote up what still didn't work, like the free amount option on payment links.
Time to finish the tasks
7.1 min
round 2
from 12.6 minBefore vs after
Positive first impressions
86%
round 2
from 63% in round 1Before vs after
Maze, rounds of 28 Jan and 10 Feb 2026, with different participants. 14 people completed round 2.
Testing
Research
Before
After
What shipped
The core screens on desktop, and the same product on the phone, where many of these sellers work.
Shipped
Shipped
Impact
Payment links created
1,033
by 430 sellers, May to October 2026
from 0 before JimdoPayBefore vs after
Invoices issued
3,181
2 Apr to 13 Sep 2026
from 0 before JimdoPayBefore vs after
Sources: Mixpanel, May to October 2026; JimdoPay invoicing review, September 2026.
Honest read
No control group
The product was new and growing. These numbers measure use, and they can't tell how much of it the design caused.
Built is not adopted
By September, invoicing had about half the users the plan expected. The research in the next case started from that gap.
Different people each round
Round two had new participants, mostly English speakers from a panel. The next round should test with German-speaking sellers.
Team and role
- Me, product designer
- Designed JimdoPay end to end, alongside an eight-person team. Built the prototype in code, ran both usability rounds, wrote the team's guide "Prototyping with Cursor" and opened pull requests in production.
- Product Owner
- Owned scope and priorities.
- Engineering Manager
- Owned delivery.
- Engineers
- Built production on top of the prototype and reviewed my pull requests.
What I learned
- Learn it once. Payment links, invoices and quotes share one creation flow, and only the fields change.
- The prototype was the spec. Engineers built from the same code I worked on.
- Know where design code stops. Money logic stays with engineering, by rule.
