← Lessons

quiz vs the machine

Silver1050

System Design

Back of the Envelope Estimation

Turning a vague feature into rough numbers in a few minutes so design choices have a footing.

4 min read · intro · beat Silver to climb

Why estimate at all

Back of the envelope estimation is the habit of producing rough numbers fast, before any code or hardware exists. The goal is not precision but order of magnitude: is this thousands or billions, megabytes or petabytes.

How it works

  • Start from a known driver, like daily active users or requests.
  • Multiply through to the quantity you care about, such as storage or traffic.
  • Round aggressively to powers of ten so the arithmetic stays in your head.

Useful anchors

  • A day has about 86400 seconds, often rounded to 100000.
  • One million seconds is roughly 12 days.
  • A kilobyte is about a thousand bytes, a megabyte a million, a gigabyte a billion.

These anchors let you chain multiplications without a calculator.

A good estimate tells you which design dimension dominates, so you can spend effort where it matters and skip what is clearly cheap.

Key idea

Estimation trades exactness for speed, giving you an order of magnitude that steers design before you commit resources.

Check yourself

Answer to earn rating on the learn ladder.

1. What is the main goal of a back of the envelope estimate?

2. Roughly how many seconds are in a day, for quick math?