{"course":{"slug":"independent-creative","title":"Working for Yourself","url":"https://addaly.com/learn/independent-creative","level":"intermediate","track":"create"},"lesson":{"slug":"the-kickoff","title":"The hour that decides the project","url":"https://addaly.com/learn/independent-creative/the-kickoff","position":43,"of":84,"minutes":9,"answer":"Write the kickoff record within a day (what we are making, what is excluded, the stages.","keyIdea":"Write the kickoff record within a day (what we are making, what is excluded, the stages, and above all what you need from the client with a date and a stated consequence) because most freelance relationships erode through small unspoken adjustments rather than one large betrayal."},"body":{"format":"markdown","text":"## Where most bad projects were decided\n\nMost 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.\n\nThree 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.\n\nThe kickoff is one hour and one document that prevents most of this.\n\n## The document\n\nAfter 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:\n\n- **What we are making**, restated in one paragraph.\n- **What is not included**, in the same words as the quote.\n- **The stages**, with what is delivered at each and roughly when.\n- **What I need from you, and by when.** This is the section that does the work.\n- **How feedback happens**: who consolidates it, in what form, by which date.\n- **Who signs off.**\n- **Anything unresolved**, listed as unresolved with a date by which it must be settled.\n\nSend 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.\n\n> Figure: The hour, and the record that outlives everybody's memory. Steps: 1. One hour on a call (Take notes visibly, and read back the top five things you heard); 2. A written note within a day (What we are making, what is excluded, the stages, who signs off); 3. The dependency list, with dates (If the photographs arrive after 14 March, the launch moves by the same number of days); 4. Their reply, even just looks right (Every later disagreement is now settled by reading rather than by remembering). Scale the ceremony to the job. A fifteen-thousand-rupee menu does not need a kickoff deck, and it still needs the written record, which takes ten minutes at any size.\n\n## The dependency list\n\nThe 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.\n\nGive each one a date, and state the consequence plainly and without threat:\n\n> \"If the product photographs arrive after 14 March, the launch date moves by the same number of days.\"\n\nThis 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.\n\n## The questions worth asking at kickoff\n\nBeyond the practical list, four questions reliably surface the things that derail projects.\n\n**\"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.\n\n**\"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.\n\n**\"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.\n\n**\"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.\n\n## Technical constraints, established before anything is drawn\n\nFor 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?\n\nThe 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.\n\n## Getting the assets in a usable state\n\nClients 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.\n\nSay 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.\n\n## The meeting itself\n\nAn 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.\n\nIf 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.\n\n## The free tooling\n\nNone 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.\n\nIf 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.\n\n## The limitation\n\nA 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.\n\nThat 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."},"check":{"question":"A kickoff note says: 'If the product photographs arrive after 14 March, the launch date moves by the same number of days.' The photographs arrive on 18 April. What has this sentence actually achieved?","options":[{"text":"It transfers legal liability for the delay to the client, so the freelancer cannot be held in breach of the delivery date in the contract.","correct":false,"tempting":"Overstates a working note. Liability depends on the contract, and this line's value is practical rather than legal."},{"text":"It converts the delay from a private grievance into a dated fact both sides agreed to in advance, so the rescheduling conversation is short.","correct":true},{"text":"It creates a deterrent, so the client is more likely to supply assets on time than a client who was given no deadline for their own dependencies.","correct":false,"tempting":"Dated dependencies do improve compliance somewhat, but this client still delivered five weeks late: the sentence earned its place afterwards, not before."},{"text":"It establishes grounds for charging a delay fee, since the client was warned in writing that late assets would carry a cost to the schedule.","correct":false,"tempting":"A schedule consequence is not a monetary one, and converting it into a charge would require a term nobody agreed to."}]},"prev":{"slug":"tax-and-the-books","title":"The share that was never yours","url":"https://addaly.com/learn/independent-creative/tax-and-the-books"},"next":{"slug":"presenting-work","title":"Asking for a judgement, not a preference","url":"https://addaly.com/learn/independent-creative/presenting-work"},"authorship":"Founder and series editor: Dr Mustafa Mun. Written by AI models to a written standard. Exam keys checked blind by a second model: 3,665 of 3,666 agreed. Academic review invited.","review":{"status":"Draft, open for academic review"},"cite":"Addaly (2026) 'The hour that decides the project', in Working for Yourself. Edited by M. Mun. Addaly. Available at: https://addaly.com/learn/independent-creative/the-kickoff (Accessed: 13 October 2026).","licence":{"name":"CC BY-NC-SA 4.0","url":"https://creativecommons.org/licenses/by-nc-sa/4.0/"},"reader":{"schema":1,"title":"The hour that decides the project","courseTitle":"Working for Yourself","module":{"index":5,"slug":"running-the-job","title":"Running the job"},"answer":null,"keyIdea":"Write the kickoff record within a day (what we are making, what is excluded, the stages, and above all what you need from the client with a date and a stated consequence) because most freelance relationships erode through small unspoken adjustments rather than one large betrayal.","hero":{"kind":"figure","figure":{"t":"figure","label":"Figure 5.1","figure":{"type":"flow","steps":[{"label":"One hour on a call","detail":"Take notes visibly, and read back the top five things you heard"},{"label":"A written note within a day","detail":"What we are making, what is excluded, the stages, who signs off"},{"label":"The dependency list, with dates","detail":"If the photographs arrive after 14 March, the launch moves by the same number of days"},{"label":"Their reply, even just looks right","detail":"Every later disagreement is now settled by reading rather than by remembering"}],"title":"The hour, and the record that outlives everybody’s memory","caption":"Scale the ceremony to the job. A fifteen-thousand-rupee menu does not need a kickoff deck, and it still needs the written record, which takes ten minutes at any size."},"alt":"Figure: The hour, and the record that outlives everybody’s memory. Steps: 1. One hour on a call (Take notes visibly, and read back the top five things you heard); 2. A written note within a day (What we are making, what is excluded, the stages, who signs off); 3. The dependency list, with dates (If the photographs arrive after 14 March, the launch moves by the same number of days); 4. Their reply, even just looks right (Every later disagreement is now settled by reading rather than by remembering). Scale the ceremony to the job. A fifteen-thousand-rupee menu does not need a kickoff deck, and it still needs the written record, which takes ten minutes at any size."}},"blocks":[{"t":"h2","id":"where-most-bad-projects-were-decided","runs":[{"text":"Where most bad projects were decided"}]},{"t":"p","runs":[{"text":"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."}]},{"t":"p","runs":[{"text":"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."}]},{"t":"p","runs":[{"text":"The kickoff is one hour and one document that prevents most of this."}]},{"t":"h2","id":"the-document","runs":[{"text":"The document"}]},{"t":"p","runs":[{"text":"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:"}]},{"t":"ul","items":[[{"text":"What we are making","b":true},{"text":", restated in one paragraph."}],[{"text":"What is not included","b":true},{"text":", in the same words as the quote."}],[{"text":"The stages","b":true},{"text":", with what is delivered at each and roughly when."}],[{"text":"What I need from you, and by when.","b":true},{"text":" This is the section that does the work."}],[{"text":"How feedback happens","b":true},{"text":": who consolidates it, in what form, by which date."}],[{"text":"Who signs off.","b":true}],[{"text":"Anything unresolved","b":true},{"text":", listed as unresolved with a date by which it must be settled."}]]},{"t":"p","runs":[{"text":"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."}]},{"t":"h2","id":"the-dependency-list","runs":[{"text":"The dependency list"}]},{"t":"p","runs":[{"text":"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."}]},{"t":"p","runs":[{"text":"Give each one a date, and state the consequence plainly and without threat:"}]},{"t":"quote","runs":[{"text":"“If the product photographs arrive after 14 March, the launch date moves by the same number of days.”"}]},{"t":"p","runs":[{"text":"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."}]},{"t":"h2","id":"the-questions-worth-asking-at-kickoff","runs":[{"text":"The questions worth asking at kickoff"}]},{"t":"p","runs":[{"text":"Beyond the practical list, four questions reliably surface the things that derail projects."}]},{"t":"p","runs":[{"text":"”What would make this a failure?”","b":true},{"text":" 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."}]},{"t":"p","runs":[{"text":"”Has anyone tried to solve this before?”","b":true},{"text":" A previous attempt tells you what was rejected and why, and it is usually not in the brief because it is mildly embarrassing."}]},{"t":"p","runs":[{"text":"”Who else will see this before it is approved?”","b":true},{"text":" The decision-maker question, asked again because the answer often changes between the enquiry and the start."}]},{"t":"p","runs":[{"text":"”Is there anything that absolutely cannot change?”","b":true},{"text":" 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."}]},{"t":"h2","id":"technical-constraints-established-before-anything-is-drawn","runs":[{"text":"Technical constraints, established before anything is drawn"}]},{"t":"p","runs":[{"text":"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?"}]},{"t":"p","runs":[{"text":"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."}]},{"t":"h2","id":"getting-the-assets-in-a-usable-state","runs":[{"text":"Getting the assets in a usable state"}]},{"t":"p","runs":[{"text":"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."}]},{"t":"p","runs":[{"text":"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."}]},{"t":"h2","id":"the-meeting-itself","runs":[{"text":"The meeting itself"}]},{"t":"p","runs":[{"text":"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."}]},{"t":"p","runs":[{"text":"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."}]},{"t":"h2","id":"the-free-tooling","runs":[{"text":"The free tooling"}]},{"t":"p","runs":[{"text":"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."}]},{"t":"p","runs":[{"text":"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."}]},{"t":"h2","id":"the-limitation","runs":[{"text":"The limitation"}],"role":"limit"},{"t":"p","runs":[{"text":"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."}]},{"t":"p","runs":[{"text":"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."}]}],"check":{"question":[{"text":"A kickoff note says: ‘If the product photographs arrive after 14 March, the launch date moves by the same number of days.’ The photographs arrive on 18 April. What has this sentence actually achieved?"}],"options":[{"text":[{"text":"It transfers legal liability for the delay to the client, so the freelancer cannot be held in breach of the delivery date in the contract."}],"correct":false,"tempting":[{"text":"Overstates a working note. Liability depends on the contract, and this line’s value is practical rather than legal."}]},{"text":[{"text":"It converts the delay from a private grievance into a dated fact both sides agreed to in advance, so the rescheduling conversation is short."}],"correct":true,"tempting":null},{"text":[{"text":"It creates a deterrent, so the client is more likely to supply assets on time than a client who was given no deadline for their own dependencies."}],"correct":false,"tempting":[{"text":"Dated dependencies do improve compliance somewhat, but this client still delivered five weeks late: the sentence earned its place afterwards, not before."}]},{"text":[{"text":"It establishes grounds for charging a delay fee, since the client was warned in writing that late assets would carry a cost to the schedule."}],"correct":false,"tempting":[{"text":"A schedule consequence is not a monetary one, and converting it into a charge would require a term nobody agreed to."}]}],"order":[3,0,1,2],"why":null},"prev":{"slug":"tax-and-the-books","title":"The share that was never yours","minutes":9},"next":{"slug":"presenting-work","title":"Asking for a judgement, not a preference","minutes":9}}}