Put the math in one place
The most expensive spreadsheet error in a service business is not a typo in some internal tracker. It is the proposal that quotes one price and the contract that binds you to another. Both documents did their own arithmetic, in their own file, copied from the same source at different times. Eventually they disagree, and a client notices before you do.
I built an internal platform for a marketing agency that ended this problem the only way it actually ends: one engine computes every figure, and every document asks it.
The copy is the bug
The failure pattern is always the same. Sales configures a package in one tool. Someone pastes the numbers into a proposal template. Someone else pastes them into the contract. Then the package changes, one document gets updated, and the other one keeps the old number forever.
No amount of care fixes this, because care is not the missing ingredient. The architecture is wrong. Any workflow where the same fact is typed into two places will drift, guaranteed, on a long enough timeline.
If a number appears in two documents, it should be computed once and rendered twice. Anything else is a discrepancy on a delay timer.
One engine, many faces
The fix is structural and small. A single pricing engine holds the products, the rates, the discount rules, and the math. When a sales rep selects products, the engine computes the totals once. The client-ready proposal PDF and the signature-ready contract packet are just two renderings of that one result. They cannot disagree, in the same way two photographs of one person cannot have different faces.
This changed more than accuracy:
- Speed: a proposal and matching contract that took an afternoon of assembly became a few minutes of selection.
- Trust: review shrank from “check every number” to “check the choices.”
- Change tolerance: a rate update happens once, in the engine, and every future document is instantly right.
The pattern is bigger than pricing
Pricing is the sharpest example because the errors are legally binding, but the rule generalizes to any fact your business states in more than one place: service definitions, deliverable lists, campaign metrics repeated across report, dashboard, and invoice. Each of those wants a single source that computes or stores the fact, and dumb templates that render it.
When I audit a company’s operations, “where does this number come from” is the first question I ask about every document. When the answer is “someone copies it,” I have found the next system to build.
Count how many places your prices live today. If the answer is more than one, that is the leak. Get in touch if you want it plumbed.