Case study · AI-powered B2B product

Synapse: redesigning an AI mortgage broker application

Synapse: redesigning an AI mortgage broker application

Synapse: redesigning an AI mortgage broker application

I redesigned the platform brokers use to upload documents and review AI-generated reports, so the interface keeps up with the speed of the AI.

Role

Product owner & UX/UI designer

Team

Team of 2

Duration

4 weeks

Platform

Web application

Add image: Hero: the three final Synapse screens (dashboard, documents, report)

What Synapse does

What Synapse does

What Synapse does

Synapse is an AI-powered platform that helps mortgage brokers and lenders process document-heavy applications. It reads the applicant’s documents, generates a report, and flags data points that don’t match so the broker can resolve them or follow up with the applicant. The client’s customers are mostly in Canada, with some in the US.

Value

Less human effort and time spent on document processing, with a more accurate result.

Objective

Redesign the platform to improve the user experience and make it ready to scale.

The AI was fast. The interface was holding it back.

The AI was fast. The interface was holding it back.

The AI was fast. The interface was holding it back.

Synapse already cut manual document review from hours to minutes. The benefit never reached brokers because the product was hard to use.

2–4 hrs

Lenders, manual review

1–1.5 hrs

Brokers, manual review

10 mins

With Synapse

What was going wrong

What was going wrong

A poor interface frustrated less tech-savvy users.

Client engagement was low because the design wasn’t intuitive.

Brokers struggled to navigate the system despite the AI’s benefits.

Key insight

AI reduced processing time, but the poor experience stopped brokers from adopting the platform. That lowered client engagement and retention.

Starting point: auditing the existing product

Starting point: auditing the existing product

Starting point: auditing the existing product

I reviewed the three core screens and mapped what was getting in the way.

Add image: Old screens: applications dashboard, document management, AI-generated report

Applications dashboard

Applications dashboard

Wasted space and no analytics.

Document management

Document management

Usability issues and an unclear upload flow.

AI-generated report

AI-generated report

No scalability, no hierarchy, repetitive data.

Who I designed for

Who I designed for

Who I designed for

Research and periodic user feedback pointed to one core user: the mortgage broker.

James

James

Mortgage broker, 50 years old

Pain points

Time-consuming processes

High costs

Errors in data

Limited growth

Employee burnout

Goals

Save time

Improve accuracy

Deliver better service

Focus on clients

Handle more applications

Designing for efficiency, one iteration at a time

Designing for efficiency, one iteration at a time

Designing for efficiency, one iteration at a time

Discovery

Discovery

I walked through the existing flow screen by screen and annotated what got in the way: an almost empty landing page, a menu that didn’t show the active item, unclear labels like Assets, Liabilities and Property, and no way to open a document straight from the report.

Add image: Annotated audit of the existing flow

Ideation

Ideation

I started with sketches and low-fidelity wireframes to explore the dashboard, document upload and report layouts quickly.

Add image: Hand sketches and low-fidelity wireframes

User flow and statuses

User flow and statuses

I mapped the full application lifecycle and decided on the statuses, so brokers always know where an application stands and what to do next.

Add image: Swimlane flow: awaiting documents, document submission, generating report, report ready

Prototype and iterate

Prototype and iterate

I built low-fidelity prototypes and demoed them to the client. After several rounds of feedback and added feature suggestions, I finalised a high-fidelity design in the client’s design system.

Add image: Low-fidelity report prototype

Application statuses

Awaiting documents

Processing

Report ready

Needs review

On hold

Resolved

How the design evolved

How the design evolved

How the design evolved

Each core screen went through four to five versions, shaped by client feedback and what brokers needed day to day. Here is where each one started and where it landed.

Dashboard

Dashboard

Before

Add image: Old dashboard screen

Main column wasn’t emphasised

Text links for actions instead of icons

Weak pagination

No status chips

Poorly placed main call to action

No search or filtering

After

Add image: Final dashboard screen

Metrics added at the top, based on client demand

Colour-coded status chips

First column looks clickable

Clearer date format

Better pagination and a better placed main call to action

Applicant email access

Documents

Documents

Before

Add image: Old documents screen

Documents weren’t well organised

The design wasn’t scalable

Uploading documents was challenging

After

Add image: Final documents screen

Documents grouped by borrower, co-borrower and miscellaneous, with a clear message for unsupported files

Tab bar per category to reduce scrolling

Upload sidebar moved to the right, consistent with the report page

Generate report button for more control

Send email to the applicant, and archive actions

Unnecessary elements removed

Report

Report

Before

Add image: Old report screen

Didn’t scale to more documents and data points

Difficult navigation

No applicant name or ID

After

Add image: Final report screen

Documents tab and back button for easier navigation

Applicant name and ID always visible

Only the validated value shown instead of every variation

Property data points added

Borrower and co-borrower data clearly separated

Export replaced by emailing the report straight to lenders

The result

The result

The result

Clients found the new interface modern and intuitive, and satisfaction improved. The redesign helped the startup attract new customers, and they were happy with the outcome.

Reflections and what’s next

Reflections and what’s next

Reflections and what’s next

Challenge

Managing a short timeline while keeping the design quality high.

Opportunity

Usability testing would have added deeper insights, but it wasn’t feasible in the timeline. The report flow is where I’d test first.