Nobody Remembers How Bad It Was

We built an application for a client that took a daily two-hour job down to about fifteen minutes.

Six weeks after go-live, their operations manager told me it was working well. Then she said the old way "wasn't that bad."

The old way involved three spreadsheets, a shared mailbox and a printer.

She was not wrong to forget. That is what happens when a tool works — the pain it removed stops being available to memory.

But it meant that when we came back to discuss phase two, neither of us had a single number to point at.

So we stopped doing it that way.

Custom Software Is The Hardest Thing To Buy

There is no vendor comparison page. No peer to call. No free trial.

A business is asked to spend real money against a description of something that does not exist yet, and every objection raised is the same objection underneath.

How do I know this will pay for itself?

For years our answer was some version of "look at what you are spending on the manual process." Which is a fine answer and completely unprovable, because nobody had ever measured the manual process.

Day Zero: Write Down What Today Costs

Before any part of a new system goes live, we spend half a day with the people who actually do the work and record the current state.

Minutes per transaction, measured rather than estimated.

How many times the same piece of data gets typed into a second system.

How long the whole process takes start to finish.

How often work comes back wrong, and what fixing it costs.

Who touches it, and what their time is worth.

The client signs that page. Not as a contract — as a shared record of what was true before, while it is still true.

Then we measure the same things again on day 100.

Four Things We Keep Finding

The expensive problem is never the one you pointed at. It is the small, quiet one nobody complains about, because it only takes ninety seconds. Forty times a day. The loud problem is usually the one that already has a workaround.

Adoption is binary and it settles inside three weeks. If the old spreadsheet is still reachable, people keep using the old spreadsheet. Switching it off is not a technical step. It is the whole project.

Reclaimed hours do not show up in payroll. Nobody gets sent home early. They show up as work that used to sit in a pile and never get done — the follow-ups, the reconciliations, the calls nobody had time to make.

The biggest number is usually a hire that does not happen. One avoided coordinator is roughly $78,000 fully loaded. That is most of a build, in year one, before you count a single reclaimed hour.

What 100 Days Does And Does Not Prove

A hundred days does not mean the system has paid for itself. On a larger build it usually has not.

What you get is a measured result and a payback date on a real calendar, instead of a feeling.

That distinction matters more than it sounds. A feeling cannot be taken to a board. A feeling cannot be compared against the next three things competing for the same budget. A measured number can.

And we publish that number whether it flatters us or not.

No guarantee attached, nothing clever in the methodology. We measure it and report what it says. Which should not be unusual, and is.

Why Anyone Should Care

Most software spending is justified once, at purchase, and never examined again.

Businesses end up carrying tools nobody can defend, because the person who bought them left, and nobody wants to be the one who admits it was a mistake.

Measuring on a fixed date breaks that pattern. It creates one moment where the honest question gets asked while the answer is still cheap to act on.

Sometimes the answer is that the build returned more than anyone expected. Sometimes it is that adoption stalled in week two and the problem is process, not software.

Both of those are worth knowing. Only one of them is comfortable.

Try It Without Us

The Day Zero worksheet is not proprietary and it is not complicated. Half a day with the people doing the work, five questions, one signed page.

You do not need us to run it, and plenty of businesses will not. It still works.

If you want a copy of the worksheet, or you are weighing a custom build and want to know how to prove it was worth it, Methodology IT can walk you through the framework.

Learn more at methodologyit.tech or call 800-270-0016.