Yoked
Simplifying real estate finance for agents, builders, and lenders
Designed an AI sales assistant platform helping teams prioritize accounts, build deal packs, and generate outreach content. Created the information architecture, user flows, design system, and end-to-end experience.
AI-powered B2B sales platform
Lead Product Designer
UX Design · UI Design · Design System
Legacy Group Capital serves three very different audiences: agents who bring deals and referrals, builders who finance projects, and lending professionals managing deals internally. All three faced the same problem in different costumes — dense financial processes that made users work too hard to know where they stood and what to do next.
The core constraint: the business logic couldn't change. Lending is regulated and full of edge cases for a reason. My job was to make the complexity navigable, not to pretend it didn't exist.
Agent Portal: status at a glance
Problem: Agents submit deals, refer borrowers, and invest in Legacy's fund — but had no single place to track any of it. Status checks meant emails and calls.
Insight: An agent's mental model isn't "deals" and "loans" — it's my stuff, and whether it's moving. Status is the product.
What I did:
Built the dashboard around status-first scanning: deals and referrals side by side, each row reduced to what, when, and a color-coded status chip.
Replaced status labels with a nine-stage visual pipeline on deal pages (Submitted → Sold Out), paired with a timestamped activity feed — showing both where a deal is and what's ahead, which cut the "what happens next?" calls.
Kept analytics to a pulse check — two numbers, two bar charts. Agents needed a glance, not a BI tool.
Builder Portal: Less friction, honest numbers
Problem: Builders run projects, borrow against them across multiple loan types, and pick up Legacy-sourced opportunities. Onboarding was long and demanding, and requesting a loan was intimidating — the wrong first impression for a product handling millions.
Insight: The complexity wasn't the enemy — the sequencing was. Builders were asked for everything upfront, before seeing any value. And loans only make sense inside projects, not as a separate world.
What I did:
Simplified onboarding by asking only for what the next screen genuinely needs. [Add: X steps → Y steps]
Structured the portal around the project–loan relationship — every loan links to its project and back, so builders never dead-end.
Co-led the redesign of the Request a Loan flow with PM and engineering, breaking it into logical sections shaped by which validations had to run server-side. [Add: before/after step count]
Made loan capacity visible and honest: total borrowed vs. credit limit as a progress bar ("Remaining capacity: $2.4M · 76% utilized") — killing the "can I even apply?" uncertainty upfront.
Lender Portal: the Deal Engine
Problem: Legacy's internal platform for managing deals: multi-step workflows, dense financial forms, charts, edge cases. Daily-use professionals faced walls of fields with no hierarchy — screens that demanded reading instead of scanning.
Insight: Working a deal is two alternating modes — orienting ("what state is this in?") and editing. The old screens collapsed both into one wall, so users paid the orientation cost on every visit.
What I did:
Introduced an Overview card at the top of every deal — key context before editing, no scrolling to reconstruct it.
Rebuilt editing in a 737px container: two-column layout, 24px spacing, fields grouped by meaning ("borrower details," "loan terms") instead of a field-by-field wall.
Applied progressive disclosure to break large forms into sequenced sections, with step boundaries validated against the business's own logic.
Learned the domain properly — digging into concepts like LTV with stakeholders — because a designer who doesn't understand a metric will mislabel or bury it.
When requirements shifted mid-project, I owned the ripple: updated the flow, revised screens, and documented it all in a Linear ticket so design, product, and dev shared one source of truth.
