Fintech · Product strategy & UX
Freemium Sign-Up Flow
Creating a free tier for users finishing a trial or choosing to downgrade from a paid plan.

About Invoice2go
Invoice2go, a BILL subsidiary, helps small businesses create estimates and invoices, accept online payments, and manage day-to-day billing. BILL provides financial software for small and midsize businesses, including payables, receivables, and spend management.
Introducing a free tier
Invoice2go had paid plans but no free tier. Users finishing a trial or stepping down from Premium needed a way to continue with limited features. We called this the “Freemium” project. “Basic” was the customer-facing name for that same free tier, with card payments required.
We had to use third-party services for setup: Adyen for payment approval and Plaid for bank linking. Their interfaces and approval decisions were outside our control, so I focused on making each hand-off, requirement, and next step clear.

Make the dependencies visible
I owned the end to end UX and UI design, partnering with four product managers across pricing, invoicing, payments, and Adyen, alongside the lead engineer. Journey mapping connected the plan rules, payment approval, and bank linking dependencies. This gave the cross functional team one view of the primary path and alternate states.
- 1
Plan choice
Choose Basic with a clear view of its limits and card payment requirement.
- 2
Application status
Complete the payment application and understand the pending approval state.
- 3
Bank linking
After approval, link a bank account to complete payment setup.


Make the free plan requirements explicit
A $0 subscription still came with limits, payment fees, and a card payment requirement. I made those conditions visible in the plan comparison page, using tooltips for the extra detail. After selection, the page shows pending approval rather than asking users to choose Basic again. This separates plan selection from activation and prevents conflicting calls to action.




Prepare users for the payment application
Adyen controlled the payment application and approval requirements. I could shape the hand-off, but not redesign every third party screen. The transition page explains why payment setup is required and what comes next, keeping the product experience coherent within those integration constraints.


Keep pending status clear
Approval is asynchronous, so the journey needs to make sense after users leave onboarding. I carried the pending state across confirmation, the dashboard banner, and plan selection. Each message explains limited access and offers a clear choice: wait for approval or choose another plan. Consistent status messaging helps users understand where things stand without suggesting that setup is complete.



Approved, with one step left
Once Adyen approves the application, the user receives an approval email. Bank linking is the final setup step. I designed the approval email to explain that users still needed to link a bank account, with a clear link back to finish setup. It tells them why bank linking is required and what to have ready.
Before the next third party hand-off, the product introduces Plaid and explains its role. The sequence connects approval, bank selection, and authentication without making users piece the requirements together themselves.



Ready for the everyday work
With payment approval and bank linking complete, setup is finished and the user can get back to running their business on Basic. The free plan gives them a limited set of features suited to their needs, so they can keep using Invoice2go without a paid subscription.

A more direct path into the free tier
The design proposal turns a fragmented, multiple provider setup into one understandable journey. Plan selection, pending approval, and bank linking each have a defined state and next action. The intended outcome is a less ambiguous route into Basic, with clear requirements before commitment and consistent guidance after each hand-off.