Price the Wait Before You Price the Project

When a business looks at a software or automation project, the conversation almost always starts with the price of the fix. It rarely starts with the other number: what it costs to do nothing for another month. Waiting never sends an invoice, but it is not free. It gets paid in staff hours, in money that arrives late or not at all, and in risks that grow while nobody is looking.

We cannot tell you what waiting costs your business. That figure only exists in your own data. What we can do is show you where to look and how to do the arithmetic, so that when a quote lands on your desk you have two numbers side by side instead of one.

1. Hours spent on work that repeats

This is the easiest cost to measure and the one most often ignored. Look for work someone does by hand, again and again:

• ✓copying the same data between two systems;
• ✓answering the same questions by phone or email every day;
• ✓chasing documents, signatures or payments manually;
• ✓rebuilding a report every week from the same sources.

The arithmetic: hours per month on that task × the loaded cost of an hour. The loaded cost is the full monthly cost of the role to the business (salary plus employer taxes and benefits), divided by the hours actually worked that month. Your accountant has the first number. For the second, ask the person who does the task to note their time for two weeks. Two weeks of notes beat any estimate.

2. Money that arrives late, or never

A quote that goes out three days after the request loses some deals to whoever answered the same day. A call nobody picks up after hours is a customer who rings the next business on the list. An invoice sent late gets paid late.

You do not need a benchmark for this. Your CRM, your phone system and your accounting software already hold the numbers: how long a quote takes today, how many calls go unanswered, how many days between work done and invoice sent. Write down what you see. Do not add a hoped-for improvement percentage. The difference can only be measured after a change is running, against the same period before it.

3. Costs that have a date written on them

Some delays have a fixed price. A contract with a penalty clause. A compliance deadline with a stated fine. A supplier's notice that prices go up on the first of next month. A licence that renews automatically unless you cancel by a certain day.

When a delay has a written price, it stops being an estimate. It is that amount, on that date. Put it in the table exactly as written, and let whoever reads contracts for you confirm what applies.

4. Problems that grow while they wait

Some problems cost the same this month and next. Others compound: software or hardware that no longer receives security updates, a key process that only one person knows how to run, data held by a vendor in a format you cannot easily take with you. There is no honest monthly number for these. There is a question instead: what happens on the day this turns into an incident, and how long would the business stand still?

The table to fill in

What you measure	Where the number comes from	Per month
Repeated hours × loaded hourly cost	The person doing it (2 weeks of notes) and your accountant	...
Revenue delayed or lost	CRM, phone logs, invoicing dates	...
Costs with a written date	The contract, notice or regulation itself	...
Problems that grow	Your list of systems, key people and vendor-held data	no number, a date

Putting the two numbers side by side

Add the first three rows. That is the monthly cost of waiting. Multiply it by the number of months until the problem would be solved if you do nothing now, for example until next year's budget. Then set the price of the fix next to it.

If the fix costs less than waiting over the same period, waiting is the expensive option. If it costs more, you now have a written reason to wait, and that is a good outcome too. Not every project should start this quarter.

What we will not do

We will not promise you savings, and we will not put our numbers where yours belong. A cost-of-waiting figure built by a vendor, from the vendor's assumptions, does not help you decide anything. When we write a proposal, we run the calculation above on the figures you give us, with the formula in plain view so you can check it and reuse it without us. The price itself is fixed, after a written scope.