Katrina Donegan monogramKatrina DoneganDesigner & Artist

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.

Role
Staff Product Designer
Company
Invoice2go @ BILL
Freemium Sign-Up Flow interface overview
Company overview

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.

The challenge

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.

Trial-ended dashboard with a subscription banner, the starting point for choosing a plan
The “trial ended” dashboard notification banner is one entry point into plan selection.
01 / Map the journey

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. 1

    Plan choice

    Choose Basic with a clear view of its limits and card payment requirement.

  2. 2

    Application status

    Complete the payment application and understand the pending approval state.

  3. 3

    Bank linking

    After approval, link a bank account to complete payment setup.

Primary journey from trial expiration through Basic plan selection, payment approval, and bank linking
Primary journey from trial expiration through Basic plan selection, payment approval, and bank linking
An overview of the journey: the longer setup flow is shown at the top, with the shorter journey we’d like to work toward below.
02 / Set expectations

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.

Plan comparison showing Premium, Professional, and the new $0 Basic tier
Basic introduces a $0 subscription alongside the paid plans.
Plan comparison with expanded explanation of the Basic card payment requirement
A tooltip explains the card payment requirement before selection.
Basic plan selected with an awaiting approval status
The selected plan stays visible while payment approval is pending.
Selected Basic plan with contextual help explaining when the user can start
A status tooltip explains when the user can begin using Basic.
03 / Work across product boundaries

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.

Payment onboarding introduction explaining the card payment offering
Payment onboarding prepares users for the application.
Payment application requesting business information and business type
The application collects business details required for payment setup.
04 / Design the waiting states

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.

Application submitted confirmation with review expectations and an option to choose another plan
Submission confirms review is underway and explains limited access.
Dashboard banner indicating the card payment application is pending
A dashboard banner keeps application status visible.
Pending-state dialog offering another plan or the option to wait
Users can choose another plan or continue waiting.
05 / Resume after approval

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.

Approval email explaining that bank linking is required before accepting card payments
The approval email identifies bank linking as the remaining step.
In-product Plaid introduction explaining bank linking and automatic payment transfers
This pop-up explains why the user is moving to Plaid.
Plaid sequence showing consent, bank selection, bank authentication, and successful linking
Plaid guides the user through consent, bank selection, authentication, and linking.
06 / Begin using Basic

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.

Basic dashboard after setup, without the trial-ended banner
Design outcome

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.