No saved estimates

Project

Hours

Base hours
Hours under ideal conditions, as if writing from scratch with no surprises. The anchor: everything else is an adjustment around this.
Nominal hours
Base after all multipliers and reductions. The hours you actually estimate to get the work done.
Risk hours
Extra hours to cover unexpected issues. Only from risks with 'Include' enabled.
Total hours
Nominal + Risk. This is what the price is calculated on.

Deliverable

prototype
Throwaway. No multiplier: Base is already that.
mvp
Works, minimal tests.
production
Solid, in real use: tests, error handling, docs.
enterprise
Hardening, observability, implicit SLAs.
mission_critical
Zero tolerance, redundancy. Maximum multiplier.

Reuse (reduces hours)

none
Writing everything from scratch.
internal_component
Reusing one of your own components, with adaptations.
white_box
Reusing code you know inside out and can modify.
black_box
Reusing a box that just works without touching it (e.g. Webround stack). Maximum reduction.
generated
Generated code that you then refine.

Offloading (delegating to external systems)

What it is
Work you do NOT write because someone else's system handles it. Different from Reuse (which is YOUR code reused).
none
Not delegating anything — you write it all yourself.
saas
Fully managed, turnkey service (e.g. Firebase Auth, Algolia). Maximum reduction.
existing_platform
An entire platform you already have (e.g. Webround). Maximum reduction.
api
Calling an external service's API: the logic is theirs, you orchestrate the calls.
sdk
Using their library in your code (e.g. Stripe SDK). Saves time, but more manual integration.
framework
Relying on a framework that structures the work (e.g. Cloudflare Workers runtime).
microservice
Delegating to a separate microservice.
Hidden cost
The more you delegate, the more 'Integration hours' you need: making the external system talk to yours still costs.

Complexity (8 axes, 1–5)

How it works
Each axis contributes separately. Many medium axes weigh more than a single high one, but without exploding (there's a dampening factor).
1 / 3 / 5
1 = trivial, 3 = moderate, 5 = very complex on that axis.

Skill (gap)

required vs available
How much is needed vs how much you master. If more is required than you know, hours go up (you need to learn).
If you're already proficient
available ≥ required: no penalty. It doesn't scale below: 'I'm overqualified' doesn't save hours.

Risk

Not a task
It's an uncertain event ('the DB breaks'), estimated roughly. Lives separately from the task tree.
Probability
How likely the problem is to occur as-is, 1–5.
Impact
How much it costs if it happens, 1–5 (converted to hours by coefficients).
Mitigation hours
Hours you spend specifically to make the risk less likely (e.g. a validation prototype). Always paid, because you actually spend them.
Resid. prob
The probability that REMAINS after spending mitigation hours. Start at 3, mitigate, drops to 2.
Risk hours
Resid. prob × impact + Mitigation hours. A buffer for what slips through, plus the prevention work.
Include
ON: hours are factored into the price. OFF: kept out, monetized later as fixes. Your call.

Strategy (doesn't affect hours)

What it does
Moves only the PRICE, not the work. 3 across the board = neutral.
Downward
Project that benefits you (portfolio, reuse, future work, easy client) → discount.
Upward
Risk premium (high expected budget) → markup.
Multiplier < 1
Overall discount. > 1 = markup.

Price

Chain
Total hours × rate = subtotal → × strategy → − discount → + margin = final price.
Effective rate
Final price ÷ total hours. What you're actually earning per hour.

Work breakdown

Select an item to edit

Estimate

Nominal hours
32.0 h
Risk hours
0.0 h
Total hours
32.0 h
Rate
60 €/h
Subtotal
1920 €
Strategy multiplier
1.000
Discount
0%
Margin
15%
Final price2208 €

Strategy

Trust
30.0%
Client competence
30.0%
Communication ease
30.0%
Success probability
30.0%
Expected budget
30.0%
Portfolio interest
30.0%
Commercial interest
30.0%
Future work probability
30.0%
Webround reuse
30.0%
Price multiplier1.000

Risks

No risks yet.

▼

Export

Paste JSON

FAQs

What is Project Estimator?

Project Estimator is a free tool built by the Webround team to calculate precise cost estimates for software projects. By combining established software cost models and metrics, it helps developers, freelancers and consultants produce clear and defensible pricing for their clients without guessing the work.


Who should use Project Estimator?

Developers, consultants, Software Engineers, designers and everybody who's in the technology / consultancy field. It's not a requirement to use Webround to make good project estimates, you can use the "Webround reuse" parameter for any platform / SaaS / Tool you already use that gets things done faster.


What do I get from Project Estimator?

You get a clear and precise estimate of the cost and price of your work on a specific project. By entering project requirements, goals, client parameters, level of skill and reuse of existing tools, you can easily extract a clear pricing for your customer, without guessing the work.


Can I export estimates?

Yes, you can easily export estimates with the full details of each activity, number of hours and cost, calculated according to your parameters.


Are parameters exported too?

No, your parameters are only used to calculate costs. They're not showed, except for risk management activities.


Does Project Estimator reflect a specific Software Cost Model?

Not exactly. Project Estimator is a result of studies that combine different metrics traditionally used to calculate Software costs. From the Mythical Man-Month metrics, LOC (Line of Codes) metrics, FP (Function Points) metrics, up to Algorithmic Models (COCOMO, COCOMO 2), Project Estimator keeps up and summarizes all the existing concepts, condensing them into a single mathematical model that keeps track of everything needed to precisely define the cost of software for clients and developers.


Are calculations stored?

Yes, but only locally on the device and browser you used to create them. No backend, no database, no data transmission of any kind is involved. If you switch device or browser, previous estimates won't be available. Clearing your browser's site data for this domain will also clear the local store where estimates are saved.

PROJECT ESTIMATOR

A Webround Product — built with Webround

Project Estimator is a local-first estimation tool for software projects.

Everything runs in your browser: data is stored in IndexedDB and never transmitted anywhere.

Free to use with no sign-up required.

LINKS

Webround
Image without alt text