Main Street Renewal · 2023–2024

Reimagining the Lease Application

Turning a costly, fragmented application into a guided resident experience — while creating a foundation that could scale beyond the application itself.

Role
Lead Product Designer
Led product strategy and end-to-end experience design from problem definition through launch.
Responsibilities
Product strategy
Research & insights
UX/UI design
Prototyping
Systems & patterns
Partners
Product management
Engineering
QA
Leasing operations
Business stakeholders
Product ecosystem
Application
ID & Income verification
Household management
Payment
Application status
Renewal
Resident portal
My focus
Move the team beyond redesigning a form and toward a connected resident experience — simplifying today's application while establishing patterns that could scale across products.
Impact
A simpler experience for applicants — and a more efficient process for the teams supporting them.
+71%
Increase in
lease conversions
−60%
Reduction in
support calls
6 → 1
Days to average
application approval
~75%
ACH adoption
up from ~40%
The Experience

One resident journey, redesigned from application to approval.

The redesign connected application, verification, status, and payment into a clearer experience for prospective residents.

01 Application
Redesigned rental application
02 Status Board
Redesigned applicant status board
03 Payment
Redesigned resident payment experience
01
Apply

A clearer application with stronger navigation and integrated verification.

02
Track

Applicants could see progress, household status, and what needed to happen next.

03
Pay

A reusable payment experience designed to extend beyond the application.

01 · The Challenge

The application was only one part of a much larger problem.

Main Street Renewal manages thousands of single-family rental homes across the U.S. The application was often the first meaningful interaction a prospective resident had with the company—and the experience was falling short.

Applicants navigated a lengthy, outdated application with little guidance about what came next. Manual verification and operational processes created additional work for leasing teams.

Design constraint

The existing experience was constrained by Yardi.

Yardi's design limitations restricted how much we could improve the application within the existing platform. The redesign required us to rethink not only the interface, but the system supporting it.

Business impact

Across the resident lifecycle, Amherst was spending approximately $1M annually on customer service calls.

The opportunity wasn't simply to make the application look better. We needed to reduce friction for residents while reducing the operational work required to support them.

01

A broken first impression

Outdated UI and limited guidance made the first interaction feel harder than it needed to be.

02

Slow approval

Manual identity verification and screening created operational work and slowed the path to approval.

03

Application drop-off

Lengthy requirements and mobile friction caused applicants to abandon before completion.

04

One payment platform

Moving to Stripe created an opportunity for a scalable payment experience across the resident lifecycle.

02 · Research

Understanding where the experience was breaking down.

We combined an audit of the existing application with product data and feedback from applicants and leasing teams to understand where people were getting stuck—and where those problems created more operational work.

01 Experience Audit

Mapping the existing experience

Our PM and I mapped the application end-to-end to identify friction, dependencies, and where the experience was creating unnecessary complexity.

02 Product Data

Finding where applicants dropped off

Funnel data showed where applicants were abandoning the process. With ~80% of applicants on mobile, mobile friction couldn't be treated as a secondary problem.

03 Feedback

Connecting applicant and operational pain

Feedback from applicants and leasing teams helped us understand where confusion was creating support calls, manual work, and delays in the application process.

What became clear

The problem wasn't simply that the application was too long.

Applicants needed to understand where they were, what they needed to do next, and what other household members were responsible for. Those same gaps were creating additional work for leasing teams.

Platform shift

The application needed more than a redesign.

Yardi's design limitations constrained how far we could improve the experience. Rather than continue working around those limitations, the team moved toward a custom application experience with greater control over the resident journey.

Existing platform Yardi Limited design flexibility
New foundation Custom Experience More control + scalable patterns
The strategic shift
Instead of asking

How do we redesign the application?

We asked

How do we create a resident experience that removes unnecessary complexity from the entire journey?

Key Design Decisions

Making the application easier to understand and complete.

The redesigned status experience gave applicants more visibility into what was happening, what still needed to be completed, and what to do next.

Before

Applicants were left waiting without enough context.

The original experience provided limited visibility into application status, pending household actions, fees, or what applicants needed to do next.

Previous application status experience
After

One place to understand progress, responsibilities, and next steps.

01

Clear next steps

Surfaced required actions and important updates in one place, so applicants always knew what to do next.

02

Clear progress

Reorganized the experience around understandable stages so applicants could see where they were in the process.

Annotated redesigned application status experience
03

Application status

Made pending steps and household progress visible instead of leaving applicants waiting without context.

04

Fee transparency

Surfaced payment requirements earlier so applicants could understand costs before reaching checkout.

Identity & Income Verification

From manual review to a guided application.

The redesign didn't just simplify the interface. It brought identity and income verification into the application, reducing manual work while creating a clearer path for applicants.

Redesigned application experience
Original application experience
Before
After
01

Verification happened outside the application.

Identity and income information required manual review by leasing teams, adding operational work and slowing the path to approval. Applicants also had limited guidance on what happened next.

02

Verification became part of the application.

Identity and income verification were integrated into the experience and moved later in the flow—reducing manual work while letting applicants build momentum before completing more time-intensive steps.

Design decision

Put the more demanding steps at the right moment.

Identity and income verification were new steps and could take additional time to complete. Rather than introduce that friction early, we moved verification later in the journey after applicants had already made progress.

Payment Experience

One payment experience. Multiple resident journeys.

ACH, card, and autopay patterns were designed to extend across application, renewal, and the resident portal — using the new payment platform, Stripe.

01

Rent payment selection

Clearer guidance helped residents add payment method and payment amount.

02

ACH setup

Simplified bank account setup while keeping the payment flow focused.

03

Card payment

A consistent card experience gave residents another clear way to pay.

04

Autopay

Reusable payment patterns created a foundation for recurring rent payments.

03 · Scalable Foundation

Building a system, not just screens.

Moving away from Yardi gave us more control over the experience—but also meant creating a foundation that could scale. We built a shared design system and aligned it with Tailwind CSS, creating reusable patterns across design and development.

Forms
Form components from the design system
Actions
Button and action components from the design system
Status
Status components from the design system
Navigation
Navigation components from the design system
Payment
Payment components from the design system
Illustrations
Feedback and alert components from the design system
From design to development
Design Figma Design System

Shared components, interaction patterns, states, and standards created a common foundation for the resident experience.

Development Tailwind CSS

The design system was aligned with reusable Tailwind patterns, helping design and engineering work from a more consistent implementation foundation.

Built to scale across
01 Application Forms, verification, status, payment
02 Resident Portal Payments, account management, status
03 Renewal Reusable resident and payment patterns
Impact

Less friction for applicants. Less manual work for leasing teams.

The redesigned experience improved conversion, reduced support needs, and shortened the time it took applicants to move through approval.

71%
Increase in lease conversions
60%
Reduction in support call volume
1 day
Average approval time, down from ~6 days
75%
ACH adoption, up from ~40%
Reflection

The redesign solved the immediate problem—but revealed the next one.

Post-launch data showed that primary applicants still struggled when asked to provide information for other household members, especially on mobile.

The next opportunity would be to rethink the household application model entirely—allowing each person to complete their own portion instead of relying on one applicant to collect information for everyone.

What I'd explore next

A co-application model that gives each household member ownership of their part of the application while keeping the overall status visible to the primary applicant.