Rue's Discovery Call System

How to sound like
exactly who they need
in 20 minutes.

Your complete framework for running discovery calls — the questions to ask, how to diagnose the problem, what to say, and how to close with confidence.

The One Rule That Makes Everything Work

Your job on a discovery call is not to pitch your services. It's to make the client feel so understood that hiring you feels like the obvious next step. Diagnose first. Prescribe second. A doctor who prescribes before diagnosing is dangerous. A consultant who pitches before understanding is desperate. Be the doctor.

Before the Call

Prepare Like a Pro — 15 Minutes

15 min
before
Research their business
Never go into a call cold. 10 minutes of research = 10x more confident
Prep
What to look up
  • → Their website — what do they sell, how big are they, who's the founder?
  • → Their LinkedIn — what did they post recently? Any mentions of being overwhelmed, hiring, scaling?
  • → Their Instagram or Twitter — gives you a feel for their brand voice and personality
  • → What tools they mention using — Notion, Shopify, Slack, Airtable? Shows you their current setup
Opening line — use what you found
"Hey [Name] — I had a look at [their business] before our call. I noticed you're [doing X / selling Y / recently launched Z]. Really interesting. I wanted to understand more about how your backend operations support that."
This one sentence signals that you're not reading from a script. You showed up prepared. That alone separates you from 90% of freelancers they've ever talked to.
The Call

20-Minute Call Structure

💡

The split: 70% of the call is you listening and asking questions. 30% is you talking. If you're talking more than the client, you've lost control of the call.

Min
0–2
Open — Set the Frame
Take control warmly. Tell them how the call works so they relax.
Open
Say exactly this
"Thanks for making time. Here's how I like to run these — I'll ask you some questions about your business and your current setup for the first 10–12 minutes, then I'll share what I'm seeing and whether I think I can help. Sound good?"
This does three things: it positions you as the one running the conversation, it sets expectations so there's no awkwardness, and it signals that you're not going to spend 20 minutes pitching. Clients love this.
Min
2–12
Diagnose — Ask the 5 Questions
This is the most important part. Listen more than you talk. Take notes visibly.
Diagnose
Question 1 — Understand their world
"Tell me a bit about how your business runs day to day — what does a typical week look like for you operationally?"
This is an open question that lets them talk freely. You're listening for: what tools they use, where they're spending time, who's doing what, and what feels chaotic vs. organized.
Listen for: phrases like "I'm always having to check on…", "we do it manually in spreadsheets", "it all lives in my head", "nobody else knows how to…" — these are your entry points.
Question 2 — Find the pain
"What's the biggest bottleneck in your operations right now — the thing that costs you the most time or causes the most stress?"
This gets specific. Don't let them say "everything is a bit messy" — if they do, follow up with: "If you had to pick just one thing, what would it be?"
Listen for: the emotion behind the answer. If they sigh before answering, or laugh nervously, that's the real pain. Note it — you'll mirror it back later.
Question 3 — Quantify the cost
"How much time per week do you think that's costing you — or your team?"
This is where your price justifies itself. If they say "8–10 hours a week" — and their time is worth $100/hour — that's $800–1,000/week being lost. Your $800 project pays for itself in one week. You don't have to say this out loud. They'll do the math.
Follow up if needed: "And what does that mean for the business — are things falling through the cracks, or is it more that you can't focus on growth?"
Question 4 — Understand what solved looks like
"If that problem was fixed — what would be different? What would you be able to do that you can't do now?"
This question makes them visualize the outcome. Now they're selling themselves on the solution before you've proposed anything. This is the most powerful question on the call.
Their answer becomes the headline of your proposal: "Based on our call, the goal is [their exact words here]."
Question 5 — Understand the urgency
"How long have you been dealing with this, and what's made you look for help now?"
This tells you how motivated they are to move. "6 months, and it's getting worse" = high urgency, close quickly. "Just exploring options" = more nurturing needed. Adjust your energy accordingly.
Bonus follow-up: "Have you tried to solve this before — with tools, or with someone else?" If yes, ask what didn't work. This tells you exactly how to position your approach differently.
Min
12–15
Reflect — Mirror Their Problem Back
This is where you sound like an expert. Without having done anything yet.
Reflect
The reflect script
"Okay — based on what you've shared, here's what I'm seeing. You're spending [X hours] a week on [their specific pain]. The core issue isn't just the time — it's that [underlying cause: no system, everything in your head, no clear workflow]. What that means is [consequence: you can't delegate, you can't scale, you're the bottleneck]. Does that sound right?"
When they say "yes, exactly" — and they will — you've just demonstrated that you understood their problem better than most people they've talked to. That's expertise. Not a certification. Not years of experience. Just deep listening and clear articulation.
Example — filled in
"Based on what you've shared, here's what I'm seeing. You're spending about 10 hours a week managing orders and customer inquiries manually. The core issue isn't just the time — it's that everything lives in your head and in scattered spreadsheets, so nothing is visible to anyone else on your team. What that means is you can't step away without things falling apart — and that's exactly what's keeping you from growing. Does that sound right?"
This is built entirely from their answers. You didn't invent anything. You just organized what they told you and played it back clearly. That's consulting.
Min
15–18
Prescribe — Present the Solution
Only now do you talk about what you do. Keep it short and specific.
Prescribe
The prescription script
"Based on this, here's what I'd recommend. I'd start with a Backend Organization System — what that means is I'd build you a central workspace in Notion that covers [their specific needs: order tracking, task management, SOPs, whatever they mentioned]. The goal is that by the end, you're not the only one who knows how things work — your team can operate without you in every decision. Timeline is about [1–2 weeks]. Investment starts at $800."
Notice: you didn't say "I offer a Backend Organization System starting at $800." You said "based on THIS, I'd recommend THAT because of YOUR specific situation." The link between their problem and your solution is what justifies the price — not the deliverable list.
Min
18–20
Close — The Next Step
Never end a call without a clear next action. "I'll send you more info" is not a close.
Close
The close — two versions
If they seem ready: "I'll send you a proposal within 24 hours with the full scope, timeline, and investment. If everything looks good, we can get started [next week / first week of [month]]. Does that work?"
If they seem hesitant: "I'll send over a proposal so you can review everything properly. I'll include a few options at different scope levels so you can see what fits best. What's a good timeline for you to make a decision?"
Always end with a question. A question keeps the conversation open. A statement closes it. You want them to commit to a next action — even if it's just "review the proposal by Friday."
Diagnosis

