Quotes — an enquiry becomes a priced offer
The role that turns an enquiry into a priced offer on your letterhead, with the assumptions listed at the bottom, sitting in your drafts folder waiting for you to press send.
It never sends. An offer leaving the building is a commercial decision and it stays yours — which is also why this role is safe to try.
Monday to Friday,
in specifics rather than verbs.
Invented and generic on purpose — there are no clients yet, so nothing below describes a real business. What it does describe accurately is what the role would do and where it would stop.
An enquiry describes a job in a paragraph. The quantities, the dates and the address are pulled out and listed back, so you can see what it understood before you read the price.
It prices each line against your list. One line has no price on the list; it is left blank and marked, rather than estimated.
The offer is in your drafts in your usual wording, with the assumptions at the bottom: quantities assumed, access assumed, timing assumed.
You fill in the blank line, delete one assumption that does not apply, and send it. Four minutes.
The customer replies asking for a variation. A revised draft appears with only the changed lines marked.
Three offers have had no reply for a fortnight. They are listed for you — chasing is your call, and the draft is written either way.
What you actually do,
and how long each part takes.
"Easy onboarding" is not a claim anybody believes. This is the list, with a duration on every line, and the longest line is the fortnight where it does nothing.
Send your price list, however it exists — a spreadsheet, a PDF, a page of your website.
Send one offer you have already sent that you were happy with. That is the tone it copies.
Two weeks of watching: it drafts against real enquiries and shows you what it would have written.
Read those drafts against what you actually sent. The differences are the rules nobody had written down.
It drafts into your folder from then on. It still never sends.
Three ways this role fails,
and what happens then.
It will be wrong. The design assumption is not that it will not be — it is that when it is, the item stops, says so and waits, and that you find out from the system rather than from a customer.
It prices a line wrong.
You catch it, because the offer is in your drafts and not in the customer's inbox. That is the entire design of the role.
It misreads the quantity.
The quantities are listed at the top of the draft in the role's own words, above the price, so the misreading is visible before the number is.
The enquiry is too vague to price.
It writes the questions instead of the offer. A list of three good questions is a better reply to a vague enquiry than a wrong number.
It never sends the offer. An offer leaves the building when you say it does.
What this role does not touch.
A role that claims to take everything is a role nobody with a real business believes. Naming what stays with you is what makes the rest of the page worth reading.
Three questions
this one gets and the others do not.
Our pricing is not really a list.
Then say so on the call, because that decides whether this role is worth buying. If pricing is genuinely a judgement every time, it will spend its life stopping and asking, and we will tell you not to buy it rather than sell you a role that generates work.
Can it use our offer template?
It writes into your document, with your letterhead and your wording. The template is one of the two things it needs at setup and it is copied rather than approximated.
What about follow-ups?
It lists what has gone quiet and drafts the follow-up. Whether a customer gets chased, and how hard, is a relationship decision and stays with you.
Watches the inbox so you can stop refreshing it.
Issues them, chases the quiet ones, matches the payments.
Reads what arrives as a PDF and files it where it belongs.
Bookings, reminders, cancellations, and who did not turn up.
One message a week: what came in, what went out, what needs you.