Software sales has a habit of making reps believe the product will do the talking. The demo looks good, the feature list is strong, so the call itself gets less attention than the slides. Then a buyer asks "why now?", a technical contact asks about security, or a finance director asks what the payback is, and the rep realises the real selling happens in the conversation around the product.
This article covers the phone and video-call moments in B2B software and SaaS sales that are worth rehearsing aloud, with a drill for each.
What makes software calls different
- Several people buy. A single champion rarely signs alone. A technical reviewer, a budget holder and often a user team all have a voice.
- The cost of change is the real competitor. Often you are not up against another vendor. You are up against a spreadsheet, a workaround or doing nothing.
- Buyers research first. They have seen your website and probably a competitor's. Reciting features adds nothing they could not read.
- The sale is a sequence of calls. Each call has to earn the next one, so each must end with a specific, agreed step.
- Questions are technical and commercial at once. Within a single call you can be asked about integration, price and risk.
Six calls to rehearse
1. Discovery with an analytical buyer
Analytical buyers answer questions precisely and expect you to ask precise ones. They are quickly bored by a rep who asks generic questions or jumps to the demo.
Drill: the customer answers briefly and factually, and gives nothing extra. You may not mention a feature until you can say, in one sentence, what the problem costs them in time, money or risk, and they agree with your sentence. The scenario for analytical discovery of business needs is built on this.
2. The technical gatekeeper
Before anything goes further, someone in IT or security wants to know how your product handles data, access and integration. Evasive or over-confident answers stop deals.
Drill: the customer asks three pointed questions in a row about security. Practise answering what you know plainly, saying "I'll confirm that and come back to you by Thursday" for what you do not, and then actually proposing who should talk to whom. Never improvise a technical claim. See the technical security review scenario for the shape of this conversation.
3. The price conversation with an analytical buyer
After a proposal, a careful buyer will examine the numbers. Defending a discount is the weak response. A better one asks what they are measuring the price against and which part of the value they doubt.
Drill: the customer says the licence is 30 percent above what they expected. You may not offer a concession in the first round. Ask what the expectation is based on, and restate the value in their own words. The price scenario with an analytical buyer lets you practise this directly.
4. The business case for the finance director
A finance director does not need to hear about features. They want to know what changes in the numbers and how sure you are.
Drill: you have five minutes with a finance director who interrupts. Connect your product to one outcome that matters to the business, say what you would need to know to estimate it, and admit what you do not yet know. Avoid quoting percentages you cannot support. The business case scenario is a good rehearsal.
5. The multi-stakeholder call
When three people join a call with different priorities, the loudest voice often wins airtime. A good seller makes sure each person hears something relevant to them.
Drill: three simulated roles with competing concerns, such as ease of use, cost and risk. Name each person's concern back to them before you answer anything. Then summarise where they agree. See the multi-stakeholder panel scenario.
6. Closing with a next step, not a signature
In many SaaS deals, a call does not close the deal. It closes the next step: a pilot, a security review, a meeting with finance. Many reps leave this vague.
Drill: end the call by stating what was agreed, who owns each action and by when. Ask the customer to confirm. The close scenario for a decision panel rehearses this.
A simple structure for software discovery
When you do not have a script, this order is hard to beat.
- Context: how does the customer do this work today?
- Problem: what is not working, and for whom?
- Impact: what does it cost, in time, money or risk?
- Decision: who decides, by when, using what criteria?
- Summary: repeat it back in one or two sentences.
- Next step: a specific action with a date.
You earn the right to demo only after steps one to five. If you want a fuller walkthrough, read how to prepare for a discovery call.
How to practise without wasting your pipeline
Real prospects are expensive. Practising on them means every mistake costs you a lead. A safer way to build the habit is to rehearse out loud against a realistic customer before the call that matters.
DIRI AI lets you do that by voice. The AI plays the customer, whether sceptical, analytical or short of time, and afterwards produces a report with key moments and one suggestion for the next attempt. It plays only the customer, never the seller, and it will not tell you what your product can do. Pair it with a quick written note after each session: one phrase you want to keep, one you want to drop. There is more on setting up a software-focused routine on the SaaS demo practice page, and a wider view in cold call practice without burning leads.
A one-week routine
- Monday: discovery with a terse analytical customer. Aim for a clear problem statement.
- Tuesday: a security question round. Practise saying "I don't know yet, here is how I will find out".
- Wednesday: price pushback without offering a discount.
- Thursday: a five-minute finance conversation.
- Friday: a group call, ending with owners and dates.
Short sessions, repeated, do more than a single long workshop. After each one, write down the one thing you would change.
Related: Renewal and Upsell Call Practice for Account Managers, Cold Call Follow-Up Calls: How Often and What to Say, Telecom and Subscription Calls. Free tool: Sales Glossary.
Try it on your hardest call
DIRI AI has a Free plan: 3 voice calls a month of up to five minutes each, with a report afterwards, and no card needed. Start free, pick the software call you dread most, and run it against an AI customer today.