Exsited
billing platform
Recurring billing, subscriptions, and ERP are where SaaS products usually turn ugly. I made Exsited feel premium for the finance teams who use it daily.
Three critical friction points
Manual billing setup. Repetitive manual entry, rules buried deep in menus, and errors that only surfaced at invoice time left finance teams doing the same work twice.
Complex subscription config. Long multi-step configuration, too many required fields, and no guidance for edge cases meant setups got abandoned part-way through.
Fragmented interface. Layouts differed by module and dense enterprise data was handled poorly, which slowed onboarding for every new client.
My role & process
I led the design team, working with product management, engineering, and QA, and owned the design system.
- 01
Discover
Merchant interviews and finance workflow mapping, which surfaced friction no analytics showed, plus a review of support tickets.
- 02
Define
Competitor benchmarking and a heuristic evaluation narrowed it to three friction points: manual billing setup, long subscription configuration, and a fragmented interface.
- 03
Design
Rebuilt billing and subscription flows on one visual language, with the team working from a shared toolkit rather than individual taste.
- 04
Scale
The toolkit I maintained kept every module added since consistent as Exsited grew to 35+ enterprise clients.
Goals & research
Cut the manual work out of recurring billing and invoicing, make subscription setup finishable in one sitting, rebuild the interface on one consistent design system, handle dense financial data without overwhelming people, and make an ERP-class product feel premium rather than industrial.
Merchant interviews, finance workflow mapping, competitor benchmarking, heuristic evaluation, and support ticket analysis all pointed the same direction: finance teams want fewer decisions, not more options, long forms quietly stall adoption, a wrong number costs trust immediately, and consistency across modules is what makes a product feel enterprise.
Strategy into interface
Three principles carried the whole surface: reduce the thinking required, make outcomes predictable, and unify the surface into one visual language.
Key decisions
- 01
Guided billing setup with early validation
In billing, a wrong number costs trust immediately. Setup uses sensible defaults, surfaces rules where they are needed, and catches problems before an invoice reaches a customer.
- 02
Group configuration the way finance teams think
Long configuration forms were stalling adoption. Settings are grouped by how finance teams actually work, drafts save themselves, and a preview shows what a change will do before it is committed.
- 03
One toolkit rules, not one designer's taste
Consistency across modules is what makes a product feel enterprise. Leading the team meant the shared toolkit made the calls, so every module looks like the same product.
Learnings
In enterprise tools, clarity beats capability every time. Mapping the finance workflow surfaced friction no analytics showed, and leading a team meant the shared toolkit ruled, not any one person's taste.
Exsited went from a capable but punishing platform to one finance teams move through without hesitating. Rebuilding it on a shared toolkit kept every module added since consistent, which is what let it scale to 35+ enterprise clients.