Inside an automation discovery call: what good looks like
Every automation project starts with a conversation, and the quality of that conversation predicts the quality of everything that follows. Here is what a serious discovery call covers, what should come out of it, and the warning signs that you are talking to the wrong people.
What a discovery call is actually for
A discovery call is not a sales pitch with a calendar invite. Its job is to work out, honestly, whether automation would create enough value in your specific business to justify the cost of installing it. That is a factual question, not a persuasion exercise, and it can only be answered by looking at how your firm actually runs: how enquiries arrive, how quotes get produced, how jobs get scheduled, how invoices go out, and where the hours disappear.
At AGMM the discovery call runs for sixty minutes. That length is deliberate. Thirty minutes is enough to trade pleasantries and generalities. Sixty minutes is enough to walk through a real process end to end, put rough numbers on it, and decide whether a deeper analysis is worth anyone's time. If a provider wants to sell you something after fifteen minutes, they are selling a product, not solving your problem.
The questions a good consultant asks
You can judge the person on the other end of the call by their questions. Vague questions produce vague projects. On a good call you should hear things like:
- Walk me through the last enquiry you received. What happened to it, step by step, and how long did each step take?
- How many quotes did you send last month, and how many did you win? Who produced them, and how many hours did that take?
- Where do jobs stall? Waiting on suppliers, waiting on sign off, waiting on you?
- What software do you already pay for, and which parts of it does the team actually use?
- If you had one extra working day per week back, what would you do with it?
Notice what is missing: nobody should be asking you to pick features off a menu. The point is to find the two or three processes where automation would pay for itself fastest, which is a smaller and more useful list than everything that could theoretically be automated. If you want a sense of how firms usually sequence this, see where to start automating a trade business.
What happens in the three to seven days afterwards
The call itself proves nothing. What matters is the analysis that follows. At AGMM the discovery call feeds a three to seven day analysis, and the output is a quantified business case, not a brochure. That document should put numbers against four things:
If the numbers do not stack up, the honest outcome is that the provider tells you so and you both walk away having spent an hour and lost nothing. That happens, and it should. A business case that always says yes is marketing wearing a spreadsheet costume. For a fuller treatment of how to sanity check these numbers yourself, read measuring automation ROI.
Red flags on either side of the table
Some providers run bad discovery calls. Watch for these:
- Pitching before understanding. If they name the solution in the first ten minutes, they decided before they met you.
- No numbers requested. A consultant who never asks for volumes, hours or win rates cannot quantify anything.
- Everything is automatable. A credible analysis rules things out. If nothing gets ruled out, nothing was analysed.
- Pressure to sign on the call. The whole point of a discovery plus analysis structure is that the decision comes after the evidence.
And to be fair, clients can sink a discovery call too. Turning up without any sense of your own numbers, insisting on a tool you saw in an advert, or delegating the call to someone who does not know how the business runs all waste the hour. The owner, or whoever genuinely runs operations, should be on the call.
What you are committing to (nothing, yet)
A discovery call commits you to sixty minutes, nothing more. The analysis that follows produces the business case, and only then does a proposal appear with a defined scope and a price. At AGMM, onboarding runs from £2,000 to £10,000 depending on scope, plus ten percent of the value the system actually creates, tracked in your own CRM so the counting happens on your side of the fence. The structure matters: the provider only does well if the numbers in that business case turn out to be real. You can see how the full installation runs, from discovery through to the month four expansion review, on the QS Quoter Commercial page.
Sixty minutes is a small stake for finding out, with numbers, whether your firm is leaking a day a week to admin that a system could absorb. The worst realistic outcome is a clearer picture of your own operation. The best is a business case that pays for itself many times over.
Sixty minutes, then a business case
One call, then a three to seven day analysis that puts real numbers on time saved, cost saved, capacity gained and revenue unlocked. No commitment until you have seen the case.
Book a discovery call