What a project kickoff call with us actually covers, and why it's 90 minutes not 30

A lot of agencies treat kickoff as a formality: quick intros, confirm the timeline, done in 30 minutes. We run ours at 90, and the extra hour isn't padding, it's the single highest-leverage conversation of the entire engagement, because everything downstream gets easier or harder depending on what actually gets nailed down here.

We resisted this format for a while, worried it would feel excessive to a busy client eager to get started. In practice it's the opposite: clients consistently tell us afterward that it's the most useful ninety minutes of the whole project, precisely because it answers questions they didn't know they needed to ask yet.

Before anything creative gets discussed, we map exactly who has final approval authority at each stage: design direction, copy, functionality, launch. On more than one project, this fifteen minutes has surfaced a stakeholder nobody had mentioned who turned out to have veto power over the whole design direction, which is far better to learn in week one than week six.

We ask this in a specific, slightly uncomfortable way: "if you and I loved a direction and someone else on your side hated it, who wins?" That framing surfaces the real approval structure faster than a generic "who's involved" question, which tends to produce a polite, incomplete list.

"A great website" isn't a success criterion. We push for something measurable: a conversion rate target, a specific number of qualified leads per month, a page speed benchmark. If the client genuinely doesn't know yet, that's a fine answer too, but it changes how we scope the first few weeks, usually toward faster iteration and more built-in measurement rather than a big single launch.

When a client can't yet name a specific number, we help them find a proxy that's at least directionally measurable, so there's something concrete to check the finished work against later, rather than ending the project with only a subjective, hard-to-resolve opinion about whether it succeeded.

Not a Gantt chart glanced at once. We walk through what happens in each specific week, what we need from the client and when, and what happens if a review takes longer than the two business days we've budgeted for it. Clients leave this part of the call knowing exactly when they'll be asked for something and how much delay a late response actually costs the schedule.

We specifically walk through what a late review does to the following weeks, not just the current one, since a two-day slip in week two quietly becomes a two-week slip by launch if nobody's tracking how delays compound through a dependent schedule.

Which tool for what: quick questions in Slack, formal approvals in the project board, nothing important buried in an email thread nobody checks. We also set expectations here about response time in both directions, since a same-day acknowledgement promise from us only works if client feedback also arrives within a reasonable window on their end.

We ask clients directly what channel they're most likely to actually check daily, rather than assuming, since we've had projects slow down simply because we defaulted to a tool the client's team quietly didn't check as often as we assumed they would.

We ask directly: what's the most likely thing to derail this project from your side. Budget approval delays, a stakeholder who travels a lot, a busy season coming up. Naming the risk in week one means we can build slack into the schedule around it instead of discovering it reactively when the delay actually happens.

This question routinely gets an honest, useful answer precisely because it's asked late in the call, once some trust has already been built during the previous seventy-five minutes. Asked cold at the very start, it tends to get a vague, defensive non-answer instead.

We ask the client to bring whoever will actually be involved week to week, not just the most senior person available, since a kickoff attended only by an executive who then hands the project to someone else internally means the ninety minutes of context gets lost in translation rather than absorbed directly. We'd rather push a kickoff back a few days to get the right people in the room than run it on schedule with the wrong ones.

On our side, the actual people who'll be doing the work attend too, not just the account lead who sold the project. A developer or designer who was in the room when a client explained a specific constraint remembers it more accurately, weeks later, than one relaying it secondhand from someone else's notes, and it saves a repeated round of clarifying questions once the real work starts.

A short agenda goes out 48 hours ahead, along with two or three specific questions we want the client thinking about beforehand, particularly the approval chain and success metric questions, since those benefit from a moment of reflection rather than being answered off the cuff for the first time on the call. Clients who've had a chance to think about these in advance give noticeably more specific, useful answers than ones hearing the question cold.

We've tried running kickoff without this advance notice, treating it as a live discovery session start to finish, and consistently got shallower answers to the questions that matter most. A little advance thought from the client turns ninety minutes of live conversation into ninety minutes of genuine decision-making rather than ninety minutes partly spent just formulating a first answer on the spot.

Within 24 hours, we send a written summary of every decision made during the call, the approval chain, the success metrics, the communication norms, the named risks, so nothing discussed live depends purely on memory a few weeks later when it actually matters. This document becomes the reference point for the rest of the engagement whenever a question comes up about what was originally agreed.

We've resolved more than one later disagreement simply by pointing back to this document, not as a way of scoring a point, but because it genuinely settles ambiguity faster than trying to reconstruct what was said in a conversation from months earlier. A good kickoff is only as durable as the record made of it.