The problem
Enquiries arrive by email, through the website form, by phone and by word of mouth. Each one gets read by somebody who then has to work out whether it is worth the time. Is it the kind of work you do? Is it somewhere you go? Is it a size you take on? Is the person asking the person who decides? Have they told you enough to say anything useful back?
Most of that is worked out by the same few people, usually the ones who also price the work and run the jobs. So the enquiry waits for them. When they get to it, the good ones have been waiting as long as the bad ones, and the bad ones have had the same amount of attention. The reply asking for the missing details goes out late, if at all.
The cost is the time spent on enquiries that were never going to become jobs, and the good enquiries that went cold while they waited in the same queue.
Every enquiry is checked against the same written rules the moment it arrives, so the ones that fit are in front of a person the same day and the ones that do not are parked with a reason.
The reply asking for what is missing is drafted before a person opens the enquiry, so the client is asked the right questions once, not again and again over a week.
The person who decides sees the enquiries that need their judgement, with the routine checks already done, instead of reading everything from the top.
What it does
Every enquiry is checked against your rules for the work you want, as it arrives. The ones that fit reach a person the same day. The rest are parked, with the reason, for a person to review.
The build reads each enquiry as it arrives and checks it against your rules for the work you want: the trades and job types you take, the areas you cover, the minimum size, the kinds of client you have decided not to work for, whatever you tell it. It scores nothing and guesses nothing. Each rule either passes, fails, or cannot be judged because the enquiry does not say.
An enquiry that passes goes to the right person with the checks shown. One that fails is parked with the rule it failed, and a polite reply is drafted for a person to send. One that cannot be judged gets a drafted reply asking for the specific things the rules need, and the enquiry waits for the answer rather than for a person.
Who it suits
A business getting more enquiries than it can read properly. Some are the wrong kind of work, the wrong place or the wrong size. A few people decide on all of them. It suits teams that already know, in conversation, what a good enquiry looks like.
It suits less well where almost every enquiry is worth a conversation, or where the decision is mostly about a relationship rather than the job. The build can still take the routine checks off the desk in those cases, but the saving is smaller.
What it needs from you
Your rules for what you take and what you turn down, written down. Getting them out of people's heads is the slow part. Your recent enquiries, including the ones you ignored, because those show the rules better than the ones you won. And the questions you always end up asking a client before you can say anything useful.
The rules will conflict. One person takes small jobs from a good client and another turns them all away, and both are following the policy as they understand it. The build has to be given one answer. Your enquiry history has gaps: many of the phone enquiries were never written down anywhere, so the first weeks of the parallel run are also the first weeks you have a full record.
Signature to live: from 4 weeks, depending on the size of the job.
What it does not do
It does not reply to anyone on its own. Every reply it drafts waits for a person to read and send. It does not decide anything the rules do not cover: an enquiry the rules cannot judge goes to a person, not to a guess. It does not price, and it does not book anything.
It does not know about the client who is worth an exception, or the job that is out of area but next to another job you are already doing. A person still reads the parked list, because the first version will park something you would have taken, and only the person who would have taken it will notice. The parallel run exists to catch exactly that before anything is turned off.
This is a Checks build. It checks an enquiry against your rules and sorts it, with the reply drafted for a person. It does not write the quote and it does not assemble the job.
Checks One route, signature to live: from 4 weeks, depending on the size of the job and the state of your data. We'll tell you on the audit.
Where it sits in the process
Lead qualification is one route, built on its own. The free 10-minute call tells you whether it fits and gives you a rough estimate: a range for the first route, not a quote. The paid audit looks at your real documents and your real data, works out what the work costs you a year in your own figures, and writes down what to build first. The fixed price for the build comes from the audit, with three options that cut scope rather than corners. Then the data check, the build, the parallel run, go-live and training, and monthly running. All nine stages are on the About page.