Rush fees: price the schedule, not the urgency
A rush plan has its own hours, helper cost and risk. Price the compressed schedule from those inputs, then test a flat surcharge against the cost floor.
The estimating field notes
Better bids begin with better questions.
Worked examples for the decisions a bid actually turns on — what to charge, what to promise, what to change when the budget is tight. Start with your next decision, then put the numbers to work.
Subscribe by RSS · Follow an estimating workflow · Search all resources
Start with the decision in front of you
Set a defensible price. Start with margin versus markup, choose P50 or P80 confidence, then work through a client budget below your quote, pricing a change request and who keeps the savings when AI makes you faster.
Make a delivery promise. Understand dependencies and elapsed time, check what on time and on budget together really means, and see how to price a late-delivery penalty into a quote.
Build a better estimate. Compare PERT and Monte Carlo, see why task P80s do not add up, read the cone of uncertainty, add contingency without double-counting, and learn from completed jobs.
Protect the economics. Explore the cost of an underpriced job and break-even while the clock is running.
Rates, scope and the cost of saying yes
Price the available hours. Check billable utilization, distinguish cost rates from billing rates, and compare the use of scarce capacity.
Protect the delivery plan. See how a discount removes profit and unbilled hours change margin, then check milestone cash flow, mitigation value and effort versus duration.
All field notes (28)
28 articles. All links work without JavaScript.
Rate increases: how many hours can you lose?
A 15% rate rise can still leave an existing client worth more, even after it buys fewer hours. Two break-even tests show how far the hours can fall.
Three-point estimates: ranges before guesses
Narrow ranges look confident and price risk as if it were gone. A worked example shows how the pessimistic value, not the most likely one, moves your quote.
The 40 unbilled hours that turn a 25% project margin into 10%
Cost an incremental change, compare absorbing it with charging a fee, and keep the original project economics separate from the change margin.
Is a risk mitigation worth its cost? Compare the residual risk too
A 1,500 mitigation produces 1,300 net expected benefit in this worked example. See why that does not guarantee a saving or define a P80 reserve.
400 hours of work is not a delivery date
Separate effort, available capacity and dependency-driven duration with a three-person capacity check and a small parallel-task schedule.
Your freelance rate depends on billable hours, not working hours
A worked annual budget shows why 1,840 available hours can mean only 1,104 billable hours, and how utilization changes the required rate.
A 10% project discount can remove 40% of your profit
Follow a 20,000 quote through a requested discount, calculate the margin floor, and compare a price concession with an actual scope reduction.
A profitable project can still need cash before the next milestone
A 24,000 project earns 6,000 gross profit yet reaches a 2,400 funding gap. Follow the deposit, delivery costs and collections in order.
Cost rate versus billing rate: do not put the selling price into the cost model
An 80-hour example separates loaded delivery cost, client billing rate and target margin, and shows how an unnoticed second margin changes the quote.
A profitable bid can still be the wrong use of scarce capacity
Compare two illustrative projects with the same gross profit but different specialist-hour requirements, then check the constraints behind the ranking.
How many Monte Carlo iterations does a bid need?
A worked test: repeat one project simulation 200 times at four run counts and see how much P50, P80 and P95 move, and when more runs stop mattering.
Can you add task P80s? Why the sum overshoots
Eight task P80s add up to $58,551, but the project’s P80 is $51,765: that sum sits at P98.7. Why percentiles don’t add, and what correlation changes.
Pricing a change request on a fixed-price project
Two identical $7,200 changes: one barely moves the date, the other cuts on-time odds from 84% to 25%. A flowchart and the numbers for pricing a change.
How to price a late-delivery penalty into a quote
A $600-a-day delay clause added $3,063 to the quote that keeps 80% margin confidence. How to price the clause, and which negotiating lever moves it most.
Cone of uncertainty: how wide should a quote be?
A project’s final cost can land from a quarter to four times your first estimate. How the range narrows by stage, and what to quote at each one.
Pricing fixed-price work when AI makes you faster
A 35% speed-up on AI-assisted tasks is about a 25% cut in project cost. Cutting your price 35% drops the odds of a 25% margin from 80% to 28%.
Task dependencies: why adding durations gives the wrong deadline
A four-task example separates elapsed time, labor cost and shared resources before you estimate deadline confidence.
Project contingency: build a reserve without counting risk twice
Separate base uncertainty, discrete events and the pricing reserve with a worked $75,000 P80 project example.
On time and on budget: why two 80% chances are not one
A 1,000-scenario worked example shows how to count joint deadline and budget success, and why multiplying two headline probabilities can mislead.
Margin vs markup: price a fixed-price project correctly
A worked $60,000 cost example shows why a 25% markup gives a 20% margin, and how to apply your margin to a simulated cost percentile.
Client budget below your quote? Change the scope with numbers
A worked $80,000 budget example separates a discount from a scope change, with three options you can explain in a fixed-price negotiation.
Calibrate project estimates with completed jobs
Use a small forecast log to compare promised percentiles with actual outcomes, diagnose misses, and improve the next estimate without rewriting history.
PERT vs Monte Carlo: three-point estimates lie
PERT squeezes a whole range of outcomes into one average. Here is why that fails on a real 10-task project, and what to do instead.
P50 vs P80: choose the confidence behind your quote
P50 and P80 describe modeled cost coverage. A worked example separates margin confidence, loss probability and customer acceptance.
The fixed-price death spiral: one job eats three
An overrun costs more than the overrun: senior hours you cannot bill, deadlines you miss elsewhere, and the desperate next bid.
Deadline confidence: the number clients want
Clients do not want an earlier date. They want one they can plan around. Padding every task by 20% quietly costs you both — a worked example.
Your break-even is not a price — it is a clock
In fixed-price work, break-even moves every day the project runs. Same fee, nine extra days, and a healthy margin is a loss. Here is the math.
No field notes match. Clear your search or browse all resources.
Want the engine behind these numbers? BidVariance runs full Monte Carlo on your real project — one-time license, no account, local-first.