Case studies / Representative engagements
Better connections, visible in the work.
These fictionalised examples show how joined-up product design and systems thinking can make complex financial operations easier to understand and improve. They are not client endorsements.
01 / Representative engagement · UK payment institution
One merchant journey from application to settlement
Client context and challenge
A growing UK payment institution handled merchant onboarding across separate intake, due-diligence and settlement tools. Evidence was re-keyed, case status was hard to establish and operations staff moved between queues to resolve settlement breaks.
What we delivered
Meridian mapped the merchant and operations journeys, defined shared case states, designed a controlled onboarding workbench and sequenced a staged settlement-operations improvement.
Integration scope
- Merchant CRM and application intake
- Identity and company verification provider
- Payment processor events
- Settlement files and ledger records
Delivery approach
A short discovery with operations and control owners was followed by interface mapping, prototype reviews and incremental releases around the highest-friction hand-offs.
Representative outcome: The representative design reduced manual hand-offs between application and settlement teams and created a single operational view of onboarding progress and unresolved settlement exceptions.
Discuss a similar challenge02 / Representative engagement · Regional lender
Underwriting work beyond the spreadsheet queue
Client context and challenge
A regional lender coordinated application review through shared spreadsheets, email and a legacy case system. Reviewers lacked a consistent view of missing evidence, decision rationale and the next accountable action.
What we delivered
The team defined a clearer case lifecycle, designed role-based underwriting and review queues, and specified an auditable decision record with explicit evidence requests.
Integration scope
- Digital application form
- Credit reference and affordability feeds
- Document storage
- Existing loan origination and case management
Delivery approach
We shadowed caseworkers, mapped decision variants with credit and compliance leads, then delivered a thin workflow slice before extending the model to more case types.
Representative outcome: The proposed workflow made outstanding evidence and ownership visible, reduced spreadsheet-led coordination and gave managers a clearer view of case ageing.
Discuss a similar challenge03 / Representative engagement · Wealth platform
Portfolio context carried into adviser service
Client context and challenge
Advisers on a regional wealth platform moved between portfolio screens, reporting tools and service notes to prepare for a client conversation. Data timing and ownership were not obvious when holdings changed.
What we delivered
Meridian brought account, portfolio and service information into a coherent adviser concept, clarified report-generation states and designed a review step for exceptions before client distribution.
Integration scope
- Custody and portfolio data feeds
- Performance and valuation services
- Document generation and client portal
- Adviser CRM and service tasks
Delivery approach
Product and engineering teams agreed source-of-truth rules and freshness cues first. Adviser walkthroughs then tested the information hierarchy and escalation paths.
Representative outcome: The representative solution aligned portfolio data, client reporting and adviser tasks around one account context, reducing repeated navigation during service preparation.
Discuss a similar challenge04 / Representative engagement · Cross-border fintech
Faster sight of cross-border payment exceptions
Client context and challenge
A cross-border fintech had payment status in one system, bank statements in another and reconciliation decisions recorded in team notes. Investigation time varied depending on who knew the route.
What we delivered
We mapped transaction states across providers, introduced a break taxonomy and designed an investigation view connecting payment events, statement lines and ownership history.
Integration scope
- Payment orchestration and provider APIs
- Bank statement ingestion
- Ledger and reconciliation engine
- Operations case and notification tools
Delivery approach
A joint review of representative exceptions led to a traceable event model, followed by a focused prototype and operational walkthrough with treasury and support colleagues.
Representative outcome: The representative changes shortened exception investigation time by reducing context gathering and made reconciliation visibility more consistent across corridors.
Discuss a similar challengeYour operating context is different
Start with the part that feels hardest to connect.
We will help you turn your particular system boundaries and team hand-offs into a practical question to solve.
Discuss your challenge