AI Project Kickoff Meeting: A Practical Agenda

A kickoff meeting is the first working session after the client has said yes. Its job is narrow: make sure both sides agree on what is being built, who decides what, how feedback flows, and what happens when the plan changes. Run it well and most of the arguments you would have had in week five never happen.

This is different from the discovery call. Discovery happens before a deal, to learn the problem and decide whether you can help. Kickoff happens after, once the proposal is signed, to start work cleanly. Keep it to 45 to 60 minutes and send the agenda in advance.

The seven-part agenda

1. Restate the goal in one sentence (5 minutes)

Read back what the project is for, in the client's terms, not yours. "A booking page that lets customers pick a time without calling us" beats "a scheduling web application". Ask the client to correct it. If they hesitate, you have found a misunderstanding before it cost money.

2. Walk the scope line by line (10 minutes)

Go through what is included and, just as clearly, what is not. Say the exclusions out loud: "This version does not include online payment" is much cheaper to say now than to explain later. Everything you add in this step should end up in writing afterwards.

3. Explain what the AI will and will not do (10 minutes)

This is the part specific to AI builds. Clients often arrive with one of two wrong ideas: that AI makes everything instant and free, or that it will do whatever they imagine. Set expectations plainly:

• AI speeds up drafting and building, but every output is reviewed by you before it reaches them.

• Some outputs will be wrong on first try and need iteration.

• Anything involving their customers' data needs their decisions about what may be sent to which tool.

If the project processes personal data, agree now who is responsible for what, and write it down.

4. Name the decision maker and the feedback loop (5 minutes)

Ask: who gives final approval? How fast can they respond? Delays in feedback stall more projects than technical problems do. Agree on one channel and one expected turnaround, for example "feedback within two working days".

5. Agree milestones and what "done" means (10 minutes)

Break the work into stages the client can see and approve. Tie each to an acceptance statement that two people could not disagree about, such as "a customer can book, cancel, and receive a confirmation email". Link payments to those stages if that is your arrangement; our post on payment milestones for an AI project covers how.

6. Agree how changes are handled (5 minutes)

Name the process before anyone needs it. When the client asks for something outside scope, you will write it up with a price and a date impact, and work begins only on approval. How to handle scope creep explains the thinking, and how to write a change order gives you the document.

7. Collect what you need and set the next date (10 minutes)

List every item you need from the client: logos, copy, accounts, access, example data. Give each an owner and a due date. End the meeting with the next check-in already in both calendars.

Questions worth asking

What to send afterwards

Within a day, email a short summary: the one-sentence goal, the scope and exclusions, the milestones with acceptance statements, the decision maker, the feedback turnaround, the change process, and the list of what you are waiting on. Ask for a reply that says "agreed" or lists corrections. That reply is your protection.

Common mistakes

• Skipping the exclusions because they feel awkward.

• Letting the meeting turn into a design session. Park design questions for later.

• Talking about tools instead of outcomes. Clients rarely care which AI model you use.

• Leaving without dates. An action without a date does not happen.

For the larger picture of turning AI skills into income, see the guide to AI monetization strategies.

Frequently asked questions

What is a project kickoff meeting?

It is the first working session after a client agrees to a project. It confirms the goal, scope, roles, milestones, and how changes and feedback will be handled.

How long should a kickoff meeting be?

Forty-five to sixty minutes is usually enough for a small project. Send an agenda beforehand so the time goes to decisions.

How is a kickoff different from a discovery call?

Discovery happens before the deal and explores whether and how you can help. Kickoff happens after the agreement and starts the work.

What should an AI project kickoff cover that other projects do not?

How AI will be used, what review happens before the client sees output, and who decides what data may be sent to which tool.