Skip to content
4.7

from 1,840 ratings

Project Estimate Builder

Break the job into tasks, give each one an optimistic, likely, and pessimistic figure, and get a cost range with the expected value marked on it. Add your rate, a contingency, and the assumptions you are pricing under. Nothing you type leaves your device.

Your estimate

Three-point PERT

Estimated cost, low to high

$23,760 to $36,300

316.8 to 484 hours · 10% contingency included · $75 an hour

Where the hours land

ConfidentUncertain9 runs in 10

Expected 397.5 h
316.8 h low370.1 to 424.9 h most likely484 h high

The marker is the PERT expected value, (optimistic + 4 × likely + pessimistic) ÷ 6, which counts your most likely figure four times. The shaded slice is where nine estimates in ten land once the tasks are combined, because they rarely all overrun at once.

Expected effort

397.5 h

About 49.7 days at 8 hours a day

Expected cost

$29,810

The middle of the range, not a promise

Nine runs in ten

370.1 to 424.9 h

$27,755 to $31,865

Contingency

36.1 h

10% on top, $2,710

Working estimate

spread 42% of the expected value

A normal band for a job you have scoped but not fully specified. Keep the assumptions written down and revisit as decisions land.

Tasks and their three points

Hours per task, optimistic to pessimistic

  • 32 h · 9% · $2,400
  • 80 h · 22% · $6,000
  • 200 h · 55% · $15,000
  • 49.3 h · 14% · $3,700

Break the job small. Four to eight parts is usually enough, and every part you split makes the total more trustworthy than one guess for the whole job.

$/ hour

A buffer on top for the normal surprises

%

Start from a shape

Loads a task list you can rename and re-point. It replaces whatever is in the list now.

The conditions these numbers depend on. They travel with the copy and the CSV.

Every figure is worked out on your device. Your rates, margins, and client notes are never uploaded, logged, or stored.

🔒

Private by design

Everything runs in your browser. Nothing you enter is uploaded, logged, or stored.

Instant results

No server round-trip and no queue. The answer appears the moment you ask for it.

🎁

Free, no limits

No account, no email, no daily cap, and nothing useful hidden behind a paywall.

📴

Works offline

Once the page loads it keeps working with no connection, even in airplane mode.

Our free project estimate builder helps you work out the likely cost and effort of a job as an honest range, from a low figure to a high one, before you commit to a firm price, with the whole thing done inside your browser. You break the work into phases or line items, put a low and a high number against each, write down the assumptions you are pricing under, and the tool totals the range and any contingency you add. There is no sign-up and no account, and because every figure is handled on your own device, your planning numbers and client details never leave your hands.

An estimate is a plan, not a promise. It is the number you reach for while a job is still taking shape, when you know enough to size it but not enough to commit to an exact price. That is a different job from a quote, and using the right one at the right time is the difference between pricing work confidently and getting caught out. This page covers what a project estimate builder does, how an estimate differs from a quote, how to build an honest range with phases and assumptions, two worked examples with real numbers, and how an estimate becomes a firm quote once the details are settled.

What a project estimate builder is, and who it is for

A project estimate builder is a tool for sizing a job before you price it firmly. Instead of forcing a single number out of incomplete information, it lets you break the work into parts, give each part a low to high range, note what you are assuming, and see the whole thing add up. The result is a ballpark you can use to plan, to decide whether a project is worth pursuing, and to give a client an early sense of the cost without committing to a figure you might regret.

The people who reach for a project estimate builder are the ones who have to size work before they can price it. Freelancers scoping a build before they write a proposal. Agencies planning the cost of a campaign across several phases. Builders and contractors giving a homeowner a ballpark before a full site survey and quote. Project managers pulling together a budget for approval. What they share is a moment where a rough, honest range is more useful and more truthful than a firm number nobody can yet stand behind.

The key word is honest. A good estimate does not pretend to know what it cannot know. It shows a range that reflects the real uncertainty, lists the assumptions that hold the numbers up, and makes clear that it is a planning figure rather than a commitment. Done well, an estimate builds trust, because the client sees you being straight about what is settled and what is not, and it protects you, because nobody can later treat a ballpark as if it were a signed quote.

