All insights

Why we say no to wireframes in the first meeting

The case for slowing down at the start of an engagement — and what happens to projects that skip straight to design.

Clients occasionally arrive at a first meeting expecting wireframes. It's an understandable expectation — visible progress feels like progress. It's also, in our experience, how projects end up rebuilding themselves six months post-launch.

Skipping discovery doesn't remove the questions discovery answers. It just defers them to a point where they're far more expensive to address — after design sign-off, or worse, after development.

Our first meetings are deliberately light on visuals and heavy on questions: who is this for, what does success look like in six months, what constraints are non-negotiable. It can feel slower. It isn't — it's the fastest route to a product that doesn't need to be redesigned a year later.

Pixels are cheap to produce and expensive to throw away. Strategy is the other way around.

Let's build something remarkable.

Tell us about your business and what you're trying to achieve — we'll respond within one business day.

Start a Project