01
Name the real work.
Frame the moment, the people involved, and the constraint worth designing around.
Independent product studio · New York / everywhere
Meridian shapes digital products for the teams doing consequential work: the workflows, systems, and services people need to trust on an ordinary Tuesday.
Discuss a product
01 / The starting point
The expensive problems do not start in a component library. They start when a team cannot name what is changing, who it serves, or how it should work when the day is busy.
We give early product thinking a working shape: a focused problem, a credible first release, and a way to make trade-offs without losing the thread.
02 / A way of making
01
Frame the moment, the people involved, and the constraint worth designing around.
02
Translate complexity into journeys, interfaces, language, and a visual system with a point of view.
03
Build and release the part that matters, with the team who will carry it forward.
A considered build
03 / Ways to work together
01
A compact engagement to define the opportunity, align the room, and find a credible first move.
02
One close studio team, from a working model through a production-ready release.
03
Ongoing design and engineering support for a team navigating a meaningful change.
04 / Common questions
Early enough to shape the problem, or late enough to make a specific release more coherent. A clear decision boundary is more useful than a perfect starting point.
Yes. The work can complement an existing team, create momentum around a contained initiative, or help clarify an ambiguous product direction.
Products with operational depth: tools, workflows, platforms, and services where clarity matters as much as polish.
A good place to begin