Estimate versus quote: a range and a plan, not a firm price

This distinction is the heart of estimating, so it is worth being exact about it. An estimate is a preliminary figure, usually a range, that you give while the scope is still loose or before you have all the costs in front of you. A quote is a firm, client-facing price you commit to for a defined scope. The estimate says roughly this much and here is what that depends on. The quote says exactly this much and I will stand behind it.

The reason the difference matters is that it changes what the client can hold you to. An estimate leaves room to move as the details firm up, which is exactly what you want early on, when a dozen things about the job are still open. A quote closes that room deliberately, because by the time you send one you understand the work well enough to commit. Trouble comes from mixing them up. Treat an estimate as a quote and you may get locked into a price built on guesses. Treat a quote as an estimate and you look unsure, or you invite a fight when the final bill lands higher than the client expected.

The healthy flow runs in one direction. You estimate first, while the job is still taking shape, to plan and to give the client a ballpark. As the scope, the materials, and the timeline settle, the range narrows and your confidence rises. When you know the job well enough to commit, you turn the settled figures into a firm price with the project quote builder. The estimate is the thinking and planning stage, and the quote is the commitment that follows. One feeds the other, and the project estimate builder is the tool for the first half of that journey.

The parts of a solid estimate: effort, phases, assumptions, and ranges

A number on its own is a guess. What turns a guess into an estimate is the structure around it, and a few pieces do most of the work.

  • Effort. Most project cost comes from effort, the time it takes to do the work. Even for a materials heavy job, labor is usually the swing factor. Estimating effort in days or hours, then applying a rate, is more reliable than trying to feel your way to a lump sum.
  • Phases. Breaking a big job into phases, such as discovery, design, build, and testing, turns one large unknown into several smaller ones. Small unknowns are far easier to size, and estimating each phase separately, then adding them, is more accurate than guessing the whole.
  • Ranges. Each phase or item gets a low and a high figure, not a single number. The low is a good run where things go smoothly, the high allows for the normal friction of real work. The gap between them is your honesty about what you do not yet know.
  • Assumptions. These are the conditions your numbers depend on. The client will supply the copy. Standard fixtures will be used. The site is accessible. Nothing major will change mid project. Writing them down is what makes an estimate defensible, because if an assumption breaks, everyone can see why the real cost moved.
  • Contingency. A buffer on top, often a percentage, that covers the small surprises every project has. A ten or fifteen percent contingency is not padding, it is a realistic acknowledgment that not everything goes to plan.
  • Exclusions. What the estimate does not cover. Naming the things you have left out, such as third party fees or content you are not producing, prevents a client from assuming a wider scope than you priced.

Rough order of magnitude and the cone of uncertainty

Early estimates deserve a word of their own, because they are the ones most often misunderstood. A rough order of magnitude, or ROM, estimate is a very early ballpark whose job is to show the scale of a cost rather than its exact value. It answers the question is this a five thousand dollar project or a fifty thousand dollar one, so a client can decide whether the idea is worth pursuing before anyone spends time on a detailed quote. A ROM is deliberately wide, sometimes framed as roughly a quarter under to three quarters over the midpoint, and it is honest about being coarse.

Estimating professionals describe how accuracy improves over time as the cone of uncertainty. At the very start, with little settled, any estimate carries a wide band on either side. As you scope the work, make decisions, and remove unknowns, the band narrows, and the range you can honestly give tightens. The project estimate builder is designed to live in that cone. Early on you enter wide low to high ranges and a healthy contingency. Later, as you learn more, you tighten the numbers, drop the contingency, and the estimate starts to look a lot like a quote. Trying to give a narrow estimate too early is the classic mistake, because it hides uncertainty that has not gone away, it has just been papered over.

How to use the Toolfiddle project estimate builder

