A good estimate is the difference between a profitable project and one you subsidize with unpaid hours. Most freelancers and small teams estimate by guessing a total number — "this feels like a $10,000 project" — and then discover at invoicing time that the work took 30% more hours than the number assumed.
The fix is to break the project into stages, estimate each stage separately, attach real hourly rates, and add a contingency for the work you can't predict yet. That's what this calculator does. No signup, no email wall — enter your stages and get a structured estimate you can send to a client.
The structure of a good estimate
An estimate isn't one number. It's a table:
Total Estimate = Σ (Stage Hours × Stage Rate) + Contingency
Each row is a stage of the project with its own hours and rate. The contingency is a percentage on top — usually 10–20% — that covers the work you know will exist but can't scope yet: scope creep, revisions, technical surprises, the client's feedback rounds that take longer than expected.
Why break it into stages instead of giving one number?
- Accuracy compounds. Estimating "40 hours of design" is a guess. Estimating "6 hours of research, 12 hours of wireframes, 20 hours of visual design, 4 hours of revisions" is four smaller guesses that add up to something closer to reality.
- Rates can vary by stage. Discovery might be $150/hr; QA might be $90/hr. A blended rate hides the value differential. Staging it makes the estimate transparent and defensible.
- Clients understand stages. "I estimated 40 hours for design" is less persuasive than "I estimated 6 hours for research, 12 hours for wireframes, 20 hours for visual design, and 4 hours for revisions — here's what each stage includes."
- You can track against it. Once the estimate is staged, you can watch actual hours per stage against the estimate — and catch a runaway stage before it sinks the project.
How to use the estimate
Once you have a staged estimate, three things follow:
Set it as the project budget
The estimate isn't a document you send and forget. It's the budget the project runs against. Ayron's estimate-vs-actual tracking ingests your estimate (PDF, text, or CSV), breaks it into stage budgets, and shows a margin bar per project that fills as you track time — green under 85%, orange 85–100%, red over. The difference between "I tracked 40 hours" and "design is 30% over budget with 3 weeks of work left" is the difference between a timesheet and a business tool.
Track actual hours against it
Every hour you track should be attributable to a stage. If you estimated 12 hours for wireframes and you're at 16 hours with wireframes still unfinished, that's a signal — either the scope grew, the estimate was wrong, or the work is harder than expected. All three are conversations you want to have with the client before the invoice, not after.
Use the how-to guide on tracking billable hours to set up the tracking discipline. If your task list lives in Asana or Linear, the tracked hours attach to the right tasks automatically — no copy-paste.
Invoice from the estimate or the actuals
Two billing models, both valid:
- Fixed-fee: you quoted the estimate total. The client pays that amount regardless of actual hours. The estimate is the contract. If you come in under, you profit. If you come in over, you absorb it — which is why the contingency exists.
- Hourly with cap: you bill actual hours up to the estimate total. If you go over, you bill the overage (or eat it, depending on your agreement). The estimate is the ceiling.
Either way, the tracked hours become the invoice. Ayron turns them into branded PDFs with Stripe payment links — the estimate stages become the invoice line items, and the rates you set in the calculator are the rates on the invoice.
Which contingency percentage to use
The contingency is the honest part of the estimate — it's the buffer for what you can't predict. The right percentage depends on how much you know:
| Contingency | When to use it | Why |
|---|---|---|
| 0% | Repeat work with a known client and stable scope | You've done this exact project before. Uncertainty is minimal. |
| 10% | Familiar work with a new client, or new work with a familiar client | One variable is unknown. 10% covers minor surprises. |
| 15% | New work, new client, defined scope | Both variables are unknown but the scope is clear. The standard default. |
| 20% | New work, new client, fuzzy scope | You don't fully know what "done" looks like yet. 20% protects you. |
| 25%+ | Research-heavy, exploratory, or "we'll figure it out as we go" | The scope is a hypothesis. Use 25% or bill hourly instead. |
If you find yourself consistently adding 25%+ contingency, consider billing hourly instead of fixed-fee. A 25% contingency is a sign you don't know the scope well enough to commit to a number.
Common estimation mistakes
Estimating by the project, not by the stage. "This is a $15,000 project" is a guess. "This is 8 hours of discovery at $120, 16 hours of design at $110, 40 hours of development at $100, 8 hours of QA at $90, 12 hours of PM at $100, plus 15% contingency = $12,765" is an estimate you can defend, track, and adjust.
Not estimating project management time. PM — scheduling, client communication, status updates, review cycles — is typically 10–15% of the total project hours. If you don't estimate it, you're donating it. Add a PM stage to every estimate.
Setting the contingency to zero. Zero contingency means you're betting the project will go exactly as planned. Projects never go exactly as planned. Even 10% is better than 0%. If you're confident, use 10%. If you're not, use 20%.
Estimating at one rate. Not all hours are equal. Senior strategy time at $175/hr is worth more than junior QA time at $75/hr. A blended rate hides the value differential and makes the estimate harder to defend. Stage your rates to match the actual work.
Never revisiting the estimate. An estimate is a hypothesis. The actual hours are the fact. If your estimates are consistently 20% low, your contingency needs to be 20% higher — or your estimation methodology needs to change. Review estimate vs actual after every project and adjust.
Worked example
Here's what the calculator produces for a web development project with the default template:
| Stage | Hours | Rate | Subtotal |
|---|---|---|---|
| Discovery & Planning | 8 | $120 | $960 |
| Design | 16 | $110 | $1,760 |
| Frontend Development | 40 | $100 | $4,000 |
| Backend Development | 32 | $120 | $3,840 |
| QA & Testing | 8 | $90 | $720 |
| Project Management | 12 | $100 | $1,200 |
| Subtotal | 116 | $12,480 | |
| Contingency (15%) | +$1,872 | ||
| Total estimate | 116 | $14,352 |
That's 116 hours at a blended rate of ~$107.60/hr, with a 15% buffer for revisions, scope surprises, and the work you can't predict yet. The client sees a structured estimate with stages they can understand. You see a budget you can track against.
FAQ
How do I estimate a project by stage? Break the project into its natural phases — discovery, design, development, QA, project management — and estimate hours for each stage separately. Multiply each stage's hours by the appropriate hourly rate (rates can vary by stage), add them up, and apply a contingency percentage (10–20%) for unpredictable work. The interactive calculator above does this automatically.
What contingency percentage should I use? 15% is the standard default for new work with a defined scope. Use 10% for repeat work or familiar clients. Use 20% for new clients with fuzzy scope. Use 25%+ for exploratory work where you don't fully know what "done" looks like — or consider billing hourly instead of fixed-fee. See the contingency table above.
Should I include project management in the estimate? Yes. PM — scheduling, client communication, status updates, review cycles — is typically 10–15% of total project hours. If you don't estimate it, you're donating it. Every estimate template in the calculator above includes a PM stage.
What if the client wants a single number, not a staged estimate? Give them both. The staged estimate is the backup; the total is the headline. Most clients prefer transparency — a staged estimate shows you've thought through the work, which builds trust. A single number without stages looks like a guess.
How do I track actual hours against this estimate? Ayron's estimate-vs-actual tracking ingests your estimate, breaks it into stage budgets, and shows a real-time margin bar per project. Track time against the stages using the billable hours workflow, and the margin view tells you whether each stage is on track — before the project ends.
Can I turn this estimate into an invoice? Yes. If you bill fixed-fee, the estimate total is the invoice amount. If you bill hourly, the tracked hours become the invoice line items — Ayron's invoicing turns them into branded PDFs with Stripe payment links. The rates you set in the calculator are the rates on the invoice.
Is this calculator free to use? Yes. No signup, no email, no paywall. Enter your stages, set your rates, and get your total in under a minute. If you want a tool that tracks actual hours against this estimate and turns them into invoices, Ayron is built for it — Free to start, Pro is $12/mo annual.
Does the calculator work for any type of project? Yes. The templates cover web development, design, and consulting, but you can add custom stages for any type of work — construction, legal, accounting, content creation, anything that breaks into phases with hours and rates. Use the "Custom" template to start from scratch.
Ayron details are based on its public landing page and should be treated as marketing claims rather than independent product verification.