Waymaker Tools

Give your pricing calculator a known answer before you trust the pretty chart

A quick test for builders turning a spreadsheet into a public planning tool.

By Ashley Kays Rabbitt · November 18, 2026

A calculator tells a founder to charge $75 per delivery. The chart is clear and the result is precise. What did it count as a delivery, and where did it put the time spent finding the customer? A calculator can perform flawless arithmetic on an incomplete definition.

Make a handwritten reference case. Suppose one order takes two delivery hours and one selling hour. The founder wants $30 for each working hour and spends $12 on materials. The minimum price under those assumptions is $102 before overhead, taxes or any margin cushion. Enter the same values in the prototype. If it returns $72, it probably counted only the two delivery hours.

Reference case for a minimum-price calculator
3 hoursdelivery plus selling
$12materials
$102at $30 per hour before overhead

Try the cases the slider hides

Set the number of expected orders to zero. A per-order allocation should explain why it needs a positive denominator. Leave the material cost blank. Decide whether blank means “unknown” or “zero” and make the screen say which. Enter a fractional number of hours, then check the rounding only at the final display.

MDN’s form validation guide explains how to constrain values and provide correction messages. The arithmetic still needs its own reference cases. MDN • Client-side form validation Put your three examples beside the formula so somebody else can retest after a design change.

Finally, ask a founder to explain the $102 result in their own words. If they think it predicts what a customer will pay, revise the label. A minimum under stated assumptions and a market-tested price are two different facts a single number should never blur.