Kickoff Calls That Actually Set Up the Project: The 60-Minute Agenda

TL;DR: The kickoff call is the single highest-leverage hour of the entire engagement. Get it right, the project moves smoothly. Get it wrong, spend the next eight weeks fighting confusion. The 60-minute agenda below is timestamped, scripted, and battle-tested. It covers goals, scope, roles, communication, timeline, risks, and the four phrases that prevent half of all future disputes. Use it as-is.

I ran my early kickoffs without an agenda. "Let's chat about the project!" Forty-five minutes of friendly conversation, no scope confirmation, no decision-maker identified, no communication norms set. Project starts. Week four, the CEO sees the design for the first time and rejects it. The marketing manager I'd been working with had no authority to approve. Three weeks of design work, gone. I rebuilt for free because it was technically my fault for not asking who the actual approver was.

I'm Sammie Oku, founder of Eximius Studio, a web design and dev agency in Tyler, TX. The kickoff has happened in the same 60-minute structure for every Eximius engagement since that disaster. Zero kickoff-related project blowups in the 18 months since.

This is the agency kickoff meeting agenda I use, minute by minute, plus the scripts and the four phrases that prevent half of all future disputes.

For context, how to run a web design agency covers the seven systems this fits inside, and the 14-day onboarding checklist covers the broader onboarding flow this kickoff sits inside.

The cost of a vague kickoff

A vague kickoff doesn't fail loudly. It fails six weeks later, when the symptoms appear far enough from the cause that you blame the client. Common patterns:

• Week 4: Designs presented to the wrong approver. Rework required.
• Week 5: Scope item the client thought was included isn't in the proposal. Awkward conversation.
• Week 6: Client expects daily standups; you scoped for weekly. Tension builds.
• Week 7: Feedback comes in piecemeal over two weeks; revision budget burns out by week 8.
• Week 9: Client surprised by Change Order because "we didn't discuss" the scope policy.

Every one of those failures traces back to the same hour: the kickoff that didn't actually lock anything in. An hour of structure at kickoff is worth 15 to 30 hours of cleanup later. That ratio holds across every project I've run.

The structure below is 60 minutes total (50 minutes of agenda plus 10 minutes of buffer). It's tight on purpose. A kickoff that runs to 90 minutes loses the room.

The agenda at a glance

Now the detail.

Minutes 0 to 10: Reintroductions and goal recap

The opening sets the temperature. Don't waste it on small talk.

Step 1: Round of intros (3 minutes). Everyone on the call says their name, role, and what they're contributing to the project. This includes you. Don't assume anyone knows anyone. If new people are on the client side you didn't meet in sales, you find out now instead of week three.

Step 2: Goal recap (5 minutes). You recap the project goal as you understand it from discovery. Use the client's own words from their questionnaire answers wherever possible. The recap script:

"To make sure we're aligned, here's what I understand we're solving for: [Client's stated goal from questionnaire]. The success metric we'll measure against is [client's answer to Q3, the 6-month success question]. Does that match how you'd describe it today, or has anything shifted since we last talked?"

That last sentence is the trap door for surprises. Sometimes the goal has shifted in the two weeks between proposal and kickoff. New information surfaces. Stakeholders weighed in. Better to discover that now than after design is underway.

Step 3: Agenda preview (2 minutes). Walk the client through the next 50 minutes so they know the structure. "Over the next 50 minutes we'll walk through scope, roles, timeline, and risks. By the end, you'll know exactly what's happening for the next 14 days and we'll know exactly what we need from you."

That preview makes the meeting feel professional and gives you license to keep things moving if a discussion runs long.

Minutes 10 to 25: Scope walkthrough

This is the longest section, and the most important. Read the scope out loud. Yes, out loud. Yes, even though the client signed the proposal.

Why out loud: Most clients skim proposals. They sign because the price is right and the vibe is right, not because they read every line. Reading the scope at kickoff is the first time the entire room hears it together, with the chance to clarify or object.

The structure:

