Remote Selling Skills
You can know your product well and still give a remote demonstration that is hard to follow. The buyer may be looking at a small screen, trying to follow your cursor or thinking about a question while you have already opened another page.
Remote selling skills help you manage those moments. You need to understand what the buyer wants to do, show the relevant detail and leave enough room for them to respond. These are things you can practise with a colleague before the next call.
We'll use a hypothetical example: you sell scheduling software to a company that sends technicians to customers' homes. The office needs to fit urgent visits around appointments already booked. The software and conversations below are examples, not claims about a particular product.
Find the task you need to demonstrate
“Scheduling is difficult” isn't enough to choose a useful demonstration. Ask about an actual incident:
You: “What happened the last time an urgent job came in?”
Buyer: “We had to move another visit. The office called three technicians before finding someone available.”
You: “Which part took the most work?”
Buyer: “Finding a free slot without moving a customer who had already taken time off.”
Now you know what to show: how the dispatcher, the person arranging the visits, can see existing appointments and find an appropriate opening. Opening the invoicing settings would not answer this question.
Summarize before opening the example: “So the difficult part is finding an available technician while keeping the appointments you've already agreed. Have I understood that correctly?”
Salesforce's soft-skills training gives examples of listening and checking your understanding during sales conversations. The useful skill is noticing which detail should change what you show next.
Try it: ask a colleague to describe a problem without naming the feature they want. Follow one detail, then say which part of your offer you would show and why. Let them correct your understanding before continuing.
Make the shared screen easy to follow
Prepare the page, document or demonstration before the call. Use sample data rather than another customer's private information. Open the material you need before the buyer joins, so they don't have to wait while you search through unrelated tabs.
In the scheduling example, prepare a few appointments and an urgent visit to discuss. Show enough of the day's schedule to explain the choice, then focus on the times and technicians involved.
A buyer needs to see the context as well as the detail. Zooming into a single appointment may make its text readable but hide the other visit that prevents you from moving it. Explain what they are looking at: “These are the afternoon appointments for the two technicians we're considering.”
If you are already speaking by phone, Screen Share lets you add that view to the conversation. You install the Chrome extension, choose a tab or window, check the preview and send the viewing link. The buyer watches in a browser without installing anything or creating an account. You operate the software; the voice conversation stays on your existing call. The setup guide shows the steps.
Check the view after they join: “Can you read the appointment times?” If they cannot, enlarge the relevant part or show a simpler document. Once the view is readable, move the pointer to the item you name rather than moving it around while talking.
Try it: have a colleague join from the kind of device your buyers use. Ask them to find the two appointment times you mention. If the labels are too small or they cannot tell which item you mean, adjust the view and try again.
Explain one action, then hear the response
Tell the buyer what you are about to change before clicking. In our example, suppose the software lets the dispatcher move a visit and see a clash with another appointment.
You could say: “I'll put the urgent visit at two o'clock for Sam. Notice that it overlaps with the appointment already booked.” Make the change, then pause so the buyer can look and respond.
This gives them a chance to explain a requirement you had not heard: “We also need time for the technician to drive between the jobs.” Now you can check how your product handles that. If it does not account for travel time, say so rather than treating an empty calendar slot as proof that the visit fits.
Connect the action to the work it helps them do. Moving an appointment is a feature. Finding a suitable technician while keeping an existing customer's appointment is the result this buyer cares about. Explain that connection, then show what the dispatcher still needs to check. When discussing setup, explain who enters the existing appointments and helps the team learn the process.
Gong's guide to product demonstrations argues for explaining the buyer's particular problem without adding unnecessary complexity. That doesn't mean hiding a limit. Here, travel time affects whether the schedule works, so it belongs in the discussion.
Clarifying a question is another skill to practise. If the buyer asks, “Can we move it?”, don't immediately start dragging the appointment. Ask what they mean:
- A different time: check how the appointment can be rescheduled and what else it affects.
- A different technician: show reassignment if the product supports it.
- A different day: check the customer's agreed date and how the change would be handled.
You do not have to demonstrate every possibility. Clarify their question, show the relevant action and check anything you cannot answer. “I'll confirm how that works” is useful only when you also agree who will check and when you'll respond.
Try it: ask a colleague to interrupt with an ambiguous question during the demonstration. Practise clarifying it before opening another screen. Then explain one action and give them room to reply.
Practise a short call and fix one thing
Put the skills together in a role-play. One person is the buyer; the other uses the actual materials and sharing setup they plan to use on a call. The buyer can change one requirement, ask an unexpected question or say that a label is difficult to read.
Afterward, check observable actions:
- Did you follow a specific detail instead of guessing the problem?
- Did you choose an example that addressed it?
- Did you explain the useful result and the work still required from the buyer?
- Could the buyer read the information needed to judge the example?
- Did you explain what you were changing and pause for a response?
- Did you clarify an unclear question and acknowledge anything unknown?
- Did both people understand the next action?
In the scheduling example, a useful next action might be a review with the person who arranges the real visits. Agree which scheduling question to check and when to meet. A compliment about the demonstration is not the same as agreeing to do that work together.
Choose one weak part of the practice call and repeat it. If you spent too long finding the right page, practise navigating there. If your colleague could not follow the change, practise explaining that one action. You don't need to restart the whole presentation to work on one skill.
Try the viewing setup before your next call
Have a colleague join your Screen Share link and check the example from their side. Make the text readable, practise the explanation and stop sharing when finished.
Install Screen Share for Chrome