A small calculator UX problem: whose numbers are you showing?

A calculator can get every multiplication right and still give someone a misleading answer. The awkward part is often the meaning of the inputs.

A residential cleaning estimate is a useful example. There are at least three things on the screen that look like “the price”: the business’s costs, the selling price, and the profit left after costs. Mixing them up makes a tidy interface much less useful.

Hours need a unit

Imagine two cleaners spending two hours at a property. A field labelled Hours could mean two hours or four. Both answers sound reasonable until you ask what the calculation expects.

Total labor hours is clearer. A short example next to the field is even better: 2 cleaners × 2 hours = 4 labor hours. You should not need a help article to discover the unit.

Room counts have a similar problem. If someone adds three bedrooms, does the app estimate the cleaning time, or just record the scope? Either approach can work. The interface needs to say which one it uses.

Margin is not markup

For a cost C and target margin m, expressed as a decimal, the selling price is:

price = C / (1 - m)

That is different from multiplying costs by 1 + m, which calculates a markup. With $100 in costs and a 20% target margin, the selling price is $125. A $120 selling price leaves a margin of about 16.7%. These are example inputs, not recommended service prices.

A field called Profit % makes the user guess which calculation is happening. A precise label and a visible explanation are more useful than an extra decimal place.

The PDF has a different audience

The person preparing the estimate needs cost and margin details. Their customer needs the agreed services, exclusions and selling price. Exporting the whole workspace gives both audiences the wrong document.

Quotewise is the concrete example I’m sharing here: a free house-cleaning estimate tool with PDF export and no signup. It uses entered labor hours, costs and a target margin, and keeps internal costs and private notes out of customer exports.

For anyone working on a small business calculator, these are useful review questions:

• Does each quantity say what it measures?
• Can users tell an assumption from a value they entered?
• Are margin and markup named correctly?
• Does the export contain only what its reader needs?

None of this requires a complicated interface. It does require deciding what each number means before polishing how it looks.