The hour that decides the project

Where most bad projects were decided

Most creative projects that go badly were decided in the first week, and usually in the specific gap between the client saying yes and anybody writing down what was agreed. The quote was accepted. Work started. Nobody restated the brief, nobody listed what was needed from the client, and nobody put dates on the things that were not yours to produce.

Three months later there is an argument about whether the third language was included and why the project is six weeks late. Both sides remember differently and both are sincere.

The kickoff is one hour and one document that prevents most of this.

The document

After the kickoff call, you write and send a short note. Not a contract (that is separate), and not a proposal. A working record, half a page to a page:

• What we are making, restated in one paragraph.
• What is not included, in the same words as the quote.
• The stages, with what is delivered at each and roughly when.
• What I need from you, and by when. This is the section that does the work.
• How feedback happens: who consolidates it, in what form, by which date.
• Who signs off.
• Anything unresolved, listed as unresolved with a date by which it must be settled.

Send it within a day, and ask them to correct anything wrong. Their reply (even “looks right”) is now the shared record, and every later disagreement is settled by reading it rather than by two memories competing.

The dependency list

The single most valuable part is the list of things the client must supply: copy, photographs, logos in usable formats, product samples, access to their printer, the legal wording, the name of the person who decides.

Give each one a date, and state the consequence plainly and without threat:

“If the product photographs arrive after 14 March, the launch date moves by the same number of days.”

This is not a defensive manoeuvre. It is the only honest way to describe how the schedule works, and clients generally accept it immediately because it is obviously true. What it prevents is the very common end-state where the client supplied the copy five weeks late and is nonetheless surprised and annoyed that the work is late.

The questions worth asking at kickoff

Beyond the practical list, four questions reliably surface the things that derail projects.

”What would make this a failure?” People will tell you their real fear, and it is often not what the brief says. “If it looks like the competitor” or “if my father-in-law hates it” is a constraint you need on day one.

”Has anyone tried to solve this before?” A previous attempt tells you what was rejected and why, and it is usually not in the brief because it is mildly embarrassing.

”Who else will see this before it is approved?” The decision-maker question, asked again because the answer often changes between the enquiry and the start.

”Is there anything that absolutely cannot change?” Existing typography, a colour the founder is attached to, a mark that has to be preserved, a legal requirement, a size the machinery imposes. Finding a hard constraint in week four costs a round of work.

Technical constraints, established before anything is drawn

For anything that gets made, ask the production questions at kickoff, not at delivery. Which printer, and what are their specifications? What is the stock? How many colours? Is there a die line, and can you have it? What resolution and colour space does the platform require? What is the minimum size this will appear at? What formats does their web team need?

The cost of not asking is not a small revision. A logo designed without knowing it would be embroidered, or a layout built without the printer’s bleed and safety margins, gets rebuilt rather than adjusted.

Getting the assets in a usable state

Clients send what they have, which is frequently a logo screenshot from their own website at 400 pixels wide. Ask specifically for vector originals, editable text rather than PDFs of text, and photographs at full resolution rather than versions already compressed for social media.

Say why, because the request is otherwise mysterious: “a screenshot cannot be printed: it will be visibly blurred at any size larger than a business card.” When the original no longer exists, which is common with small businesses, that is a scoping fact you have just discovered in week one rather than week six, and redrawing it is chargeable work you can quote for now.

The meeting itself

An hour is enough, with the client’s own team present if there is one. Take notes visibly. End by reading back the top five things you heard, which catches misunderstandings while they are cheap.

If the project is small, this can be fifteen minutes and three emails. Scale the ceremony to the job (a ₹15,000 menu redesign does not need a formal kickoff deck) but do not skip the written record, which takes ten minutes at any size.

The free tooling

None of this needs software. The note is an email. The dependency list is five lines in that email. A shared folder (any free cloud storage) for assets, named clearly, beats attachments scattered across a thread.

If you want a shared task list, a free tier of any project tool works, but be honest about whether the client will open it. Most small clients will not, and a beautifully maintained board that one person reads is worse than an email they actually receive.

The limitation

A kickoff document does not make a disorganised client organised. They will still send the copy late, change their mind, and add a stakeholder in week five. What changes is that each of those events becomes a visible, dated, discussable fact rather than a source of private resentment on your side and vague dissatisfaction on theirs.

That is a smaller benefit than it sounds and a larger one than it feels. Most freelance relationships do not break down over one large betrayal; they erode through a series of small unspoken adjustments, each of which the written record would have made into a two-line conversation.