Someone finally said yes to a call. It's on your calendar for Thursday, and you've never run a sales call in your life. You built the product, so you know every screen by heart, and that's the problem: left alone, a lot of technical founders give a 30-minute tour nobody asked for, then end with "so, let me know what you think." Here's the playbook I'd hand a founder before their first live SaaS sales demo call, from prep to the follow-up email, including the awkward pricing question.
Quick answer
To run your first SaaS sales demo call as a founder, prepare one guess about the buyer's problem and one workflow to show. On the call, set a short agenda, spend the first third asking how they handle the problem today, then demo only the part of your product that does that one job, using their words. Answer pricing and "send me more info" questions directly. Before you hang up, agree on one concrete next step with a date, and send a short follow-up email within the hour.
What this call is (and isn't)
This is the live call with a real prospect who might pay you. Founder-led sales just means you, not a hired rep, run it. It's not a validation interview where you hide your idea, and it's not a recorded walkthrough for strangers on your homepage. For that, MakerHunt has a separate guide on how to film a 90-second product demo that converts cold visitors. And if your calendar is still empty, start a step earlier with how to get your first 10 paying customers without a launch day, which covers picking a narrow buyer, outreach and paid pilots.
The live call is different because the other person can interrupt, push back and ask what it costs. That's the fastest feedback you'll ever get, if you go in with a plan.
Before the call: 30 minutes of prep
You don't need a sales deck. You need four things on one page.
1. Ten minutes on who they are
Read their company site, their LinkedIn, and whatever they wrote when they booked. Note their role, team size and any tool you can see them using. You want enough context for a sharp follow-up question, not their funding history.
2. One guess about the job
Write one sentence: "I think they're trying to ___ and today they do it with ___." You'll probably be wrong about some detail. That's fine. The guess gives your questions a direction, and correcting it on the call is where you learn the most.
3. One workflow to show
Pick the one path through your product that does the job in your guess. Set up a demo account with realistic data for someone like them, not "Test User 1" and lorem ipsum. If they run a small agency, the workspace should look like a small agency's week. Click through it twice so you know where the slow screens are.
4. Logistics
Send a two-line agenda the day before. "Plan for Thursday: 10 minutes on how you handle this today, 10 minutes of the product on your use case, then we see if a next step makes sense. 30 minutes total."
Test your screen share and close every tab and notification you wouldn't want a buyer to see.
Ask before you record. Consent rules differ by place. In the US, the Reporters Committee's introduction to its recording guide notes that about 11 states require consent from everyone on the call, and suggests assuming the stricter law applies when people are in different states. Easiest habit: ask at the start, every time, and take no for an answer.
The 30-minute agenda
Thirty minutes is enough for a first call. An hour mostly gives you room to ramble.
Minutes | What happens | What you're aiming for |
|---|---|---|
0–3 | Hello, confirm time, agenda, ask to record | They know what's coming and that you'll respect the clock |
3–13 | Discovery questions | You can describe their problem in their words |
13–23 | Demo of one workflow, tied to what they just said | They can picture using it next week |
23–28 | Their questions, pricing, objections | No fog left about cost or fit |
28–30 | Agree a next step with a date | Something is on both calendars before you hang up |
Open with something like: "Thanks for making time. I'd like to start by asking how you handle this today, so I only show you the part that's relevant. Then I'll show you that part, and at the end we can decide if a next step makes sense, or if it doesn't. That okay?" Then check they still have the full 30 minutes.
Discovery: the ten minutes that decide the call
The first third of the call matters more than the demo. Skip it and you're guessing which features to show. Rob Fitzpatrick's The Mom Test was written for customer conversations, and its three rules carry straight over to sales calls: talk about their life instead of your idea, ask about specifics in the past instead of opinions about the future, and talk less than they do.
Questions that tend to work on a first call:
"Walk me through the last time you had to do this. What happened?"
"What are you using for it right now? A spreadsheet, another tool, someone on the team?"
"What's annoying about that setup?"
"How often does this come up, and how long does it take each time?"
"What made you take this call now, and not six months ago?"
"Have you tried anything else to fix it? What happened?"
"Who else would be involved if you changed how this works?"
You won't get through all seven, and you shouldn't try. Ask one, then chase whatever's interesting with "tell me more about that" or "why was that a problem?" Question five is the easiest one to skip, and it's the most useful. Something changed for them, maybe a new hire, a missed deadline or a client who complained, and that change is what your demo needs to speak to.
Write down their exact phrases. If they say "I lose half of Monday chasing invoices," that sentence is worth more than anything on your homepage. You'll reuse it in the demo and the follow-up email.
Demo the one job, not the product
Now show the workflow you prepared, adjusted for what you just heard.
Say why before you share. "You said Monday mornings go to chasing invoices. Let me show you what that looks like in here." Now every click has a reason.
Start near the result. Show the finished thing first, then how it got there. Nobody needs the settings page in minute one.
Keep it to three or four screens. When you feel the urge to say "and it also does," stop.
Check in every couple of minutes. "Is this close to how you'd do it?" Their answer tells you whether to keep going or change course.
If something breaks, say so. "That's a bug, I'll fix it this week" lands better than pretending. Early buyers know you're small. They're judging whether you're straight with them.
Stop sharing when you're done. Seeing faces again turns a presentation back into a conversation.
An illustrative example (made up, not a real company): you sell a booking tool for physiotherapy clinics. In discovery, the clinic manager says no-shows are the real problem, not booking. So you skip the calendar setup you'd planned and go straight to the reminder and waitlist screen, using a fake clinic with a full Tuesday and two cancellations. Same product, a quarter of the screens, and the whole demo answers what she said.
Handling the questions that scare first-time sellers
"Can you send me more info?"
Sometimes that's a polite exit, sometimes it's genuine. Don't guess. Ask: "Happy to. What should it cover, so I don't send you a wall of stuff?" If they name something specific, like security, a pricing breakdown or how it fits their current tool, that's a real next step. If they can't name anything, it's usually a soft no, and it's fine to say: "No problem if the timing's off. Should I check back in a month, or leave it with you?"
"How much does it cost?"
Say the number, in one sentence, without apologizing. Something like "It's $49 a month for a team your size, cancel any time" (use your real price, obviously). Then stop talking. "It depends" on a first call makes you sound like you're about to overcharge them. If you truly don't have a price yet, say so and offer the paid pilot terms you'd accept.
"Does it do X?"
If it does, show it in under a minute. If it doesn't, say no and ask why they need it: "Not today. What would you use it for?" Often the underlying need is something you already cover another way. Don't promise a feature to save the deal. Write it down and decide later, without a buyer watching.
"I need to check with my boss"
Fair enough. Help them make the case: "What do you think they'll ask? I'll send a short summary that answers it." Then ask whether it makes sense to bring that person to a 20-minute follow-up. You'd rather show the decision maker yourself than hope your champion explains it well.
Close with a concrete next step
The worst ending to a good call is "great, let me know." The Mom Test calls the fix commitment and advancement: a meeting went well if the other person gave up something real to move forward, like their time, reputation or money. Compliments don't count.
Good next steps look like this:
A second call booked with the person who signs off
A trial or pilot account set up with their real data, plus a check-in date
An intro to a colleague with the same problem
A paid pilot agreed, with the invoice going out today
If they're keen, set them up right there. Paul Graham's essay Do Things That Don't Scale describes how the Collison brothers, when anyone agreed to try Stripe, would say "Right then, give me your laptop" and set them up on the spot. On a video call, "Want me to set up your workspace now while we're both here?" is the same idea.
Whatever the step is, put the date in the calendar while you're both still on. "I'll send an invite for Tuesday at 3, does that work?" beats "let's find a time."
Send the follow-up email within the hour
Do it while you still remember the details. Keep it short and use their words, not your feature list. (Names and numbers below are illustrative.)
Subject: Thursday's call, next steps
Hi Priya, thanks for the time today. Quick recap so we're on the same page.
What you told me: Monday mornings go to chasing late invoices across three clients, and it got worse with the new retainer.
What I showed you: the reminder flow and the overdue view, set up for a team of four.
Next step: I'll set up a workspace with your client list by Friday, and we'll check in Tuesday at 3pm with Sam. Price we discussed: $49/month, cancel any time.
If I got anything wrong, just reply and tell me. Thanks, Alex
That last line matters. People correct a recap far more readily than they write one, and the correction is often the most useful thing you'll hear all week.
A simple call-notes sheet
You don't need a CRM for your first 20 calls. One spreadsheet, one row per call, filled in right after the follow-up email:
Column | What goes in it |
|---|---|
Date / company / role | Basics, so you can spot patterns later |
Their words for the problem | The exact phrase, in quotes |
What they use today | Tool, spreadsheet, person, or nothing |
Why now | The trigger that made them take the call |
What I demoed | Which workflow, and where they leaned in or went quiet |
Questions and objections | Word for word where you can |
Next step + date | Blank means there wasn't one. Be honest. |
Outcome | Paid, pilot, stalled or lost, and why |
After ten or so rows, read the "their words" and "why now" columns together. That's where your homepage headline and your outreach opener are hiding. When a deal goes cold anyway, IndieHunt's guide to running a lost-deal debrief when you only have a handful of customers picks up where this sheet stops.
A 14-day practice plan
Days 1–2: Write your one-page prep template, your discovery questions and the follow-up email skeleton. Build one realistic demo account.
Day 3: Run a full mock call with a friend playing a skeptical buyer. Ask them to interrupt and ask about price. Record it, with their OK.
Day 4: Watch it once. Note how long you talked before your first question and how many screens you showed. Cut both.
Days 5–10: Run three to five real calls. Use the agenda every time, even when it feels stiff. Send every follow-up within the hour.
Day 11: Read your notes sheet top to bottom. Which question got the best answers? Which screen made people lean in? Which objection came up twice?
Days 12–13: Change one thing (your opener, the demo order, how you say the price) and run two more calls.
Day 14: Count calls that ended with a dated next step. If it's under half, practice the close next, not the demo.
Traps to avoid
The feature tour. Showing everything so they "get the full picture." They won't remember it, and it tells them you didn't listen.
Discovery as a formality. If your demo would've been the same without the questions, you didn't really do discovery.
Selling the roadmap. "That's coming next quarter," five times. Sell what exists.
Price fog. Making them ask twice feels polite and reads as evasive.
Ending on vibes. A friendly call with nothing on the calendar is a nice conversation, not a deal.
Arguing with objections. When someone says it's too expensive, ask what they're comparing it to before you defend anything.
FAQ
How long should a first SaaS sales demo call be?
Thirty minutes: about ten for discovery, ten for a focused demo, and ten for questions and the next step. If they want to go deeper, book a second call with the people who'd use it daily.
When should I hire someone to run sales calls?
Not before your own notes can tell you who buys, why now, and which demo workflow gets them to yes. If you can't explain that to a new hire, they can't repeat it.
Your first few calls will feel clunky. That's normal. Run the agenda, ask more than you show, say the price plainly and leave with a date. And when you want more of those calls on your calendar, launching on Aura++ is one way to get your product in front of founders and early adopters who are already looking for new tools.