1. The access collection black hole
You need Figma access, Google Analytics, WordPress admin, GitHub, and the client's Slack. You ask. They forward a password email from two years ago. You ask again. Their developer says they'll get back to you. Three days pass.
The fix: Send a single, complete access list on Day 1 — not "we'll need some access" but the exact list, with specifics for each tool, and a deadline. Include what happens if the deadline is missed. Framing it as "we start discovery without these, but integration builds are blocked until week 3" changes behavior fast.
A good intake form covers this before the project starts. Here's a free 27-question version if you need a starting point.
2. Scope drift that starts in the kickoff call
The sales call sets one expectation. The kickoff call assumes something slightly different. The project brief says something else. By week two, you're building features nobody explicitly agreed to.
The fix: Send a written kickoff summary within 24 hours of the kickoff call. Not meeting minutes — a plain-language document that says: "Here's what we're building. Here's what we're not building. Here's what triggers a scope change conversation."
Ask the client to confirm it explicitly. "Reply with OK or any corrections" clears ambiguity in a way that a call summary in Notion does not.
3. The assumption handoff from sales to delivery
Your salesperson knew the client's real pain point. The delivery team doesn't. So delivery builds to the spec, not to the problem.
The fix: A structured sales-to-delivery handoff doc. Ideally filled in by the salesperson while the memory is fresh, covering:
- What problem the client actually wants solved
- What they're worried about
- What they mentioned off the record
- Any political context (stakeholders, existing vendor relationships)
Five minutes of capture prevents hours of rework.
4. The "we'll figure it out" kickoff agenda
A kickoff call with no structure turns into a 60-minute relationship-building session that covers none of the questions you needed answered. You leave with good vibes and no information.
The fix: Send the kickoff agenda 48 hours before the call. Include the specific decisions you need to make, the access items you need, and the one question the client most needs to answer clearly. Clients who see the agenda in advance show up ready — you get twice as much done in the same time.
5. No follow-up system for client responses
You send three requests in the first week. One gets answered immediately. One gets a partial answer. One disappears.
You don't have a clean way to track which thread is outstanding, so you either let it drop or send an awkward "just following up" email that makes you feel like a debt collector.
The fix: A standard set of follow-up messages that escalate in specificity without escalating in tone. The first follow-up restates exactly what you need. The second ties it to a project impact ("we can't start X until we have this"). The third offers a simple alternative ("if this isn't available, here's our fallback").
This is tedious to write fresh every time — most agencies use 3-5 reusable templates for this.
6. Recreating the same structure every time
Every new client gets a new folder structure, a new project board, a new onboarding checklist. Your senior project manager does it from memory. Your junior does it slightly differently. By month three you have three inconsistent onboarding setups and no institutional knowledge.
The fix: A single canonical onboarding template. One folder structure. One project board template. One checklist. When something doesn't fit a client, you adapt the template — not invent something new.
This sounds obvious. Most agencies don't have it. If you build one folder structure and one checklist and use them exactly twice, you've already recouped the time spent.
7. The first deliverable that surprises the client
You build exactly what was in the brief. The client expected something different. Not because you did it wrong — because neither of you understood the gap between "what we agreed" and "what they were picturing."
The fix: A pre-delivery alignment check before you share the first real deliverable. Not "here's what we built" — "here's what we built, here's how it maps to the brief, here are two decisions we made that weren't covered in the spec."
Surface the choices before they become surprises. Clients who feel informed are forgiving. Clients who feel surprised are not.
The pattern
Every one of these breakpoints has the same root cause: information that exists somewhere didn't make it to the right person at the right time.
The solution isn't software. It's a repeatable system for capturing and transferring context — intake questions before the project starts, a kickoff structure that surfaces decisions, templates that remove the "rebuild from scratch" tax, and follow-up language that escalates without burning goodwill.
If you want a starting point, we put together two free resources:
- 10-step AI-native onboarding checklist — what to cover in the first two weeks
- 27-question client intake form — the questions to ask before work starts
Or if you want the full system — folder structure, SOP, email templates, automation recipes, kickoff brief generator — we bundled all of it into the Agency Onboarding OS (€49, founding batch).
What's the onboarding breakpoint that's cost you the most? Genuinely curious what the distribution looks like in practice.