{"course":{"slug":"independent-creative","title":"Working for Yourself","url":"https://addaly.com/learn/independent-creative","level":"intermediate","track":"create"},"lesson":{"slug":"estimating-time","title":"Estimating from records, not imagination","url":"https://addaly.com/learn/independent-creative/estimating-time","position":47,"of":84,"minutes":9,"answer":"When you estimate you imagine the work going as intended and omit the waiting, the reopened brief and the admin, so ask instead how long the last three jobs like this actually took.","keyIdea":"When you estimate you imagine the work going as intended and omit the waiting, the reopened brief and the admin, so ask instead how long the last three jobs like this actually took, which is why the hours column in your project record is worth more than any task breakdown."},"body":{"format":"markdown","text":"## Everyone is wrong in the same direction\n\nAsk any freelancer how long a job took against what they thought, and the answer is almost always \"longer\". Not sometimes longer: systematically longer, by a factor that stays roughly constant across a career. Experience makes the estimates faster to produce and does not make them much more accurate.\n\nThis is not a personal failing. It is a well-documented bias in how people forecast tasks, and it has a mechanism: when you estimate, you imagine the work going as intended. You picture the drawing, the layout, the export. You do not picture the two days waiting for the client's copy, the file that would not open, the brief changing on Thursday, or the morning lost to a tax form. Those things happen on every project and are absent from every mental simulation of one.\n\nThe correction is not to try harder to imagine them. It is to stop estimating from imagination and start estimating from records.\n\n## Estimating from the outside\n\nThe reliable method is to ask: **how long did the last three jobs like this actually take?**\n\nThat single question outperforms any amount of careful task breakdown, because your past projects already contain all the interruptions, delays and repeated exports that your imagination omits. They happened, and they are in the number.\n\nThis requires a record, which almost nobody keeps, which is why almost everybody keeps estimating from imagination. The record needed is small: for every project, the type of work, what you quoted, and the hours it actually took. One row in a spreadsheet, filled in at handover, alongside the portfolio images and the testimonial ask.\n\nAfter six or eight projects you have something that no amount of thinking produces: your own multiplier. Most people find theirs is somewhere between 1.5 and 2.5. Once you know it, estimating becomes arithmetic: imagine the work honestly, then multiply by your number.\n\n## Tracking hours without misery\n\nYou do not need to bill hourly to track them, and tracking them is worth it even on fixed-price work, because it is the only way to know your effective rate.\n\nThe lightest version that works: a note of start and stop times in a text file or a notebook, totalled at the end of the week. Free timer tools exist (Toggl's free tier, Clockify, or a plain stopwatch) and the software barely matters. What matters is capturing the whole project, including the admin: the emails, the calls, the quote you wrote, the invoice, the file delivery, the trip to the printer.\n\nThat last point is where most surprises live. Designers habitually count only the hours with the software open. A project with twelve hours of drawing and nine hours of everything else has an effective rate half of what the designer believes, and they will price the next one identically.\n\n## The estimate you give the client\n\nTwo useful practices.\n\n**Quote a range, or a date with a condition.** \"Three to four weeks, assuming the photographs arrive by the 14th.\" The condition is what makes the date real, and it names the dependency in the same breath.\n\n**Add contingency before you say the number, not after.** Deciding privately that a job is fifteen hours and then telling the client twenty is not padding; it is including the hours you know from experience will exist and cannot itemise. What does not work is quoting fifteen and absorbing the other five, which is the default behaviour and is where a rate quietly halves.\n\n## The multipliers that are not your fault\n\nThree things reliably extend a project and none of them are estimation errors:\n\n**Client response time.** A one-week revision cycle with a client who replies in five days is not a one-week cycle. Calendar time and working time are different quantities and should be quoted separately: \"about twenty hours of work, spread over four weeks\".\n\n**Number of stakeholders.** Each additional person with an opinion adds coordination, contradiction and delay. A project with one decision-maker and the same project with a committee of five are not the same job, and they should not carry the same price.\n\n**Unfamiliar production.** The first time you prepare artwork for embroidery, screen printing on fabric, a new platform's specification or a format you have not used, budget extra and expect to learn something the hard way. The second one costs a third of the first.\n\n## When you are already over\n\nIt happens on a fixed price. Three options, in descending order of grace.\n\n**If it was your estimate that was wrong**, absorb it, deliver, and record the real number so the next quote is correct. This is the cost of estimating, and asking a client to pay for your mistake damages more than it recovers.\n\n**If the scope grew**, that is a different thing and there is a mechanism for it: a priced change note at the time, not a complaint at the end.\n\n**If it is going to be substantially late**, say so early, with a new date and the reason, without waiting to see if you can catch up. Nearly every client can handle a two-week delay announced three weeks ahead. Almost none can handle it announced on the deadline, because by then they have made commitments to other people based on your silence.\n\n> Figure: A late project is one of two things, and they differ. A two by two grid, rows Your estimate was wrong and The scope changed, columns How you can tell and The remedy: Your estimate was wrong and How you can tell: Every job of this kind runs about twice the guess; Your estimate was wrong and The remedy: Absorb it, deliver, and record the real hours; The scope changed and How you can tell: This one ran over after a new request arrived; The scope changed and The remedy: A priced change note at the time. Asking a client to pay for your own estimating error damages more than it recovers, and absorbing a scope change quietly is how a rate halves. Telling them apart needs the hours column in the project record.\n\n## The estimate you should refuse to give\n\nWhen a client asks for a figure on the phone, before any scope exists, the honest answer is a range wide enough to be useless, or a refusal with a reason.\n\n> \"It depends on how many variants and how many languages: for something like this it usually sits between X and Y. Let me send a proper quote tomorrow once I know which.\"\n\nA number said casually becomes the number they remember, and every subsequent quote is measured against it. This is one of the few places where saying less protects you.\n\n## The limitation\n\nBetter estimating does not make projects shorter, and it will not make you accurate. Even with good records, individual projects vary enormously: one client's decisiveness against another's, one printer's competence against another's.\n\nWhat records give you is accuracy *on average*, which is the only kind that matters for a business. You will still lose money on individual jobs and make it back on others. The freelancer who tracks is not the one who never misjudges; it is the one whose annual income matches what they thought they were charging."},"check":{"question":"A designer breaks a project into fourteen tasks, estimates each carefully, and sums them to 22 hours. The job takes 39. She repeats the exercise more carefully on the next project and is wrong by a similar margin. Why does a finer breakdown not help?","options":[{"text":"Fourteen tasks is too granular, and small per-task rounding errors compound across the list into a large total error.","correct":false,"tempting":"Rounding does accumulate, but it would produce error in both directions; the bias here is consistently in one direction."},{"text":"She is estimating working hours while the client experiences calendar time, so the two numbers were never meant to match.","correct":false,"tempting":"Calendar and working time genuinely are different quantities worth quoting separately, but she measured 39 actual working hours, not elapsed weeks."},{"text":"Every task is imagined going as intended, so a finer breakdown produces more of the same optimistic simulation rather than correcting it.","correct":true},{"text":"Task breakdowns omit the admin around a project (quoting, invoicing, file delivery) and adding those categories to the list would close the gap.","correct":false,"tempting":"Counting admin is a real and commonly skipped improvement, but those tasks would then be estimated with the same optimism as the rest."}]},"prev":{"slug":"translating-feedback","title":"The complaint is real, the diagnosis is not","url":"https://addaly.com/learn/independent-creative/translating-feedback"},"next":{"slug":"files-and-handover","title":"The last four hours","url":"https://addaly.com/learn/independent-creative/files-and-handover"},"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) 'Estimating from records, not imagination', in Working for Yourself. Edited by M. Mun. Addaly. Available at: https://addaly.com/learn/independent-creative/estimating-time (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":"Estimating from records, not imagination","courseTitle":"Working for Yourself","module":{"index":5,"slug":"running-the-job","title":"Running the job"},"answer":null,"keyIdea":"When you estimate you imagine the work going as intended and omit the waiting, the reopened brief and the admin, so ask instead how long the last three jobs like this actually took, which is why the hours column in your project record is worth more than any task breakdown.","hero":{"kind":"figure","figure":{"t":"figure","label":"Figure","figure":{"cols":["How you can tell","The remedy"],"rows":["Your estimate was wrong","The scope changed"],"type":"matrix","cells":[["Every job of this kind runs about twice the guess","Absorb it, deliver, and record the real hours"],["This one ran over after a new request arrived","A priced change note at the time"]],"title":"A late project is one of two things, and they differ","caption":"Asking a client to pay for your own estimating error damages more than it recovers, and absorbing a scope change quietly is how a rate halves. Telling them apart needs the hours column in the project record."},"alt":"Figure: A late project is one of two things, and they differ. A two by two grid, rows Your estimate was wrong and The scope changed, columns How you can tell and The remedy: Your estimate was wrong and How you can tell: Every job of this kind runs about twice the guess; Your estimate was wrong and The remedy: Absorb it, deliver, and record the real hours; The scope changed and How you can tell: This one ran over after a new request arrived; The scope changed and The remedy: A priced change note at the time. Asking a client to pay for your own estimating error damages more than it recovers, and absorbing a scope change quietly is how a rate halves. Telling them apart needs the hours column in the project record."}},"blocks":[{"t":"h2","id":"everyone-is-wrong-in-the-same-direction","runs":[{"text":"Everyone is wrong in the same direction"}]},{"t":"p","runs":[{"text":"Ask any freelancer how long a job took against what they thought, and the answer is almost always “longer”. Not sometimes longer: systematically longer, by a factor that stays roughly constant across a career. Experience makes the estimates faster to produce and does not make them much more accurate."}]},{"t":"p","runs":[{"text":"This is not a personal failing. It is a well-documented bias in how people forecast tasks, and it has a mechanism: when you estimate, you imagine the work going as intended. You picture the drawing, the layout, the export. You do not picture the two days waiting for the client’s copy, the file that would not open, the brief changing on Thursday, or the morning lost to a tax form. Those things happen on every project and are absent from every mental simulation of one."}]},{"t":"p","runs":[{"text":"The correction is not to try harder to imagine them. It is to stop estimating from imagination and start estimating from records."}]},{"t":"h2","id":"estimating-from-the-outside","runs":[{"text":"Estimating from the outside"}]},{"t":"p","runs":[{"text":"The reliable method is to ask: "},{"text":"how long did the last three jobs like this actually take?","b":true}]},{"t":"p","runs":[{"text":"That single question outperforms any amount of careful task breakdown, because your past projects already contain all the interruptions, delays and repeated exports that your imagination omits. They happened, and they are in the number."}]},{"t":"p","runs":[{"text":"This requires a record, which almost nobody keeps, which is why almost everybody keeps estimating from imagination. The record needed is small: for every project, the type of work, what you quoted, and the hours it actually took. One row in a spreadsheet, filled in at handover, alongside the portfolio images and the testimonial ask."}]},{"t":"p","runs":[{"text":"After six or eight projects you have something that no amount of thinking produces: your own multiplier. Most people find theirs is somewhere between 1.5 and 2.5. Once you know it, estimating becomes arithmetic: imagine the work honestly, then multiply by your number."}]},{"t":"h2","id":"tracking-hours-without-misery","runs":[{"text":"Tracking hours without misery"}]},{"t":"p","runs":[{"text":"You do not need to bill hourly to track them, and tracking them is worth it even on fixed-price work, because it is the only way to know your effective rate."}]},{"t":"p","runs":[{"text":"The lightest version that works: a note of start and stop times in a text file or a notebook, totalled at the end of the week. Free timer tools exist (Toggl’s free tier, Clockify, or a plain stopwatch) and the software barely matters. What matters is capturing the whole project, including the admin: the emails, the calls, the quote you wrote, the invoice, the file delivery, the trip to the printer."}]},{"t":"p","runs":[{"text":"That last point is where most surprises live. Designers habitually count only the hours with the software open. A project with twelve hours of drawing and nine hours of everything else has an effective rate half of what the designer believes, and they will price the next one identically."}]},{"t":"h2","id":"the-estimate-you-give-the-client","runs":[{"text":"The estimate you give the client"}]},{"t":"p","runs":[{"text":"Two useful practices."}]},{"t":"p","runs":[{"text":"Quote a range, or a date with a condition.","b":true},{"text":" “Three to four weeks, assuming the photographs arrive by the 14th.” The condition is what makes the date real, and it names the dependency in the same breath."}]},{"t":"p","runs":[{"text":"Add contingency before you say the number, not after.","b":true},{"text":" Deciding privately that a job is fifteen hours and then telling the client twenty is not padding; it is including the hours you know from experience will exist and cannot itemise. What does not work is quoting fifteen and absorbing the other five, which is the default behaviour and is where a rate quietly halves."}]},{"t":"h2","id":"the-multipliers-that-are-not-your-fault","runs":[{"text":"The multipliers that are not your fault"}]},{"t":"p","runs":[{"text":"Three things reliably extend a project and none of them are estimation errors:"}]},{"t":"p","runs":[{"text":"Client response time.","b":true},{"text":" A one-week revision cycle with a client who replies in five days is not a one-week cycle. Calendar time and working time are different quantities and should be quoted separately: “about twenty hours of work, spread over four weeks”."}]},{"t":"p","runs":[{"text":"Number of stakeholders.","b":true},{"text":" Each additional person with an opinion adds coordination, contradiction and delay. A project with one decision-maker and the same project with a committee of five are not the same job, and they should not carry the same price."}]},{"t":"p","runs":[{"text":"Unfamiliar production.","b":true},{"text":" The first time you prepare artwork for embroidery, screen printing on fabric, a new platform’s specification or a format you have not used, budget extra and expect to learn something the hard way. The second one costs a third of the first."}]},{"t":"h2","id":"when-you-are-already-over","runs":[{"text":"When you are already over"}]},{"t":"p","runs":[{"text":"It happens on a fixed price. Three options, in descending order of grace."}]},{"t":"p","runs":[{"text":"If it was your estimate that was wrong","b":true},{"text":", absorb it, deliver, and record the real number so the next quote is correct. This is the cost of estimating, and asking a client to pay for your mistake damages more than it recovers."}]},{"t":"p","runs":[{"text":"If the scope grew","b":true},{"text":", that is a different thing and there is a mechanism for it: a priced change note at the time, not a complaint at the end."}]},{"t":"p","runs":[{"text":"If it is going to be substantially late","b":true},{"text":", say so early, with a new date and the reason, without waiting to see if you can catch up. Nearly every client can handle a two-week delay announced three weeks ahead. Almost none can handle it announced on the deadline, because by then they have made commitments to other people based on your silence."}]},{"t":"h2","id":"the-estimate-you-should-refuse-to-give","runs":[{"text":"The estimate you should refuse to give"}]},{"t":"p","runs":[{"text":"When a client asks for a figure on the phone, before any scope exists, the honest answer is a range wide enough to be useless, or a refusal with a reason."}]},{"t":"quote","runs":[{"text":"“It depends on how many variants and how many languages: for something like this it usually sits between X and Y. Let me send a proper quote tomorrow once I know which.”"}]},{"t":"p","runs":[{"text":"A number said casually becomes the number they remember, and every subsequent quote is measured against it. This is one of the few places where saying less protects you."}]},{"t":"h2","id":"the-limitation","runs":[{"text":"The limitation"}],"role":"limit"},{"t":"p","runs":[{"text":"Better estimating does not make projects shorter, and it will not make you accurate. Even with good records, individual projects vary enormously: one client’s decisiveness against another’s, one printer’s competence against another’s."}]},{"t":"p","runs":[{"text":"What records give you is accuracy "},{"text":"on average","i":true},{"text":", which is the only kind that matters for a business. You will still lose money on individual jobs and make it back on others. The freelancer who tracks is not the one who never misjudges; it is the one whose annual income matches what they thought they were charging."}]}],"check":{"question":[{"text":"A designer breaks a project into fourteen tasks, estimates each carefully, and sums them to 22 hours. The job takes 39. She repeats the exercise more carefully on the next project and is wrong by a similar margin. Why does a finer breakdown not help?"}],"options":[{"text":[{"text":"Fourteen tasks is too granular, and small per-task rounding errors compound across the list into a large total error."}],"correct":false,"tempting":[{"text":"Rounding does accumulate, but it would produce error in both directions; the bias here is consistently in one direction."}]},{"text":[{"text":"She is estimating working hours while the client experiences calendar time, so the two numbers were never meant to match."}],"correct":false,"tempting":[{"text":"Calendar and working time genuinely are different quantities worth quoting separately, but she measured 39 actual working hours, not elapsed weeks."}]},{"text":[{"text":"Every task is imagined going as intended, so a finer breakdown produces more of the same optimistic simulation rather than correcting it."}],"correct":true,"tempting":null},{"text":[{"text":"Task breakdowns omit the admin around a project (quoting, invoicing, file delivery) and adding those categories to the list would close the gap."}],"correct":false,"tempting":[{"text":"Counting admin is a real and commonly skipped improvement, but those tasks would then be estimated with the same optimism as the rest."}]}],"order":[0,3,2,1],"why":null},"prev":{"slug":"translating-feedback","title":"The complaint is real, the diagnosis is not","minutes":10},"next":{"slug":"files-and-handover","title":"The last four hours","minutes":10}}}