A well-run kickoff meeting saves weeks of confusion. The goal is aligning everyone on what’s being built, when it’s due, how work will happen, and who decides. Here’s how to run one that works.
Preparation: Set Up for Success
Send an email three days before with the agenda, background materials, and attendee list. Give people time to prepare.
Prepare visuals you’ll reference. Wireframes, brand guidelines, examples, or a shared project outline. If using Waco3 to track proposals and progress, open it in a browser tab so you can walk people through it.
Schedule for 45 minutes to an hour. Longer and people check out. Shorter and you’ll miss something.
Block the calendar so you won’t be interrupted. Shut down Slack and put your phone away. Model focus so attendees do the same.
Opening: Set Tone and Expectations
Set expectations for the meeting. “We have an hour to cover scope, timeline, and how we’ll work together. I want everyone to understand what we’re building and when we’re launching.”
Thank people for being there. It sets a collaborative tone. You’re aligning, not dictating.
Do a quick round of introductions if anyone doesn’t know each other. Names, roles, what they care about. Keep it to two minutes.
Section 1: Project Overview and Scope (10 minutes)
Start with the big picture. What problem are you solving? Who’s it for? Why does it matter?
Get specific about deliverables. Design mockups? A finished website? Written content? A built product? Be concrete.
Share success criteria. How will you know the project succeeded? “Success is reducing customer support tickets by 20%” or “Success is ranking in top five for our target keyword.”
Name constraints. Budget limits, timeline restrictions, technical requirements. Constraints clarify, they don’t restrict.
Ask if anyone has questions about scope. Don’t move forward until scope is clear.
Section 2: Timeline and Milestones (15 minutes)
Share a visual timeline. A spreadsheet with dates works. A Gantt chart is nicer but not necessary.
Walk through each milestone. When is it due and what does it include? “Milestone one is discovery and strategy, due June 10th. It includes competitive analysis, user research summary, and our recommended approach.”
Mark decision points and review dates clearly. “On June 12th, we need your approval on the design direction. If we don’t have it, we’ll slip the launch date.”
Discuss what happens if milestones slip. If the client doesn’t deliver assets on time, what happens? If feedback comes in late, do you push the deadline? What’s the contingency plan?
Section 3: Communication and Process (15 minutes)
This is where most meetings fail, so give it time. Explain exactly how the team will work together.
“How will we communicate? Email for major decisions, Slack for quick questions, weekly Zoom calls Thursdays at 10am. Does that work?”
State your availability and response time. “I check email twice daily and aim to respond within 24 hours. I don’t work weekends.”
Explain how you’ll present work. “I’ll deliver designs in Figma. Leave feedback directly in comments, or we can talk through it on a call.”
Define revision rounds. “The initial scope includes two revision rounds. Beyond that, we either extend the timeline or treat it as additional work with extra fees.”
Show clients how to access your project management software, see progress, and provide feedback.
Section 4: Roles and Decisions (10 minutes)
Name who does what. “As the designer, I handle creative direction and execution. On your side, who’s the primary decision maker? Who approves designs? Who handles budget approvals?”
Get explicit answers. “So Jane, you’re the decision maker on brand direction. Mark, you handle technical requirements. Does that work?”
Discuss decision-making. “If we disagree on direction, how do we resolve it? Do you have final say or do we vote?” Better to clarify now than fight later.
Identify dependencies or blockers. “We need you to provide brand guidelines and logo files by June 3rd.”
Role clarity removes half your project management headaches. When everyone knows exactly what they’re responsible for, work flows smoothly.
Closing: Next Steps
Summarize what was decided. “To recap, we’re launching by July 15th. Milestones due on the 10th and 24th. Feedback within 48 hours of each delivery. Jane is the decision maker. Mark handles technical questions. We sync weekly on Thursdays.”
Confirm alignment. “Does this all make sense? Does anyone have concerns?”
Set a clear next step. “I’ll send a written summary today. Please review and send corrections by Friday.”
Send that written summary within a few hours. Include dates, responsibilities, and decisions. Ask for written confirmation. This written record prevents disputes later.
A good kickoff meeting takes an hour and prevents weeks of conflict. When teams understand scope, timeline, and process upfront, everything runs better. Projects launch on time and you do your best work because expectations are clear from day one.
Related: Project Kickoff Meeting Agenda Template for Freelancers provides a ready-to-use template you can adapt for your next meeting.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
