Maestro AI

Maestro AI is Nesto's internal underwriting workspace. When a mortgage application lands, it checks the file against policy — credit, capacity, character, and the documents behind each one — then shows the underwriter what cleared, what failed, and what still needs a decision.

The point was never to automate the decision. It was to remove the manual reading so underwriters spend their time on the exceptions that genuinely need judgment, with every check traceable back to the document it came from.

Maestro AI review workspace with identification documents open
Goal
100x faster underwriting review
Role
Sole Senior Designer
Timeline
7 months

Understanding the user

Underwriting is expert work under time pressure. These notes came out of sitting with reviewers.

Job to be done

Time is spent reading, not deciding

Underwriters weren't slow at judgment. They were slow because every file had to be read in full before they knew what actually needed them.

Risk

Trust is the real bottleneck

If they don't believe Maestro, they re-check everything. Speed features don't matter if the habit is to verify by hand.

Behaviour

Exceptions first, always

They scan for what's wrong. Completed checks are noise. Failed and warning states have to be louder than approvals.

Mental model

Checks are connected

A credit flag can change capacity. Horizontal links have to be visible or they lose the thread of why a decision was made.

Need

The decision still belongs to them

Policy isn't perfect. They need to override a check, attach a reason, and keep the file moving without fighting the system.

Context

Built for long desktop sessions

This is expert software. Density, keyboard reach, and staying in one workspace beat a simplified, consumer-like UI.

How the review works

Exceptions first, judgment last

01

File lands in the queue

Application, documents, and prior context arrive together.

02New

Automated checks run

Credit, capacity, character, and supporting documents are validated against policy.

03New

Only exceptions surface

Cleared checks collapse; missing or conflicting evidence is flagged.

04New

Underwriter decides

Approve, request more evidence, or decline, with reasons captured in place.

05New

Decision recorded

Rationale and audit trail stay attached to the file.

The reading is automated and the decision is not. Underwriters open a file already triaged, with every check linked to its source.

Architecting the experience

Three levels of depth, each one answering the question an underwriter asks next. Every level is a different fidelity of information.

I mapped the experience this way because of the goal: 100x faster review of a single file. Speed alone was never going to get us there. If underwriters didn't trust Maestro's decisioning, they would fall back on the habit of reading every detail themselves — enough to win minutes, nowhere near enough to win orders of magnitude.

So the levels are really a trust ladder. Level 1 asks you to trust the outcome, level 2 shows the reasoning behind it, and level 3 hands back control when that reasoning is wrong. The bet was that as trust built, underwriters would skip approved checks entirely and spend their time only where there were warnings or failures.

  1. Level 1

    Show me the decision

    Highlight the key data points inside the application for the underwriter as fast and as accurately as possible.

  2. Level 2

    Show me how Maestro made the decision

    Open up what sits under the hood of a decision and why Maestro approved or flagged something. The data has to tell a story an underwriter understands. Data points from horizontal checks often change the status of other checks, so it has to be obvious where you are, what is linked, and the decision path that was taken.

  3. Level 3

    Allow me to control the decision

    Underwriting is not a perfect science, and there are rules that sometimes need to be broken or overwritten. This level is about enabling the underwriter to act on the data or the documents to control the decision of a check, and ultimately the decision on the file.

From intake to recommendation — a structured path that keeps underwriting fast, auditable, and collaboratively owned.

Maestro AI review workspace

Built as a desktop-first system for complex file review — dense enough for power users, calm enough for long sessions of focused decision-making.

Maestro AI identification checks panel

Clear signals

Risk, document gaps, and next actions are prioritized so reviewers know what needs attention — and what can wait.

Maestro recommendation to conditionally approve
Maestro AI submit application confirmation

Validated decisions

All of Maestro's decisioning is easy to discover, so the underwriter can validate checks, documents, and decisions at the speed of thought.

Maestro AI identification documents panel
Maestro AI identification checks, 6 of 6 passed
Maestro AI document verification modal
Maestro AI extracted applicant data

Review notes

Notes are written automatically for the underwriter, based on their notes. The underwriter always owns the final set that is submitted with the application.

Maestro AI notes workspace with Assets and Income notes
Maestro AI Assets note card with a note hovered
Maestro AI Assets note card with the composer open

Next project

Rekwai

Rekwai

AI-enabled requirement and RFP management