What working with a design studio actually looks like
If you have never commissioned a brand or a website, the process can feel opaque: what happens first, what it costs to get wrong, what is expected of you. Here is how an engagement runs, start to finish, including the parts where projects usually go wrong.
Before the project: the conversation
It starts with a call, and the call is mutual. You are checking whether we understand your business faster than the last agency did; we are checking whether the project has the ingredients that make good work possible: a real goal, a decision-maker, a budget that matches the ambition.
Expect direct questions about money early. Not because the number decides everything, but because "we'll see" is how projects get scoped wrong in both directions. A studio that will not discuss budget ranges on the first call is planning to have that argument later, at a worse time.
The brief
Before design starts, the brief gets written down: what we are making, for whom, what it must achieve, what is out of scope. If you arrive without one, writing it together is the first piece of work, and it is short. A brief that does not fit on two pages is usually hiding a disagreement.
This document matters because it is the referee. Weeks later, when someone asks "should the homepage do this too?", the answer comes from the brief, not from whoever spoke last.
The rhythm
A healthy project has a boring rhythm: work is shown every week or two, in progress, with the thinking attached. You will see things before they are polished, deliberately. The expensive mistakes in design are the ones discovered late, and the only prevention is showing work early enough that changing course is cheap.
What we need from your side is one point of contact who gathers internal opinions and delivers decisions. Feedback from your whole team is welcome; it just needs to arrive through one person, reconciled. "Marketing wants it bigger and the CEO wants it smaller" is not feedback a designer can act on. Someone on your side has to win that argument first.
The feedback that helps
The most useful feedback describes problems, not solutions. "This page doesn't feel trustworthy" gives a designer something to solve. "Make the logo bigger" skips the diagnosis, and the diagnosis is usually where the real issue lives. You are the authority on your business and your customers; we are the authority on how to translate that into screens and systems. Projects run best when both sides hold their own end.
Where projects go wrong
After years of doing this, the failure modes are predictable: the decision-maker who appears for the first time at the final review; the content that stays "nearly ready" for a quarter; the scope that grows one small favour at a time until the timeline quietly doubles. None of these are design problems, and all of them are preventable in the first two weeks. This is why we insist on the unglamorous things: the named approver, the content plan, the written scope.
How it ends
A project is done when it is live and you own it: the site shipped, the files handed over, the brand assets organised so your team can actually use them, and a clear answer to "who do we call when something breaks?" Handover should feel like being given keys, not being left a puzzle.
If you have a project in mind and want to know what it would look like as a plan with dates and a number attached, send us a brief. Two pages is plenty. One paragraph is a fine start.
