A Calculator, Not a Form: What Coffee Abacus Taught Me About Software People Actually Use

Coffee Abacus is the least businesslike thing I've shipped: a free calculator that tells you how much water to pour over how much coffee. But it taught me more about why employees use some software and quietly abandon the rest than any internal tool I've built. Here's the transferable part.

The form version would have been fine, and forgotten

The obvious build was a form: four inputs, a calculate button, an answer. Twenty minutes of work. It would have been correct, and nobody would have used it twice.

Instead, the four values (coffee, water, ratio, cup volume) are linked. Change any one and the others move instantly, following rules the app states plainly: your ratio is sacred; the math accounts for water your grounds absorb. On a phone you don't even type: you press a number and drag sideways, and it clicks up and down like a dial, with a tiny vibration on each tick.

The difference isn't decoration. A form asks you to already know the answer's shape. An instrument lets you explore ("what if I only have 20 grams of coffee?") and see consequences immediately. People play with instruments. Nobody plays with forms.

Why this matters for the software your business buys

Every business tool faces the same fork. The order-entry screen, the quoting tool, the scheduling board: each can be a form that demands data, or an instrument that responds to it. The failure mode of internal software is rarely "it's broken." It's "the team finds it annoying, so the real process lives in a spreadsheet and the tool gets updated on Fridays, badly."

Three specifics from the calculator that translate directly:

Show which number is the input and which are derived. In Coffee Abacus, the field you touched is outlined and labeled "user input"; the rest visibly recalculate. In a quoting tool, that's the difference between trusting the total and re-checking it by hand. Ambiguity about where a number came from is where trust in software goes to die.

Make the common case gestural, the rare case typable. Most adjustments are small: a little more, a little less. Dragging beats typing for those. But the keypad is one tap away for exact entries. Business software usually optimizes the rare case and taxes the common one.

Encode the domain rule, then say it out loud. "Ratio never silently recalculates" is a one-line contract. Users learn it in seconds and then predict the tool's behavior forever. Every internal tool has equivalent rules (invoices never change after posting) that are usually discoverable only by being surprised.

The unglamorous half of the lesson

The other thing Coffee Abacus taught me: a tool this small still deserved 32 test files, analytics on every interaction, and structured data for search. Not because a coffee calculator is critical infrastructure, but because shipping discipline is a habit, and habits don't switch off for small projects. The same hands build your customer portal the same way they built the toy. That's precisely why I show clients the toy.

When someone asks whether an internal tool is "worth doing properly," the answer is that the properly-done version is the only one that gets used, and software nobody uses is the most expensive kind, whatever it cost. If your team is working around a form somewhere, tell me about it. The fix is often less about features and more about feel, and feel is buildable. It's what custom software is for.