Repeatable communication frameworks for prospect calls — each with the mechanics, a live script, and why it lands.
More detail here (their business, what stage this is, what's already been said) sharpens both the ranking and the full script. Short on details? The script will flag what it had to assume.
Showing all frameworks — start typing to rank by relevance.
Early in the call, before the prospect sees why automation applies to their business specifically.
The processes a business owner runs daily are invisible to them precisely because they're routine — nothing flags itself as "AI territory." Naming that blind spot, then positioning yourself as the trained eye that spots it, earns trust and justifies price in one move.
"The processes you're so used to doing that you don't even see them anymore — those are exactly where the opportunity is hiding, because it never comes with a flashing sign that says 'automate me here.'"
Reframes what they're paying for: not "AI," but the judgment to see what they can't see in their own business.
Habituation — repeated exposure to a routine stimulus reduces the brain's responsiveness to it, so a familiar daily process stops registering as a "problem." (Thompson & Spencer, dual-process theory of habituation, 1966)
Informal first contact — networking events, warm intros, anywhere there's no "sales moment" yet.
Six small moves that all sound like ordinary curiosity, never a pitch. The prospect names their own pain out loud — the more they say it themselves, the more real it becomes. What you do only comes up at step 5, and even then it's a door left open, not a pitch.
Patience does the work. Nothing feels like a pitch because it feels like their own idea.
Self-generated persuasion / the saying-is-believing effect — people believe and commit to a statement more when they generate it themselves than when told the same thing by someone else. (Higgins & Rholes, 1978; core technique in Motivational Interviewing, Miller & Rollnick)
No price named anywhere in this conversation.
Any moment you're about to describe what you actually build.
Never lead with "AI," "automation," or a tool name. Lead with what changes for them, in their own words from earlier in the call.
Instead of: "I can build you an AI-powered WhatsApp bot with automated logging."
Say: "Imagine you're never the one they have to text at 9pm because a part didn't show up — it just gets logged and flagged, and you only hear about it if it actually needs you."
Prospects buy outcomes, not mechanisms. Jargon makes them evaluate whether they "need AI"; outcome language makes them evaluate whether they want the problem gone.
Benefit-selling over feature-selling — benefit statements empirically correlate with sales success in complex, high-value sales, while feature statements don't. (Neil Rackham, SPIN Selling, 1988, based on research across 35,000 sales calls)
Structuring or explaining why the offer is worth the price.
Value = (Dream Outcome × Perceived Likelihood of Success) ÷ (Time Delay × Effort & Sacrifice). Work all four levers into the conversation: paint the outcome, give proof it'll work, shrink the time delay, remove effort from their side.
"You'll see this live in about a week, not a quarter. You don't need to learn a new tool — it just shows up in the WhatsApp you already use. And if it doesn't save you those hours in the first month, you don't pay for that piece."
Pre-answers the four silent questions every prospect has — do I want this, will it work, how long, how much effort — before they have to ask.
This four-part framing is a popularized business model (Alex Hormozi, $100M Offers) — not itself a peer-reviewed finding. What makes it work: loss aversion drives the guarantee lever (Kahneman & Tversky, Prospect Theory, 1979), and the Fogg Behavior Model drives the effort-reduction lever — reducing required effort raises "ability," making the behavior more likely regardless of motivation. (BJ Fogg, Stanford, B=MAT, 2009)
Presenting price.
Default to three tiers, not one number. Tier 1 (pilot) de-risks the decision. Tier 3 (build + retainer) anchors Tier 2 as the reasonable middle choice — the one you actually want them to pick.
"Most people start with the pilot — small scope, live in days, so you can see it work on one real job before trusting it with everything. Then there's the full build, end to end. And if you want it actively managed and improved every month, there's the retainer on top."
A single price is a yes/no decision. Three tiers turn it into a which-one decision — psychologically easier to say yes to something.
Decoy effect / asymmetric dominance — a third option changes how people evaluate the other two, without itself being chosen (Huber, Payne & Puto, 1982). The pilot tier also leans on the foot-in-the-door technique — agreeing to a small request raises the odds of agreeing to a larger related request later. (Freedman & Fraser, 1966)
Right before naming a number.
Show what the status quo already costs them — hours, errors, missed jobs — before stating your price. Your fee then compares to an existing cost, not a new expense out of nowhere.
"So right now, between the back-and-forth and the mistakes that slip through, that's probably costing you a few hours a week and the odd job that falls through the cracks. What we're talking about is a fraction of that, once."
"Expensive" is relative. Anchoring on a cost they've already named makes the fee look small by comparison.
Anchoring effect — the first number introduced into a conversation becomes the reference point everything after is judged against. (Tversky & Kahneman, 1974)
Near the end of the call, before they've raised an objection themselves.
The two objections you'll hear almost every time: "we need to think about it" and "it's expensive." Naming and defusing them yourself — tied to the pilot and the cost-of-inaction anchor — takes the air out before the prospect has to say it.
"Two things people usually think at this point — 'is this actually going to work' and 'is it worth it.' That's exactly why we start with the small pilot: you see it work on one real job before committing to anything bigger, and it's priced against what the problem is already costing you, not against nothing."
Objections raised by the salesperson land as honesty, not pressure — and remove the prospect's need to be the one to voice doubt.
Inoculation theory / two-sided messages — pre-exposing someone to a weakened counterargument builds resistance to it and reads as more honest than a one-sided pitch. (McGuire, 1961; Hovland et al.)
The prospect says they already use a tool, an in-house person, or another agency for this.
Don't argue that what they have is bad — that puts them on the defensive of a decision they already made. Separate "having something" from "having it solved," and ask a question that lets them notice the gap themselves.
"That's actually a good sign — means you already believe this is worth solving. Quick one though: does what you've got now catch it before it becomes a problem, or does someone still have to notice and go fix it?"
Reframes the ask from "replace this" to "close the gap this doesn't cover" — a much smaller yes.
Cognitive dissonance theory — directly criticizing a choice someone has already made creates dissonance they resolve by defending it harder, not updating it; a diagnostic question lets them notice the gap themselves instead. (Festinger, 1957)
A technically-minded prospect, or their ops/engineering lead, pushes back with specifics to test whether you actually know what you're talking about.
A technical skeptic isn't asking you to prove AI works in general — they're asking you to prove you understand their specific failure modes. Lead with the boring, unglamorous detail (what happens when it's wrong, who's on the hook) before the impressive parts. Precision about limits reads as more credible than confidence about capability.
"Honestly, it's not magic and I won't pretend it is — here's exactly what happens when it gets something wrong: it flags it, logs it, and defaults back to you, not the client. I'd rather you see the failure case than just hear the pitch."
Leading with the failure mode signals you've actually built this before, not just sold it — the one thing a skeptic can't get from a slide.
The pratfall effect — a competent person's likability and perceived credibility increase when they reveal a minor flaw or limitation, because it reads as more relatable and honest. (Aronson, Willerman & Floyd, 1966)
A call went well, they said they'd think about it or check with someone, and it's gone quiet for several days.
Never follow up with "just checking in" — it signals you have nothing new and are chasing them. Bring something that moves the conversation forward on its own: new information, a smaller version of the offer, or a specific reason to revisit.
"Not chasing you on this — but I put together a smaller-scope version of the pilot since we talked, in case the original felt like a bigger first step than you wanted. Want me to send it over?"
Reduces their reply from "make a decision" to "yes or no on a smaller thing" — reopening the door without spending "just checking in" for nothing.
The Zeigarnik effect — people remember and feel a pull to resolve unfinished or interrupted tasks more than completed ones; a stalled conversation is an open loop the prospect's own mind wants closed. (Zeigarnik, 1927)
You've already opened with your pitch too early — led with "I do AI automation" instead of letting them talk first — and a price got named, or almost got named, before the pain was ever said out loud.
Don't fix a bad opener by repeating it harder in the follow-up. The number still has nothing to anchor against, because they never said the pain in their own words. Reopen the conversation and go back to the missed steps — getting them to describe the mess themselves — before price ever comes up again.
"Hey [name], good bumping into you the other day! Random question — with the contract workers on your jobs, how does it usually go when something changes mid-project, like someone needs a part or hits a delay?" Let them answer and vent, same as steps 3–4 of the Curiosity Ladder. Only after they've described it again, in their own words, does a number get another airing.
Repeating a rejected ask tends to make people dig in harder to protect their earlier "no." Reopening through their own words sidesteps that, and lets the price trail their language instead of yours.
Psychological reactance theory — when people feel a decision they've already declined is being pushed on them again, they become more resistant, not less, to protect their sense of autonomy. Getting them to re-generate the argument themselves (see FM-02) avoids re-triggering that resistance. (Brehm, 1966)
Recovery wasn't a cheaper number. It was reopening with the script above, letting him restate the mess in his own words again, then letting a smaller, pilot-tier number come up naturally afterward.