Which Service Do They Need?

Based on what they say on the call, match their pain to your service. Here's the cheat sheet.

They say this →

Backend Org System — $800

  • "Everything is in my head"
  • "We have no real system"
  • "Tasks fall through the cracks"
  • "My team doesn't know what to do without me"
  • "We use like 5 different tools and nothing talks to each other"
They say this →

Automation Systems — $600

  • "I do the same thing manually every day"
  • "Follow-ups keep getting missed"
  • "Onboarding new clients takes forever"
  • "I'm copying data between tools constantly"
  • "I wish this just happened automatically"
They say this →

Website Systems — $900

  • "My website doesn't reflect the business anymore"
  • "People can't find what they need on our site"
  • "We have no landing page for this offer"
  • "Our website isn't connected to our ops at all"
They say this →

Monthly Retainer — $700/mo

  • "I need ongoing support not just a one-time fix"
  • "Things keep breaking after we set them up"
  • "I want someone to just keep things running"
  • "We're growing fast and the system needs to grow with us"
💡

Always lead with Backend Org System when you're unsure. Almost every client needs this first — it's the foundation everything else builds on. Then upsell automations after. This is also how you protect your workload: don't try to automate chaos. Organize it first.

Expert Language

Beginner vs. Expert — Side by Side

The difference isn't knowledge. It's how you frame what you know.

When describing what you do

❌ Beginner

"I build Notion workspaces and set up Zapier automations for businesses."

✅ Expert

"I design backend operations systems that remove the manual work slowing your team down — so you can scale without adding more chaos."

When they ask about your experience

❌ Beginner

"I'm fairly new but I've been learning a lot and I'm confident I can help you."

✅ Expert

