A client kickoff meeting agenda for freelance developers

A client kickoff meeting is the first call after the contract is signed, where the goal, the scope, the people and the access are agreed in front of everyone who matters. This guide gives freelance developers and independent consultants a one-hour agenda with timings, the questions to ask in each block, what to write down, how to prepare, and the recap to send the same day. It applies to kickoffs on Google Meet and Microsoft Teams, whoever hosts the call. It picks up where the discovery call guide leaves off.

What is a client kickoff meeting for?

A kickoff turns a signed proposal into a working project. By the end of it both sides should agree on the goal, on what is in and out of scope, on who approves the work, and on the date of the first milestone. Nobody should leave it waiting for access they did not know they needed.

It is not a second discovery call or a pitch. The client has already said yes; what they want now is evidence that the project is in hand. The kickoff also produces the first written record of the engagement, the one you will quote in week six when somebody remembers the scope differently.

What should a project kickoff meeting agenda include?

Seven blocks, in this order, in an hour. Put the agenda in the calendar invitation and send it two working days ahead, so the client can add anything before the call rather than during it.

Time	Block	What has to come out of it
0:00–0:05	Introductions and roles	Who approves, who is day-to-day, who controls access
0:05–0:15	The goal, read back	One sentence on the goal that the client agrees with
0:15–0:25	Scope	What is in, what is out, what is "later"
0:25–0:35	Access and environments	A list of accounts and systems, each with an owner and a date
0:35–0:45	Ways of working	Channels, meeting rhythm, response times, what "done" means
0:45–0:52	Risks and milestones	Outside dates, dependencies, the first milestone
0:52–1:00	Actions and next call	Every action read aloud with an owner and a date; the next call

Read the goal back yourself rather than asking the client to restate it. "Here is how I understood it: you need the monthly invoice run to take an hour instead of three days. What would you change?" Corrections at this point cost nothing. The same correction in week four costs a sprint.

Which questions should you ask at a kickoff?

One or two per block is enough. Ask them plainly and let the answer run.

Block	Question	What you are listening for
Roles	"Who signs off on the work, and who do I go to day to day?"	Two names, or one name said twice
Roles	"Who else will have an opinion that we haven't met yet?"	The stakeholder who appears at the first demo
Scope	"What is the one thing that has to work at the first release?"	The real priority, which is rarely the first feature listed
Scope	"What did we agree is not in this phase?"	The client saying it, so it is theirs as well as yours
Access	"Who can create my accounts, and how long does that usually take?"	A person and a realistic lead time
Access	"Is there a staging environment, and who deploys to production?"	Whether you will ever touch production
Ways of working	"Where should questions go: email, a chat channel, or the weekly call?"	One answer, not "wherever"
Ways of working	"When a piece of work is done, is that merged, on staging, or accepted by you?"	A definition of done you can write down
Risks	"Is there a date outside this project that it depends on?"	A launch, an audit, a board meeting, a holiday
Notes	"Is it all right if I record our calls for the notes?"	A yes, a no, or "not this one"

If the client is giving you an email address on their domain, ask for it now, so invitations arrive where you can see them; see the Google Workspace and Microsoft 365 guides. If a notetaker will join your calls, say so here; how to tell clients you use an AI notetaker has the wording. Rules on recording differ by country and by contract, so check yours.

What should you write down word for word?

Anything you will quote later. That means:

• Every name with its role, spelt correctly. Ask for the spelling.
• Every date: the first milestone, the launch, the holidays.
• Every "not now", "later" or "phase two", with who said it.
• The definition of done, in the client's words.
• Every promise of access, with the person and the day.

Summarise the rest: the history of the previous agency and your own explanation of how you will work get a line each. If you are running the call and taking notes at once, type only the lines in that list; taking notes while running a video call has techniques.

What should you prepare before the kickoff?

Half an hour, the day before:

• Reread the discovery notes and the proposal. Copy the client's own description of the problem into your agenda.
• List the access you need as a table: repository, staging, cloud console, error tracking, design files, a test account, a shared channel. Paste it into the invitation so the person who creates accounts sees it before the call.
• Draft the first milestone date you will propose, and the reason for it.
• Decide your own working hours and the reply time you will offer. Clients remember the first number they hear.
• Open the meeting link once. If the client hosts on Teams and you have never joined their tenant, find out now whether you land in a lobby.
• Agree which language the minutes are written in, if the client's team does not all read English. A client whose operations team works in French may want French minutes; meetings without a shared first language covers how to settle it.

What do you send after the kickoff?

A recap, the same day, under three hundred words. It is the first document of the engagement, so give it a subject line you will reuse.

Subject: Kickoff recap: [Client] [project], [date]

Hi Priya,

Thanks for today. Here is what we agreed.

Goal: Cut the monthly invoice run from three days to under an hour.

In scope (phase one): invoice import, matching, export to the accounting system.
Not in this phase: the customer portal, the mobile view.

Decisions
1. Work is "done" when it is on staging and you have accepted it in the review.
2. Questions go to the shared channel; I reply within one working day.

Access
- Repository and staging: Tom, by Friday 30 October.
- Test account on the accounting system: Priya, by Wednesday 4 November.

Actions
- I will send the first milestone plan by Tuesday 27 October.
- Priya will confirm the year-end freeze dates by Monday 26 October.

Next call: weekly status, Thursdays 10:00 (UK time), first one on 29 October.

If I have misstated anything, tell me by Monday and I will correct it.

Attach the full minutes as a PDF; the client meeting minutes template has a layout, and the follow-up email guide has templates for later calls. Keep the recap in the client's folder. It is the first thing you will open when the scope starts to move.

What usually goes wrong at a kickoff?

Four things, each fixable on the call:

• The approver is absent. A scope agreed without them is a draft. Hold that block until they are there.
• "We'll work it out as we go." Write it as an open question with a date, not as scope.
• Access drifts. Name a person and a day for every item, and chase on that day.
• Nobody defines done. Without it, every review becomes a negotiation.

How does TrackHeros handle a kickoff meeting?

TrackHeros is an AI meeting notetaker that joins Google Meet and Microsoft Teams calls as a visible participant, about two minutes before the start. Connect the calendar account the client issued you, Google or Microsoft, under that client, and the kickoff lands in that client's own workspace from the first meeting. The bot's name can be set per client, and it can post a welcome message in the meeting chat when it joins.

After the call it writes a summary with a fixed shape: summary, decisions, discussion by topic, agenda, milestones with dates, and action items. The agenda is taken from the calendar invitation when it has one, so the agenda you put in the invite becomes the agenda in the notes; otherwise it is reconstructed from the conversation and marked as such. Each action item carries the owner's name as heard, flagged for you to check if that name was not in the meeting, and a due date kept verbatim ("by Friday") and resolved to a date.

To send the recap, Copy for email puts the minutes on your clipboard as formatted text, on every plan. On paid plans (pricing) Download PDF lays them out as formal minutes in the client's own template, with a heading, one of five colour themes and a switch for each section. Nothing is sent on your behalf. Weeks later, you can open the client and ask "what did we say was out of scope for phase one?" and get an answer cited to who said it and when, linked to the moment in the recording. More at meeting minutes, ask your meetings and every calendar in one notetaker.