Make the scope as clear as the price.
Build an estimate from tasks, hours and rates. Record exclusions, compare versions and export a scope you can review with a client.
Estimated project total
Your numbers.
A clearer decision.
Calculate to see the breakdown, then save a baseline and explore a second scenario.
Example inputs — replace them with your assumptions, then calculate.
Saved inputs stay until you remove the draft or clear site data. Do not enter sensitive information on shared devices. Exported files contain your inputs.
Understand the numbers
Labor = sum of each task’s hours × hourly rate. Subtotal = labor + direct expenses. Contingency = subtotal × contingency percentage / 100. Estimate = subtotal + contingency.
Worked example
Fictional example: discovery takes 4 hours, implementation 16 and review 4, all at $75/hour. Labor is $1,800. Add $100 of direct expenses and a 10% contingency on the $1,900 subtotal: the estimate is $2,090. If implementation grows to 24 hours, the same method gives $2,750 — a $660 increase.
Try a different scenario
Describe a deliverable, not just an activity: ‘a tested signup form with an error state’ is easier to review than ‘development’. Record an acceptance check and what is excluded. Freeze a baseline before adding scope, so the discussion can show which hours changed. Export both versions and review the document before sharing private commercial information.
What this estimate leaves out
The estimate excludes sales tax, currency conversion, financing, discounts and payment terms. It is not an invoice, contract or guarantee. Contingency is not markup or margin. Confirm which expenses may be passed to the client and agree how scope changes will be approved.
Make the result actionable
Read the related practical guide →Method and examples by Techy · September 13, 2026 · Editorial policy (Spanish)