# The seven words that disqualify a prospect Source: https://getstartedwithai.net/blog/the-seven-words-that-disqualify-a-prospect Site: Get Started With AI Tagline: Build AI automations that actually run your business. Audience: solo professionals, freelancers, consultants and AI implementers in training Contact: hello@getstartedwithai.co.uk This Markdown companion is generated from the prerendered page for AI crawlers. # The seven words that disqualify a prospect How to qualify consulting clients in 2026: listen for the seven phrases that disqualify a prospect inside the first 10 minutes of a discovery call. After 200+ AI consulting discovery calls, these phrases reliably predict that the prospect is not ready for an implementation engagement and that the conversation should turn into a recommendation rather than a proposal. Disqualifying a prospect early saves both sides hours of wasted conversation, frees the consultant pipeline for prospects who are ready, and earns the disqualified prospect a useful next step. This post is the seven phrases, what each one signals, the right next move for each, and how to disqualify gracefully without burning the lead. ## We just want to explore the space Exploration is fine; explorers are not buyers. A WIRE Method engagement starts with a process to automate. If there is no process, there is nothing to scope. The conversation usually arrives because the founder has read about AI in a Sunday paper or seen a competitor announce something on LinkedIn. The right answer is to send the free Starter Kit and revisit when there is a candidate workflow that takes a named person more than two hours a week. The conversation is six months too early; in 80 percent of cases the prospect comes back later with a real workflow and the engagement starts cleanly. ## Our team is really excited about AI Excitement is not a brief. The candidate signal is missing entirely. There is no candidate workflow, no baseline measurement and no success metric in sight. The conversation needs to become an audit conversation before any build can be scoped. The right next move is the Audit Mini at £1,500, which produces the candidate list and the costed Time Tax. The prospect arrives at the audit with one specific workflow rather than a general feeling about AI; the engagement that follows is build-ready. Excitement-led prospects without a workflow burn 40 to 60 percent of consultant time before any build ships, which is why the audit is the right gate. ## We do not have data yet A common one. The candidate workflow has not been run enough times to produce a baseline. The build will be guessing. The right move is the Time Tax conversation on a different workflow the team does have data on. About a third of the time, the conversation surfaces a different candidate (usually a workflow the team did not think of as automatable) that does have the volume and the documentation to support a build. The other two thirds, the prospect leaves with a clearer view of what data work needs to happen first, and a return date for the conversation in three to six months when the data is in place. ## We need this to be done by next Friday A WIRE Method build runs in days, not next-Friday-panic. If the timeline is panic-shaped, the build will inherit the panic, and the build that inherits the panic almost always fails the fortnight of output review because nobody had time to set up the named owner. The right answer is a 30-minute conversation to find a smaller candidate that can ship cleanly inside a week. The Friday deadline is usually arbitrary (an upcoming board meeting, a competitor announcement, a vendor demo); the underlying need is real but rarely tied to that specific date. Surfacing the underlying need usually produces a smaller, faster, more reliable first build. ## We want to start with strategy Strategy decks do not produce working automation. The right answer is the practitioner case: ship the smallest working version, then write the strategy from the running build. Most prospects who started with strategy have already paid for one and have nothing running, which is the failure pattern I track. The conversation needs to reframe what they are buying. If the prospect insists on strategy, the right move is to recommend a different consultancy that sells strategy decks; that work is real and has a real role for very large investments. For SMB AI work, strategy after a working first build produces better strategy than strategy before any build, because the team now knows what works in their own context. ## We will figure out who owns it later No named owner means no Bus Test, which means a build that drifts. If the conversation is happening without an owner in the room, the right answer is to schedule the conversation that gets one in the room. The two-call structure I run for discovery handles this directly: call one is with the founder or sponsor, call two is with the named owner candidate. Both calls are 30 minutes. If the prospect cannot identify an owner candidate by call two, the build is not ready to scope and the recommendation is to revisit when the role is filled. Builds without owners run at a 70 percent failure rate by month six in the engagements I have audited. ## We just need someone to set it up A set-up consultant is not the right shape. Builds that survive get embedded with a fortnight of output review and a written governance layer. Set-up alone is the Silent Drift case: tool configured on Friday afternoon, runs for two weeks, drifts past month three, quietly cancelled at month nine. The right reframing for the prospect is that set-up costs about a third of the engagement and the rest is the embedding work that decides whether the build survives. If the prospect insists on set-up only, the engagement does not start. The honest practitioner test: would I be willing to put my name on this build a year from now if the embedding work was skipped. If the answer is no, the engagement should not start. ## How to disqualify gracefully without burning the lead Disqualification does not have to be brutal. The structure I use: name the gap honestly, recommend the right next step (free Starter Kit, audit at a different timing, different consultant for strategy work), and offer to revisit at a date that fits the gap. Most disqualified prospects come back inside 12 months with a clearer brief, having done the data work or filled the owner role. The leads that burn are the ones the consultant tries to engage anyway; the engagement fails downstream and the prospect blames the consultant. Disqualifying early protects both reputations. About 20 percent of my best engagements started as disqualifications six to twelve months earlier. ## Why disqualifying speeds up the pipeline A counter-intuitive point most consulting sales coaching misses. Disqualifying a prospect inside 10 minutes of a 30-minute call frees up the remaining 20 minutes for the consultant to work on the right kind of next step. The pipeline runs faster because each call ends with a clear outcome, the calendar opens up for the next ready prospect, and the consultant reputation as someone who does not waste time spreads. UK SMB founders talk to other UK SMB founders; the consultant who disqualified a prospect well today gets recommended next week to a prospect who is ready. The polite-yes-to-everyone path slows the pipeline rather than speeding it up. ## Build your first AI system live with Richard A 60-minute live build with Richard Batt. Bring one repeatable task. Leave with a mapped automation, success metrics and a deploy plan you can test the next morning. Free seat, no upsell. ### Live build session The next live session covers the WIRE Method end to end on a real audience build. [Join the next session](/webinar) ## Questions people ask before they start ### undefined undefined ### undefined undefined ### undefined undefined ### undefined undefined ### undefined undefined ### undefined undefined