Lead Product Designer · 2022 · Fintech
Making a hard-money lending MVP credible enough to raise on — without a research phase
Shipped on time, held up in investor pitches, and left a structural language later features could layer onto without redesigning the core.
RevStar needed a hard-money lending product that could move real money on day one and survive investor demos — while the existing flows still read like engineering tools. As Lead Product Designer I owned borrower, lender, and operator experience under an MVP clock with no formal research phase. Constraint: three audiences, one codebase, credibility over feature count.
01 · The problem
Technically correct, but it didn’t look investable
Hard-money lending puts six-figure decisions on short timelines. The existing workflows worked for operators who already knew the jargon, and fell apart when the client put the same screens in front of investors who didn’t. The fragmentation wasn’t just ugly. It leaked trust before anyone questioned the lending model.
So speed wasn’t the only constraint. Whatever shipped had to look like a product people would fund, for three audiences (borrowers, lenders and operators) on one codebase.
02 · What I found
The gaps were all assumed knowledge
There was no formal research phase, so research had to happen inside the work. I sat in client reviews, watched investor demos, listened in on engineering implementation talks, and walked the borrower flow until the gaps were obvious: terminology that froze non-technical users, dense screens that hid the next action, and operator workflows that looked opaque over someone’s shoulder.
None of those were missing features. Every one was a clarity problem, which meant adding capability would make things worse.
03 · Key decisions
Three calls that made an MVP credible
Decision 1
Make clarity the feature, and publish the cut list
I cut anything that muddied the first screen and made “what we will not ship” as explicit as the roadmap.
- Instead of
- Adding lending depth to prove sophistication.
- Why
- More capability on an already overwhelming surface would have made the credibility problem worse.
- Trade-off
- Depth I'd scoped on the design side stayed deferred.
Decision 2
One component kit, three role homes
Borrowers, lenders and operators each got a home built around their main job (the next payment due, pending deals, approvals that block a disbursement), all composed from the same components.
- Why
- Engineering stayed fast on an MVP clock, and the product still felt deliberate.
- Trade-off
- No one-off layouts for any audience. Every screen had to come from the shared kit.
Process
Three audiences, one component kit
Role-specific homes built from the same structural language under MVP constraints.
Borrower
Next-due payment and loan structure they can explain
Lender
Pending deals and credibility in investor pitches
Operator
Blocking approvals and disbursements without jargon
Shared components · primary intent first · no one-off layouts
Decision 3
Every step says what's decided, who decides and what's next
I gave every flow the same structure, with the primary action read first and inline help where the jargon used to be.
- Instead of
- A separate help center, which there wasn't time to build.
- Why
- People froze on terminology and couldn't find the next action on dense screens.
04 · Outcome
Shipped on time, and held up in the room
The MVP shipped on schedule and held up in investor pitches.
The evidence here is commercial and structural rather than a metric. The depth I deferred stayed deferred, correctly, because the structure survived every feature layered on later without a redesign of the core.
05 · Reflection
Shipping fast isn’t shipping shallow
Early-stage fintech is credibility under constraint, not feature parity. Most of what I cut from the MVP wasn’t missed. That’s usually how I know the cuts were right.
The judgment I’d point to isn’t a longer feature list. It’s the foundation that still carries the product after the pitch deck is gone.