How to demonstrate AI services to a sceptical prospect

Site Owner 8 min read

The demo is the sale. Not a slide deck, not a video - a number they ring from their own phone. Here is how to run one without it going wrong.

Someone presenting to colleagues in a meeting room

You will not talk anyone into this. A sixty-year-old roofer who has decided AI is nonsense is not going to be argued out of it by a person half his age with a laptop.

What changes his mind is hearing it. Specifically: ringing a number, from his own phone, and having a normal conversation with something that is not a person. There is a moment about eight seconds in where the face changes. That moment does the selling. Your job is to arrange it and then get out of the way.

This article is about arranging it well, because a badly run demo can cost you the sale that a well-run one would have won.

Rule one: they ring it, not you

The single most common mistake is playing a recording, or ringing the number yourself on speaker.

Both fail for the same reason. A recording could be anything. Your call on your phone could be a set-up. Neither creates the moment.

Hand them the number. Let them ring it on their own mobile. Let them ask whatever they want, including the awkward things. The demo is only persuasive because it is not under your control, and any move that puts it back under your control destroys the effect.

If you are hesitant to hand over control, that usually means you have not tested the demo enough. Fix that, not the method. Ringing a demo yourself a few times first is the cheapest preparation there is.

Rule two: it must sound like their trade

A generic demo answering as "Acme Solutions" is a wasted opportunity. Build a version that answers as a plumbing firm before you go and see a plumber.

It should handle the questions their customers actually ask. Do you cover my postcode. How soon can someone come out. Do you charge for a quote. Are you Gas Safe registered. When the prospect asks one of those and gets a sensible answer, they stop evaluating the technology and start imagining it on their own line. That transition is the whole point.

Building three or four trade variants takes an afternoon. It is a much better use of time than a slide deck.

Rule three: open with their problem, not your product

Do not open with artificial intelligence. Open with a question.

"How many calls do you think you miss in a normal week?"

Most owners underestimate, say something like "couple, maybe", and then get an uneasy look because they are not sure. Some check. The uncertainty is more useful to you than any figure they give, because now the topic is their problem rather than your service.

Other openings that work in the same way:

  • "What happens to a call that comes in while you are under a sink?"
  • "When someone leaves a message, how long before you get back to them, honestly?"
  • "If someone fills in the form on your website at nine at night, what happens?"

Every one of these invites them to describe a leak they already know about. Then you show them the thing that plugs it. You did no persuading.

Rule four: shut up during the call

When they ring the demo, say nothing. Do not narrate. Do not point out how natural the voice is. Do not say "listen to this bit".

Narration signals that you need them to be impressed, and people resist being told what to feel. Silence lets the thing be surprising on its own terms.

When they hang up, still wait. Let them speak first. The first thing they say tells you exactly what to talk about next, and it is very rarely what you had planned.

What to show after the voice demo

The call is the hook. It is not the whole service, and if you stop there you sell a novelty rather than a system.

Show, in this order:

  1. The notification. The text or email that arrived on your phone within seconds of the call ending, with the caller's name, number and what they wanted. This is the actual product. The voice is how it is collected.
  2. The website chat. Pull up a site with an AI chatbot and let them type something rude or awkward into it. They will try. Let them.
  3. One automation. Just one. A review request that goes out after a job, or a reminder the day before an appointment. Pick whichever matches the complaint they raised earlier. Showing five automations is worse than showing one relevant one - it turns a clear offer into a menu they now have to think about.

Handling the objections you will definitely hear

The same few come up in almost every meeting, so it is worth rehearsing the objections local businesses actually raise about AI before you are sitting in front of one.

"My customers want to speak to a real person"

Agree with them. "They do. Right now, when you are on a job, they get a ring tone and then they ring someone else. The choice is not between this and you. It is between this and nothing."

That reframing is honest and it usually lands, because they know the second half is true.

"It will sound like a robot and embarrass me"

This is the one the demo answers by itself, which is why the demo comes before the objection wherever possible. If it comes up first, do not defend - just hand them the number.

"What if it gets something wrong?"

Do not claim it will not. It will, occasionally. It will mishear a postcode or a surname.

The honest answer: "It sometimes mishears a name - but it always gets the number, and you can ring them back. Compare that to a missed call, where you have nothing at all." Admitting the flaw makes everything else you have said more believable. Overclaiming here is how you end up with an angry client in month two.

"Can it transfer urgent calls to my mobile?" / "Can it book straight into my diary?"

Depending on the provider and the configuration, often yes. But do not answer confidently unless you have already set it up and tested it on the exact setup you would use for them. The right answer when unsure is "I think so - let me confirm it properly and come back to you tomorrow", and then do.

"How much?"

Answer it. Do not deflect to "it depends on your needs". Give a setup figure and a monthly figure with what is included. Small business owners have been dodged by enough agencies to read deflection as a sign you are working out how much you can get.

When the demo goes wrong

It will, eventually. The line is bad, the agent mishears everything, it gives a strange answer to a normal question.

Do not panic and do not apologise repeatedly. Say what happened plainly - "that one is misconfigured, it should not do that" - and offer to ring them back with it working. Then actually ring them back.

Oddly, a demo that fails and is fixed by Thursday can be more persuasive than one that works first time, because they have now seen what happens when there is a problem. That is the thing they were really worried about.

What not to do

  • No slide deck. Nobody in a van wants a deck.
  • Do not explain the technology. They do not care which model it uses and asking makes them feel obliged to pretend to follow.
  • Do not demo six services. One clear thing sells. Six things get postponed.
  • Do not leave without a next step. Not "have a think" - a specific day you will ring back. Then ring back on that day.

The part that is still hard

A good demo makes the conversation easy. It does not make the conversation happen.

Getting in front of the prospect at all - the walking in, the ringing at three on a Wednesday, the eighteen who brush you off before the two who do not - is your work, and no demo shortens it. What the demo does is make sure that when you finally have someone's attention, you are not wasting it explaining.

If you want to see the demo you would be handing people, the receptionist is live here, and what comes with it is listed in full. Anything the pages do not cover, ask directly rather than guessing.

Want the agency already built?

The website, AI receptionist, chatbot, automations, service packages and sales resources, assembled into one business under your brand. You still build the client base.

Related reading

Build my agency Pricing

We use a small number of cookies to keep this site working and to remember how you found us. We would also like to use analytics cookies to see which pages are useful. These are only set if you accept. Cookie policy.