Client Kickoff Meeting: Agenda and Questions for Freelancers

The contract is signed, the deposit is paid and everyone is excited. This is the moment most freelancers skip straight to the work. It is also the moment where most project problems begin: unclear feedback rules, a decision maker nobody met, a deadline that depended on content nobody owned.

A kickoff meeting fixes that in an hour. It turns the proposal into a shared plan and gives you a clear record of what everyone agreed. Here is how to run one.

Why the kickoff matters

The proposal describes what you will deliver. The kickoff settles how the project will actually run:

• Who decides. The person who signed the contract is not always the one who approves the work.
• How feedback works. One consolidated round per deliverable, or comments from five people in three tools?
• What the client owes you. Content, access, assets and approvals, each with a date.
• What success looks like. A sentence you can come back to when the project drifts.

An hour spent here saves many hours of rework later, and it shows the client that you run projects, not just tasks.

Before the call

• Send a short agenda a day or two before, so the client can bring the right people and materials.
• Ask who should join. Insist politely on the person who gives final approval. Twenty minutes with them now beats a surprise veto in week four.
• Reread the proposal and note every assumption that depends on the client.
• Ask for consent to record. A recording lets you listen instead of type. Our guide on recording client calls legally explains how to ask.

A 60-minute agenda

For small projects, 30 minutes is enough: keep the same order and spend less time on each block. Do not drop the last block. It is the one that turns the conversation into a plan.

Questions worth asking

You don't need all of them. Pick the ones that fit the project and write the answers down.

Goals

• What made you start this project now?
• What does success look like in three months?
• How will you measure it?
• What would make this project a failure, even if we deliver everything?

Scope

• Which deliverable matters most if time gets tight?
• Is there anything you expect that is not in the proposal?
• What have you already tried, and what did you not like about it?

People

• Who gives final approval?
• Who else will give feedback, and how do we bundle it?
• Who is my day-to-day contact, and who covers when they are away?

Process

• Where should questions go: email, chat, a shared document?
• How quickly do you usually give feedback?
• Are there dates when nothing can happen, like holidays, trade fairs or board meetings?

The question about what is "not in the proposal" is the most valuable one. It brings hidden expectations into the open while they are still cheap to discuss. If something comes up, handle it as a change, not as a favor. Our guide on scope creep has scripts for that conversation.

Settle these before work starts

Before you hang up, make sure you have a clear answer to each of these:

• The final approver, by name
• The number of revision rounds and who consolidates feedback
• The communication channel and your working hours
• The client's inputs: content, assets, logins, with dates
• The milestones, each with a date
• The next meeting, already in both calendars

If one of these is still open, it becomes an action item with an owner and a date.

After the call

Within an hour, while everything is still fresh:

1. Send the recap. Decisions, action items, open questions, next step. Our meeting summary template gives you the structure.
2. Write clear action items for both sides, the client's included. See how to write action items that get done.
3. Put the milestones into your calendar, together with the work blocks that lead up to them. A deadline without planned work is a hope. Our guide to weekly planning shows how to fit it in next to your other clients.
4. Log the time. The kickoff is part of the project, and usually billable.

Common mistakes

• Treating it as a sales call. The client has already bought. Focus on planning, not on convincing.
• Skipping the decision maker. If they cannot join, schedule a 15-minute call with them separately.
• No dates for client inputs. "Texts will follow" is how launches slip. Agree on a date.
• No written recap. Without it, the kickoff exists only in everyone's slightly different memory.

Checklist

• Agenda sent in advance
• Final approver present or scheduled separately
• Consent to record confirmed
• Goal of the project in one sentence
• Scope walked through, hidden expectations discussed
• Feedback rounds and channels agreed
• Milestones and client inputs dated
• Recap with action items sent within the hour

Start the project with a protocol

Winnie records your kickoff call in the browser and writes the transcript, a summary with decisions and open points, and the action items with owners and deadlines where they were mentioned. The protocol is filed under the client, next to their tasks and tracked hours. See how the meeting protocol works.