Cost estimation is hard—creating a project budget that works for your agency and your clients is practically an art form.
How do you do it right? Start with the template, examples, and step-by-step instructions in this cost estimate guide.
Download the project budget template for a website redesign below. By the end of this post, you’ll know which type of estimate to use—and when—and the steps and tools to manage your project budget.
In this article
Project Estimate Template
If you’re on the hunt for a project estimate template, then you’re in luck. We’ve created this project budget template for a typical web design project for $100k. It matches the project plan that we created so you can use the two in tandem.
Download the template and use it as you follow along with the rest of this guide.
The files include project cost estimation and project estimate templates which you can repurpose for your own projects. If you’re looking for a project budget template for excel, we’ve included that in this bundle, as well as a simple project estimate checklist.
Project Budget And Estimation Basics
Whether you like it or not, money talks.
Creating accurate budgets and controlling costs is essential to project success. Budgets are usually the overriding factor that trumps all else, and are often the reason why we end up needing to resolve conflicts between agencies and clients.
There’s a lot of pressure, too. The cost estimation process can be stressful and scary; there’s always guesswork involved (hence why it’s a cost estimate, not an accurate forecast) and if you get the project budget wrong, as the project manager, you can find yourself in the firing line.
Managing project budgets successfully isn’t simple. But if you follow the steps for estimating properly, and combine it with a well-written statement of work, you can be confident that your project budget won’t let you down. Read on to find everything you need to start making your project budget work for you!
First, let’s cover the fundamentals. Find answers to common estimation questions below, as well as a list of useful tools for managing estimates and budgets. They won’t do the entire job for you, but project cost estimation tools can track and supply project information that feeds into your estimates and budget plan.
The Best Project Cost Estimators
There aren’t many pure-play cost estimator tools, but here’s some software that includes tools for projects cost estimation, such as time- and budget-tracking functionality that makes for more accurate project estimates.
- Microsoft Excel – Widely used project cost estimator with plenty of project estimate templates.
- Google Sheets – Free project cost estimation tool, alternative to Excel.
- Price&Cost – SaaS estimating and cost management tool to manage project financials.
- BrainLeaf – Project scoping tool that helps to accurately estimate project costs.
- Eastimate – Free SaaS estimation tool to create estimates and timelines collaboratively.
- Simplestimate – Free project cost estimator SaaS tool with three-point cost estimation and easy sharing.
- Web Development Project Estimator – Simple project cost estimator to estimate time and materials for web projects.
- CMAP Software – Estimation software with a clean interface; produces estimates for complex projects.
Beyond these tools, there are a lot of resource management tools that have estimation and forecasting features built in.
Project Estimate Definition
Within project management, an estimate is simply an approximate calculation of the effort and cost it might take to complete a project. It’s not a guarantee of the final cost—instead, it provides a client with a quote or guide (often a ballpark range estimate) of how much it might cost to do or deliver something so that they can secure budget to start the project. Budgetary estimates are made before a project is officially started.
Reasons Why You Need To Cost Estimate
Estimating might seem like a painful process, but it’s a crucial one. And while it might be tempting to copy and paste a cost estimate and send it on its merry way, it’s important for project managers to understand that every cost estimate is unique. Estimating is a fundamental part of the role of project management – the process of calculating how much a project might cost is important in defining the parameters of a project.
Here’s why you need to cost estimate your project before getting started:
- Estimates provide a price – you need to know what you’re going to charge the clients, (and when) so the client can decide whether it’s worth the investment to proceed with the project
- Estimates provide clarity – when you know how much budget a client has, the process of producing a cost estimate helps define the approach as the team will need to work together to define the overall approach, roles, responsibilities, deliverables, process, and resourcing plan.
- Estimates provide milestones – by breaking a project into phases and tasks, with a level of effort assigned to each, cost estimation provides an opportunity to ‘pulse check’ a project so you can know whether it’s on track or not.
- Estimates dictate a resource plan – in defining the approach and estimate, it also defines the level of effort you can apply to the project sometimes requiring the timeboxing of activities or limiting the amount of senior oversight.
Project Estimate Parts
Here’s what a typical estimate will show the client. A basic estimate calculation factors in:
Tasks (what’s going to be done)
Resources (by who)
Rate (at what billing rate, in what currency, with how much tax)
Duration (for how many hours or days)
+any markup and 3rd party costs (such as hosting, photography, travel, or subsistence)
= Estimate Total
Estimate vs. Budget
An estimate is an approximation, while a budget is some type of financial plan. Usually, a project estimate becomes a project budget after the client approves the project estimation. The project budget determines the total cost allocated by the client for the project.
Estimating For Agile Projects
In the post-waterfall world of agile, there’s a trend to not try to give cost estimates in hours or days at all. Because after all, when is a cost estimate ever right? The alternative is to simply size tasks and get going on a project, see how much you can accomplish and then work out how much you’ll be able to accomplish when you’ve established your velocity.
On the face of it, it sounds great – you don’t have to provide any real estimates and you just keep spending until you run out of cash. If you can get away with that, then great. Stop reading now.
The trouble is, that rarely flies. If clients are going to embark on a project, they need to know how much it’s going to cost so they can determine whether it’s worth doing. They need to be able to calculate the ROI and decide if the benefits of the projects outweigh the risks and costs. And for that, they need a cost estimate.
Overestimating Vs. Underestimating
Want to play it safe? One of your project manager responsibilities is to deliver projects profitably and on budget. So the easy and safe option can be to over-estimate and add lots of fat, or “pad your estimate”, to ensure you won’t go over the project budget.
But playing it safe could cost your agency the entire project—estimate too high and the project could get written off as too expensive and never get started.
The other temptation, especially if you’re a people (or client) pleaser, is to play it risky—to come up with a budget which you know isn’t high enough, but that will be palatable for the client. That’s no good either as it simply defers the difficult discussions of needing more budget to later.
The real answer: walk the estimate tightrope
Getting the balance right between estimating too high or low enables you to manage the tension between these two elements; safety and risk – creating a cost estimation that the client can buy, but that’s high enough to enable you to deliver on budget.
Types Of Agency Pricing Models
Common agency pricing models include (1) time & materials estimates and (2) fixed price. This list is by no means all-inclusive, but when you’re estimating projects it helps to understand the type of pricing model your agency uses so that you can create estimates and budgets that fit with your model. Find a simple definition along with the pros and cons of each pricing model below.
Time And Materials (T&M)
A time and materials type of estimate where the client agrees to pay based upon the time spent, and for materials (plus mark up), no matter how much work is required.
- The advantage for the client is that they can keep changing their mind about the requirements, and not have to worry about the contract needing to be changed and if the job doesn’t take as long as originally estimated, they don’t pay for time they don’t use.
- The advantage for the agency is that if the job takes longer than expected, the client should keep paying. With a time and materials budget, the client carries the risk.
In reality, most contracts tend to be weighted in favour of the clients; time and materials contracts are typically capped, with a guaranteed maximum price meaning the client gets money back if the project is completed quickly and the agency takes the risk and has to pay for any overages. Furthermore, because in a time and materials contract the scope is often not clearly defined, sometimes clients start to try to dispute the hours. So for these types of contracts, it’s really important to keep clean and accurate timesheets, tracking the time spent of the project.
Fixed Price Estimate
A fixed price estimate is where the client agrees to pay a fixed price, regardless of the amount of effort applied to the project.
- The advantage of fixed price estimates for the client is that they know if they can secure the budget for the project, they’ll get everything that is offered for that price.
- The advantage of fixed price budgets for an agency is if you can get the client to agree to a high price, and deliver it more efficiently, you stand to make a bigger profit.
Clients can sometimes be nervous about fixed price estimates (or value based pricing) as they worry that they’re paying too high a price for the services that are being delivered.
Consequently, clients sometimes use ‘best and final fixed price budgets’ to shop a project around, and try to get agencies to bid against each other. Another disadvantage is that if you go over the project budget, the client won’t pay any more money for the project. With a fixed price budget the agency carries the project risk so it’s important that the scope of the project is tightly defined.
Which Agency Pricing Model Should I Use?
- Time and Materials estimates are great for projects where it’s difficult to accurately estimate the size of the project, or when it is expected that the project requirements are likely to change.
- Fixed price estimates are great to use when there’s little uncertainty or risk in the project: a price is agreed and then paid.
Types of Estimates
What are the types of estimates? There are many, but here are a few of the most common estimates that digital agencies use:
Use a ballpark estimate when the client is trying to work out if they have the budget to do a project.
The client will need a very rough estimate to decide whether the project is going to be remotely feasible. Usually a ballpark estimate is ranged, so if you think the project might cost $100k, you’d give a (-25% to +50% variance) range of $75k – $150k, to see the client’s budget.
Use a budget estimate when the client thinks they have the budget and needs some more detail.
Supposing the client is happy with the ballpark estimate provided, you might then pull together a quick project plan, consisting of a cost estimate and timeline that you can tailor to the client’s budget. If you still think your $100k ballpark was accurate, you might give a (-10% to +20% variance) $90k – $120k range.
Definitive SoW estimate
Use a definitive SoW estimate when you’ve completed all due diligence and need project budget approval.
Assuming the client is still good to go, the final step in the estimate refinement is pulling together the Statement of Work (SoW) which will include the estimate and total project budget. Again, assuming your $100k budget estimate is still valid, you’d estimate (0% to +15% variance) $100k + $15k contingency.
Of course, you can jump straight into a definitive SoW estimate, but having more detail means it will usually take a lot more time to produce. Depending on the type of estimate you’re going to produce, you can use different estimating techniques and estimating approaches to ensure you create an appropriately accurate cost estimate.
A Simple Project Budget Example
Let’s make a cake. A very expensive cake.
Below, you’ll find a budgetary estimate for making a cake. You could present a document like this to a client and see if they could secure $1000 to start the cake-making project. Then, after refining the cost estimate, you’d create a statement of work and get approval with a purchase order.
Then, you’d bake your kick-ass cake. Admittedly, it’s a ridiculously expensive cake, but hey, you deserve it.
This example estimate includes some critical project information with the project name, project manager, and the date. The estimate breaks down the tasks into phases, and shows who will be doing what task, in each phase of the project, and what level of effort they will apply.
Importantly, this estimate example also shows 3rd party costs (which very generously, we didn’t mark up) and an estimate summary which a client could use as their budget. In this project budget example, we didn’t include a risk budget, change budget, contingency, or assumptions, because after all, it’s just a cake.
Pre-Estimate Checklist: 5 Things To Know Before Creating A Cost Estimate
You’re on the phone to a client (as they’re going down the lift, of course, so you can’t hear them properly).
They want a number:
“So I need an app—basically like Facebook but a bit different. How much will that be? Can you tell me how much today? I REALLY need to know today. Okay…? What…? I can’t hear you. Just send me the number in the next hour. Thanks so much bye.”
Alright. Before you start scrambling around to give any numbers, cover this checklist:
- Know the project
- Have a budget
- Have a plan
- Know why you’re estimating
- Know what kind of estimate you need
1. Know The Project
Before you start estimating anything, the first thing you need to get your head around is why you’re doing the project in the first place. You have to understand the client’s brief, what they’re trying to achieve, and why.
You need to understand the desired results of the project and what success looks like to them. Without that basic understanding of strategic objectives, it’s difficult to know where to put an emphasis on effort in the project.
2. Have A Project Budget
It’s good to have some sense of a client’s budget before you start doing anything. Often a client will claim they don’t know their project budget, which means you’ll need to discuss a few options.
First, start high. Find out what’s above their project budget, and work down from there. Even if they don’t think they’ve got a budget, they obviously will have some idea what they think they’re willing to pay for something, and what they’re not.
But if you can help a client at least work out the limits of their project budget it’ll save a lot of time from having to look at all the possible options.
3. Have A Plan For The Project
When you’re estimating a project, it’s much easier to do if you’ve got at least a simple project plan. The reality is that you’ll need to edit the project plan to align with the estimate, and you’ll need to refine the estimate to align with the project plan.
The relationship between cost estimation and project plan is symbiotic; they feed from one another. If you dive straight into an estimate with no plan, you’ll quickly discover that you’ll need an accompanying project plan for it to have any meaning.
That said, it can also be helpful for project planning if you do a quick top down estimate. Think of it similar to a project plan sketch. Its purpose is to put a stake in the ground and work out how much effort you could afford to apply to different phases of a project to see if it might be feasible.
Top down website estimate example
For example, if you know that you have $100k for a website redesign project, you could split up $100k or 20 weeks of effort (assuming it’s $5k/per person/per week) as below:
Creating this kind of very high-level cost estimation is helpful before you start your project plan to provide a sanity check to avoid over-engineering the process. If you don’t have any idea of the level of effort you can afford, you’ll get halfway through your project plan and realize you’ve overcooked it.
4. Know Why You’re Estimating
Answer this question: What are you trying to achieve with your budget and the estimate you’re creating?
Are you estimating to get an accurate project budget? Or are you estimating to hit a specific number? Are you trying to win new business, or sell a project as a loss leader to get more work down the line? Do you want to invest heavily in the upfront discovery, which can be leveraged for a group of projects down the line, or is it a risky technical project where more effort should be allocated for development?
Cost estimation will always have a context. Knowing the full picture ensures that you don’t waste your time producing something that might be technically correct but totally inappropriate for the project.
5. Know What Kind Of Estimate You Need
In the run-up to a project budget being signed off by a client, there’s a process of defining the budget. So how do you make sure you’re not wasting time creating a detailed cost estimate that’s way outside of a client’s budget? At different phases of a project, we can use different types of estimates.
5 Project Budget Estimation Techniques
So what are the project estimation methods in project management? There are a few different ways to estimate a project and it’s worth being familiar with them so that you know what estimation technique to use in your project. In this section, we’re going to cover off five estimation techniques:
Decide the total, then divide that total into the tasks or phases
Top down estimation is a great ballpark estimate technique that involves taking a project budget, and slicing it up so that you allocate a number of hours to phases or project tasks.
Then you decide (yes, guess) whether the amount that’s allocated for a phase or task is appropriate and try to adjust the scope of the project to match the budget allocated.
As we mentioned when discussing, ‘Having a plan for the project’ – top down estimating is a useful technique to use in the early phases of a project when you’re trying to validate if a client’s budget is sufficient to deliver a project.
The disadvantage of top down estimating is that it’s totally inaccurate, and arguably not really estimating at all – it’s carving out chunks of budget for different tasks. It assumes that the overall project budget is determined before the project starts and isn’t going to change.
The advantages of top down estimating is that it can be very quick which can be useful if you’re trying to help a client determine whether or not their budget is viable. It’s also useful in helping a client try and understand what kind of scope their budget might allow for.
Use data from similar projects to decide a similar total
Another great ballpark estimating technique is analogous estimating. Analogous estimating might sound fancy but it just means a project budget like one you’ve done before. An example of analogous estimating would be to say, ‘Last year we did three website design projects which each cost us $100k, so here’s a budget for $100k for your website design.‘
Simple right? Well yes, if you’ve actually got relevant historical data that accurately matches with the current project you’re trying to estimate. It assumes you’ve got data from previous projects that are similar enough to provide a useful comparison.
Analogous estimates can also be derived from examples outside your—or your team’s—project experience (for example, here’s a survey with rough figures on mobile app development costs).
Use caution—outside examples can be a good place to start if you’ve never done that type of project before, but you’ll still need to do a fair amount of due diligence as you break down the costs for your specific case.
The disadvantage of analogous estimating is that it’s inaccurate. While there may be similarities between projects, projects are always unique – it’s often like trying to compare apples and oranges. Furthermore, for analogous estimates to be viable and useful, they’re heavily reliant on accurate historical data.
The advantage of analogous estimating is that it’s very quick and easy, and can be used with limited information available about the project – similarly to top down estimating, it’s a great estimation technique to use when you just need a ballpark estimate.
Using data and variables to calculate the total
If you’ve got the data, and some more time on your hands – a potentially more accurate ballpark estimating technique is parametric estimating. Parametric estimating takes variables from similar projects and applies them to the current project.
For example, suppose you had a project to develop a 2-minute animation. Say the cost of a previous project that involved developing a 30 second animation was $10,000. You could then extrapolate the cost for the current project would be roughly 4 x the cost, or around $40,000.
The advantage of this process is that it’s more accurate than the analogous estimation because it employs more than one data set and uses the statistical relationship between historical data and variables.
The disadvantage is that with digital projects it’s often hard to find useful data points.
Three Point Estimation
Get three different estimates and take an average to calculate the total
Assuming you’re done with ballpark estimating and the client has asked for a proper budget estimate, you need to start using more accurate estimating techniques. A single hourly estimate per task is easiest, but sometimes it’s nice to think in ranges and take a weighted average.
Three point estimation is a way to calculate a realistic cost estimation using a best case estimate, worst case estimate, and most likely case estimate. There are different ways of using these numbers, depending on how you want to weight the result but a simple way to use the data is to use the formula:
(Best + Worst + Most likely) / 3 = Expected estimate
As an example, after discussing with your team, you estimate the time to design a web page as follows:
- Best – 3hrs
- Worst – 9hrs
- Most likely – 5hrs
(Best + Worst + Most likely) / 3 = Expected estimate
(3 + 9 + 5) / 3 = 5.7 hrs
The advantage of three-point estimating is that it reduces risk – by taking into account best, worst case, and most likely outcomes, you get a project estimation which takes into account some of the uncertainty and risk in a task.
The only real disadvantage of three-point estimating is that it takes a bit longer to do!
Estimate all the individual parts and add them together to get the total
When you’re at the point of creating a statement of work, it can be helpful to do a bottom-up estimate. Bottom-up estimating uses a work breakdown structure (WBS) which you can take from your project plan, and breaks down a project into its individual tasks which are estimated separately and then added together to calculate the total project cost.
The advantage of the bottom-up estimating technique is that it’s most accurate and by being granular, enables robust tracking of a project’s progress against the estimate. You know very quickly if a project is going over budget if tasks start taking longer than were estimated.
The disadvantages of bottom-up estimating is that it’s time-consuming to produce, and can only really be used when you know all the details about every task in a project. Also, by becoming very granular (and estimating at a task level) it can sometimes inflate the cost of an estimate. For this reason, it’s a great technique to use alongside analogous estimation, when you’re trying to validate the appropriateness of your estimate.
Which Estimation Techniques Should You Use?
There’s no right or wrong estimating method – you just need to use an appropriate estimation technique for the budget, timeline, and stage that a project is at. Obviously, the more accurate a cost estimation method is, the costlier and more time consuming the process of producing it becomes.
So while bottom-up estimating might seem like the best approach, it’s not always advisable when you are short on time or resources, even though it might be the most accurate.
How To Create A Project Budget
Use our cost estimate checklist below to create a project budget in 10 steps. Here’s a cost estimation infographic that sums up the steps:
In this project estimate checklist, we’ve simplified the process of how to create a project cost estimation to ten simple steps. They’re the basics you need to master to develop a robust cost estimate for your project:
1. Define the idea
Get some clarity. Understand what you’re doing, why, and how. You need to quickly rework the early idea into a viable solution that matches the client’s project budget and timeline, and delivers on the strategic objectives so that it produces results.
2. Identify the parts
Break it down. When you’re clear on the idea, identify the specific deliverables and map out the process that is required to deliver each one so you can accurately estimate the effort for the total budget.
3. Do your research
Leave no stone unturned. Go back to your pre-estimate checklist and get acquainted with the client, team members, and project history so you’re clear on expectations, budgets, skills, experience, and past performance.
4. Ask difficult questions
Ask how and why. To estimate properly, you need to be completely clear on every aspect of the project so you can ask your team how they can best deliver it, and then keep asking why – probing their estimates so you begin to uncover their assumptions.
5. Prepare for the unexpected
Plan for plan B. Your planned costs are the least of your worries—it’s the unexpected costs that are the real deal-breakers. Projects rarely go exactly to plan so account for an appropriate amount of budget for risk, changes to the project schedule or scope, and uncertainty with your estimate so that you can still deliver on budget.
6. Know your estimate limits
Don’t guess. Know your planning horizon and split the project into phases so that you only give estimates for the phases that you can confidently provide costs for – for the rest, only provide ranged ballpark estimates.
7. Account for hidden costs
Include everything. Be sure to include indirect project costs; for account and project management, for estimating the project, labor materials, project expenses, reporting, invoicing, 3rd party costs, travel and subsistence and closing the project.
8. Check it
Mistakes are expensive. Review the post-estimate checklist to ensure labor costs, process, phases, tasks, rate cards, exchange rates, formulas, and 3rd party costs are all properly accounted for and double checked for accuracy.
9. Caveat your estimate
Don’t expose yourself. Never supply a cost estimate without including boilerplate assumptions that provide detail around deliverables, client expectations, and communication expectations, as well as ownership of the project’s final outputs.
10. Be smart
Wildly underselling or overselling a project creates headaches later in the project so try to be as honest and realistic as you can; it’ll make reporting more straightforward and build trust with your clients.
Once you’ve established a budget (and it’s approved by the client), you’ll need to manage and track budget usage throughout the project. There are several ways to do this, which we don’t have time to fully cover in this article. I’ve covered the subject in our articles on the project management lifecycle and scope creep.
Not Sure Where to begin?
Becoming a confident, successful project manager is no simple feat—if you’re looking for a good place to start, our online course in Mastering Digital Project Management will light the way. In this 7-week course, you’ll gain access to relevant, practical expertise that will help you lead happy teams and deliver high-value projects in the digital world.
Whether you are formally trained as a project manager or an account manager who has been cast into the role, it’s your job—and privilege—to become a master in the art of managing projects. Our course will equip you with the fundamentals that will help you meet the daily challenges of project management, evolving as a professional in the big, wild world of DPM.
DPM MEMBERSHIP RESOURCE
Looking for a rock-solid Project Estimate Template? Would a filled in sample help?
Become a Member to get this template (and lots more). Membership is a supportive community with access to mentorship, networking, and ongoing resources to grow your career.
Power-up Your PM Skills With Expert Training
Here’s an overview of our upcoming Mastering Digital Project Management Online Course, where you can gain access to expert instruction for leading happy teams and delivering high-value projects in the digital world.
Want To Read More On Project Estimation Techniques?
Need more project budgeting help or some project budget management advice? Check out these articles for more guidance on project estimation techniques.
- Paul Boag: How To Work Out What To Charge Clients: The Honest Version
- Sam Barnes: 4 Effective Strategies To Estimate Time For Your Design Projects
- Sam Barnes: Estimating Time For Web Projects More Accurately: Part 2
- Jeff Gardner: Quality-Price-Ratio in Web Design (Pricing Design Work)
- John Reeve: How to Accurately Estimate a Web Design Project
- Alyssa Gregory: How To Estimate Time For A Project
- Peter Mouland: Effective Estimating — Scoring (Story) Points For The Team
- Benjamin Jackson: Agile Billing Guarantees Your Income