Seat expansion
2026
Increasing revenue by turning unused seats into expansion
Problem area
Successful onboarding, poor adoption metrics
Businesses were paying for seats their teams never used. In average, 1 user was active per account. Expense submissions of the team were on one person and the product never became part of how the team worked. For us, that meant poor adoption, unused included seats, and an expansion revenue target with nothing feeding it.
Funnel at start
Screens before work
Opportunity 1
Make included seats visible. So, admins can see the capacity they already pay for and fill it before the account stops at one user.
Opportunity 2
Show pending invites and make them easy to recover, improving acceptance and getting teammates to their first expense.
Design goals
What I aimed to achieve
Design decision 01
Show the first nudge after seeing value instead of during setup
The obvious place to prompt team invites was onboarding, where completion was already high. But inviting a teammate before the admin sees the product work gives them not much reason to invite people. I timed the first nudge to the next login after an expense was approved. It meant every admin who just experienced the main workflow would view it.
1
Cohort and timing
Admins who already approved some expenses and have more to approve views it in next login.
Design decision 02
Embedded UI to show seat usage
A side banner or modal at login would have been faster to ship and more visible on the page. But seat usage is a permanent state of the account rather than a dismissable overlay. I built it into the Users page as an embedded UI with Customer.io, showing used, pending and free seats, and additional seat pricing above the users list. Trade off was context over visibility. It's less eye-catching than a modal, but it's there every time the admin manages their team.
2
Controls stay in the table
Resending an invite or adding a new user actions still stay in the table, not to change the product experience.
Design decision 03
No upsell message to accounts at the limit
When an account had used all its included seats, the obvious pattern was a limit message or an upgrade modal the moment the admin tried to add someone. But blocking an admin at the exact moment they're trying to grow their team turns a good signal into friction. Instead, the same seat indicator shows the account is full and still states what the next seat costs, while Add users stays the primary action. The trade-off was clarity over urgency: showing the price up front might make some admins pause, but nobody hits a wall or a surprise charge, and the decision stays theirs.
Retrospective
Adoption before expansion
What's changed already
Metrics to track
Invite acceptance
Nr of invites accepted in the first three days
What I'd do differently in the next round
Get the product analytics in before the design review
Ship the cheapest one first instead of three nudge flow