1. Read each deliverable. Pause. Confirm understanding. Move on.
2. Read the out-of-scope list. Pause. Confirm. Move on.
3. Ask: "Is there anything you expected to be included that isn't on this list, or anything on this list that's surprising?"

That third question is critical. If a client expected an extra page or an integration that wasn't in the proposal, this is when it surfaces. Better now than week six. Either you absorb it (small, your fault for not catching in discovery) or you raise it as a Change Order before work has started (clean, no awkwardness).

Phrase 1 (the first of four that prevent half of all disputes):

"To confirm, this is in scope: [list]. This is out of scope: [list]. Anything we need to discuss before we move on?"

Get verbal confirmation. Document it in the kickoff recap email you send within 4 hours.

Scope objection handling. Sometimes the client raises a scope concern that wasn't in the proposal. Two paths:

• Small (under 1 hour of work): Absorb on the spot if it's reasonable. Note it in the recap as "added at kickoff, no impact to scope or timeline."
• Larger: "That's a great catch. Let me scope it out as a Change Order and send it over tomorrow. We can decide together whether to add it now or list it for a future phase."

Don't say yes to scope additions in the kickoff room. Promise to scope them and respond in writing. Memory is unreliable. Written Change Orders are not. The full Change Order workflow lives in how to stop scope creep in a web design agency.

Minutes 25 to 40: Roles, communication, decision authority

This is the section most agencies skip and almost every project failure traces back to.

Step 1: Decision authority (5 minutes). Force the named approver question.

Phrase 2:

"Final design approval comes from [single named person], who has authority to sign off on behalf of the company. Is that right?"

If the client says "well, the CEO will weigh in too," you have a problem. Probe:

"Let's clarify. If [primary contact] approves a design but [CEO] later disagrees, who wins? I want to set this up so we're not in a position where we ship a design that gets reversed two weeks later."

The answer reveals the real decision-maker. Sometimes it's the primary contact with CEO sign-off at major milestones. Sometimes it's the CEO with the primary contact as facilitator. Both work. What doesn't work is ambiguity. Force the answer. Document it.

Step 2: Communication channels (5 minutes). What channel for what type of communication.

• Daily work: Email or Slack? (Pick one.)
• Urgent issues: Phone? Slack DM? Email with "URGENT" in subject?
• Weekly updates: Where will they land?
• Formal approvals: Email, for paper trail.
• Files and deliverables: Project Home page in Notion, with email notification when something new is posted.

Phrase 3:

"You'll have feedback for us within [X] business days of every deliverable. We'll respond to your messages within [Y] business hours during our normal business hours of [hours]. Outside those hours, we'll respond the next business day. Does that work?"

Lock the response expectations both ways. This is the language that prevents 24/7 expectations. For retainer engagements, this should already be written into the retainer agreement clauses the client signed; the kickoff is where you reinforce it out loud.

Step 3: Meeting cadence (5 minutes). How often do we talk, and about what?

The default rhythm I propose:

• Monday morning: Status update from us (3-bullet email or Loom video)
• Wednesday: 30-minute check-in call only if there are open decisions
• Friday: End-of-week summary

Some clients want more, some want less. Negotiate at kickoff so nobody is surprised in week three. Daily standups with clients are almost always a bad idea unless the project is genuinely urgent. A 5-minute Monday status email is more valuable than a daily 15-minute call.

Minutes 40 to 55: Timeline, milestones, dependencies

The timeline section is where the project's reality gets confirmed.

Step 1: Walk the timeline (8 minutes). Show the milestone calendar. Confirm key dates:

• Phase 1 (Discovery): start to end dates
• Phase 2 (Design): start to end dates, including first design review
• Phase 3 (Build): start to end dates
• Phase 4 (QA and Launch): start to end dates
• Hard external deadlines (product launch, event, fiscal year)

For each milestone, name the deliverable and the approval gate. "By April 12, you'll have homepage designs for review. We need your written feedback by April 17 to keep the timeline."

Step 2: Dependencies (5 minutes). What does the project depend on from the client side?

Common dependencies:

• Final copy by [date]
• Brand photography by [date]
• Access to third-party tools by [date]
• Stakeholder availability for review on [dates]

