Home Portfolio AFT - Timeline for Syndicate Fintech Loans
Agentic AI Enterprise B2B

Deals don’t fail.
Visibility does!

An AI-driven decision-support timeline for syndicated-loan finance - turning deal activity into decisions, with an agent that acts on them.

Try the Live Demo (opens in a new tab)
The Product

A real fintech client - syndicated-loan, cross-organizational deal operations.

My Role

Product Designer - domain research, UX strategy, and end-to-end UI design.

Scope

The decision-support timeline - my design end to end, from research to hi-fi UI.

Under NDA - every name, screen and data point here was recreated from scratch. Nothing is client material.

Problem

The Hidden Cost
of Missing Visibility

Deals don’t slow down because of decisions. They slow down when no one knows what’s missing - or who owns it.

On a syndicated-loan fintech platform for cross-organizational trading data, teams couldn’t answer one question: where does the deal stand? Management asked for confidence and transparency - that brief became the timeline.

Deal Workflow diagram - illustrative scenario, fictional data reflecting the platform's real client profile
What kept slipping:
Approval bottlenecks
Fragmented information

The market’s own math: LSTA data.

Standard is T+7 · 2024 average ≈ 16 days
only ~29% settle within a week

Visibility alone doesn’t solve the problem

Teams Didn’t Need More Data
- They Needed Clarity on What to Act On

PROBLEM
  • No visibility across deal stages
  • Delays caused by approvals
  • Cross-team coordination overhead
DATA
  • Dozens of tasks and documents
  • Many owners, many dates
  • Every status - no priority
DECISION
  • What needs action now?
  • What’s blocking progress?
  • What matters most?
Research

Exploring
Unfamiliar Domain

  • Mapped syndicated transactions: phases, documents, approvals
  • Analyzed where manual workflows create bottlenecks
  • Charted roles and approval responsibilities across organizations
  • Benchmarked the tools deal teams actually use
Research artifact - mapping the syndicated-loan domain

What Existing
Tools Miss

No tool combines Gantt-grade planning UX with loan-market semantics - that became the design opportunity.

Finastra logo

The market’s servicing backbone - used by 21 of the top 25 syndicated lenders.

Gap: back-office servicing, not a planning UX for deal teams.
Versana logo

Industry-backed real-time agent-data platform (J.P. Morgan, BofA, Citi).

Gap: data transparency - not workflow planning.
S&P Global logo

The market-standard platform for settling syndicated loan trades between institutions.

Gap: covers settlement at the end - not the planning and coordination before it.

Roles

I evaluated each role through 4 lenses:

Pain points Emotional impact Solution Target impact

Insights

Each role has unique needs within the transaction. One requires full control over deal progress, another prioritizes certainty in terms and commitments, a third focuses on regulation and risk, while the last demands full transparency in financing and financial conditions.

Role persona 1 Role persona 2 Role persona 3 Role persona 4
Solution

Coordinating Work
Across Teams

Designed around the Transaction Manager - the role that owns execution across banks, legal and compliance - with tailored views for underwriters, compliance officers and bankers.

Each role contributes tasks and approvals.
The timeline connects everything into one coordinated system.

The object model behind the timeline (OOUX): phases, tasks, documents and signatures as connected objects.

OOUX object model behind the AFT Timeline - user interaction diagram

What Needs
Action Now

A deal is months of dependent work under deadlines - exactly what a Gantt shows best. I built the solution as a Gantt: phases, dependencies and risks on a single time axis. No market tool offers this view.

1
Phases

Structure the process.

2
Teams

Every role works on the same shared time axis.

3
Decisions

Highlight what needs attention and suggest next steps with AI.

AFT Timeline product screenshot - Gantt view with numbered callouts

Blockers & Risks

1
What’s blocking progress?

AI identifies blockers that require action.

2
What’s at risk?

Predicted risks help teams act before delays happen.

When flagging isn’t enough, the agent acts. ✦ Magic Pro - next
Timeline showing blockers and risk flags, including a Missing Approvals alert
Key Decisions

Early Explorations -
Reconstructed

Direction A

Flat task list. Rejected: months of deal work became an endless scroll; no sense of phase or progress.

Direction A - flat task list wireframe (rejected)

Direction B

Alerts in a separate panel. Rejected: problems lost their time context; users had to map each alert back to the timeline themselves.

Direction B - separate alerts panel wireframe (rejected)

What I Chose
& What it Cost

Every decision below began as one of those explorations.

1
Hierarchy over
flat list

Considered: a flat task list - familiar, zero learning curve.

Chose: Phase → Sub-phase → Tasks.
Cost: Deeper navigation.
Gain: Months of deal noise, filtered.
2
Alerts inside the
timeline

Considered: a separate alerts panel - a cleaner Gantt.

Chose: Alerts on the bars themselves.
Cost: Visual load.
Gain: Problems visible in time context.
3
Hidden by
default

Considered: exposing every action and field - more discoverable.

Chose: Hidden Actions + role-based Table Fields.
Cost: Discoverability.
Gain: A calm screen for all-day users.
Magic Pro
✦ Magic Pro

From Showing Risk
to Proposing Action

I mapped the agent’s autonomy to its confidence - human-in-the-loop by design: it proposes when sure, steps back when unsure, and automates only what you approved in advance. Calibrated trust.

The result: it earns trust one rung at a time, and never acts where you can’t see it or stop it.

Simple Example
Problem: Deadline is close and 9 of 24 users haven’t signed - a bottleneck that will delay Board Approval. Solution: Magic Pro detects it and reminds every pending user - fast. Decision: A routine, low-risk call - and it runs automatically.
Magic Pro flow: 1. Detects the bottleneck on the timeline, 2. Acts automatically behind the scenes, 3. Shows its work in the Gantt

Not Every Decision
Is That Simple.

CONFIDENT

The agent proposes a complete action.

  • Proposes the action, backed by evidence
  • Shows the cost of ignoring it
  • Waits for you: Approve · Edit · Dismiss
Magic Pro suggestion card - confident state, proposing Approve & Send
UNCERTAIN

The agent steps back and stays honest.

  • Not enough signal - it doesn’t guess
  • Flags the risk and explains why
  • Nothing is sent
Magic Pro suggestion card - uncertain state, flagging risk without acting
Outcomes

Projected Impact -
What Changes When The Timeline Goes Live

Up to50%
Approval-related delays
Across100%
Real-time status of deal stages
~35%
Coordination time
  • These are projected design targets, benchmarked against McKinsey’s 20-50% productivity-uplift range for modernized syndicated-loan operations.
What
I Learned

Good design respects how each role works - not averaging everyone into one “user”.

I learned to break a high-stakes, unfamiliar domain into small steps I could verify.

The biggest lesson: teams don’t need more information - they need to know what to act on.

Thank
You
Try the Live Demo (opens in a new tab)

Next Case

SyncOps - incident boards and live map
Agentic AI Enterprise B2B UX Research & Design

From monitoring to deciding -
The agent proposes. The admin decides.

Agentic dispatch for fiber network operations.

Estimated ~50% faster task assignment
Try the live demo (opens in a new tab)
EXPLORE