# Web Worker 101: Estimating Basics

### 32 Comments

Summary:

As you enter a career of being an independent web worker, you can hardly avoid negotiating contracts with potential clients. Inevitably, the first questions that will come up are “how much is this going to cost?” and the closely-related “how long is it going to take?” […]

As you enter a career of being an independent web worker, you can hardly avoid negotiating contracts with potential clients. Inevitably, the first questions that will come up are “how much is this going to cost?” and the closely-related “how long is it going to take?” Providing reasonable (and acceptable) answers to these questions is often the difference between a signed contract and an insincere commitment to call you back later. Whatever your skills as software developer or web designer (or whatever your web work career entails), you need to also understand the basics of estimating.

Unless you’re doing utterly routine piecework (data entry from paper forms or perhaps transcription), estimating is more art than science. But there are some things you can do to increase your chance of turning out a good estimate: one that ends up bearing some resemblance to the time it takes to do the actual work. Here are five tips to help you get started on refining your own time estimates.

1. Estimate in inch-pebbles, not milestones. When you’re faced with a large piece of work to estimate, don’t try to come up with a single number to cover the entire job all at once. Break it down into pieces, and then break those pieces down into pieces until the pieces are small enough that you can see how you would do each one and put a number on them. As a general rule of thumb, if the pieces take more than 4 to 8 hours, they’re not small enough yet. Most people have trouble guessing their time to perform any job that will take longer than that.

2. In estimating, 2 plus 2 doesn’t equal 4. After you’ve broken the job down into tiny pieces and estimated them all, the temptation is overwhelming to add up all the individual estimates and make that the estimate for the entire job. Don’t fall for this. The problem is that you won’t hit your estimates, and the variance is asymmetrical – if you estimate 4 hours for a task, you can’t take much less than 1 hour, but you could take 20 hours if you were wildly wrong. So 2 plus 2 might equal 4 – or it might equal 12. There are fancy applications to apply statistics to this problem, but as a rule of thumb, take your best total estimate and multiply by 2.5 to allow for this.

3. Don’t estimate by wishful thinking. You may know that the client only wants to spend \$15,000 on a particular job. If your estimate comes in at \$37,500, don’t let this fact pressure you into submitting a \$14,900 number in its place. No good will come of not finishing the job or taking only half of the rate you need to live. You should estimate realistically and, if necessary, point out places where the work can be scaled back to fit within a lower budget.

4. Don’t estimate in a vacuum. To produce an accurate quote of hours or price, you need to know what you’re quoting on. If your potential customer didn’t provide a good spec up front, you need to call them, meet with them, or swap email until you really understand the work that you’re agreeing to do. The alternative is to try to move to a more agile approach, where you’re selling hours to be applied to whatever tasks are mutually agreed as the job proceeds – in which case it becomes impossible to estimate a total “finished” cost.

5. Track and correct. Make sure you track your time and, at the end of the job, compare it to your initial estimate. You can use this information to tell you whether your estimates are consistently low, high, or just right – and to adjust your next estimate accordingly. This won’t help on your first estimate, but down the road a year or two you’ll be glad for the increased accuracy, and so will your customers.

You're subscribed! If you like, you can update your settings

## Related stories

1. As a newbie freelancer, I NEEDED this. Sometimes, having a step-by-step guide is the best thing, especially when you’re faced with 150 “little things” that pile up quickly. Thank you so much!

Share
2. Regarding the difference between a company’s expected budget and your expected costs: you’re right to advise NOT to lowball the estimate, because then it sets a precedent for willing to work for less than what you’re worth.

However, if bidding low means you get your foot in the door with a company that may give you more business down the road, consider whether a one-time loss is worth a long-term profit…

… unless that initial lowball (again) turns out to be all the client ever expects you’ll be worth. In that case, you’ve done yourself more harm than good.

Share
3. [...] Web Worker 101: Estimating Basics « Web Worker Daily [...]

Share
4. thanks, very usefull!

Share
5. [...] You can read the rest of this blog post by going to the original source, here [...]

Share
6. I’d have to agree.

One thing that I’ve found out is to develop an a la cart menu. If you have a list that gives the price or estimates for web design, graphic design, photography, SEO, etc it keeps you from getting roped into doing something you didn’t originally planned on, and it gives you an out when the client asks about it. So you don’t start with designing a web page, and end up developing their entire brand for the same price.

Share
7. Great article, I’ve written on this same topic myself. I honestly believe that being able to accurately estimate tasks you are given is a great way to prove your reliability and is a first step towards showing management how good you are. Nicely done, Mike.

Pete Johnson
HP.com Chief Architect
Personal blog: http://nerdguru.net

Share
8. [...] post on WebWorker Daily, titled Web Worker 101: Estimating Basics hits the primary suggestions that I encourage consultants and freelancers to follow, like [...]

Share
9. [...] Web Worker 101: Estimating Basics. [...]

Share
10. This is helpful – thank you. One of the GTD “holes” I’ve discovered is the lack of built-in planning, and the wonderful value of estimating work. This goes in my toolbox for clients.

Share

Comments have been disabled for this post