Lead Product Designer/2022/Fintech
Shipping an investor-ready hard-money lending platform on an MVP timeline
I led the design of a hard-money lending platform built by RevStar — shaping the borrower, lender, and operator experience for a product that needed to look investor-ready from its first day of public use. Real money flowed through it from launch, on an MVP timeline that left no room for traditional research phases, and the version that shipped had to earn its credibility on the first screen.
Hard-money lending needed to feel investor-ready, not just functional
Hard-money lending sits in a corner of fintech where the people lending and the people borrowing both make six-figure decisions on short timelines. The existing workflows were technical, fragmented, and built by engineers for engineers — a borrower might be looking at a loan structure beside a lender reviewing the same deal beside an operator approving disbursements, all using interfaces that assumed everyone already knew the terminology.
The bigger problem was that RevStar’s clients were trying to use the platform in investor pitches, where the audience hadn’t built that vocabulary yet. The constraint that mattered wasn’t speed; it was that whatever shipped had to look like a product people would invest in. A lending workflow that’s technically correct but visually fragmented loses credibility before it loses users.
Three audiences, one platform, no time to test
Because formal testing wasn’t an option, research had to come from the work itself. I sat in on client review sessions, watched investor demos, took notes during engineering implementation conversations, and ran the borrower flow end-to-end myself enough times to catch where the assumed-knowledge gaps lived. Patterns surfaced fast — financial terminology that made non-technical users hesitate, dense screens that hid the next step, workflows that worked for operators but read as opaque to anyone watching over their shoulder.
The reframe was that clarity wasn’t a polish pass — it was the feature. Adding more capability to a platform that already overwhelmed its users would have made the credibility problem worse, not better. The hard part of the MVP wasn’t going to be deciding what to build. It was going to be deciding what not to.
Clarity was the feature
I rebuilt the workflows around a shared structural language: each step states what’s being decided, who decides it, and what the next action looks like. Hierarchy got tightened so that the screen’s primary intent reads before anything secondary — a borrower sees their next-due payment, a lender sees pending deals, an operator sees blocking approvals, and each role gets a different home screen built from the same components. Navigation between sections and data views was rebuilt so a user reviewing a deal doesn’t lose context when they click into a related document.
Component consistency was the leverage point under MVP constraints. By committing to a small, predictable set of UI patterns and not introducing one-off layouts, the platform reads as deliberate without slowing engineering down. Integrated support touchpoints — inline help, contact prompts, embedded explanations — handle what would normally require a separate help center. The platform feels designed even though the timeline didn’t leave room for the kind of polish phase a non-MVP product would get.
Shipping fast doesn’t mean shipping shallow
The MVP shipped on time and held up in front of investors — which is the actual delivery target for early-stage fintech, not feature parity. A few capabilities I’d scoped on the design side didn’t make the cut, and most of them were the right things to cut. What stayed in was the structural clarity. What got deferred was depth that could be layered on without disturbing the core experience later.
What stayed in the build is what I’d point to. The structural language — same components everywhere, primary intent above secondary, role-specific home screens built from the same kit — survived every feature added on top of it later. Most of what I cut from the MVP didn’t end up missed. That’s usually how I know I cut the right things.