Phrase 4:

"This timeline assumes feedback within [X] business days at each milestone and assets delivered by the dates we just discussed. Delays on your side will shift the timeline by an equivalent amount. We'll flag any risks early so we can adjust together."

That sentence prevents the "you missed the launch date" conversation later. The timeline is conditional on the client meeting their dependencies. If they don't, the timeline shifts. Said in advance, accepted in writing, never a surprise later.

Step 3: Risks (2 minutes). Name the top two or three risks you see. Examples:

• "Copy is the most common cause of delay. If we can't get it from you by [date], we'll need to either extend the timeline or use placeholder content."
• "We've scoped one round of design revisions per phase. If we need more, that's a Change Order conversation."
• "The migration of 80 blog posts from your current CMS is a real chunk of work. We've scoped for it, but if any unexpected formatting issues come up, we'll flag them as we find them."

Naming risks upfront is not pessimism. It's professionalism. Clients trust agencies that surface risks. They distrust agencies that pretend everything will go smoothly.

Minutes 55 to 60: Next actions and sign-off

The close. Tight, specific, action-oriented.

Step 1: Single next action per party (3 minutes). What's the one thing each side owes the other in the next 48 hours?

• "From us in the next 48 hours: I'll send the kickoff recap email with everything we agreed to today, plus the asset request list. You'll see those tomorrow morning."
• "From you in the next 48 hours: confirm the named approver in writing if you need to check with anyone, and send over [the first asset item] to unblock the discovery phase."

Step 2: Confirm everyone understands (2 minutes). Ask: "Is anyone leaving this call with a question they didn't get answered?" Wait for the silence. Sometimes someone speaks up at this point with the thing they were too polite to interrupt for. Capture it.

End the call on time. A kickoff that ends at 58 minutes signals respect. A kickoff that runs to 75 minutes signals lack of discipline.

The kickoff recap email (sent within 4 hours)

This is the deliverable from the kickoff. Send it the same day, ideally within 4 hours.

Structure:

"Hi [Client], thanks for the kickoff today. Here's the recap:

Project goal: [one sentence]

Success metric: [from the discovery]

Scope in: [bulleted list]

Scope out: [bulleted list]

Final approver: [name and role]

Communication: [email/Slack, response time expectations, cadence]

Timeline milestones: [list with dates]

Top risks: [list]

Next actions from us: [list with dates]

Next actions from you: [list with dates]

Please reply with any corrections within 2 business days. If I don't hear back, I'll proceed assuming this captures our agreement. Looking forward to a great project."

That recap becomes the source of truth for the engagement. If anything is disputed later, the recap is the reference point. If the client doesn't respond, the recap stands by default. That sentence at the end ("if I don't hear back, I'll proceed assuming this captures our agreement") is the most underused piece of language in agency onboarding. Save the recap as the Kickoff Notes section of the Project Home page in your Notion workspace so it stays linked to the project, not buried in email.

Building this from scratch is slow. The full kickoff agenda, the recap email template, the four phrases, and the scope walkthrough script are inside Agency Operations OS. Deploys in an afternoon, $79. Link at the end.

The four phrases that prevent half of future disputes

Recapped here for easy reference. These are the language patterns that hold over the life of a project.

1. "To confirm, this is in scope: [list]. This is out of scope: [list]. Anything we need to discuss before we move on?"
2. "Final design approval comes from [single named person]."
3. "You'll have feedback for us within [X] business days of every deliverable."
4. "This timeline assumes feedback within [X] business days and assets delivered by [dates]. Delays on your side shift the timeline equivalently."

Every one of those phrases prevents a specific common dispute. Memorize them. Use them.

Kickoff variations by project size

The 60-minute structure works for most engagements. Two variations:

Smaller projects (under $5,000). Compress to 30 minutes. Skip the deep risk section, condense scope walkthrough. Still hit all five sections. The four phrases stay.

Larger projects ($30,000+). Extend to 90 minutes if multiple stakeholders are on the call. Add a "team introductions and capabilities" section at the start (10 minutes) and a "approval workflow" section in the roles part (5 minutes) so you understand how decisions flow through their organization. The agenda structure scales.