The tool is built to produce a clear, honest range without any special training, and the flow is short.

  • Break the job into phases or items. List the parts of the work, whether those are project phases like discovery and build, or line items like labor and specific materials. Smaller parts are easier to size accurately.
  • Give each part a low and a high figure. For each phase or item, enter a low estimate for a smooth run and a high estimate that allows for friction. The middle box is what you think will actually happen, and it carries the most weight in the expected value.
  • Write down your assumptions. Note the conditions your numbers depend on, such as the client supplying content or standard materials being used. This is what keeps the estimate honest and defensible later.
  • Add a contingency. Apply a percentage buffer for the normal surprises. The project estimate builder adds it on top of the range so the client sees a realistic band rather than a best case.
  • Review the range and the marker. The tool totals the low figures and the high figures into an overall range and marks the expected value inside it. Check that the spread reflects how much you actually know at this stage, and read the confidence line underneath.
  • Save or share the estimate. Copy the summary or download the CSV, and keep it for your own planning or share it with the client as a clearly labeled ballpark. When the scope firms up, you carry the settled numbers into a firm quote. At no point does any figure travel to a server.

The marker inside the range bar is the PERT expected value, which weights your most likely figure four times as heavily as the two extremes. The shaded band around it is where nine estimates in ten land once the tasks are combined, since it is unlikely that every single task hits its worst case in the same project. Seeing both at once is the difference between a range you can defend and a pair of numbers you picked.

Worked example: estimating a mobile app build

Say you are a freelance developer and a client wants a rough cost for a simple mobile app before they commit to anything. This is an estimate, not a quote, because the features are still loose. Open the project estimate builder and break the job into phases. Discovery and planning, a low of 3 days and a high of 5. Design, a low of 8 days and a high of 12. Build, a low of 20 days and a high of 30. Testing and launch, a low of 5 days and a high of 8. You work at a 600 dollar day rate.

Add the low days: 3 plus 8 plus 20 plus 5 is 36 days, which at 600 dollars is 21,600 dollars. Add the high days: 5 plus 12 plus 30 plus 8 is 55 days, or 33,000 dollars. So the honest range is about 21,600 to 33,000 dollars. You write your assumptions plainly: the client provides all content and branding, the app targets one platform, and there is no custom backend beyond a standard service. You add a 10 percent contingency for the usual surprises, and you label the whole thing an estimate for planning. The client can now decide whether the project fits their budget, and when the features are locked down you tighten the ranges and produce a firm quote. Every figure was worked out on your own machine.

Worked example: estimating a bathroom renovation

Now say you are a contractor and a homeowner asks what a bathroom remodel might run before you have done a full survey. This calls for a rough order of magnitude estimate. Open the project estimate builder and list the parts of the job with a low to high range on each, covering labor and materials together. Strip out and prep, 800 to 1,200 dollars. Plumbing, 1,500 to 2,500 dollars. Tiling, labor and materials, 2,000 to 3,500 dollars. Fixtures and fittings, 1,800 to 3,000 dollars. Finishing and paint, 900 to 1,500 dollars.

The low figures add to 7,000 dollars and the high figures to 11,700 dollars, so the ballpark is roughly 7,000 to 11,700 dollars. You spell out the assumptions that hold that range up: standard mid range fixtures, no moving of the plumbing stack, no hidden damage behind the walls, and the existing floor being sound. You note that a full quote follows a site visit. The homeowner gets an honest sense of the scale, and you have protected yourself, because if the survey turns up rotten joists or they pick premium fixtures, the written assumptions explain exactly why the firm quote lands where it does. When you are ready to commit, those settled numbers become a quote.

Turning an estimate into a quote

An estimate is the first half of a story, and it helps to see where it leads. Early on, the range is wide and the contingency is healthy, because a lot is unknown. As you scope the work, talk through the details, and pin down the materials and the timeline, the unknowns fall away one by one. The low and high figures move closer together, your confidence climbs, and the estimate starts to resemble a firm price. That is the signal that you are ready to quote.

To make the switch, you take the settled figures, usually landing near the lower, more confident end of the range once the guesswork is gone, and turn them into client-facing line items with a committed total. The project quote builder does exactly that, producing a professional quote the client can accept. The estimate was the planning tool that let you size the job and decide whether to pursue it. The quote is the commitment that follows once you know it. Because both tools run entirely on your device, the numbers that started as a rough range in the estimate stay with you all the way through to the firm quote and, later, the invoice. Nothing about your pricing journey lives on anyone else's server.

