EasyKnock Financial Estimate Redesign

EasyKnock was a startup offering financial products to help homeowners access the equity in their homes. The legacy financial estimate was confusing and didn’t give customers the tools they needed to understand the product and make an informed decision.
2024
CLIENt
Role
UX Lead

Background

Problem

After an online financial prequalification, the next step was a call with an Account Executive (AE). During this call, the AE walked customers through the initial estimate. The estimate showed high-level numbers with no clear explanation, used financial jargon and EasyKnock-specific terms, and wasn’t mobile-friendly.

This design slowed down the sales process and hurt customer trust. AEs had to spend multiple calls explaining the estimate, and even then, many customers still didn’t fully understand how the product worked. The estimate felt confusing and opaque. The legal team prioritized improving this, since it was critical for customers to understand the product.

Customer Financial Strain


Many customers were in difficult financial situations, using their homes as a last resort. Relying on their home as a last resort was emotionally difficult. The product itself was complex, and EasyKnock wasn’t well-known, so building trust was a challenge. Customers were especially afraid of making a bad decision with their homes on the line.
Additionally, most were not financially or tech savvy, and 80% of traffic came from mobile. So the redesign had to be clear, transparent, and mobile-first.

My Role


I led the UX work in collaboration with the B2C product owner, working across departments. This was a cross-functional project with a big impact on the top sales funnel. I focused on user needs while mediating between departments to balance user goals and business priorities.

Process and Impact

Research

Stakeholder Collaboration

I partnered with my PM to identify and involve key stakeholders. We ran design thinking sessions with sales, marketing, branding, legal, engineering, and product to understand internal pain points and perceived user needs.

Call Analysis

I listened to 20 recorded AE calls to find user pain points, common questions, and behavioral patterns.

Personas & Journey

Based on stakeholder input and call findings, I built a persona and detailed user journey. These artifacts were shared and refined collaboratively and were later reused for other projects.

Sell & Stay Main Persona
Sell & Stay User Journey

Competitor Analysis

I researched competitor flows and best-in-class similar experiences to find patterns and inspiration for solving different sections.

Patterns found in similar experiences

Scoping & Limitations

We defined the initial project scope and long-term goals, considering not just user and business needs, but also tech and legal constraints.

Prototyping


We prioritized mobile-first design while also creating responsive layouts. I created quick prototypes and ran iterative reviews with stakeholders:

  • Tech: to check feasibility
  • Sales: to align on presentation and business needs
  • Marketing: to ensure voice and brand consistency
  • Legal: for compliance
  • The project evolved over several iterations as the business changed.

    First Iteration

    Focused on visual refresh, copy updates and mobile adaptation to match new branding. This also gave engineers time to update backend logic. Also, the first iteration for the sales team wasn't radical.

    Full Redesign Iterations

    The second and main iteration addressed structure, legal language, A/B tests, and ongoing adjustments to business rules.

    Key Design Decisions
    AE Name and Photo

    Added to build rapport. Included full contact info to help customers easily reach out.

    Progressive Disclosure

    Financial info was split into three logical steps, at closing, as a renter and lease end. This made the experience easier to follow and helped structure sales calls. It solved several problems:

    • Customers were overwhelmed by the long scroll
    • They jumped ahead before AEs could explain
    • It made navigation easier for older users
    Clear Context & Tooltips

    We added inline copy to explain key sections and tooltips for less common questions. This helped customers understand and also made it easier to share details with partners without needing extra calls.

    Charts

    Simple visuals made money breakdowns easier to understand. Users found plain numbers confusing or untrustworthy.

    Reframed Financial Logic

    We kept the math but changed the framing. Instead of presenting how underwriting thought about the deal, we explained how using their home equity could help customers access cash.

    Copy

    Used clearer, shorter language. We avoided jargon and aimed for more empathetic messaging. We made some compromises with the legal team, but still tried to simplify the language as much as possible within compliance limits.

    Calculators

    Added interactive tools so customers could explore different scenarios on their own instead of relying on sales to send multiple estimates.

    Testing

    We ran multiple rounds of testing using usertesting.com, focusing on specific areas of the estimate. We used feedback to iterate and test again. We also tested the final version with customers who had recently gone through the process. We A/B tested copy as well.

    Usertesting.com round of testing summary. We designed the testing, screened participants and selected the most closer to the customer.

    Defining Metrics

    Despite frequent changes to fees, scripts, and policies, we worked to define metrics that could be reliably tracked.

    Developer Handoff

    Everything was documented in Figma, including notes, prototypes, and videos to explain interactions.

    Outcome

    Impact

    Fewer Sales Calls

    Average calls dropped from 3 to 2 before customers signed a purchase agreement, which was the next milestone in the sales funnel.

    Increased Estimate Visits

    Estimate views went up, signaling stronger engagement (exact number not available).

    Portal Account Creation

    More customers signed up for the portal after viewing the estimate.

    Navigation Clarity

    Users navigated between different sections, showing the navigation was clear.

    Stakeholder Buy-In

    Involving stakeholders early helped build alignment, supporting decisions and made design approvals smoother for this and future projects.

    User Feedback

    Post-redesign interviews showed customers understood more, reported fewer questions, and trusted the product more thanks to the clearer visuals.

    Sales Feedback
    • Conversations were easier to lead
    • Common questions decreased
    • New sales team members had a lower learning curve
    • The initial sales cycle was shorter
    • Customers better understood the deal's complexity

    Main Learnings

    • Testing helps validate user understanding and builds stakeholder alignment
    • Balancing many stakeholders is tricky, but taking a step back to align everyone with user and business needs helped move things forward.
    • Simplicity wins, users don’t want complexity, just clear and helpful design
    • When working with multiple stakeholders who have fixed approaches, starting with small changes to improve the experience can help build trust
    next

    Citi UX Leadership

    I led a team of talented creatives, including UX architects, visual designers, and a copywriter, and collaborated with cross-functional colleagues such as product owners, researchers, strategists, subject matter experts, and engineers. Our objective was to deliver engaging designs that simplify the complex world of finance and humanize the banking experience.