About Meridian Ledgerworks
We bring product strategy, user experience, integration engineering and delivery discipline into one accountable team.
Our point of view
“A financial product is never just the screen someone sees. It is every system, decision and working day that makes that screen true.”
Products fail when the customer experience and operational reality are designed separately. A journey may look simple while evidence is collected twice, exceptions have no owner or teams cannot tell which record is right. We start by making those relationships visible.
Meridian Ledgerworks is a fictional independent consultancy built around a senior, integrated team. Strategy, design, engineering and service delivery share decisions from the beginning, so a product can be useful to customers and manageable for the people who operate it.
Twelve disciplines, one delivery team
Our fictional team combines product, service, platform and operational experience. The original editorial portraits below are illustrations created for Meridian Ledgerworks.
Founder & Managing Director
Eleanor has led product and technology programmes across payments and retail banking. She works with leadership teams to connect commercial intent, accountable ownership and a delivery plan that can be governed.
Director of Product Strategy
Daniel shapes propositions from early market questions through to prioritised roadmaps. His work brings customer evidence, service economics and operational readiness into product decisions.
Head of Systems Integration
Priya leads integration design for banking and payment platforms. She focuses on clear interface ownership, reliable data exchange and the practical controls that keep dependencies visible.
Principal Fintech Architect
Oliver reviews platform boundaries and turns legacy constraints into explicit architecture choices. He has designed core banking and payment integrations with careful attention to change paths and service continuity.
Design Director
Harriet sets the interaction and accessibility direction for complex financial services. Her design practice joins clear customer language with the decision states and evidence needs of the service.
Lead Payments Engineer
Marcus builds and tests payment services, from initiation and status events through to settlement exceptions. He pays particular attention to idempotency, observability and safe operational recovery.
Compliance Product Lead
Aisha translates compliance and financial-crime requirements into workable product states. She partners with control owners to make evidence, escalation and audit needs explicit in the journey.
Data & Reporting Lead
Thomas defines metrics, reporting flows and lineage for operational decisions. He helps teams understand where a figure came from and how to act when source records disagree.
Senior Service Designer
Sophie maps the work that surrounds customer-facing journeys, including hand-offs, queues and exception paths. Her service blueprints help teams design around the people operating the product.
Delivery Director
James leads multi-disciplinary delivery across client, supplier and internal teams. He makes dependencies, decision ownership and release readiness part of the daily delivery conversation.
Client Operations Lead
Lucy works with service teams to establish useful procedures, issue routes and handover material. She keeps the transition from project delivery to daily operation grounded in real work.
Platform Reliability Engineer
Nathan helps teams design for observable, recoverable services. His focus includes deployment safety, actionable monitoring, incident learning and reducing avoidable operational noise.
A team that joins the work
We work alongside your teams, make decisions explicit and leave behind the context needed to keep moving after an engagement ends.
Talk with our team