Real world use cases across different fields

A project estimate builder earns its place wherever a job has to be sized before it can be priced.

  • Freelancers and developers. Scoping a build, a design system, or a content project before writing a proposal. An honest range with phases shows the client the shape of the cost and gives you room while the brief is still moving.
  • Agencies and studios. Planning a campaign, a website, or a launch across several phases, often for internal budgeting before a client sees a number. Phase by phase ranges make the plan legible and easy to adjust.
  • Builders and contractors. Giving a homeowner a rough order of magnitude before a full survey, so both sides know whether the project is realistic before investing in a detailed quote.
  • Project and product managers. Pulling together a budget estimate for approval, where a range with assumptions and a contingency is exactly what a finance team expects to see rather than a single optimistic figure.
  • Consultants and service providers. Sizing a piece of work whose scope is still being defined, so the client can plan a budget while the details are worked out.
  • Anyone weighing up a project. Sometimes you just need to know roughly what something would cost before deciding whether to go further. A quick, honest estimate answers that without pretending to a precision nobody has yet.

Tips for estimates that hold up

A few habits make an estimate you can defend later rather than one that comes back to bite you.

  • Estimate from the bottom up. Sizing each phase or item and adding them beats guessing a single number for the whole job. The parts are easier to reason about, and the total is more trustworthy.
  • Keep the range honest. Resist the urge to narrow the low to high band to look decisive. An early estimate should be wide, because the work genuinely is uncertain. The range is information, not a weakness.
  • Write assumptions down every time. The client supplies content, standard materials apply, the site is accessible. These lines are what let you explain, calmly and with a record, why the real cost moved if an assumption breaks.
  • Add a contingency and say so. A ten or fifteen percent buffer for surprises is normal and honest. Stating it openly is better than hiding it inside inflated line figures. The percentage calculator is handy if you want to check what a buffer adds in cash.
  • Label it clearly as an estimate. Put the word estimate on it and note that a firm quote follows. That one label is what keeps a ballpark from being treated as a commitment.
  • Revisit as you learn. An estimate is a living number early in a project. Tighten the ranges as unknowns resolve, and let it converge toward the quote rather than freezing an early guess.

Common mistakes to avoid

  • Giving a single number too early. A lone figure at the start of a job hides uncertainty that has not gone away. A range is more honest and far safer while the scope is loose.
  • Calling an estimate a quote by accident. If the client hears a firm price, they will hold you to it. Be explicit that an early figure is an estimate, or you may be locked into numbers built on assumptions.
  • Skipping the assumptions. An estimate with no stated conditions is impossible to defend when the job changes. The assumptions are not fine print, they are the reason the number is what it is.
  • Forgetting a contingency. Pricing a perfect run, with no buffer for the normal friction of real work, almost guarantees the real cost lands above the estimate.
  • Narrowing the range to win approval. Squeezing the low and high together to look competitive or decisive just moves the pain to later, when the true cost appears.
  • Trusting a platform with your planning numbers. Your ranges, rates, and margins are commercially sensitive. Entering them into an account based tool puts them on a server you do not control, which an on device tool avoids entirely.

Your client and pricing data never leave your device

This is the part that sets our project estimate builder apart, and it is why the tool is built the way it is. Everything you enter, the client, the phases, the low and high figures, the assumptions, and the contingency, is handled entirely inside your browser, on your own device, using your own processor. There is no upload step, no account, and no copy of your estimate sitting on a server anywhere. Once the page has loaded, you could switch off your connection and the tool would keep working exactly the same, which is the clearest proof that your numbers are staying put.

That privacy matters more for an estimate than people realize. An estimate exposes how you think about cost, the effort you expect a job to take, your day rate, your margins, and the buffer you build in. That is some of the most commercially sensitive information you have, the kind a competitor would love to see and a client trusts you to keep to yourself. Account based estimating platforms ask you to store all of it on their servers, under terms you probably did not read. Our approach removes the account, the upload, and the stored record, so the thinking behind your pricing never leaves your hands.

