Onboarding a new client: the first two weeks, step by step

The first two weeks of a new engagement matter disproportionately, since that's when a client forms their real, lasting impression of how the relationship will actually work, regardless of what the sales conversation promised. We run a specific, repeatable process for those two weeks rather than improvising, because the cost of getting the first impression wrong is high and hard to fully recover from later.

Most of what makes those two weeks feel chaotic to a new client isn't the actual work, it's the absence of visible structure around it. A client who doesn't know what happens next, or when, fills that gap with anxiety by default, regardless of how competently the work is actually progressing behind the scenes. The fix isn't doing more work faster, it's making the existing process visible enough that the client never has to wonder what's happening or when they'll hear from us next.

Day one to three: all necessary account access requested and confirmed, project board set up and shared, and a kickoff document circulated covering scope, timeline, and points of contact on both sides. Day four to five: a structured discovery call, not a repeat of the sales conversation, digging into the specific details (brand assets, technical constraints, prior work) that inform the actual build.

We send a short access checklist on day one rather than requesting credentials piecemeal as we discover we need them, since a drip of last-minute access requests reads as disorganized even when each individual request is reasonable. Getting everything lined up in one pass, even if a few items take a day or two to arrive, sets a much better tone than a string of separate asks trickling in over the first week.

We prioritize getting something visible in front of the client by the end of week two, even if it's a rough wireframe or a partial build, specifically so the first feedback loop happens early, while direction is still cheap to adjust, rather than after weeks of work in a direction that turns out to be off.

The specific format of that first deliverable matters less than its timing. A rough, clearly labeled draft shown in week two, with an explicit note that it's meant to validate direction rather than represent finished quality, does more for the relationship than a more polished deliverable that doesn't arrive until week four. Clients consistently tell us the early rough version, paired with a real conversation about what's working and what isn't, is what convinced them the engagement was on track.

Before the discovery call even happens, we circulate a short kickoff document covering scope, timeline, communication cadence, and a named point of contact on both sides. It's deliberately short, two or three pages, because a document nobody actually reads defeats its own purpose, and a shorter document that both sides genuinely read is worth more than a comprehensive one that gets skimmed once and forgotten.

We ask the client to confirm they've read it, not just received it, before the discovery call, since that small step surfaces misunderstandings about scope or timeline while they're still cheap to correct rather than three weeks into the project when a misaligned expectation has already shaped what the client thinks they're getting.

A client who sees clear structure, fast initial progress, and a real feedback loop in the first two weeks develops trust that carries the relationship through the inevitable slower, less visible weeks later in a project. A client left waiting without visible progress or clear process in that same window starts a relationship already anxious, and that anxiety colors every interaction that follows, fairly or not.

This matters even more on longer engagements, where the middle stretch of a project is often genuinely quiet from a client's point of view, heads-down build work with less to show week to week. A client who trusts the process, built during a strong first two weeks, tolerates that quieter middle stretch without anxiety. A client who never developed that trust starts reading every quiet week as a warning sign, which creates friction neither side actually needs.

Early on, our onboarding process was less structured, closer to a general checklist than a specific two-week script, and we saw a wider spread in how confident clients felt after their first month. Formalizing the exact cadence, what happens on which day, what gets shared and when, closed most of that gap, since it removed the variance that came from different team members running onboarding slightly differently each time.

We also learned to standardize the tools involved rather than letting each project lead pick their own preferred setup, since a client working with us across multiple projects noticing a different project board or update format each time reads as a lack of internal consistency, even when the underlying work quality is identical. A shared, repeatable template now covers the kickoff document, the project board structure, and the discovery call agenda, which frees the project lead to focus on the actual substance of the conversation instead of reinventing the format each time a new engagement starts.

One of the more overlooked items in a kickoff document is naming a single point of contact on each side, explicitly, rather than leaving communication to happen through whichever channel feels convenient in the moment. Without that clarity, requests scatter across email, Slack, and a project board simultaneously, and something inevitably falls through a gap nobody was watching.

We ask clients to name one internal point of contact even on projects with a larger stakeholder group involved in reviews and decisions, specifically because a single funnel for day-to-day communication prevents the common failure mode where two different stakeholders give conflicting direction to two different people on our team without either side realizing it happened until the conflict surfaces in delivered work.