The job
The quote goes out the same day. Not Saturday at the kitchen table.
The request comes in at ten in the morning, while you are on a roof or under a truck or three customers deep at the counter. It is still sitting there at six. So it gets priced after dinner, or Saturday, or it does not get priced at all.
By then somebody else has already answered. Not because their price was better. Because theirs arrived on Tuesday and yours arrived on Friday, and the customer had already stopped waiting.
Most quotes are not hard to price. They are hard to get to. The work is not the pricing, it is finding an hour that the day never gives you.
What a build looks like
It prices the request from your own pricebook while you are still on the job.
A request arrives however it arrives. An email, a form on your site, a text with a photo and a rough list. It reads what was asked for, matches each line to your pricing, applies the rules you actually use, and builds the quote on your own template. AI is what makes sense of a request written in the customer's words instead of your part numbers.
Then it waits for you. The quote sits ready with the original request beside it, and you send it, change a number first, or throw it out. From your phone, between jobs, in the time it takes to read it. Anything it could not price confidently is marked rather than guessed, so a thin request turns into a question for the customer instead of a number you have to honour.
It uses your pricing, not a market average. If your numbers live in a spreadsheet, that is where it reads them. Nothing gets migrated and you do not start maintaining a second copy of your prices.
What it does not do
It does not decide what to charge.
It applies the pricing you already use. It does not set margin, it will not decide that this customer gets a break, and it does not quote a job it cannot price from the information in front of it. Those are judgement calls and they stay yours. What it removes is the hour of looking things up.
It also will not make a slow quote fast if the hold-up is somewhere else. If quotes wait on a supplier price you do not have yet, that is the real problem, and a faster document does not fix it. That is the kind of thing a twenty-minute call turns up before anybody builds anything.
Questions
What you are probably wondering.
Does it send the quote to the customer by itself?
No. It hands you a priced quote and stops there. What it buys you is time of day: a request that lands at ten is ready while the customer is still thinking about it, rather than after dinner once they have stopped.
Our pricing is not in a system. It is in a spreadsheet and in my head.
The spreadsheet is fine and it is usually where I start. The part in your head is the useful conversation: the rules you apply without thinking about them are what turn a list of prices into a quote, and writing those down is most of the work.
What about the jobs that need a site visit before anyone can price them?
Those still need the visit. The difference is they get separated on arrival, so the simple ones are gone by lunchtime and the rest become a scheduled appointment rather than a pile you work through on Saturday.
Free 20-minute call
Twenty minutes. No pitch.
Tell me how a quote request reaches you and what happens to it next. You'll leave with what it would take to automate it, what it would cost, and whether it's worth doing at all. If it isn't, I'll say so on the call.
Other jobs I build for: orders entered without retyping · leads answered and followed up · showing up when customers ask ChatGPT · everything else