FSA Simple
Making a complicated reimbursement process easy.
FSA Simple was a mobile app that streamlined FSA/HSA claims submissions—a notoriously onerous process. As product lead, I spearheaded UX design, working with a broad problem statement through a React Native MVP.
ROLE
Project Lead · Product Design · UX/UI · Prototyping · Front-end implementation
TEAM
2 Business Leads · UX Researcher · Developer
TIMELINE
3–4 months
TOOLS
Adobe XD · React Native · React · TypeScript · Redux
MY CHALLENGE:
How do you take a complicated, rules-heavy process and make it simple?


FSA reimbursement is a documentation-heavy process.
A user might have a simple itemized receipt—or a multi-page medical bill that requires additional receipts, dates, payment information, subscriber information, or other documentation.
Worse, the consequences of omitting one of these items aren't always obvious. A claim can be rejected for any number of reasons. More often than not, if the required information is missing, the user must figure out what went wrong and restart the entire process.


01. START WITH AN IDEAL PICTURE
What if submitting a claim were as simple as taking a photo?
Before thinking about every edge case, I envisioned the best possible scenario for one user.


02. Anticipate Complexity
But wait — one can’t simply snap their fingers and submit a form!
Without much added complexity, however, we can get pretty close.
From a loosely defined idea to a working MVP.
Over roughly 3–4 months, we took FSA Simple from a loosely defined business concept to a working mobile application.
Our team:
Defined the major claim workflows
Created a complete mobile UX
Developed a working React Native application
Tested the experience with users
Submitted the application through Apple's testing process
The founding team’s priorities shifted and FSA Simple was put on hold, but the product and design work still stands.
We had taken an ambiguous, complicated problem and turned it into a functioning experience that could actually be used and tested.
Key Takeaways
Understand the system.
Break it into smaller pieces.
Solve the simplest valuable version first.
Introduce complexity only when it's necessary.
Build, test, and refine.
METRICS
3–4 months from problem statement to working MVP
4-step receipt flow: capture, extract, review, submit
3 tiers of claim complexity planned: receipts, healthcare bills, account info
Tested with users and submitted through Apple’s testing process
© 2026 BEN NICHOLSON








