A new client signs the proposal, the deposit clears, and then the real work begins. Too often, this transition is marked by a flurry of fifty unorganized Slack messages, half-broken Google Drive links, and immediate misalignment. At Northwind Studio, we learned early on that the first 14 days of a design project are not a warm-up period. They are the exact window where projects either set a course for creative success or quietly begin to derail.
When onboarding goes wrong, it is rarely because of a lack of talent. It is because of a lack of structure. If you do not set the rules of engagement early, your client will set them for you.
Why the first 14 days make or break a design partnership
Onboarding is not administrative overhead — it is the foundation of the entire creative relationship. It sets the cultural tone, establishes boundaries, and defines how you will handle friction when it inevitably arises.
When you rush past onboarding to get straight to the fun design work, you build on shaky ground. Without a clear process for feedback and decision-making, you will find yourself three weeks into a project redesigning a homepage because a stakeholder who was never mentioned in the kickoff suddenly weighed in.
Early misalignment on goals or feedback loops is the primary driver of scope creep and missed deadlines. By treating the first two weeks as a structured phase of the project, you show the client that you are stewards of their budget and their time.
The technical access checklist: Stop chasing logins
Nothing kills momentum faster than waiting three days for a password reset. We have a strict rule — we do not schedule a kickoff meeting until we have the keys to the client's current digital ecosystem.
Chasing logins mid-project wastes creative energy. Before your team opens a single design file, send the client a clean, non-negotiable checklist of required assets and access permissions.
Your checklist should require:
- Figma access: Entry to their team space or permission to invite them to yours.
- Brand assets: Vector files of their logo, existing brand guidelines, typography files, and high-resolution imagery.
- CMS and hosting credentials: Admin access to Webflow, WordPress, or whatever platform hosts their current site.
- Analytics platforms: Read-only access to Google Analytics or Plausible to understand current user behavior.
- Communication channels: Shared Slack channels or agreed-upon project management workspaces.
Collect these assets in a central, secure folder before the kickoff call. If the client is slow to provide them, push the kickoff date back. It sounds harsh, but it protects their timeline.
Mapping the decision-makers (and the silent partners)
Every agency owner has experienced the "seagull effect." You spend three weeks collaborating with a marketing manager, only for an executive sponsor to fly in at the final presentation, leave a mess of contradictory feedback, and fly away.
To prevent this, you must map out the stakeholder hierarchy during week one. Ask your primary contact two direct questions:
- Who is responsible for the day-to-day feedback on this work?
- Who has the final veto power and budget sign-off?
Document these roles clearly. The day-to-day contact is your partner — they help you navigate internal politics. The executive sponsor is the decision-maker — they do not need to be in every weekly sync, but they must sign off on major milestones like the creative direction and the final wireframes. If the final decision-maker cannot make the milestone meetings, pause the work until they can.
The kickoff agenda that focuses on constraints, not introductions
A great kickoff is an alignment workshop, not a slide deck presentation. Do not waste 60 minutes introducing your team and reading through slides the client has already seen. Instead, focus on constraints and creative boundaries.
Keep the agenda lean and focused on three areas:
- Defining success: Ask the client what a successful project looks like six months after launch. Is it a 20% increase in demo sign-ups? Is it a cohesive brand identity that makes them feel confident during their next funding round?
- Identifying technical constraints: Talk about engineering limitations, accessibility requirements, and content management needs early. Knowing these boundaries prevents you from designing beautiful layouts that their development team cannot actually build.
- Handling disagreements: Establish how you will resolve creative differences. Agree that design decisions will be guided by user data and project goals, not personal aesthetic preferences.
Establishing the communication cadence
To protect your team's creative focus, you must set clear boundaries around how and when you communicate. Constant, unstructured feedback via Slack or email leads to reactive design decisions and fractured focus.
At Northwind Studio, we offer retainer-based design ops support to keep these feedback loops tight and predictable. This ensures we build on top of established design systems rather than starting from scratch every week.
We establish a simple, weekly rhythm:
- Monday: A brief, asynchronous video walk-through showing the progress made and outlining what we need from the client that week.
- Wednesday: The client submits consolidated, written feedback.
- Thursday: A live, 30-minute review session to discuss complex feedback and align on the next steps.
This structure gives the client peace of mind because they always know when to expect updates — and it gives your designers uninterrupted blocks of time to actually do the work.
The week-two quick win
Clients feel vulnerable during the first two weeks of a project. They have handed over a significant deposit, and they have not seen any creative work yet. You can ease this anxiety by delivering a small, tangible piece of work by the end of week two.
This is not about rushing the final design. It is about proving your capability and building momentum.
For example, let's say you are redesigning a marketing site for a B2B SaaS platform with an illustrative project scope of a 10-page site redesign and a target budget of $45,000. Instead of making the client wait a month for a full homepage mockup, deliver a mini-audit of their current site's navigation and a mood board of three distinct visual directions by day ten.
This small deliverable costs your team very little time, but it shows the client that you listen, you understand their brand, and you are already moving the project forward.
If you are looking for a design partner that values process as much as craft, we should talk. We help B2B SaaS and professional services brands build cohesive brand identities, marketing site designs, and accessible digital experiences. Let's discuss how we can support your team's next design initiative.
FAQs
What should be on a design project onboarding checklist?
A comprehensive checklist includes asset collection like vector logos, fonts, and brand guidelines — along with technical access to the CMS, Google Analytics, Figma, and Slack. It should also include a mapped list of stakeholders with their roles, and a signed-off project timeline with clear milestone dates.
How do you handle clients who delay sending onboarding assets?
Establish a clear rule during the proposal stage — the project start date is contingent on receiving all required assets. If assets are delayed by a week, the kickoff and delivery dates shift accordingly to protect the team's schedule.
Who should attend the creative agency client kickoff?
Keep the room lean. On the agency side, the lead designer and project manager should attend. On the client side, invite the primary point of contact and the ultimate decision-maker who has final sign-off on the budget and creative direction.
How do you prevent scope creep during onboarding?
Document the project scope clearly in the onboarding kickoff deck and explicitly state what is out of scope. When new ideas arise during early brainstorming, acknowledge them and suggest tracking them in a "Phase 2" backlog.