7 Minute Read

CreditSeer

Most designers stop at the prototype. I built the LLM pipeline first, to design around what AI could extract, miss, hallucinate in cred agreements.

Duration
6 months (Scope->MVP)
Role
Product Designer
Team
1 PM, 2 ML,
1 Frontend
Context
GT FinTech Lab partnered with Atlanta-area regional banks to help speed up their loan turnaround without compliance risk. I focused on credit agreement analysis, the most time consuming step.
Results
Saved credit analysts ~50% of time
PROBLEM

Credit Analysts spend ~2 hours per credit agreement hunting for key terms buried in 100-200 page documents.

AI can make this faster, but if it hallucinates a value, that’s a compliance risk.

SOLUTION

AI-powered system that transforms complex credit agreements into a structured, source-grounded dashboard, cutting review time by 50%.

PROCESS  STARTS HERE
BUSINESS CONTEXT

For regional banks, slow loan cycle means lost deals. Before an analyst can assess risk, they spend 2–4 hours manually navigating  100–200 page documents.

Manual agreement review 2–4 hrs per agreement Analyst can't start work risk model + memo delayed Loan turnaround stalls approval + closing pushed out Bank loses the deal faster competitor wins the borrower

From stakeholder meetings + workflow mapping + secondary research

CONCEPT EXPLORATIONS

Analysts needed traceable data, engineering needed a feasible MVP, and leadership wanted portfolio-level insights.

Rapid prototyping surfaced the tradeoffs and helped identify the right direction.

*Experimented with v0 by vercel

TURNING POINT

We landed on a document-level dashboard that extracts key values from credit agreements for analysts.

Early testing revealed a major roadblock: The proprietary model wasn't reliable with real agreements yet and the UI couldn't gracefully handle its failures.

Testing with dummy data would have produced misleading insights since it didn't reflect analysts' real workflows. Building a reliable UX meant waiting for the model to mature, costing valuable stakeholder access and user testing time.

That became a product roadblock, not just a technical one, so I paused UI work.

SYSTEM DESIGN

I wanted to understand what such LLM models can reliably extract from credit agreements.

So I built a lightweight extraction pipeline first to design around those constraints rather than ideal outputs.

Preparation for the pipeline

Interviewed analysts on the values they need, then encoded patterns from 15+ agreements into an annotation schema.

Worked with ML engineers to design the annotation schema around how their model works.

Step 0

Full credit agreement PDF is converted into text

picture_as_pdf
Credit Agreement.pdf2.4 MB · PDF
Step 1

Agreement is split into section-aware chunks

Cover

CREDIT AGREEMENT — excerpt

$250,000,000 · REVOLVING CREDIT AGREEMENT

This CREDIT AGREEMENT is entered into dated as of March 15, 2024 among ACME HOLDINGS, INC., as Holdings, the Borrowers party hereto, and ROYAL BANK OF CANADA, as Administrative Agent…

Definitions

ARTICLE I — DEFINITIONS

“Applicable Margin” means, with respect to any Term Loan or Revolving Loan, the rate per annum set forth below…

“Effective Date” means the first date on which the conditions in Section 4.01 are satisfied…

Step 2

Model locates the exact clause block, then extracts the required value using hints from the schema

Given to Stage 1
Given to Stage 2
Output
Definitions

ARTICLE I — DEFINITIONS

“Applicable Margin” means…

“Borrowing” means Loans of the same Class…

arrow_forward feed in
psychologyStage 1model
arrow_forward returns
§ Definitions · p.12 · located block

“Applicable Margin” means, with respect to any Term Loan, a rate per annum equal to 2.50%.

arrow_forward feed in
psychologyStage 2model
arrow_forward returns
{ "fieldId": "applicableMargin", "value": "2.50%", "section": "Definitions", "page": 12 }
data_object Annotation schema
description margin.stage1.json
1
2
3
4
5
{ "fieldId": "applicableMargin", "anchorPattern": "Applicable Margin", "task": "locate definition block" }
data_object Annotation schema
description margin.stage2.json
1
2
3
4
5
6
7
{ "fieldId": "applicableMargin", "extract": { "valueType": "percent", "pattern": "rate per annum equal to" } }
Step 3

System then presents the value in the UI as a card source-linked to the document viewer

description Document viewer

ARTICLE I — DEFINITIONS

“Affiliate” means, with respect to a specified Person, another Person that directly or indirectly Controls…

“Agreement” means this Credit Agreement, as amended, restated, supplemented or otherwise modified…

Credit Agreement.pdf · Definitions · p.12

“Applicable Margin” means, with respect to any Term Loan, a rate per annum equal to 2.50%.

“Borrowing” means Loans of the same Class and Type made, converted or continued on the same date…

FRONTEND & IMPLEMENTATION

Now I could design components for what AI could do not just the happy path.


Impact?

For the design:

Cut design–engineering feedback cycles from weeks to days, enabling rapid iteration based on real failure modes

For Lab

Created shared UI infrastructure reusable across the other projects in the lab
IMPACT

Analysts reached review readiness in roughly half the time, without skipping verification or relying on opaque AI summaries.

Through analyst walkthroughs and internal testing on 15+ real credit agreements,we compared time spent locating, cross-referencing, and verifying key terms manually vs.time spent reviewing the same terms in CreditSeer’s workflow-aligned dashboard

The largest time savings came from
-> eliminating manual cross-referencing across definitions, pricing, covenants, and defaults
-> surfacing only analyst-relevant terms in one structured view
-> enabling instant source verification instead of page-by-page searching
REFLECTION

AI Tools Pushed Me Beyond UX Into System Design

Using AI tools like Cursor helped me move beyond just designing screens. I ended up building parts of the extraction logic as well, which changed how I think about the role of a product designer—as someone who shapes system behavior, not just interfaces.

Understanding the Domain Was Necessary to Simplify It

To design for credit analysts, I had to deeply understand how syndicated credit agreements work. Learning the domain was key to turning dense, fragmented information into something usable and coherent.

Early Access to Users and Data Matters More Than Process

Working in fintech made it clear that limited access to real users and agreements can slow down the right decisions. In trust-critical domains, getting early exposure to real data and analyst workflows is essential to designing something reliable.

Designing for Uncertainty Is Part of Designing for AI

This project reinforced that AI won’t always be right, especially in high-stakes workflows. Making uncertainty visible and designing clear fallback paths helped keep the product usable and trustworthy.