sales
How to Write a Discovery Call Script for Pitching Automation Services to a Business Owner
A step-by-step framework for structuring a discovery call script that gets business owners to open up about their real automation problems — and buy.
You finally land a call with a business owner. Fifteen minutes in, you're still talking about "streamlining workflows" and they're checking their phone. No pain uncovered, no budget discussed, no next step. Call over, deal dead.
That's what happens when you pitch automation services without a real discovery call script. Business owners don't care about your tech stack — they care about hours lost, money leaking, and staff mistakes. Your script needs to get them talking about that, fast.
How Long Should a Discovery Call Script Be?
A discovery call for automation services should run 20-30 minutes, structured around 4-6 core questions, not a rigid script you read word-for-word. Anything longer and busy owners start disengaging; anything shorter and you won't uncover enough pain to justify a proposal.
The goal isn't to fill 30 minutes. It's to walk away with three things: the specific process that's broken, the cost of that process staying broken, and who else needs to sign off before they buy.
What Should the First Two Minutes of the Call Cover?
Open with a 15-second context statement plus a permission-based agenda, not small talk. Something like: "I know you're busy — I want to spend the next 20 minutes understanding how [process] works today so I can tell you honestly whether automation makes sense. Sound good?"
This does three things immediately:
Signals respect for their time — owners tune out reps who ramble before getting to the point.
Sets the frame as diagnostic, not salesy — you're there to find out if you can help, not to pitch a package.
Gets a verbal yes — small commitments early make bigger commitments (like sharing real numbers) easier later.
Skip the Feature Dump
Don't open with what your automation does. Business owners have heard "save time and reduce errors" a hundred times from a hundred vendors. Get to their specific situation instead.
What Questions Actually Uncover Real Pain?
Structure your discovery around five question categories: current process, cost of the problem, past attempts, decision process, and timeline. Ask them in that order — it moves from easy-to-answer to harder-to-answer, which keeps the conversation flowing.
Current process: "Walk me through how [task] happens today, start to finish." Let them talk for 2-3 minutes uninterrupted. This is where you find the manual steps, the spreadsheets, the "someone emails someone" bottlenecks.
Cost of the problem: "How many hours a week does your team spend on this?" and "What happens when it goes wrong — a missed order, a late invoice?" Get a number. Vague pain doesn't close deals; a number does.
Past attempts: "Have you tried fixing this before? What happened?" This tells you if they've been burned by a bad implementation and what objections are coming.
Decision process: "If we found the right fix, who else would need to be involved in saying yes?" Owners often aren't the sole decision-maker even when they act like it.
Timeline and urgency: "Is this a this-quarter problem or a nice-to-have someday?" If there's no urgency, there's no deal — better to know now.
Follow the "So What" Rule
Every time they mention a pain point, ask "and what does that cost you?" or "and then what happens?" one more level down. The first answer is surface-level ("it takes too long"). The second answer is the real budget justification ("we lost a $12k client because the follow-up email went out three days late").
How Do You Transition From Discovery to Pitch Without Sounding Pushy?
Use a summarize-and-confirm bridge before you pitch anything: repeat back what you heard in their own words, then ask permission to share how you'd approach it. This single move — "So if I'm hearing you right, [X] is costing you [Y] hours a week and it's mainly a problem when [Z] happens — did I get that right?" — does more for close rate than any feature list.
Once they confirm, you've earned the right to pitch. Now you're not selling automation in the abstract — you're proposing a fix to the exact problem they just described, in their words.
If your outreach and follow-up before this call happens on Telegram, CRMChat keeps every prior conversation, note, and booked-call context in one pipeline so you walk into the discovery call already knowing what they responded to and why. CRMChat also automates the pre-call sequence — reminders, confirmations, reschedule handling — so fewer of these hard-won calls get missed. If you're already syncing booked meetings into a calendar tool, check out how to sync Telegram booked meetings with a sales calendar to keep this step from slipping.
What Should You Do When the Owner Gives Vague Answers?
When you hit vague answers like "it's fine, just a bit slow," don't move on — anchor them to a specific recent instance instead of a general assessment. Ask: "Can you think of the last time that actually caused a problem — what happened?" Specific memories produce specific numbers; general impressions don't.
Ask for the "last time" version of any vague complaint, not the general trend.
Use silence deliberately — after a vague answer, pause 3-4 seconds before your follow-up. Owners often fill the silence with more detail.
Reflect their number back — "so that's roughly 6 hours a week across two people" — to make the cost concrete and hard to dismiss later.
Watch for the real decision-maker — if they defer to "I'd need to check with my partner," qualify that person into the next call before you build a proposal.
How Do You Qualify the Prospect Before Building a Proposal?
A discovery call isn't a win just because the conversation went well — you need budget authority, a real timeline, and a defined problem confirmed before you invest time in a proposal. If any of those three is missing, your next step is a clarifying follow-up, not a full proposal.
This is the same discipline covered in how to qualify a prospect before handing off to a closer — the earlier you filter out "not now" prospects, the more of your proposal-writing time goes toward deals that actually close.
Where Do You Find Business Owners to Get on This Call in the First Place?
Before you can run this script, you need the owner's actual contact, not a generic support inbox. If you're prospecting in Russia or the CIS, the fastest path is registry-to-Telegram lookup: pull companies by industry and revenue from a data provider like DataNewton, then run each company's founder through CRMChat's contact-lookup tools to get a phone number, and convert that number into a Telegram username. CRMChat's phone-to-Telegram conversion typically enriches around 50% of CIS and MENA numbers into usable usernames, so you're booking calls with verified owners instead of guessing who's behind a company page.
For broader top-of-funnel prospecting, parsing relevant public groups is a solid secondary tactic — but for owner-level decision-makers specifically, the registry-lookup route gets you a direct line faster.
Discovery Call Script Checklist
Open with a 15-second context statement and get a verbal yes to proceed.
Ask about current process first — let them talk 2-3 minutes uninterrupted.
Push every pain point one level deeper with "and what does that cost you?"
Get a specific number: hours lost, dollars lost, or deals missed.
Confirm the real decision-maker before assuming the owner alone can sign.
Summarize what you heard in their words before pitching anything.
Only build a full proposal once budget, timeline, and problem are all confirmed.
Get this script right and you stop pitching automation in the abstract. You start proposing a fix to a specific, costed problem the owner told you about themselves — and that's the pitch that actually closes.
