Sid

Poitiers, France

Expandi ProductSeats and billing

Fixed Expandi's seat billing, which was wrong in both directions: leaking revenue one way, taking paid time the other.

Adding seats didn't charge until the next invoice: a direct revenue leak. Reducing seats or cancelling took effect immediately, so customers lost time they had paid for. Cancel-and-refund was the largest cluster of support contacts.

billing rules, applied to every flow
8
flows shipped, July to September 2026
6
of scheduled changes can be undone
100%

Expandi · Senior Product Designer · 2026 · Shipped, one flow pending

    • A seat and the LinkedIn account on it are separate things, and the old logic treated them as one.
    • People confused disconnecting an account with cancelling its seat, and support refunded the difference by hand.
    • Agency owners scaling seats up and down with their client list, month to month.
    • Finance, who needed every flow to follow the same eight rules.
    • Asymmetric on purpose: upgrades take effect and charge now, downgrades wait for the billing date. Fair to the customer and to the business.
    • The customer always chooses which accounts are affected. The system never picks for them.
    • Upgrades show the amount before confirming, and a failed payment changes nothing.
    • Downgrades and cancellations are scheduled, visible and undoable until the date.
    • Six flows, shipped July to September 2026.
    • Added seats are paid for when added, and customers keep what they paid for. Cancel-and-refund contacts dropped by about 40%.
    • Still to build: changing seats while a downgrade is scheduled.
A subscription's seats and the accounts on them
Subscription overview with next payment and card
Subscription invoices

(Keep browsing)

More projects