← Back to Work
AI Fintech Spec Project

Horizn

A spec project turned deep exploration: designing an AI-powered financial intelligence platform while using AI tools to accelerate every phase of the design process.

Role Product Designer
Context Interview Spec → Course Project
Platform Web (Next.js)
Try the Prototype →
Horizn Financial Intelligence Platform — deck editor with AI assistant
The Problem

Finance teams spend 80% of their time copying data into PowerPoint. The workflow is fragmented across Snowflake, Excel, and slide tools — every handoff introduces risk, outdated numbers, and hours of rework.

The Outcome

A functional prototype and a case study in AI-assisted design — from synthetic research and bias-corrected personas through to a production-grade Next.js prototype.

01 Discovery & Research

This started as a design exercise for an interview — design an AI-powered platform for finance teams building board presentations. I took the brief further during an AI in UX course, using it to explore how AI tools could accelerate every phase of design, from research through prototyping.

Without access to finance teams for primary research, I used AI tools to build a synthetic research foundation, then critically evaluated the outputs for bias.

Competitive Analysis (Perplexity)

Mapped direct competitors — Blueflame AI, Samaya AI, Rogo — and the broader finance AI landscape. Key finding: most tools were still chat-centric. No single product connected data ingestion, analysis, and presentation end-to-end.

Market Gaps Identified

Three gaps emerged: no tool connected all workflow stages, trust/data lineage was a prerequisite not a feature, and generic AI couldn't understand the financial narrative a CFO needs to tell.

Synthetic Survey & Analysis

I designed a 30-question survey targeting finance professionals, then used Gemini and Claude to generate 50 synthetic responses with realistic variation across roles, firm sizes, and experience levels.

78.4
Avg. hours worked per week
Corrected: 65-85 range, varies by firm type
29.5%
Time on manual production work
Corrected: 35-55% for junior roles
62%
Dissatisfied with time allocation
Corrected: 30-40% are "satisfied grinders"
64%
Already using AI tools at work
Top frustration: generic outputs, no firm style
The bias correction was the more valuable step.
Synthetic data flatters you with clean patterns. The averages smoothed over real-world variation — a PE analyst at a mega-fund works 70-85 hours; at a boutique, 50-70. The original data modeled uniform dissatisfaction, but in reality 30-40% of finance professionals accept the hours for compensation and exit opportunities. Questioning the data produced more realistic and nuanced personas than the raw outputs.

Bias-Corrected Personas

Three personas emerged from the corrected data, each with explicit limitations: good for structuring research and brainstorming features, not for precise market sizing or external claims.

Private Equity
Jordan
The Overextended Deal Team Member
65-85 hour weeks, variable by deal flow. Fragmented institutional knowledge — prior deal insights are buried in emails and memos nobody can find.
"I spend 15-20 hours every IC just trying to find what we learned from similar deals."
Equity Research
Emma
The Overwhelmed Researcher
Drowning in document volume — filings, transcripts, alt data, news. Spends 60% reading, 40% actually analyzing. Fighting to remain an analyst rather than a summarizer.
"I need to expand coverage but I'm already reading 12 hours a day."
Investment Banking
Alex
The Builder
Trapped in "production hell" — spending 40-50% of time on formatting and pixel-perfect deck generation instead of analysis and client work.
"I didn't get into banking to be a PowerPoint operator."

Core User Flow: AI Content Generation

I mapped four core workflows as Mermaid diagrams. The AI content generation flow was the most critical — it shows how a user goes from asking a question to getting AI-generated content inserted into a slide with a full audit trail.

flowchart LR
    A["Select Slide\nwith Data"] --> B["Open AI\nAssistant"]
    B --> C{"Request Type"}
    C -->|"Explain Variance"| D["Build Prompt"]
    C -->|"Generate Content"| D
    C -->|"Rewrite/Edit"| D
    D --> E["Query\nSemantic Layer"]
    E --> F["Fetch Current &\nHistorical Metrics"]
    F --> G["Search Prior Decks\nfor Style Patterns"]
    G --> H["Generate Draft\nCommentary"]
    H --> I["Display Draft\nin Chat"]
    I --> J{"User Reviews"}
    J -->|"Accept"| K["Insert into\nSlide"]
    J -->|"Refine"| D
    J -->|"Reject"| L["Discard"]
    K --> M["Create Audit\nTrail Entry"]

    style A fill:#f5f5f0,stroke:#999,color:#111
    style D fill:#f5f5f0,stroke:#999,color:#111
    style H fill:#e8f5e9,stroke:#4caf50,color:#111
    style K fill:#e8f5e9,stroke:#4caf50,color:#111
    style M fill:#fff3e0,stroke:#ff9800,color:#111
        

