Reading about kickoff meeting structure is useful. Seeing what one actually looks like — what’s said, in what order, and what the follow-up looks like — is more useful. This is a walkthrough of a real kickoff meeting for a five-page website redesign, with the actual conversation and the post-meeting summary.
The setup
Project: Website redesign for a 3-person consulting firm Freelancer: Independent web designer Proposal accepted: 2 days ago (sent via Waco3, includes 5-page scope, 2 revision rounds per page) Meeting length: 45 minutes
The opening (5 minutes)
The freelancer opens the call:
“Thanks for making time — I want to use this call to confirm we’re aligned on scope and working process before I start. I’ll be taking notes and sending you a summary after we’re done. I’ll guide us through a few sections, and there’s time for questions at the end.”
This does three things: sets the purpose, signals that there will be a written record, and establishes who’s running the meeting.
Then a brief project restatement: “My understanding from the proposal is that we’re redesigning 5 pages — Home, About, Services, Blog, Contact — with a focus on converting consulting inquiries. You want to launch before your conference in September. Is that right?”
The client confirms, and mentions that the Services page should actually be split into two separate service-specific pages. The freelancer notes this immediately: “Good to know — that changes the page count from 5 to 6. I’ll put together a change order estimate for the extra page after our call and include it in the summary.”
This is the kickoff doing its job — catching a scope difference before work starts.
Goals and success criteria (5 minutes)
“What does success look like for this project? If we ship this and it’s working well, what will have changed?”
The client’s answer: “We want more qualified inbound inquiry calls — right now the website gets decent traffic but almost no one fills out the contact form.”
The freelancer follows up: “So the contact form conversion rate is the primary metric. Is there a specific number you’re targeting, or more directional — just better than it is now?”
“Better than it is now — we get maybe 2 contacts a month from the website. Would love to see that double.”
This is more specific than anything in the brief and shapes how the designer approaches every page.
Scope confirmation (10 minutes)
The freelancer shares the screen and pulls up the signed proposal deliverables section.
“Let me walk through what’s included so we’re both looking at the same list.”
Going through the items, one question surfaces: the proposal includes “desktop and mobile layouts” but the client asks whether that also covers tablet. The freelancer clarifies: “The standard responsive layout I produce scales well across all screen sizes — the specific design documentation is for desktop and mobile breakpoints, but the CSS handles tablet. Is that what you were expecting?”
The client confirms that’s fine.
The freelancer also confirms the explicit exclusions: “Just to be clear — copywriting, photography, and the hosting migration aren’t in this scope. If you need help with any of those, I can refer someone or put together a separate estimate.”
Then the extra page question: “I’ll add a change order for the sixth page — at the same per-page rate as the proposal, that’s an additional $X. I’ll include it in today’s summary for your sign-off.”
Confirming scope from the signed proposal on-screen — rather than from memory — makes the conversation specific and prevents the “I thought that was included” objection.
Timeline (10 minutes)
The freelancer presents the milestone schedule:
| Milestone | Freelancer delivers | Client feedback by |
|---|---|---|
| Page 1–3 wireframes | Week 2 | 3 business days |
| Page 4–6 wireframes | Week 3 | 3 business days |
| Full visual design | Week 5 | 5 business days |
| Revision 1 | Week 6 | 3 business days |
| Final files | Week 7 | — |
The hard deadline is confirmed: the conference starts September 12th, so the final files need to be with the developer by August 29th. This is documented.
One dependency surfaces: the client needs to provide the final company bio and team photo before Week 3. “I’ll block that in on my side — I’ll send you a reminder two weeks before it’s due.”
Client responsibilities (5 minutes)
“For the project to stay on schedule, I’ll need a few things from you:
- Company bio and team photo by [date]
- Any existing brand files (logo, colors, fonts) by Friday
- Consolidated feedback at each milestone — one round of feedback from one person rather than multiple rounds from multiple people
For approvals: is it you who signs off on the deliverables, or does someone else need to review?”
The client mentions that the firm’s managing partner will want to review the final design before approval. The freelancer makes a note: “I’ll add a note in the timeline that final sign-off is with [partner name] — just keep that in mind for the feedback window so we have enough time.”
Communication (5 minutes)
“For day-to-day — email or Slack works fine for me. Which do you prefer?”
Email. The freelancer confirms feedback format: “Please send all feedback consolidated in a single email reply to my delivery message — that keeps it organized rather than scattered across messages. For urgent questions, email is fine but a same-day response might not always be possible. I check email twice a day.”
They agree on weekly Friday status emails from the freelancer, even if the update is just “all on track.”
Open questions (5 minutes)
“Is there anything you expected to be included that we haven’t discussed? Or anything in the proposal that you want to clarify?”
The client asks about the CMS — will the redesign work with their existing WordPress install? The freelancer confirms yes, and notes that they’re designing in Figma for developer handoff, not building the site.
The follow-up summary (sent same day)
Subject: Website Redesign — Kickoff Summary
The summary covers: confirmed scope (now 6 pages, with change order), timeline table, client responsibilities with dates, communication format, and the two clarifications from the call (tablet layout, managing partner approval chain).
It ends with: “Please reply to confirm this looks right. I’ll start on the Home and About wireframes this week and send you an update Friday.”
The client responds the next morning: “Looks great — looking forward to it.”
That response is the confirmation. The project starts from a shared, written understanding with no gaps.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
