Skip to content

Case study · SaaS Experience

Meridian

B2B infrastructure · Series B

Multi-tenant control plane for billing, roles, and observability.

Meridian — control plane and tenant overview
Desktop · staging
Meridian — mobile framing

Editorial composition: same system across breakpoints — how the experience reads in hand versus on a desk.

Context

Meridian’s team was outgrowing a patchwork of admin screens and one-off scripts. We designed a single calm surface for tenant lifecycle, entitlements, and finance handoffs — with audit trails and empty states that feel intentional, not apologetic.

Engagement

Timeline
Audit & IA 4 weeks · control plane build 14 weeks · SOC2 documentation track in parallel
Team shape
Weblexia tech lead + Meridian platform group; design system pairing with internal brand studio.
Engineering complexity
Legacy MySQL + read replicas; migration to stricter tenancy model without multi-day read-only windows.

Before / after

Before

Fragmented admin UIs, entitlement drift between billing and product, and support playbooks that contradicted the UI.

After

Single tenant lifecycle surface with auditable role changes, usage views finance trusts, and empty states that explain next actions.

Outcomes

Time-to-resolve
Tier-1 support tickets −31% after launch
Release cadence
Weekly deploys with zero schema surprises
Security review
SOC2-aligned access model documented in-product

Capabilities

  • Multi-tenant auth
  • Usage metering
  • Role matrices
  • Audit UI

Stack

Next.js · Laravel · PostgreSQL