When founders look for help building a product, they usually compare agencies on technology and price. The more important difference is the order they work in: do they decide the experience first, or start coding from a feature list?
What a dev shop optimises for
A traditional development agency takes a specification and builds it. That works when the specification is right. For an early-stage product it rarely is, so the mistakes are discovered after they are built, when they are most expensive to fix.
What a design-first studio does differently
- Starts with the user and the job, not the feature list.
- Prototypes and tests the experience before engineering begins.
- Hands engineering a finished, agreed design, so the build has far less rework.
- Keeps design and engineering in the same room, so trade-offs are made together.
The cost of changing your mind
Moving a button in a prototype takes minutes. Moving it in a live product can mean changes to data, APIs, tests and a release. Every decision you make in design instead of in code is a decision you get to change cheaply.
When a dev shop is the right call
If you already have a validated product, a strong in-house designer and a precise specification, a pure development partner can be efficient. For founders still finding product-market fit, design-first almost always wins.
How to tell which one you're talking to
- Ask what happens in the first two weeks. Design-first teams talk about users, flows and prototypes.
- Ask who designs the screens. If the answer is 'you send us designs', they are a dev shop.
- Ask how they handle a change in direction halfway through.
Written by Two CentsA design-first product studio helping founders design, launch and scale products. About the studio.