Meridian · Process

The full process

The research, personas and flows behind Meridian. The case study covers the decisions; this is the work underneath them.

02 — User Research

User Personas & Goals

Meridian's users range from Series B CFOs seeking real-time certainty, to VP Finance managing multi-entity consolidation, to startup Finance Managers needing automated spend controls — each with distinct evaluation criteria.

👤
Priya Mehta
Series B CFO, 38
  • Real-time visibility into cash position across all accounts
  • Automated reconciliation without manual exports
  • Clean audit trail for the board
  • 24-hour lag in bank statements
  • Monthly reconciliation taking 3 days of finance team time
🧑
James Okafor
VP Finance at Scale-up, 44
  • Multi-entity consolidation in one view
  • Custom approval workflows for large payments
  • FX exposure management at live rates
  • Managing 6 separate bank portals
  • No single source of truth for group cash
👩
Aisha Torres
Startup Finance Manager, 29
  • Automated bill pay with approval chains
  • Virtual cards for each team's budget
  • Real-time spend visibility per department
  • Chasing receipts across Slack
  • No budget-level spend controls for engineering

03 — Business Challenges

Core Challenges

CHALLENGE 01
📊
Communicating Real-Time Without Overwhelming

Real-time data is the product's core differentiator. But financial dashboards that try to show everything simultaneously create anxiety rather than confidence. Design needed to prioritize the right metrics at the right hierarchy.

CHALLENGE 02
🔒
Trust in a Skeptical Market

Post-FTX and post-SVB, finance teams are deeply skeptical of fintech promises. Security and compliance signals had to be woven into the visual design language, not buried in a footer.

CHALLENGE 03
🗺️
Feature Depth vs. Landing Page Clarity

Meridian has 14 integration categories, 4 product lines, and enterprise-grade configuration. A landing page that tried to communicate all of it would communicate none of it. Ruthless prioritization was required.

CHALLENGE 04
👥
Multi-Persona Entry Points

The CFO, the Finance Manager, and the Ops Lead evaluate the product differently. A single landing page had to speak to all three without fragmenting the narrative or creating choice paralysis.


04 — Secondary Research

Market Insights

FINDING 01
73%
Manual Reconciliation Prevalence

73% of SME and scale-up finance teams still perform manual bank reconciliation at least weekly — representing an average of 6 hours of finance staff time per cycle. This was the primary pain point Meridian needed to visually solve. (Source: Xero SME Finance Report 2024)

FINDING 02
4.2x
Real-Time Data Premium

Companies with real-time financial data access are 4.2x more likely to catch fraud within 24 hours and 3.8x more likely to identify cash flow issues before they become critical. The live data proposition was strategically central, not a feature. (Source: Deloitte CFO Survey 2024)

FINDING 03
87%
Security as Table Stakes

87% of B2B fintech buyers list security certification and regulatory compliance as non-negotiable before evaluation — not a decision factor, but a qualification gate. Meridian had to pass this gate in the above-the-fold experience. (Source: G2 Fintech Buyer Survey 2024)


07 — User Flow

The Journey

STEP 01
Live Dashboard Hero
The hero surface is a live-feel banking dashboard with real-time balance counters and reconciliation status — communicating the product's core promise before any headline is read.
STEP 02
The Problem Statement
A stark, numerical articulation of the reconciliation lag problem — "your books closed yesterday, not today" — frames the product as a solution to a specific, quantified pain.
STEP 03
Feature Architecture
Three product pillars (Treasury, Cards, Reconciliation) presented with interactive product UI — each demonstrating a distinct workflow rather than listing capabilities.
STEP 04
Trust Layer
SOC 2 Type II, PCI DSS Level 1, and bank-grade encryption signals, plus named institutional bank partners — qualifying Meridian through the security review gate before any feature evaluation.
STEP 05
Conversion
Demo request form with a "see live data, not a slide deck" framing — reducing the barrier of a traditional sales demo by positioning it as a product experience, not a sales call.

08 — Toolkits

Tools & Workflow

Tools and methods used throughout the Meridian design process — from competitive audit and CFO interview synthesis through to precision financial dashboard execution.

🎨FigmaUI Design
📊JetBrains MonoFinancial Typography
📐Claude CodeFrontend Build
🔒OWASP GuidelinesTrust Signals
🗺️FigJamIA & Flow

09 — Process

From CFO pain
to designed certainty.

Financial product design lives or dies on trust. Before any wireframe, the process started with understanding what breaks that trust — slow data, opaque fees, dashboards that show information but not insight. The process below reflects six phases, but honestly, the first three were mostly about unlearning assumptions about what a fintech dashboard should look like.

01
Competitive Audit
Analysed Mercury, Brex, Ramp, and Airwallex landing pages for visual hierarchy, trust signal placement, and feature prioritization. Identified reconciliation automation as the unclaimed differentiator.
02
CFO Interview Synthesis
Reviewed 12 published CFO interviews on fintech adoption barriers. Identified "I don't trust the numbers are real-time" as the universal anxiety across company sizes.
03
Dashboard Architecture
Designed the hero as a live dashboard surface — numbers ticking, reconciliation score updating, balance in motion — to make the core proposition felt, not explained. The first two iterations used static screenshots. Both tested poorly: users described the product as "just another dashboard." The animated version tested with "it looks like the data is actually in there." That was the signal we needed.
04
Trust Signal Layering
Mapped the security signals across the page hierarchy — not as a section, but woven into headlines, subtext, and visual treatments throughout the scroll.
05
Typography System
JetBrains Mono for all financial figures, Bricolage Grotesque for display. The monospace choice signals precision and technical credibility — the right register for a product that touches money.
06
Performance Build
Static landing page with CSS animations for dashboard elements — no heavy framework, no runtime rendering. Sub-1.5 second load on 3G.

Back Return to the case study