Meridian Platform
Product marketing site and narrative for a B2B workspace that finally sounded like the product teams loved.
- Positioning · Web design · Design system · Messaging
- +61% demo requests

+61%
Demo requests
2.4×
Time on product tours
1
Shared design system
The brief
Meridian’s product outpaced its story. Engineers loved it. Prospects still asked “what do you do?” on every demo call. Marketing and product UI spoke different dialects — different radii, different type, different ideas of what a “simple” screen meant.
The brief was to make the public site sound like the product, and to give both teams one system so screenshots stopped looking like they came from two companies that shared an office.

Narrative, then modules
We reframed the category around the job buyers hire Meridian for — not a feature list, not a metaphor that collapsed under scrutiny. Message architecture came first: homepage, product tours, proof, and a clearer path to demo.
Only then did we rebuild the site. Every module had to earn its place against a single question: does this make the next demo shorter?


One system, two surfaces
In parallel we shipped a shared component kit — buttons, spacing, type, form patterns — so marketing and product stopped reinventing basics. The kit wasn’t a trophy; it was a peace treaty with version control.
Product adopted the tokens for a settings redesign. Marketing used the same type ramp on the homepage. Suddenly the brand felt continuous from ad to app.

How it landed
Demo volume rose sixty-one percent in the first quarter. Prospects arrived already oriented. Time on product tours more than doubled because the tours finally explained something instead of decorating a feature grid.
The quieter win: Slack arguments about “which button is ours” mostly disappeared. That’s what a shared system is for.