Run the first client call like a system, not a conversation
Most kickoff meetings drift. This template gives you a structured 60-minute agenda, the 12 questions that surface project risk early, decisions to lock in before anyone leaves, and the recap email to send within 24 hours.
Why kickoff meetings go wrong
Most kickoff calls feel productive. Everyone leaves energised. Then week two hits: nobody agrees on the revision limit, the approval chain is unclear, and the client is sending feedback directly to your designer on WhatsApp.
The problem is not bad clients — it is an unstructured first call that felt good but produced no written agreements. This template replaces conversation with decisions. Every phase ends with something locked in, not just discussed.
The 60-minute kickoff agenda
Open: set the room
Confirm who is on the call, what role each person plays, and what this meeting needs to produce. Name the decisions explicitly — clients who know the agenda take it more seriously.
- Who is our primary contact for day-to-day questions?
- Who has final approval on deliverables?
- Is there anyone else who should have been on this call?
Scope review: confirm what done looks like
Walk through the contract scope out loud. This is not a legal exercise — it is a shared mental model. If your client's version of "done" differs from yours, you need to find out now.
- When you picture this project delivered, what does it look like?
- What would make this project a success for you personally?
- Is there anything in scope you're less certain about?
- Are there any hard deadlines we haven't discussed?
Lock in by end of this phase
- Confirmed final deliverable list (name each one)
- Agreed launch / handoff date
- Any scope items flagged as uncertain or TBD
Critical questions: surface the risks
This is the highest-value part of the call. The goal is to uncover constraints, preferences, and blockers that your intake form probably missed. Ask each question and listen for the subtext.
- Are there things you've seen other agencies do that you specifically don't want?
- Are there brand or design constraints we should know about beyond the brief?
- Is there a competitor whose work you admire? One you want to be nothing like?
- Who reviews deliverables before they're approved?
- How does internal feedback normally work on your team — is one person collecting it, or does everyone send separately?
- How much notice do you typically need to schedule a review session?
- Is there anything happening on your side in the next 8 weeks that could slow things down?
- Have you worked with an agency before? What went well? What didn't?
Working agreements: set the rules
These are the agreements that prevent 80% of friction. Most agencies skip this phase because it feels awkward. That awkwardness is worth 5 minutes of discomfort now versus a scope fight in week six.
Lock in before leaving this phase
- How we communicate: primary channel + expected response time
- Revision rounds included per deliverable
- Feedback turnaround commitment from client side
- Who can contact whom directly (and who must go through the PM)
- Change request process: what triggers a scope conversation
- Escalation path: what to do if something goes wrong
Access & next steps: assign everything
Every access request that leaves as "I'll get that to you" is a 3-day delay. Confirm what access you need, who owns getting it, and set a specific date — not "end of week", but a day and time.
- Who can grant access to [specific tool/account]?
- Is there a security approval process for adding third parties?
- What's your preferred method for sharing credentials or files?
Leave with
- Access request list with named owner + date per item
- First internal milestone date (your side)
- First deliverable date to client
- Next check-in scheduled
Close: confirm and recap
Summarise the decisions made, read back the next steps with owners and dates, and confirm nobody has unresolved questions. Then send the written recap within 24 hours.
- Is there anything we didn't cover that you expected to discuss?
- Do you have any questions about how we work?
- Is there anything you're still uncertain about?
Post-kickoff recap email (send within 24 hours)
The written recap is as important as the meeting itself. It creates a shared record of what was decided, surfaces any misunderstandings, and signals to the client that you run a tight operation.
Pre-kickoff checklist (complete before the call)
- Send agenda to client 48 hours before the call
- Review the signed contract and intake form responses
- Set up the project workspace (folder, board, tracker)
- Prepare the access request list in advance
- Know your revision limits and be ready to name them
- Have a second calendar invite ready to send at the end of the call
- Assign a note-taker internally (not the person running the meeting)
- Test your video/screen share setup beforehand
Common kickoff mistakes to avoid
If you are learning about the client's business for the first time in the kickoff, you did not do enough intake work. The kickoff should confirm and align, not discover from scratch.
It feels aggressive to say "we do X rounds of revisions and no more." Clients actually want these rules. Without them, every revision request creates anxiety on both sides.
Name the tool, name the person who can grant access, and set a specific date before anyone leaves the call. Open-ended access requests become the first delay in every project.
You remember what was agreed. Your client remembers something slightly different. The written recap resolves this before it becomes a dispute.
More free resources
Get the complete system
Agency Onboarding OS includes 38 practical docs, templates, and workflows — intake forms, SOPs, automation recipes, AI prompt packs, and everything you need to run a premium onboarding process from day one. $49, one-time, founding batch.
Reserve my founding-batch spot — $49 Browse free resources first