The Opening Statement: A Client Orientation Packet for Independent US Design Studios
Photo: David Adam Kess, CC BY-SA 4.0, via Wikimedia Commons
Onboarding as an Operating Discipline
The first ninety days of a client relationship are rarely decided by the contract alone. They are shaped by dozens of smaller questions: Who approves this? How quickly should feedback arrive? What counts as a revision? When is a meeting necessary, and when is a written note sufficient? Independent US design studios often answer these questions repeatedly, project after project, because the answers live in the founder's head rather than in a shared document.
A client orientation packet changes that. It is not a sales leave-behind or a polished welcome brochure. It is a practical operating document that tells a new client how the studio works, what the client can expect, and what the studio needs in return. For FNAD members, the packet is also a form of professional advocacy: it presents design work as a managed process rather than an open-ended conversation.
A Packet, Not a Pitch Deck
The distinction matters. A pitch deck persuades; an orientation packet instructs. It should be written in plain language, designed for quick reference, and delivered after the contract is signed but before project work begins. It does not replace the agreement, and it should say so. Instead, it translates contractual terms into familiar routines: where files live, how decisions are recorded, and what happens when a request falls outside the agreed scope.
A useful packet is short enough to be read and specific enough to be used. Many studios find that eight to twelve pages, plus a one-page summary, is sufficient. The summary can sit at the front and repeat the most important commitments: the primary contact, the review cadence, the feedback window, and the payment schedule.
The Essential Sections
Welcome and named roles
Open with a brief note from the studio lead. State who will manage the project day to day, who has final approval authority on the client side, and who handles billing or administrative questions. Naming roles prevents the common pattern in which several client stakeholders offer direction but no one owns the decision.
Project map and decision calendar
Include a simple phase map with the decisions required at each stage. The map need not predict every detail, but it should show where client input is essential and where the studio will proceed without a meeting. A decision calendar is especially useful for US studios working across time zones: it gives clients advance notice of review windows and reduces the urge to schedule impromptu calls.
Feedback that can be used
Design feedback improves when it is consolidated and contextual. The packet should specify a single channel for feedback, a reasonable response window, and a preferred format. For example, the studio might ask for one consolidated written response per review round, with comments tied to the project objectives rather than personal preference. This section should also explain how the studio will document decisions and confirm the next step.
Scope boundaries and change control
Clients rarely intend to expand a project; they simply ask questions that sound small. The packet should describe how additional requests are handled: a written change note, a revised estimate, and an approval before work proceeds. This is not an obstacle to service. It is a way to keep the original project healthy and to give the client an honest view of trade-offs.
Payment rhythm
The packet should restate the payment schedule in plain terms, including invoice timing, accepted methods, and the studio's policy on paused work. It is also prudent to note that the studio is not providing legal or tax advice and that clients should consult their own advisers on matters such as state sales tax where applicable.
Communication norms
State expected response times, meeting cadence, and the channels the studio monitors. A studio need not promise instant replies. It should promise a predictable rhythm. This section can also explain how urgent matters are flagged and how the studio handles vacation or holiday periods.
Files, access, and recordkeeping
Describe where working files will be stored, how the client will receive final deliverables, and what access the client retains after the engagement. For independent studios, clear file conventions protect both parties and reduce the risk of version confusion.
Pause and escalation points
Every project encounters moments when progress depends on a missing decision or an unresolved question. The packet should identify a simple escalation path: the studio contact, the client decision-maker, and the point at which work will pause until direction is received.
Making It Usable
A packet that is never opened has no value. Send it before the kickoff call and ask the client to review the one-page summary in advance. Use the kickoff meeting to walk through the feedback protocol and change-control process, not to read the document aloud. Ask for written acknowledgment that the client has received it, and keep that acknowledgment with the project record.
Design matters here as well. The packet should reflect the studio's visual standards, but clarity outranks decoration. Use headings, short paragraphs, and a consistent structure so clients can find answers quickly. A version date and a brief revision note help prevent outdated copies from circulating.
What the Studio Gains
A well-built packet reduces repeated explanations and protects studio time. It also creates a fair record of expectations. When a client asks for a fifth round of revisions or introduces a new stakeholder late in the process, the studio can point to a shared document rather than rely on memory. That is not adversarial; it is professional. The packet gives both parties a common reference for how the work will proceed.
For solo practitioners and small practices, the packet also serves as a form of continuity. If a project manager is unavailable, or if a studio brings in a freelance collaborator, the operating norms remain visible. FNAD encourages members to treat the packet as part of their studio infrastructure, not as a one-time client courtesy.
Keeping It Current
Review the packet at least annually and after any project that reveals a gap. Ask clients where they looked for information and what remained unclear. The strongest packets evolve through use. They become a quiet record of the studio's standards: how decisions are made, how time is respected, and how design work is carried through to completion.