A project kickoff meeting is not the same as a sales call, a discovery session, or a client onboarding form. It’s a focused, post-contract conversation where both parties confirm they understand the project the same way — before a line of work is produced. Skipping it saves 45 minutes at the start and costs several hours mid-project.
What a kickoff meeting is (and isn’t)
A kickoff meeting happens after the proposal is accepted and the contract is signed. It’s the transition from “we have an agreement” to “we’re ready to work.”
It’s not:
- A pitch or a sales conversation (that happened already)
- A discovery session (that should have informed the proposal)
- An opportunity to redesign the scope (if the scope needs to change, that’s a separate conversation)
It is:
- A confirmation that both parties read the proposal the same way
- A chance to ask and answer questions before work starts
- The meeting where working patterns are established
The kickoff is held before any billable work begins. If you’ve already started working on deliverables, the kickoff meeting’s ability to prevent misalignment is limited.
Who should attend
For most freelance projects: you and the primary client contact. That’s it. Adding stakeholders who aren’t central to the project extends the meeting without adding proportional value.
If there’s a decision-maker who will approve final deliverables but isn’t the day-to-day contact, ask whether they should attend. It’s better to have them in the kickoff than to discover mid-project that they have strong opinions that weren’t captured in the brief.
What to cover
Project goals and success criteria. Confirm what the project needs to accomplish and how you’ll know it worked. This isn’t just a formality — the client’s stated goal in the kickoff often includes nuance that wasn’t in the written brief.
Scope confirmation. Go through the deliverables list from the proposal item by item. Confirm what’s included. Explicitly name what’s not. Ask if there’s anything the client expected to be included that isn’t in the proposal.
This is also where you confirm revision limits. “We have two rounds of revisions per deliverable — I want to make sure we’re aligned on what a revision round looks like so we use them well.”
Timeline. Present the milestone schedule. Confirm the final deadline. Identify any dependencies — deliverables that require the client to provide content, assets, or approvals first — and assign dates to those dependencies.
Client responsibilities. What do you need from the client, in what format, and by when? Who is authorized to give feedback? Who has final approval authority?
Communication. Establish the working channel, the update frequency, and the format for feedback. Getting this agreed in the kickoff prevents the communication fragmentation that makes projects harder to manage.
Run the kickoff as a facilitator, not a presenter. Your job is to ask questions and capture answers — not to deliver a presentation about how you work.
What to skip
Don’t use the kickoff to present your portfolio, explain your process in detail, or discuss work that might come after this project. The kickoff is about the specific project at hand.
Don’t let it become an open-ended creative discussion. If the client starts generating new ideas or discussing scope additions during the kickoff, acknowledge them and redirect: “That’s worth exploring — let’s make a note and I’ll flag whether it affects our scope after the call.” This isn’t dismissive; it’s focused.
Don’t skip the questions because the brief seems clear. A brief that seems clear often has assumptions embedded in it that surface in the first deliverable. The kickoff is the place to surface them early.
The follow-up summary
Send a written summary within 24 hours of the meeting. Cover what was confirmed, any changes or clarifications from the call, the agreed timeline, client responsibilities with dates, and communication format.
This summary is the project record. It’s what you refer to if the client asks in week four whether a particular item was in scope. It’s also a professional signal: a freelancer who documents the kickoff in writing is a freelancer who manages projects with rigor.
Running your kickoff with the right setup
The practical mechanics: video call (not phone, so you can share a screen or document if needed), a pre-sent agenda, and a running notes document during the meeting. You don’t need a dedicated tool — a shared Google Doc or Notion page works fine.
If you’ve sent your proposal through a platform like Waco3, you can open the signed proposal during the kickoff and walk through the deliverables list together. Having the agreed document on screen during scope confirmation removes any ambiguity about what was signed.
A well-run kickoff meeting takes 45 minutes and prevents the kind of mid-project confusion that costs two or three times as much time to unravel. It’s worth the preparation.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