Genuinely free, with no account and no monthly fee

The second thing that separates this tool from the crowd is that it is genuinely free, without the catches that usually come attached. Many estimating tools online are the entrance to a subscription. You can size a job, but first you create an account. You can export the result, but a limit soon appears on how many free estimates you get, and the useful features sit behind a monthly plan aimed at bigger firms.

None of that applies here. There is no sign-up and no account. We do not ask for your email or your card. We do not cap how many estimates you can build or hold features back for a paid tier, because there is no paid tier we are steering you toward. You can rough out one estimate or a dozen, refine them as often as a project changes, and never hit a login or a paywall. The project estimate builder is a complete tool in its own right, not a sample that stops being useful the moment your work gets serious.

Instant and unlimited, by design

The third advantage follows straight from running on your device. Because nothing is uploaded and no result is fetched back from a server, there is no waiting on the network and no queue at a busy time. You enter the phases, the ranges update as you type, and the totals appear instantly, as fast as your device can do the sums. The work happens right where you are, so there is no delay and nothing to load.

The same design removes the artificial limits that account based tools rely on. There is no monthly estimate quota ticking down and no feature locked to a higher plan. You can revise an estimate as many times as a shifting project demands, because there is no server cost for us to recover on each one. And because the page is not loaded down with the heavy advertising and tracking scripts that clog so many free tools, it opens quickly and stays responsive while you work through the numbers. The goal is a project estimate builder that feels like a dependable utility you own rather than a service you rent by the month.

Works on any device, even offline

The project estimate builder runs on a phone, a tablet, or a computer, in any modern browser, and the layout adapts to the screen it finds. On mobile this is genuinely useful, because you can sketch an estimate during a site visit or a client call, adjusting the low and high figures as you talk through the job. Because the work happens on the device rather than on a server, you do not need a strong connection to build or change an estimate, so a weak signal will not stop you. Once the page has loaded, no live connection is needed to enter the phases, set the ranges, and read the totals, and nothing depends on being logged in or on a particular brand of browser. Your numbers stay on whichever device you used, start to finish.

Estimating is the first step in a short chain of pricing jobs, and the neighboring tools handle the rest. When the scope is settled and you are ready to commit to a firm price, the project quote builder turns your figures into a client-facing quote they can accept. Once that quote is accepted and the work is done, the invoice generator requests payment against the same lines. For the math inside an estimate, the percentage calculator works out a contingency or a margin, the discount calculator handles a reduction, and if you price across borders the currency converter checks a rate. Every one of these runs in your browser the same way the project estimate builder does, so your figures stay with you across the whole workflow.

The short version

A project estimate builder helps you size a job as an honest range, from a low figure to a high one, before you commit to a firm price. You break the work into phases or items, give each a low and a high, write down your assumptions, and add a contingency for the normal surprises. An estimate is a plan and a ballpark, different from a quote, which is a committed, client-facing price, so you estimate first and quote once the scope is settled. Do all of it here and your planning numbers and client details never touch a server, there is no account or estimate limit, and the totals update the moment you type. When you are ready, the settled numbers carry straight into a firm quote.

Frequently asked questions

The real questions people ask, answered plainly.

What is a project estimate builder and how does it work?

A project estimate builder helps you work out the likely cost and effort of a job before you commit to a firm price. You break the work into phases or line items, add a low and a high figure for each, and list the assumptions behind them. The tool totals the range and shows a ballpark from low to high. On Toolfiddle it runs in your browser, so your numbers stay on your device.

What is the difference between an estimate and a quote?

An estimate is a rough, preliminary figure, usually a range, that you use while the scope is still loose. A quote is a firm, client-facing price you commit to. The estimate says roughly this much, the quote says exactly this much. You estimate first to plan and to give the client a ballpark, then produce a quote once the details are settled and you are ready to stand behind a number.

Why is an estimate usually a range instead of one number?

