Operations
Ask an owner why quotations go out slowly and the answer is usually some version of "we've been busy." That is true and it is not the reason. Busy businesses still send invoices on time, because an invoice has a fixed shape and one obvious owner.
A quotation has neither. It stalls in specific, repeatable places, and those places are worth naming precisely — because only two of the three are software problems, and spending money on the wrong one is how a business ends up with an expensive tool that changed nothing.
An enquiry arrives as a WhatsApp message, a form submission, a phone call written on whatever was nearest, or a forwarded email with three people in the thread. Before anyone can price anything, somebody has to turn that into a statement of what is actually being asked for.
That conversion is invisible work. It is on nobody's task list, nobody schedules it, and it usually happens twice — once roughly, by whoever received the enquiry, then again properly by whoever prices it. The gap between enquiry received and enquiry understood is often longer than the pricing itself.
This one is largely a software problem. Not because software can interpret a vague message, but because a structured intake — the same fields, every time, captured at first contact — removes the second pass. The questions that always get asked eventually get asked immediately instead.
Pricing a job means assembling rates, past jobs, supplier costs and whatever adjustments the business has learned to make. In most service businesses those sit across a spreadsheet, a previous quote someone is copying from, a supplier's PDF, and one person's memory.
The delay is not arithmetic. It is retrieval, plus the verification that follows it — is this rate still current? — and the small negotiation with yourself about whether it is worth checking.
This is the clearest software problem of the three, and the most common reason a studio like ours gets a call. A quotation tool that holds current rates, carries forward the structure of past jobs and calculates the same way every time removes both the retrieval and the doubt. MRN Quoter, one of the systems on our work page, exists for exactly this shape of problem.
This is the delay owners underestimate most, and it is not a software problem at all.
The quote is priced. It sits in a draft folder because the owner wants to check it before it goes out, and the owner is on site. A day passes. Then two. The customer, who asked three suppliers, has already received two other quotes.
No tool fixes this, because the bottleneck is a decision about authority, not a missing feature. Automating around it usually makes it worse: approvals become faster to request and no faster to grant, so the queue just becomes more visible.
What addresses it is a rule the business sets in advance about which quotes go out without review at all. Under a certain value, in a familiar job type, using standard rates — send it. Reserve review for the jobs where the owner's judgement genuinely adds something. That is a management change, and it costs nothing.
If quotes are slow because the numbers are scattered, software will help and the change will be immediate.
If they are slow because enquiries arrive unstructured, software will help, but only if someone will enforce the structure at the point of contact.
If they are slow because everything waits for one person, buy nothing yet. Change the approval rule, watch it for a month, and see what is still broken. Whatever survives that is the thing worth scoping.
If a recurring administrative task is costing your business more time than it should, we offer a 20-minute workflow conversation — one task, and an honest answer about whether automation is appropriate. Get in touch.
More from the blog
Buying Software
Five things decide what a custom system costs, and a feature list is not one of them. What scope, integrations, data migration, approvals and support each do to a quote — and what you can do to lower it honestly.
Buying Software
We build custom software, and most businesses that ask us about it should buy something existing instead. Here is the line between the two, and the costs on both sides that get left out of the comparison.