One of the many questions that I get regularly asked, especially by junior project managers is how to create cost estimates for website projects. Why is estimating so important? Well, if you don’t estimate correctly, you are putting the project at risk for going over budget which makes the project less worthwhile to do; especially if you’re working in a small digital agency. This article isn’t about how to create an actual estimate to give to your client, this article focuses on the thought process of what a project manager requires and what you should be doing to estimate costs correctly.
In my experience, estimating comes from a number of factors and over time as project manager you do become more resilient and accurate on these things. Most companies and agencies associate cost with time (ie it costs £100 per hour for a developer), so it’s a clear calculation if you can understand what is required to be done and what’s agreed for the scope of the project to estimate the time and then the cost. There is a simple process you need to think about in the overall process of cost estimating:
- Determine the scope for the project.
- Try to break the scope into smaller tasks so it’s easier to cost.
- Estimate these smaller tasks in terms of time and then total overall.
- Thing about tolerances/contingencies/overages of the project.
The key action you need to do here as project manager is to work out how much these smaller tasks within the overall project will take, and there are a number of methods you can use here:
- Estimating from experience – If you’ve already delivered a similar project on various occasions you should be able to accurately estimate the project. This is where experience counts.
- Acquiring estimates from each department – If the design team need to be involved, then make sure they understand the scope of work so they can estimate their time. You then should get this agreed in writing or through meeting to make sure the scope has been understood and the work can indeed be carried out within the time given.
- Check previous projects – Have you delivered a similar project before and what were the lessons learned from that project? If that project went over by 20%, then think about that for the cost estimate you provide in this estimate.
- Allow for tolerances – You need to allow for some tolerance/contingency in any project. It needs to be reasonable if challenged by your client ie allowing 80% extra on the overall project seems excessive once costs/profits have been taken into account.
Remember you can only estimate fairly based on the scope of work you are delivering to and if that changes throughout the process, then time and cost will have to change. Some agencies argue that an estimate is purely that, it’s never definite, so if you follow that theory then make sure your client and key stakeholders understand that’s your policy.
I hope you found this useful, it’s always interesting to know the methods you use to create your cost estimates?