Website project kickoff meeting agenda for agencies
The first client call sets the habits for the whole project. This website kickoff meeting agenda gives you a 60-minute plan you can copy, with a full 15 minutes on how feedback and approvals will work, so the review process is agreed before anyone sees a first draft. There is also a follow-up email to confirm what was decided.
Why the kickoff decides how reviews go
Most kickoff calls cover goals, pages and dates, then end with "we'll send the first draft in two weeks". Nobody says who will review it, how they should leave comments, or who can sign it off. So the first draft goes out, and feedback arrives from five people in three places, two of them disagreeing, one of them the director who wasn't on the call.
The fix is cheap: spend a quarter of the kickoff agreeing how feedback and approvals will work. People are keen at the start of a project and happy to agree a process. Three weeks in, with comments already arriving by email, the same conversation feels like a complaint.
The 60-minute agenda
The times below are a suggestion for a typical small or mid-sized website. Move minutes between sections to suit the project, but protect the feedback and approvals slot.
| Time | Section | What to settle |
|---|---|---|
| 0 to 5 min | Introductions and roles | Who is who on both sides, and who does what day to day |
| 5 to 15 min | Goals and success | What the site is for, who it is for, and how you'll know it's working |
| 15 to 25 min | Scope | The pages and features at launch, and what is not included |
| 25 to 35 min | Content and access | Who writes and supplies each page, by when, and who holds the logins |
| 35 to 50 min | Feedback and approvals | Client lead, reviewers, rounds, deadlines, how comments are given, what Approve means |
| 50 to 55 min | Timeline | Key dates, review windows and the launch date |
| 55 to 60 min | Recap and next steps | Decisions read back, open questions with owners, the next action for each side |
Send this as the calendar invite text, or paste it into your meeting notes. Swap the parts in curly brackets for your own details.
What to cover in each section
Introductions and roles
Keep it short. The useful part is the second half: who the client should contact day to day, who on your side makes the changes, and who will join reviews. Write the names down; you'll need them in the feedback section.
Goals and success
Ask what the one thing is that a visitor should do on the site, and how the client will judge it after launch. If you sent a web design client questionnaire before the call, use their answers as the starting point rather than asking the same questions again. Spend the time on anything vague or missing.
Scope
Read out the pages and features in the proposal and confirm them. Then say what is not included, out loud. "The blog migration isn't part of this phase" is easier to say now than in round two, and it gives you something to point to when a request falls outside the scope. Mention how extra requests will be handled, for example with a website change request form.
Content and access
Content is the most common reason a website launches late. For each page, agree who writes it, who supplies the images, and the date it arrives. "Marketing will write it" is not an answer; a name and a date is. Then list the logins you need: domain, hosting, the current site, analytics, and any tools the site connects to.
Timeline
By this point you know the rounds and their length, so the timeline mostly falls out of the feedback section. Confirm the launch date and what it is tied to, and check for holidays or busy periods on the client side that will slow reviews.
Recap and next steps
Read the decisions back in one or two lines each, and let people correct you while they're still on the call. List every open question with an owner and a date. Finish with the next action for each side, such as "We send the sitemap on Friday; you send the About copy by the 4th."
The feedback and approvals section
This is the 15 minutes that saves the most time later. Work through these six points and get a clear answer to each. If the client can't answer one yet, it goes on the open questions list with an owner.
- One client lead. Ask for the one person who has the final say and settles disagreements between reviewers. "The team" is not an answer; ask who decides when the team disagrees. Make sure that person sees every round, not just the last one.
- Who else reviews, and which parts. Name each reviewer and what they look at: the sales director checks the services pages, legal checks the footer and forms. Reviewers who know their area leave fewer, better comments.
- How many rounds, and what each is for. For example, round one for structure and message, round two for wording, images and the phone layout, round three for final fixes. Say what happens if more rounds are needed. Our post on website revision rounds covers how to choose the number.
- Deadlines for each round. Agree a review window in working days, and what happens when it passes with no comments. A common rule is that the client lead's silence after a reminder counts as approval of that round.
- How comments are given. Agree one place for feedback, and say it plainly: comments go on the review link, not in email, chat or calls. Ask reviewers to leave one comment per point, on the thing it is about, and to check on their phone as well as a computer.
- What Approve means. Agree that approval comes from the client lead, applies to a specific version, and moves the project to the next stage. Say what changes after approval count as new work. Write down how approval will be given, so nobody argues later about whether a thumbs-up in chat counted.
For the full process behind these points, see our guide to setting up a client feedback process, and how to get client approval on a website for the sign-off stage.
If you use HTMLAnnotate, this part of the call is quick to explain. You send one review link per round. Reviewers click anything on the page to leave a comment pinned to it, with no account, and desktop, tablet and phone comments are kept separate. New versions go on the same link, earlier versions keep their comments, and the approver presses Approve on the version they're signing off, which emails you straight away.
Who should attend
Invite the people who will act on what is decided, and no one else. A crowded call makes it harder to get firm answers.
- The client lead. The person with the final say. If they can't attend, move the call. A kickoff without the decision maker produces decisions that get reversed later.
- Client reviewers and content owners. Anyone who will comment on the site or write and supply pages. They need to hear the review rules and content dates first hand.
- Your project lead. Runs the call, owns the follow-up email and runs the review rounds.
- Your lead designer. Hears the goals and the client's taste directly, and can ask follow-up questions on the spot.
- A developer, if needed. Worth inviting when the build has integrations, a migration or unusual hosting.
What to prepare
A kickoff goes faster when both sides arrive with the basics. Three to five working days before the call:
- Send the questionnaire. The client questionnaire covers business goals, people, content, access and timeline, so the call can focus on gaps and decisions.
- Send the agenda. Put it in the calendar invite so everyone knows feedback and approvals are on the list.
- Ask the client to bring logins, brand files, existing copy and photos, and two or three websites they like.
- Prepare on your side the agreed scope from the proposal, a draft timeline, and a short explanation of how reviews will work.
- Read their answers before the call, and mark anything vague or missing to raise in the right section.
The follow-up email
Send it the same day, while the call is fresh. It turns spoken agreement into something written that you can point to later, and it gives anyone who missed the call the same information. Ask the client to reply if anything is wrong, so silence means it stands.
Kickoff follow-up email
Send the same day as the call.For the emails that come next, such as the first review request and a polite chaser, see our feedback request email templates.
Questions
How long should a website kickoff meeting be?
An hour suits most small and mid-sized website projects. It is long enough to cover goals, scope, content, feedback and dates, and short enough that senior people will stay for all of it. A large project with many stakeholders may need a second session for content and technical detail.
Who should attend a website kickoff meeting?
From the client side, the person with the final say and anyone who will review the site or supply content. From the agency side, the project lead and the lead designer, plus a developer if the build has integrations or a tricky migration. Keep it to people who will act on what is decided.
What should I send the client before the kickoff call?
The agenda, the questionnaire, and a short list of what to bring: logins, brand files, existing copy and a few websites they like. Send them three to five working days ahead so the client has time to find answers and check with colleagues.
Why talk about feedback and approvals at the kickoff?
Because it is far easier to agree how reviews will work before the first draft than to change habits once comments are already arriving by email, chat and phone. Settling the client lead, rounds, deadlines and what Approve means up front prevents most late changes of direction.
What should the kickoff follow-up email include?
Every decision made on the call, written plainly: the client lead, the reviewers, the number of rounds and their length, how to leave comments, what approval means, the key dates, and any open questions with an owner and a date. Ask the client to reply if anything is wrong.
Agree at kickoff how feedback will work: one review link per round, comments pinned to the page, and Approve when it's right. Reviewers never need an account.
Start a free review