AI Content Generation Flow — from user question to slide insertion with audit trail

02 Definition & Design Goals

The synthetic research and competitive analysis converged on four design goals:

Live Data Binding

Data must be live-bound to its source with visible connection health. No stale numbers, no manual refresh cycles.

Contextual AI

AI assistance must understand the data, the deck, and the story being told — not just generate generic summaries.

Calm Interface

The interface must feel professional for long focus sessions — CFOs spend hours preparing board decks. No visual noise.

Full Traceability

Every number must be traceable back to its origin. Data lineage extends from the pipeline through AI-generated insights to the final slide.

03 Design Solution

The platform has three core screens, each solving a specific stage of the finance workflow.

Horizn Dashboard — command center with Quick Actions, Recent Presentations, and Templates

Dashboard — real-time snapshot of financial health with direct paths to common tasks.

1

Quick Actions

Direct paths to the three most common tasks: creating a deck, updating data sources, and connecting new integrations.

2

Recent Presentations

Surface the most relevant decks with status indicators and one-click access to the editor.

3

Daily Data Brief

Alerts and new data notifications keep users aware of changes that impact their presentations.

Horizn Data Sources — connection health monitoring for Snowflake, Oracle, and financial models

Data Sources — connection health visibility for every integration.

1

Connection Health

Real-time status for each integration (Snowflake, Oracle, Salesforce). Error badges with tooltips reveal exact error messages — nothing hidden.

2

One-Click Integration

New sources connect through a modal flow, removing the need for IT tickets. Available integrations show what's possible.

3

Activity Log

Real-time feed of sync events, errors, and schema changes — finance teams can't afford to discover a broken pipeline during a board presentation.

Horizn Deck Editor — three-panel layout with slide canvas and AI assistant

Deck Editor — the core of Horizn, where data, analysis, and presentation converge.

1

Three-Panel Layout

Slide thumbnails for navigation, a center canvas with live-bound charts, and an AI assistant panel — all visible without mode switching.

2

Contextual AI Assistant

Not a generic chatbot. It understands the data context. Ask "Why is revenue up?" and it offers to generate a Variance Analysis slide with data already populated.

3

Live Data Metrics

Charts and KPI cards are connected directly to the data source. Numbers update when the source syncs — no manual refresh.

04 Process & Tools

This project was as much about exploring AI-assisted design as it was about the product itself. The design system was bootstrapped with MagicPatterns, then iterated through two major visual directions before landing on the warm stone palette.

Phase Tools What they did
Market Research Perplexity Competitive analysis with sourced citations
Synthetic Research Gemini, Claude Survey response generation, analysis reports
Persona Development Claude, NotebookLM Bias-corrected personas, presentation decks
User Flows Mermaid.js 4 detailed workflow diagrams
Wireframes HTML/CSS 7 interactive wireframes
Design System MagicPatterns Initial component library bootstrap
Prototype Next.js, Tailwind, shadcn/UI Functional high-fidelity prototype
Usability Prep Claude Test script (not yet run with participants)

The design system went through two major iterations. V1 (originally called "Farsight") used Deep Forest (#01353C) backgrounds with Bright Blue accents — enterprise-grade but too heavy for long sessions. V2 (renamed to Horizn) landed on warm stone neutrals with Sage green CTAs and Bright Blue reserved for data visualization.

05 Delivery & Reflection

Delivered a functional prototype covering all core workflows: dashboard monitoring, data source management, AI-assisted deck creation, and presentation editing. Built with Next.js, Tailwind CSS, and shadcn/UI — production-grade technology choices that could scale beyond the prototype phase.

What I Learned About the Product

Trust is the prerequisite, not the feature

Data lineage extends beyond the pipeline to AI-generated insights and slides. Without transparency into where an answer came from, finance users won't adopt.

Design for the long session

Early iterations with dark themes and bold gradients didn't work for extended use. The warm stone palette came from designing for someone who spends three hours preparing a board deck.

The output is the product

Getting data into a system is a solved problem. Getting it out as a polished, narrative-driven presentation is where the real product value lives.

What I Learned About AI-Assisted Design

Synthetic data is useful but flatters you

AI-generated survey data surfaced useful patterns, but the bias correction pass — questioning the data's assumptions — produced more realistic personas than the raw outputs ever could.

Collaborators to challenge, not oracles to trust

AI tools were most valuable when I challenged their outputs. The competitive analysis from Perplexity was well-sourced. The synthetic survey data needed significant correction.

Label what's synthetic

The biggest risk with AI-generated research is that it looks authoritative. Being explicit about what's synthetic and what it can't be used for isn't just ethical — it makes the work stronger.

Next Project
Technical SEO — Conductor