Discovery call questions for automation projects: 30 that work

You got the call. The owner says they want to "automate onboarding" or "hook up AI to the inbox." You nod, you picture the n8n workflow, and you send a quote that afternoon. Three weeks later you find out onboarding has four versions, one of them lives in a spreadsheet only Maria understands, and the inbox gets 900 emails a week, not 50.

That is the normal way automation projects go wrong. The build is rarely the problem. The first conversation is. The client describes the process they think they have, not the one their team actually runs.

The questions below are grouped by what they surface: the real process, the real volume, and the real failure points, then data, ownership and money. You will not ask all 30 on every call. Pick the ones that fit, and keep asking "why" when an answer sounds too tidy.

What is an automation discovery call actually for?

A discovery call is a short interview, before any tool is mentioned, to decide whether there is a process worth automating and what it would take. It is not a demo and not a pitch. You leave with enough to write a recap and either a proposal or a paid scoping offer.

Three outcomes are all good results:

1. Yes, quote it. The process is clear, repeatable and worth enough money.
2. Yes, but scope it first. The process is real but messy; sell a paid mapping session.
3. No. The process is trivial, nobody will own it, or the client only wants a cheap bid.

A useful framing from r/salesengineers: every call should answer "why us, why now, and why do anything at all." If you cannot answer the last one, nothing else matters.

Questions that surface the real process

Ask about a specific recent example, not the process in general. People describe the ideal version in general and the real version when you ask about last Tuesday. OurIdea.ai's advice is the same: ask for last week, because people remember last week.

1. "Walk me through the last time this happened, start to finish. Can you share your screen and show me?"
2. "What starts it? An email, a form, a payment, a person deciding?"
3. "What is the very first thing you do when that arrives?"
4. "Where do you copy information from, and where do you paste it?"
5. "How many people does it pass through before it is done?"
6. "Is there a spreadsheet, sticky note or personal inbox involved that I have not seen yet?"
7. "Does everyone on the team do it the same way?"

Tip: Question 1 is the most valuable thing you will ask all call. Watching a person click through a task for five minutes shows you steps they would never think to say out loud.

On r/salesforce, an experienced admin said they start with the current state: if the client tracks something in a spreadsheet, they ask for a copy, and if there is an existing system, they ask for a demo. Do the same. The number of handovers in question 5 is the best single signal of a process worth fixing, because every handover is a place where work waits.

Questions that surface the real volume

Volume decides the price, the tool and whether the project is worth doing at all. Ask for counts and then check them against a real source.

8. "How many times did this happen last week?"
9. "What does your busiest day look like? Your slowest month?"
10. "How long does one take, from start to done?"
11. "Is the volume growing? What happens if it doubles?"
12. "Can you show me the inbox, form log or sheet so we can count a sample together?"

Here is why the arithmetic matters. Say the answers are 60 onboarding requests a week, 12 minutes each:

That is a real budget. If the same process runs 5 times a week, it is worth about $1,200 a year and probably not worth a custom build. MindStudio suggests pricing builds at roughly 10% to 20% of first-year value, which makes the volume question the one your quote rests on. Write the assumption into your proposal ("priced on about 60 requests a week") so a wrong guess becomes a conversation, not a loss. Our guide to AI automation agency pricing covers how to turn this into a setup fee plus a monthly plan, and the AI Automation pack has a five-line calculator for it.

Questions that surface the failure points

Exceptions are where automations break and where your support hours go. Ask about them directly, because clients forget the weird cases until the automation hits one.

13. "What happens when it goes wrong? What did the last mistake cost you?"
14. "What are the cases that do not fit the normal flow? How often do they come up?"
15. "What does a person decide along the way that a rule could not?"
16. "What happens if a step is skipped or done twice?"
17. "Has anyone tried to fix this before? What happened?"
18. "If the automation stopped silently for a day, how would you find out?"

Question 13 tells you how careful the build has to be and where a human should stay in the loop. Question 17 is underrated: a previous failed attempt shows you what the client believes the problem is, and sometimes turns up an old Zap nobody owns. Question 18 sets up your monitoring and, later, your care plan. An agency owner on r/n8n who builds for dozens of clients stressed logging and alerting, and a commenter on that thread had to rebuild a project because nobody planned a way to export conversation data the client later wanted. Ask now what they will want to report on.

Questions about data, tools and access

These confirm the automation is technically possible and that you can get in. Skipping them is how a two week build becomes six.

