Skip to content

Website project kickoff: a complete guide for web designers

By The Onbo team · Updated

Short answer

A website project kickoff has two parts. Before the call, collect the accepted agreement, the deposit, the questionnaire answers, brand files and a content plan. On the call, confirm goals, the sitemap, content ownership, the timeline and who approves the work. Done in that order, design can start the same week.

Most website projects that run late were in trouble before the first design. The kickoff call was spent collecting the logo, nobody agreed who would write the copy, and the sitemap changed twice in week three. A good website project kickoff fixes this by splitting the work in two: collect everything in writing first, then use the call for decisions.

What is a website project kickoff?

The kickoff is the stage between the client saying yes and design starting. It covers three things:

  • Commitment: the agreement is accepted and the deposit is paid.
  • Information: goals, audience, pages, style, content and technical setup are in writing.
  • Decisions: sitemap, content ownership, timeline and approvals are agreed with the client.

Many studios treat “kickoff” as one meeting. It works better as a short sequence that ends with a meeting.

What should you collect before the kickoff call?

Collect these in a fixed order, because each one depends on the one before:

  1. Accepted agreement, covering scope, revisions, content ownership and late content.
  2. Deposit, with later payments scheduled at milestones such as design approval and launch. Our guide to web design deposits covers amounts and schedules.
  3. Website questionnaire: goals, audience, pages, features, style, competitors. Our web design client questionnaire has the full set.
  4. Brand files: vector logo, guidelines, fonts, photography. See how to request brand assets from clients.
  5. Content status: what exists, what needs writing, and who will write it.
  6. Technical list: domain, hosting, email and any tools the site connects to.

When these arrive before the call, you can draft a sitemap from the answers and bring it to the meeting.

If the client hasn’t signed yet, a shorter website project intake form gives you enough to scope and price the work first.

How do you run the kickoff call?

With the basics in hand, a website kickoff call can follow a short agenda:

Agenda item What you confirm Output
Goals What the site must achieve and how success is judged Two or three written goals
Sitemap The draft page list from the questionnaire Sitemap to sign off
Content Who writes each page and by when Content plan with owners
Design direction Likes, dislikes and must-keeps Notes for the first concept
Timeline Phases, client deadlines and payment milestones, using a website project timeline Agreed dates
Approvals Who gives feedback and who has the final say Named approvers
Open questions Anything marked “not sure yet” Decisions or follow-ups

Send the agenda a day ahead so the client’s decision makers come prepared.

For example, a three-person web studio might receive a client’s questionnaire answers on Monday, draft a nine-page sitemap on Tuesday and hold a 45-minute kickoff on Wednesday. Because the logo, deposit and agreement were already in, the call ends with a signed-off sitemap and a first concept due the following week.

What should you agree about content?

Content is the input most likely to delay a website, so the kickoff is where you prevent it:

  • Name an owner for every page, on the client’s side or yours.
  • Give each page a due date tied to the build, not one date for everything.
  • Agree a fallback for late pages: placeholder, copywriting add-on or a later launch for that page.
  • Write it down in the agreement or the kickoff notes, so the plan survives a busy month.

Our website client onboarding checklist lists every content and technical item in order.

For planning and collecting page content in detail, see how to collect website content from clients.

What happens straight after the kickoff?

Within a day of the call:

  • Send a written summary of every decision
  • Ask the approver to sign off the sitemap in writing
  • Share the content plan with owners and dates
  • Confirm the first milestone and the next payment
  • Arrange technical access directly with the client, never by asking for passwords in a form (see how to get website access from clients)
  • Create the project in your project tool from the summary
  • Book the first design review
  • Note any scope questions raised, and how they were resolved
  • File the summary with the agreement and questionnaire answers
  • Tell the client exactly what you need from them next, and by when

Where does a kickoff go wrong?

  • Starting before the deposit. Work begins on a handshake and the first invoice gets chased.
  • Collecting basics on the call. An hour spent on logins and logos leaves no time for decisions.
  • No sitemap sign-off. Pages get added during design, and every later phase moves.
  • Vague content ownership. “We’ll send copy soon” becomes the reason launch slips.

For agencies weighing tools for this stage, compare the options for client kickoff software before choosing one.

Getting the sitemap approved in writing is covered step by step in how to get sitemap approval from a website client.

When things go wrong

Even well-run kickoffs hit problems. If the build is waiting on copy, see what to do when the client hasn’t sent website content. If the domain sits in someone else’s account, see when the domain is registered by the previous web designer. New pages mid-project go through a website change request form, and a paused project is covered in when a client puts the website project on hold.

Where Onbo fits

Onbo runs everything before the kickoff call from one link. Your client accepts the agreement, pays the deposit through your own payment link with later payments on the same invoice, answers your website questionnaire with autosave, and uploads brand files straight into your Google Drive. Reminders follow up on anything unfinished, and a Markdown hand-off brief gives you the answers for the sitemap and the call agenda. Try it free for 30 days; see pricing.

Questions

What should happen at a website kickoff meeting?

Confirm the site's goals, review the draft sitemap, agree who writes and supplies content, walk through the timeline and client deadlines, name the people who approve work, and resolve open questions from the questionnaire.

What should I collect before a website kickoff?

The accepted agreement, the deposit, answers to a website questionnaire, the logo and brand files, existing content, and a list of tools the site must connect to.

How long should a website kickoff call take?

For a small or medium site, about an hour is usually enough when the basics are collected beforehand. Longer calls tend to be a sign the information arrived late.

Start your next client relationship with everything in place.

Collect the first steps in one link. Try Onbo free for 30 days, no card required.

Start free