Card-first Spend Management
Monthly card spend went from €163 to €294k between April 2022 and January 2024, on expense cards I designed from research to Apple Pay

In short
Monthly spend through the cards
€294k
January 2024
from €163 in April 2022Before vs after
Cards used with phone payments
390
a month, January 2024
from 7 in March 2023Before vs after
Committed revenue a month from cards
€79k
January 2024
from €1.7k in January 2023Before vs after
Before vs after, no control group. Revenue also grew with new Business and Enterprise plans at €0.5 to €1 per person. Source: Factorial BI charts, April 2022 to January 2024.
- Receipts lived in a folder and approvals in a spreadsheet. Competitors sold card-based automation, and Factorial was losing yearly contracts.
- I designed Factorial's first expense cards and covered product management: physical, virtual and single-use cards, then Apple Pay and Google Pay.
- The first version let the product grow for the next two years.
The problem
Every expense meant manual work: upload the document, type the data, keep the receipt. Spendesk, Pleo and Payhawk already automated this with cards. Without it, Factorial was losing yearly contracts.
Many customers didn't trust cards either, so they kept doing it by hand, even though it was slower.
The cut
I studied Pleo, Payhawk, OKTicket, Spendesk, Revolut Business and Captio. We mapped lost sales and churn against revenue, and picked the card provider competitors trusted. Company verification with the provider was the slowest step, so I moved it as late as possible.
Phone payments stayed out of the first version on purpose. They came later as their own project.
The cards
I designed the cards in Factorial's brand and within the card printer's limits: physical for shops, virtual for online, and single-use cards.
Shipped
Shipped
One first version
Early designs went straight to the sales team, then to tests with HR managers. We launched one first version in one push: a list for managers, one screen per card with balance and controls, and the account behind the cards.
ShippedOne card, one screen: details, balance and controls together.
ShippedThe cards account, with its transfer details in a side panel.
Phone payments
Competitors showed phone payments in their sales demos, and we were losing sales and customers over it. Employees still photographed every receipt, even for a two-euro coffee. The team had no PM during the build, so I covered product too.
Round one of testing showed the Cards section was hard to find, adding a card to the phone took five taps, and the feature felt like a hidden setting. In round two it took two taps, with a screen that announces it.
ShippedA Factorial card in the phone's wallet, ready at the reader.
ShippedThe intro screen that announces the feature inside the app.
ShippedMy cards: active and inactive cards in one place.
ShippedCard details on the phone, with the spending limit next to the balance.
Impact
With phone payments in place, new pricing of €8 to €12 per card a year became reasonable, and the product started covering its own costs.
DataCommitted revenue a month attributed to cards, January 2023 to January 2024.
DataCards used with phone payments each month by card type, March 2023 to January 2024.
Honest read
Revenue wasn't design alone
New Business and Enterprise plans and the sales team grew revenue too. Design owned the card experience.
No control group
Spend and phone payments are before and after. Plans and pricing changed in the same period.
Team and role
- Design and product
- Me, on both projects: research, planning, card branding, prototypes and quality checks.
- Sales
- Gave feedback on the early designs.
- HR managers
- Tested the designs before launch.
- Card provider
- Ran company verification.
What I learned
- The right cut is the one your sales team agrees to. That first version let the product grow for two years.
- Regulators look at the screens. The flow you design is the flow the bank approves or rejects.
- Building blocks travel. The cards opened the door to IT Management, which reused the same blocks for software access and subscriptions.