"I've built ops systems for businesses across e-commerce, content, and service-based operations. The specifics vary, but the underlying problem — scattered tools, manual work, no visibility — is almost always the same. And I've solved it before."

When presenting the solution

❌ Beginner

"So I would build you a Notion workspace with databases and then set up some automations for your workflow."

✅ Expert

"What I'd build is a centralized ops hub — one place where tasks, priorities, and workflows are visible across your whole team. The goal is that by the end, your business runs on the system, not on you."

When they ask "can you do X?"

❌ Beginner

"Yes I think so, I'd have to check but I'm pretty sure I can figure it out."

✅ Expert

"Yes — I'd approach that by [brief explanation]. I'd want to understand your current setup first to confirm the best way to build it, but that's absolutely within scope."

Objections

What to Say When They Push Back

"That's more than I was expecting to spend."
"I understand — let me put it in context. You mentioned you're spending about [X hours] a week on this manually. If your time is worth even $30/hour, that's [X × 30] per week — every week. The system pays for itself in [timeframe]. That said, if $800 isn't the right fit right now, I can scope a smaller starting point — just the core task system — for $500, and we build from there."

Never just drop the price. Reduce the scope instead.
"Can I see some examples of your work?"
"Absolutely — I'll include case studies in the proposal I send over. I've also built some demonstration systems I can walk you through if that would help. [Then send: your Loom demo + 2 case studies from the website]"

Never say you don't have examples. Your demo workspace IS an example. Your website case studies ARE examples.
"How long have you been doing this?"
"I've been working in operations and systems for [however long is true] — I've built systems across e-commerce, service businesses, and content operations. What matters more than how long I've been doing it is whether the approach fits your problem — which is why I asked all those questions at the start. Based on what you've shared, I'm confident this is something I can solve for you."

Don't lie about experience. Redirect to competence and specificity.
"I need to think about it."
"Of course — totally understandable. Can I ask what's the main thing you want to think through? Is it the investment, the scope, or something else?"

[After they answer, address that specific thing, then:]

"I'll send the proposal over today so you have everything in writing to review. What would be a good date for you to make a decision by?"

"I need to think about it" usually means one specific thing is unclear. Find what it is.
"Can you do it cheaper?"
"I don't discount the price — but I can adjust the scope. What I can offer is a Phase 1 that covers [core deliverable only] for $500. Once that's built and you've seen how it works, you can decide if you want to expand. Most clients who start with Phase 1 end up continuing — because the results make the next investment obvious."

Smaller scope, same rate. Never drop your rate.
After the Call

What to Do in the Next 24 Hours

Within 2 hours — send a follow-up message
"Hey [Name] — great talking with you today. Just to summarize what we discussed: [2–3 sentences about their problem and what you'd solve]. I'll have a full proposal in your inbox within 24 hours. Looking forward to working together."
This message does two things: it shows you were listening, and it subtly assumes the deal is happening ("looking forward to working together" not "I hope we can work together").
Within 24 hours — send the proposal via PandaDoc
Your proposal structure: 1. The Problem (their words, not yours) → 2. The Solution (what you'll build) → 3. What's Included (deliverable list) → 4. Timeline → 5. Investment → 6. Next Step (sign here, deposit to start)
Day 5 — if no response, follow up once
"Hey [Name] — just following up on the proposal I sent over. Happy to answer any questions or adjust the scope if needed. What's your thinking?"
One follow-up is professional. Two is okay if there was genuine interest. Three or more is desperate. Know when to move on.

Before Every Call — Quick Checklist

RUN THIS IN THE 15 MINUTES BEFORE EACH CALL
Research
  • Looked up their website — know what they sell and their rough size
  • Checked their LinkedIn — know the founder's name and recent activity
  • Noted one specific thing to reference in the opening line
Setup
  • Notion doc open for notes — name, company, pain points, budget signals
  • This call guide open in another tab for reference
  • Camera on, clean background, good light, no distractions
  • PandaDoc proposal template ready to customize after
Mindset
  • You are not auditioning. You are diagnosing. Doctor energy, not applicant energy.
  • If they're on this call, they already think you might be able to help. Your job is to confirm it.
  • Silence is okay. If they go quiet while thinking, don't fill it. Let them think.