Three years ago I ran a kickoff call for a logistics dashboard without sending anything beforehand. We spent forty minutes defining what “done” meant for the first milestone, and the client left the call thinking we’d agreed on a working prototype in two weeks. I thought we’d agreed on wireframes. That gap cost us a week of rework and an awkward email thread. Since then, every project starts with the same three documents, sent at least two days before anyone talks.
Why written material beats a live conversation
Calls are good for reading tone and building trust. They’re bad for precision. People nod along to things they haven’t fully processed, and vague agreements made out loud have a way of becoming firm commitments in someone’s memory. Writing forces specificity, and it gives both sides something to point back to when memory gets fuzzy in week six.
The scope note
This is one page, never more. It states what we’re building, what we’re explicitly not building, and what happens if new requests show up mid-project. I write it in plain language, no jargon, because the person approving budget is rarely the person who’ll review pixels. For a recent project with a Berlin fintech called Rella, the scope note was four short paragraphs and one line that read: “Anything outside the checkout flow is a new phase, priced separately.” That single sentence prevented three separate scope creep conversations later.
The reference board
A Milanote or Figma board with twelve to fifteen images: products I admire for reasons relevant to this job, not just things I like generally. I annotate each one with a short note explaining what to take from it. For Rella I included a banking app from Monzo for its numeral typography, a hotel booking site for its confirmation screen pacing, and a grocery app I actively disliked, labeled “avoid this density of information per screen.” Showing what to avoid is as useful as showing what to chase.
The timeline with named milestones
Not a Gantt chart. A list of five or six dates, each tied to a specific deliverable a non-designer could picture: “March 14, first clickable flow for account creation.” Dates without concrete nouns attached to them get forgotten or reinterpreted. Dates with nouns attached get remembered correctly, even six weeks later.
What changes once these exist
The kickoff call itself gets shorter, usually thirty minutes instead of ninety. There’s less explaining and more deciding, because everyone has already read the material and formed questions. I’ve noticed clients ask sharper questions too, the kind that come from having sat with information rather than reacting to it live.
There’s a secondary benefit I didn’t expect when I started doing this. Sending structured material before any call signals competence in a way that the call itself can’t. A founder named Tomas Varga, who hired me for a scheduling tool last year, told me he decided to go with my studio partly because the pre-kickoff documents were the first clear writing he’d seen from any of the three designers he was considering. The work hadn’t started yet, but the process already looked trustworthy.
Clarity before contact. If people understand the shape of a project before they talk about it, the conversation becomes about decisions instead of definitions.
Where this breaks down
It doesn’t work if the client hasn’t settled internally on what they want. I’ve sent scope notes to teams who then spent two weeks disagreeing among themselves about what was in the note, which is frustrating but still better than discovering that disagreement in week four of actual design work. The documents surface misalignment early, which is uncomfortable but cheap compared to surfacing it late.
It also doesn’t work as a one-time template. I used to reuse the same reference board structure for every project until a client pointed out that half the examples were irrelevant to her industry. Now each board gets rebuilt from nothing, even if that means an extra ninety minutes before every kickoff.
A rough checklist before I hit send
- Scope note fits on one page without shrinking the font
- Reference board has a written reason attached to every image
- Timeline uses dates and nouns, never “soon” or “early phase”
- All three documents use the client’s product name, not a placeholder
- Nothing promises a specific visual style before research is done
That last point matters more than it sounds. Early on I made the mistake of including finished-looking mockups in a reference board, and the client assumed that was the direction we’d already chosen. Now anything resembling a final design stays out until research is actually finished.
What this costs
Roughly half a day per project, unpaid, before any contract is signed in some cases. I’ve made peace with that because the half day up front routinely saves two or three days of renegotiation later, and it filters out clients who aren’t serious before either of us has invested real time. A process that costs a little early and saves more later is, in the end, just good design applied to how the work itself gets organized.
