---
title: "Discussion on \"Your Estimates Aren't Random, They're Biased: Measure It With Your Last Ten Jobs\" | Hashnode"
description: "Discussion on \"Your Estimates Aren't Random, They're Biased: Measure It With Your Last Ten Jobs\". Disclosure: I help market BidVariance and the free estimate tools linked below, and this post was drafted with AI assistance. The worked example uses made-up numbers, labelled as such, so you can chec"
url: "https://hashnode.com/posts/your-estimates-aren-t-random-they-re-biased-measure-it-with-your-last-ten-jobs/6adb478bf259ab58d4be842a"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Your Estimates Aren't Random, They're Biased: Measure It With Your Last Ten Jobs](https://yunusemrevurgun.hashnode.dev/your-estimates-aren-t-random-they-re-biased-measure-it-with-your-last-ten-jobs?utm_source=hashnode&utm_medium=feed)

Disclosure: I help market BidVariance and the free estimate tools linked below, and this post was drafted with AI assistance. The worked example uses made-up numbers, labelled as such, so you can chec

Oct 23 · 7 min read · yunusemrevurgun.hashnode.dev  
Read the article

-   [#freelancing](https://hashnode.com/tag/freelancing)
-   [#project-management](https://hashnode.com/tag/project-management)
-   [#estimation](https://hashnode.com/tag/estimation)
-   [#productivity](https://hashnode.com/tag/productivity)
-   [#startups](https://hashnode.com/tag/startups)

## Written by

[Yunus Emre Vurgun](https://hashnode.com/@yunusemrevurgun)

@yunusemrevurgun

  
[View profile](https://hashnode.com/@yunusemrevurgun)

Writing about AI agents, hardware, and practical software.

## Responses 1

Markdown supported · ⌘↵ to post

[Ascendra Ventures](https://hashnode.com/@ascendra-ventures)

[Oct 24](https://hashnode.com/posts/your-estimates-aren-t-random-they-re-biased-measure-it-with-your-last-ten-jobs/6adb478bf259ab58d4be842a/comment/6adc1a9ca0df6fe90b34aa05)

Logging the last ten jobs as estimate to actual ratios is a simple habit that most teams never start, and the numbers make the case better than any argument. A median of 1.225 with ninety percent of jobs overrunning is not bad luck. It is a bias you can correct.

The point that the gap between P50 and P80 is the contingency on fixed price work is the part I would underline. It turns a guess into a number you can explain to a client. Separating change requests from estimating error matters just as much, because mixing them hides both problems.

On fixed price client work we pair this with tighter scope. Each piece is one defined problem with written acceptance criteria, so a change request is easy to see and price on its own. That keeps the history clean enough for the ratios to mean something.

Do you track the ratio per type of job, or does ten jobs become too small a sample once you split them?
