Sanity check aloud
The costliest mistake in case maths is not a wrong digit but a wrong zero: £5.2bn instead of £5.2m. A five-second ballpark, with every factor rounded to one significant figure, catches it before you say it.
Free, no sign-up. Type each answer and get it checked instantly, with the working.
The rule
Round each factor to one significant figure and multiply. If your answer is out by ×10 or ×1,000, a zero slipped. Then ask whether the number makes sense in the real world.
How it works
- Round each input to one digit: 60k customers, 3 orders a week, £29 → £30.
- Multiply the rounded numbers: 60k × 3 × £30 = £5.4m a week.
- Compare with your answer. Same order of magnitude? Good. Out by ×10 or ×1,000? Recount the zeros.
- Check against reality, out loud: “£270m a year for one grocer’s app feels high — let me check the customer number.”
A few anchors to compare against (rounded):
| Anchor | About |
|---|---|
| UK population | 68m |
| UK households | 28m |
| US population | 340m |
| Working days in a year | 250 |
| Hours in a year | 8,760 |
Worked examples
A teammate says 60k customers × 3 orders a week × £29 = £5.22bn a week.
- Ballpark: 60k × 3 × £30 ≈ £5.4m
- £5.22bn is 1,000× too high
- Right figure: £5.22m a week
Answer: £5.22m a week
1.2m transactions a day × £0.04 fee = £48 a day?
- Ballpark: 1m × £0.04 = £40k
- £48 is 1,000× too low
- Right figure: £48k
Answer: £48k a day
80 engineers × £70k = £5.6m a year?
- Ballpark: 80 × £70k = £5.6m
- Same order of magnitude: the claim holds
Answer: £5.6m (holds)
£4bn revenue × 12% margin = £480bn?
- Ballpark: £4bn × 10% = £400m
- £480bn is 1,000× too high
- Right figure: £480m
Answer: £480m
Common mistakes
- Checking only the digits. 5.22 is right in both £5.22m and £5.22bn; the zeros are what you are checking.
- Checking silently. Interviewers reward a visible check, so say the ballpark aloud.
- Over-engineering the ballpark. Within a factor of two is plenty; you are hunting for factors of ten.
Where it comes up
Before every number you say out loud, and especially after a market sizing chain. A good habit is to ballpark first, then compute exactly, then compare.
Try it yourself
Work each one out before you open the answer.
-
A teammate says: 500k users × 8% paying × £240 a year = £9.6m a year. What is the right figure? If it holds, type it back.
Show the answer
Answer: £9.6m
- Ballpark: 500k × 8% × £200 ≈ £8m
- £9.6m is in that range: the claim holds
- Exact: 500k × 8% = 40k; × £240 = £9.6m
-
A teammate says: 4m transactions a day × £0.3 fee = £1,200 a day. What is the right figure? If it holds, type it back.
Show the answer
Answer: £1.2m
- Ballpark: 4m × £0.3 ≈ £1.2m
- £1,200 is 1,000× too low: a slipped zero
- Exact: 4m × £0.3 = £1.2m
-
A teammate says: 2m users × 15% paying × £240 a year = £72m a year. What is the right figure? If it holds, type it back.
Show the answer
Answer: £72m
- Ballpark: 2m × 15% × £200 ≈ £60m
- £72m is in that range: the claim holds
- Exact: 2m × 15% = 300k; × £240 = £72m
-
A teammate says: 40 engineers × £110k each = £4.4bn a year. What is the right figure? If it holds, type it back.
Show the answer
Answer: £4.4m
- Ballpark: 40 × £100k ≈ £4m
- £4.4bn is 1,000× too high: a slipped zero
- Exact: 40 × £110k = £4.4m
-
A teammate says: 2m users × 8% paying × £36 a year = £5.76m a year. What is the right figure? If it holds, type it back.
Show the answer
Answer: £5.76m
- Ballpark: 2m × 8% × £40 ≈ £6.4m
- £5.76m is in that range: the claim holds
- Exact: 2m × 8% = 160k; × £36 = £5.76m
Practise with fresh numbers
The trainer makes new sanity check aloud questions every time, checks your typed answer and shows the working when you miss.
Questions
How precise does the ballpark need to be?
Not very. You only need to tell £5m from £50m or £5bn, so one significant figure per input is enough.
What if the ballpark and my answer disagree?
Recount the zeros first (it is usually a k vs m slip), then recheck the setup. Say what you are doing; it reads as rigour, not as a mistake.