Enterprise engagements ($100,000+). Run two kickoffs: a 30-minute "executive kickoff" with senior stakeholders to confirm goals and timeline, and a 90-minute "working kickoff" with the actual project team to dig into scope and operations. Separating these prevents you from boring executives with operational detail while still locking in operational specifics.

What to do when the client wants to "just get started"

Some clients push back on a structured kickoff. "Can we just dive in? We've already talked through everything in sales."

The response:

"Totally hear that. The 50-minute structure is what I've found prevents 90% of the issues that show up in week six. It's an investment now to save us both time later. Let's keep it tight, hit the agenda, and we'll be in delivery mode by tomorrow."

Hold the line. Clients who skip kickoffs are also the clients who later complain that "we never discussed" something. The kickoff is the conversation where you discussed it. Run it every time.

Frequently asked questions

How long should a kickoff meeting be?

60 minutes is the standard target (50 minutes of agenda plus 10 minutes buffer). Shorter than 30 minutes usually means critical alignment was skipped. Longer than 75 minutes loses the room and signals lack of structure. The five-section agenda (reintro, scope, roles, timeline, risks) fits comfortably in 50 minutes if you stick to time.

What should be in a project kickoff agenda?

Five sections in this order: reintroductions and goal recap (10 min), scope walkthrough with in-scope and out-of-scope confirmation (15 min), roles and communication including the named final approver (15 min), timeline with milestones and dependencies (15 min), and risks and next actions (5 min). Skip the icebreaker games. Clients are busy and a structured kickoff signals professionalism.

Who should attend the client kickoff meeting?

From the agency side: the project lead and one or two key team members (designer, developer). From the client side: the primary contact, the named final approver, and any internal stakeholder whose feedback will be incorporated. Keep it under 8 people total. Larger groups make it impossible to lock decisions. If more people need to be informed, send them the recap instead of inviting them to the meeting.

What's the difference between a sales discovery call and a kickoff meeting?

Sales discovery happens before the contract and answers "what should we build and what should it cost." The kickoff happens after the contract is signed and the deposit has cleared, and answers "how will we work together to actually build it." Discovery is about exploration. Kickoff is about execution. Many agencies conflate them and the result is a kickoff that re-litigates scope instead of operationalizing it.

Should I send notes after the kickoff meeting?

Yes, within 4 hours. The kickoff recap email is the most important deliverable of the entire onboarding phase. It documents what was agreed, names the next actions, and becomes the reference point for any future scope or process disputes. End the recap with "please reply with corrections within 2 business days; otherwise I'll proceed assuming this captures our agreement." That sentence makes the recap legally referenceable.

The shortcut: Agency Operations OS

Writing the kickoff agenda, the recap email template, the scope walkthrough script, and the four phrases takes a few hours. Wiring them into the actual workflow (calendar templates, the Project Home page in Notion, the asset request list that fires after the kickoff) is the harder part.

Agency Operations OS is the Notion template I use to run Eximius Studio. It includes:

• 7 core databases: Leads, Deals, Projects (with the kickoff agenda template per project), Retainers, Change Orders, Financials, AR Aging
• 5 dashboards including an Onboarding Health view that shows every active client's kickoff status
• 15 SOPs including the full kickoff process, recap email template, and onboarding cadence from this post
• 5 bonus docs: Master Services Agreement, Retainer Agreement, Project Proposal template, Discovery Call script (which feeds the kickoff), and the 47-item Pre-Launch QA Checklist

One template, deploys in an afternoon, $79.

Get Agency Operations OS →

The 60-minute structure above is the agency kickoff meeting agenda that turns the first project meeting from a friendly chat into the operational anchor of the engagement. Run it every time. The recap, the four phrases, the named approver, the in-scope and out-of-scope confirmation: these prevent half the disputes that would otherwise show up six weeks later.

For where this fits, how to run a web design agency covers the seven systems this lives inside, and the 14-day onboarding checklist covers the broader onboarding flow.