How do I run a client project kickoff meeting?

What a client kickoff meeting is for

A kickoff meeting is the first working session after the client has agreed to the project. For a freelancer or small studio, its job is narrow: turn the accepted quote into a shared plan, meet the people who will make decisions and remove the obvious risks before work starts.

It is not a sales call and not a brainstorm about new features. The price and the deliverables are already agreed. If the conversation drifts into new work, note the idea and handle it later as a separate proposal. That keeps the meeting short and the scope intact.

Hold it soon after acceptance, ideally within a week, while the reasons for buying are still fresh. A video call works well for most small projects. Keep the attendee list short: the people doing the work on your side, and the reviewers and decision makers on the client side. Anyone else can read the recap.

Prepare before the meeting

Good kickoffs are mostly preparation. Reread the accepted quote or scope and list anything that is still vague. Collect the inputs you need from the client, such as brand files, logins, content or a list of stakeholders, and check which ones you already have.

Send the agenda a day or two ahead with a short note on what to bring. Ask the client to invite the people who will review the work and the person who can approve changes to price. If the decision maker cannot attend, you will need their confirmation in writing afterward, so it is better to know now.

Prepare a one-page summary you can share on screen: the deliverables, the milestones, the revision rounds and the open questions. Reading from a shared page keeps the meeting concrete and gives everyone the same reference.

Finally, decide what you want to leave the meeting with. Usually that is three things: confirmed approvers, a confirmed first review date and a dated list of client inputs. If you write those outcomes down in advance, you will notice during the call when one of them is still missing and can ask for it before everyone leaves.

Use a timed kickoff meeting agenda

Forty-five minutes is enough for most small projects. Keep to the clock, and park anything that needs more time for a follow-up message.

1. Introductions and roles, 5 minutes: who is here, what each person does on the project.
2. Goals and scope, 10 minutes: restate the outcome, the deliverables and what is excluded.
3. Approvers and permissions, 5 minutes: who reviews work, who approves price changes and who pays invoices.
4. Timeline and inputs, 10 minutes: milestones, client deadlines for content and access.
5. Communication and feedback, 10 minutes: one channel, response times, consolidated feedback rounds.
6. Risks and next steps, 5 minutes: open questions, owners and the date of the first review.

Confirm who decides what

Many project delays start with an unclear approver. The person who attends every call is not always the person who can accept a higher price. Ask directly: “Who reviews the designs, who can approve a change to the budget, and who should receive invoices?” Write the names down.

Keep those roles separate. Reviewing a deliverable, approving a change in scope and paying an invoice are different decisions, and one person may hold only one of them. If a reviewer asks for extra work, you then know to send the priced proposal to the commercial approver, not just to whoever asked.

Agree how feedback arrives. Consolidated feedback from one named person per round is far easier to act on than comments from five people in three tools. State how many rounds the price covers, as the quote does, and what counts as a round.

Record decisions, not a transcript

You do not need minutes of everything said. Record what was decided, what is still open and who owns each next step. A short list is easier to confirm than a long summary, and the client is more likely to read it.

A practical kickoff checklist covers five things: the confirmed scope and exclusions, the named approvers, the communication channel and response times, the client’s input deadlines and the date of the first review. If any of these is still unknown when the call ends, assign an owner and a date to resolve it.

Decide where the record lives. Choose one shared place for the scope, decisions and review links, and say so in the meeting. When a question comes up in week four, both sides should know where to look instead of searching old email threads and chat messages.

Project leaders often describe the kickoff as the moment to set expectations for honest feedback and open questions. Ask about risks while everyone is in the room. A concern raised in week one is cheaper to solve than one discovered at the first review.

Send a recap email the same day

A written recap turns the conversation into a record both sides can check. Send it within a few hours, while details are fresh, and ask the client to reply with corrections.

Example: “Hi John, thanks for today. Here is what we agreed. Scope: the six-page website refresh in quote version 2, with copywriting excluded. Reviews: you consolidate feedback, and two rounds are included. Budget changes: you approve any priced additions. Inputs: Acorn sends final copy and photos by May 12. First review: homepage design on May 19. Open question: you will confirm hosting access by Friday. Please reply if anything here is wrong. Emi”

Keep the recap to what was decided. If the client mentioned a new idea, add one line saying you will send a separate proposal for it. That acknowledges the request without adding it to the scope by accident.

If the client replies with a correction, update the recap and send the corrected version in the same thread. Silence after the recap is not a signed agreement, but a corrected, acknowledged summary gives both sides a clear starting point for the first review.

How Moolamochi supports a kickoff

Moolamochi’s client portal keeps viewing, requesting, approving and paying as separate permissions. A requester can describe a change without gaining authority to accept its price; the named commercial approver decides the scope proposal. Delivery approval applies to a current published version, separately from commercial approval. Clients see a published view, not private tasks, cost rates or internal notes. New accounts are currently waitlist-only.