19. "Which tools does this touch? Which plan are you on for each?"
20. "Who has admin access, and can you give me my own login?"
21. "Is there personal, health, payment or client confidential data involved?"
22. "Are there rules about where data can be stored or which AI tools can see it?"
23. "Who will pay for the software subscriptions once it runs?"

Watch out: A low tier plan can block the API or webhook you need. Check it on the call, not after you have quoted.

Questions about people and ownership

An automation that nobody owns dies the first time it breaks. A Salesforce consultant on Reddit said the question that always matters is "who on your team is going to own the project?", because without an owner, feedback and answers stall and the project always runs long.

24. "Who will be my main contact and who signs off on the result?"
25. "Whose daily work changes if this goes live? Are they on board?"
26. "Who checks it when something looks wrong after handover?"

If the person whose job this was does not trust the automation, they will quietly work around it. Name them on the call and, if you can, talk to them before you build.

Questions about success and money

End by making the client describe success in their own numbers. That sentence becomes the goal you quote against and the baseline you report on later.

27. "Three months from now, what would make this a clear win? Hours, errors, response time?"
28. "What is this costing you today, in time or lost sales?"
29. "Why solve this now rather than next quarter?"
30. "Have you budgeted for this, and who else are you talking to?"

If the client cannot say what success looks like, you cannot prove you delivered it. Record the baseline (current hours, error rate, response time) in your recap so you can show the before and after in month one. That report is what makes a maintenance retainer easy to keep.

What are the red flags on a discovery call?

Some calls should end with a polite no or a paid scoping offer. Look for these signs:

• They want a price before they will describe the process.
• Nobody will own the automation after you hand it over.
• The process changes every week or every person does it differently.
• They cannot give you access to the tools.
• They ask for the full written plan, step by step, before paying anything.

That last one is common. On r/freelance, a freelancer found a client had built their detailed proposal with someone cheaper. The top reply, with far more upvotes than anything else, was one line: they charge for planning and scoping. Another said they never give more than one hour of free consulting. A third suggested walking the client through your plan live on a call, so there is no document to shop around.

How do you run the call, step by step?

Keep it to 30 to 45 minutes and follow a fixed order so you never run out of time before the money questions.

1. Two minutes: "What made you reach out now?" Then stop talking.
2. Fifteen minutes: screen share of the real process (questions 1 to 7).
3. Ten minutes: volume and failures (8 to 18).
4. Five minutes: tools, access, owner (19 to 26).
5. Five minutes: success and budget (27 to 30).
6. Three minutes: next step. Say you will send a recap within a day.

A tip from r/salesengineers: ask your question, then go quiet. Most people fill the silence within five seconds, usually with the detail you needed.

The recap email

Send it the same day, in the client's words. It shows you listened and sets up the next step without giving the blueprint away.

Subject: Recap of our call about [process]

Here is what I heard:
- Today [process] runs about [N] times a week, [M] minutes each, through [people].
- The main problems are [failure 1] and [failure 2].
- Success in 3 months looks like [their words].

Next step: a paid scoping session ([price], [days]) where I map every
step and exception and deliver a written build plan. The fee comes off
the build if you go ahead.

What mistakes do beginners make on discovery calls?

The most common mistakes are about talking, not asking.

• Turning the call into a demo. You show a slick workflow, they nod, and forty minutes later you still do not know the process.
• Taking the first answer. The task named first is the one that annoyed them this week, rarely the one costing the most.
• Quoting on the spot. One r/salesforce commenter doubles any estimate made before proper discovery and says client timelines are unrealistic "100% of the time."
• Pitching an AI agent when a simple rule would do. Ask why this approach before assuming the fanciest one. Our comparison of AI agents vs automations helps here.
• Giving away the plan. Free call, yes. Free blueprint, no.

Where to go from here

1. Copy the 30 questions into a call template and cut it to the 15 that fit your niche.
2. Practise on two friendly businesses, with screen share, and time yourself.
3. Build a volume and value calculator like the table above.
4. Write your recap email and a paid scoping offer before your next real call.
5. Track every call: which questions got the useful answers.

Results vary with your niche, your proof and how many calls you take; no question list guarantees a sale. If you want the full system around these calls, the AI Automation pack adds the step-by-step lessons, proposal templates, pricing calculator and handover checklists for $19, and all 16 Money Printer packs are $39.