Because early in a project you do not yet know everything that affects the cost. A range from a low figure to a high one is honest about that uncertainty and protects both sides. A single number pretends to a precision you do not have and invites a dispute later. As the scope firms up, the gap between low and high narrows, and eventually the range tightens into a quote.

How do I build a project estimate for free?

Open the project estimate builder, break the job into phases or items, and give each a low and a high figure for effort or cost. Add the assumptions you are pricing under, and the tool totals the range and any contingency. Save or export the estimate to share or to keep for planning. There is no sign-up, no account, and every figure stays on your own device.

What is a rough order of magnitude (ROM) estimate?

A rough order of magnitude, or ROM, estimate is a very early ballpark meant to show the scale of a cost, not the exact figure. It is often given as a wide range, sometimes from roughly 25 percent under to 75 percent over the midpoint, so a client can see whether a project is a few thousand or a few hundred thousand before anyone invests time in a detailed quote.

What are assumptions and why do they matter on an estimate?

Assumptions are the conditions your numbers depend on, such as the client supplying content, standard materials being used, or no major changes to the scope. They matter because an estimate is only valid while they hold. Writing them down protects you, since if an assumption turns out to be wrong, everyone can see why the real cost moved away from the estimate.

How do phases help me estimate a project?

Breaking a job into phases, such as discovery, design, build, and testing, makes a big unknown into several smaller ones that are far easier to price. You estimate each phase with its own low to high range, then the project estimate builder adds them up. This bottom up approach is more accurate than guessing a single number for the whole job and shows the client where the cost sits.

Should I add a contingency to my estimate?

Usually, yes. A contingency is a buffer, often a percentage on top, that covers the small surprises every project has. Adding, say, 10 or 15 percent to the estimate reflects the reality that not everything goes to plan. It is more honest than a bare number that assumes a perfect run, and it saves the awkward conversation when a normal hiccup pushes the real cost up.

Do my numbers and client details stay private?

Yes. Everything you enter, the client, the phases, the low and high figures, and the assumptions, is processed on your own device inside the browser. Nothing is uploaded and nothing is stored on a server. Your rates, your margins, and your planning numbers, which are commercially sensitive, never leave your machine, so an early estimate does not put your pricing on someone else's system.

Is the project estimate builder really free with no sign-up?

Yes. There is no account, no email, and no trial that turns into a bill. Many estimating tools online make you register and then hold the useful parts behind a monthly plan. This one does not. You can build one estimate or a dozen, refine them as often as you like, and never hit a paywall or a login, because there is no paid tier to steer you toward.

How do I turn an estimate into a firm quote?

Once the scope is settled and your assumptions have firmed up, the range should tighten toward its lower, more confident end. Take those settled figures and produce a firm price in the project quote builder, which turns your line items into a client-facing quote they can accept. The estimate is the planning stage, and the quote is the commitment that follows once you know the job.

How accurate should an estimate be?

It depends on how early you are. A rough order of magnitude estimate at the start might be within a wide band, while an estimate made after real scoping should be much tighter. The point of the project estimate builder is not false precision but an honest range with clear assumptions, so the accuracy matches what you actually know at that moment in the project.

Can I use this on my phone?

Yes. The tool runs in a mobile browser and the layout adapts to a small screen, so you can sketch an estimate during a site visit or a client call and adjust the ranges as you talk. Because the work happens on the device, you do not need a strong connection, and the figures you rough out stay on your phone rather than syncing to a server.

Who is the project estimate builder for?

Freelancers, agencies, contractors, and project managers who need to size a job before committing to a price. A developer scoping a build, an agency planning a campaign, a builder giving a ballpark before a full quote. Anyone who needs an honest cost range with assumptions, whether for internal planning or to give a client an early sense of the numbers.

How is this different from full estimating software?

Heavy estimating platforms ask you to sign up, learn a complex system, and store your data on their servers, usually for a monthly fee. The project estimate builder is one focused tool that runs on your device, needs no account, and keeps every figure with you. It builds an honest range with phases, assumptions, and a contingency, which is what most estimates actually need.

Related tools

Same promise: everything runs in your browser, nothing gets uploaded.