Most agency onboarding fails before the kickoff call happens.
Not because the team isn't good. Not because the client is difficult. Because nobody collected the right context upfront, and the kickoff call becomes the place where everyone discovers what they don't know yet.
The intake form is the fix. Not a 3-question "tell us about your project" form. A real one.
Here's the framework we use — 27 questions across 6 categories — and why each group of questions matters.
Why intake isn't optional
When the intake is missing or vague, these things happen in week one:
- The kickoff call is spent gathering basics instead of making decisions
- Scope gaps get discovered during delivery, not before it
- The access collection process takes 10+ days because nobody mapped all the tools
- The delivery team briefs themselves from memory, not data
A structured intake form converts the "getting started" conversation into a documented artifact your whole team can work from.
Category 1: Business Context (5 questions)
These answers tell you what the client actually does and what success looks like to them — not just the project brief.
- What does your business do, and who is your primary customer?
- What problem are you hiring us to solve?
- Who is the main stakeholder on your side, and who has final sign-off?
- Is there a team we'll be working alongside, or is this project on your side?
- Have you worked with an agency on this type of work before?
Why this matters: Question 3 (decision-maker clarity) and question 5 (prior agency experience) save the most time. You'll find out early whether the client has a clear internal champion or whether approvals will be chaotic.
Category 2: Goals and Success Metrics (4 questions)
- What does success look like at 30 days? At 90 days?
- Are there specific metrics you're tracking (leads, traffic, revenue, ranking)?
- What has NOT worked in the past when trying to solve this?
- What is the one thing you most need to be true by the end of this engagement?
Why this matters: Question 8 (what hasn't worked) surfaces hidden constraints before you propose solutions. Question 9 (one thing most needed) forces a single north star instead of a list of equally-weighted hopes.
Category 3: Tools and Stack (6 questions)
- Which project management tool do you use (Notion, Asana, Trello, ClickUp, Monday, other)?
- What CMS or website platform are you on (WordPress, Webflow, Shopify, custom)?
- What analytics/reporting tools are in use (GA4, Search Console, Mixpanel, Looker)?
- Which communication tools does your team use (Slack, Teams, email only)?
- What marketing/CRM tools are relevant to this project?
- Are there tools we'll need admin access to? (List them.)
Why this matters: This is the input for your access collection tracker. If you skip it now, you spend week 2 sending back-and-forth emails asking for credentials one tool at a time. Question 15 also starts the access-request conversation before your formal access email.
Category 4: Current Process and Constraints (5 questions)
- How are you currently handling this work (in-house, freelancer, previous agency)?
- What's the biggest frustration with how it's been running?
- Are there any platforms, tools, or processes that are off-limits or fixed?
- What is the approval process for deliverables on your side?
- Are there any legal, compliance, or brand constraints we need to know about?
Why this matters: Question 19 (approval process) predicts your delivery timelines better than any project plan. One-person approval = faster. Committee approval = build in 2x time. Question 18 (off-limits) prevents surprises after delivery has started.
Category 5: Assets and Access (4 questions)
- What assets will you need to provide us with (brand guide, copy, images, videos, logins)?
- Do you have a brand guide or style reference we should follow?
- Who on your side will be responsible for providing assets on time?
- What is your current timeline, and are there any hard deadlines?
Why this matters: Question 23 assigns explicit ownership for asset delivery on the client side. Without it, "the client" is responsible — which means nobody specific is. Hard deadlines (question 24) surface before they become surprises in week 3.
Category 6: Communication Preferences (3 questions)
- How would you like to receive updates — email, Slack, a shared doc?
- How frequently do you want status check-ins?
- What response time is realistic on your side for urgent questions?
Why this matters: This is the lowest-effort category but the one most agencies skip. Discovering a client expects daily updates after week 2 has started — when you've been sending weekly reports — is a completely avoidable trust problem.
How to use this in practice
Before the kickoff call:
- Send the intake form the same day the contract is signed
- Set a clear return deadline (3 business days is standard)
- Before kickoff, score each answer for completeness:
- 3 = clear enough to act on
- 2 = usable, but needs one follow-up
- 1 = vague or missing
Any answer scored 1 or 2 becomes a kickoff agenda item. That turns the meeting into a decision session instead of a discovery call.
At the kickoff call:
- Use the intake as your agenda
- Address every flagged gap from the missing-input check
- Document scope decisions in the meeting, not after it
The result
With a structured intake, your kickoff call becomes a decision-making meeting instead of a discovery session. Your delivery team gets a briefing document instead of verbal handoff. Your access collection starts on day one instead of day 7.
That's the boring secret to onboarding that doesn't fall apart in week two.
Free download
The full 27-question intake form is available free at:
agencyonboardingos.com/intake-form
No email required.
If you want the full system — the intake form, onboarding checklist, SOP template, 6 automation recipes, and AI prompt workflows as a bundle — it's at agencyonboardingos.com as a launch bundle.
Agency Onboarding OS · Questions → lisa@agencyonboardingos.com