> For the full site index see https://www.fenwickautomation.com/llms.txt > Every page has a Markdown version at the same URL with .md appended. # How do you automate a quote without getting the price wrong? You automate the reading, the chasing and the drafting. The estimator still prices the job and still presses send. Where the hours actually go. 16 September 2026 · Updated 1 October 2026 · 5 minute read You automate the reading, the chasing and the drafting, and you leave the pricing decision with the estimator. A system drafts, a person decides. Get that the wrong way round and you can win a job under cost and not find out for months. ## How do you automate a quote without getting the price wrong? By being clear about which part of quoting is a rule and which part is judgement. Applying your rate card to a measured quantity is a rule. It can be complicated, it can have a long list of conditions in it, and it is still a rule, because your team would all agree on the answer. Deciding that this client will walk above a certain figure, or that you want this job badly enough to take it thin, is judgement. Rules can be built. Judgement stays with the estimator. ## Where the hours go on one enquiry An enquiry arrives as an email, sometimes after a phone call, sometimes with a drawing attached and sometimes with a photograph of a handwritten note. Somebody reads it and works out what is actually being asked for. They copy the details into a spreadsheet or the job system by hand. They price it against the rate card, past jobs, and what they know about that client. They write it up in the format that client expects. They chase what the enquiry did not include. They send it, and then they chase the answer. One of those steps is the job. The rest is handling. For a sense of scale, the 1,000 UK small business owners in the American Express SME Barometer reckoned admin and finance tasks take them about 11 hours a week. American Express carried out the survey with Small Business Saturday UK, and [Retail Times reported it in July 2026](https://retailtimes.co.uk/amex-sme-barometer-small-business-owners-spend-nearly-twice-the-time-on-admin-than-growing-their-business/). It covers small businesses of every kind, so it is not a figure for estimators alone. For your own figure, time the steps in the list above that are not pricing. ## What the system does A build on [the Estimation route](https://www.fenwickautomation.com/services/estimation.md) reads the enquiry and its attachments. It pulls out the scope, the site, the dates and the client, and opens the job record so nobody retypes it. It compares what arrived against a list you wrote, names what is missing, and drafts the chaser for you to check and send. It prices the standard lines against your own rate card and your own rules. It drafts the quote in the format that client expects, with the assumptions written out. Then it stops, and an estimator opens it. The estimator prices the awkward parts, corrects anything the draft has misread, and sends it. Nothing reaches a client without that. What has gone is the typing, the formatting and most of the chasing. What is left is the part you are actually paid for. ## Why the pricing decision does not move Three reasons, and none of them go away as the system improves. The margin lives in the exceptions. Access, programme, ground conditions, the client’s payment record, how busy you are next month. None of that is in a rate card, and most of it is not written down anywhere. Your own estimators disagree. Give the same enquiry to two of them and you will get two prices, both defensible. A system trained on both will average them, and an averaged price is nobody’s price. Rate cards go stale. The week after a card is written it is already slightly wrong, and a system pricing unsupervised will be confidently wrong in a way nobody notices for months. A person looking at a draft notices in a second, because they bought the material last week. Nothing is fully automated where a mistake costs money or safety. Pricing is the clearest example of that rule there is. ## What actually improves Turnaround, mostly. The enquiry that sat until Thursday because nobody had a clear hour can go back on Tuesday, with an estimator’s eyes on it. If your win rate depends on being first back with something sensible, that is worth more than the hours saved, and it is easier to measure than you would think: look at the date the enquiry arrived and the date the quote went out, across your recent quotes. The second thing that improves is consistency. Every quote carries the same assumptions, written in the same place, so when a client argues about what was included there is something to point at. ## What will go wrong Your rate card is in someone’s head, or in several files that disagree. Finding out which is the real one is the first job, and it is not a quick one. Your past quotes may not be in a shape anything can learn your rules from. That is why the paid audit looks at your real documents and your real data first. The quote comes from the audit: a fixed price for one route, with three options that cut scope rather than corners. The first version will misread the enquiries that arrive as a photograph of a note on a van dashboard. It will also be too literal about scope where your estimator reads between the lines. Both get fixed during the parallel run, while the old way is still running. And somebody’s spreadsheet is load-bearing. ## Before you build anything Count two things: how many enquiries you get a month, and how long one quote takes from arrival to sending, including the waiting. If quoting is not near the top of your paperwork costs, the tests in [how to pick the one document to automate first](https://www.fenwickautomation.com/writing/which-document-to-automate-first.md) will probably point you at the intake check instead. Bring both numbers to the free [10-minute call](https://www.fenwickautomation.com/contact.md). I will tell you whether it fits and give you a rough estimate, a range for the first route. The paid audit then gives you the annual cost of the paperwork in your own figures, and what to build first. **Blake Fenwick**, founder of Fenwick Automation Some of the systems we've built, running right now. [More about Blake Fenwick and how we work](https://www.fenwickautomation.com/about.md). [Blake Fenwick on LinkedIn](https://www.linkedin.com/in/blake-fenwick-a5ba95433/) ## Related - [Estimation: the route this piece is about](https://www.fenwickautomation.com/services/estimation.md) - [How to work out what paperwork costs your business a year](https://www.fenwickautomation.com/writing/what-paperwork-costs-your-business-a-year.md) - [How to pick the one document to automate first](https://www.fenwickautomation.com/writing/which-document-to-automate-first.md) Last updated: 1 October 2026