Rehearse a sales demo by checking share scope, private windows, audio, slide control, and the viewer’s screen before the meeting.
Key takeaways
- Share the application, not the screen. When you share a specific application, others can't see anything other than the shared application, according to Cisco.
- Mute all system sounds. All sound from your computer, including notifications, will be audible in the meeting, according to Microsoft.
- Route video audio correctly. Check the Share your computer audio box so that the video sound comes directly through the audio conference, according to Cisco.
- Know the presenter limits. There can be a maximum of 10 simultaneous presentations in a meeting at a time, according to Google.
- Coordinate huddle sharing. Up to two people in a huddle can share their screen at a time, according to Slack.
Check share scope, privacy, audio, control, and viewer view before demo rehearsal
Before your meeting, mute notifications and close any personal or sensitive documents, according to Cisco. This step protects the viewer from seeing unrelated content during the screen share. The five checks in this guide are editorial recommendations for your recurring rehearsal routine. They are not an official standard or a certification requirement. Use them to verify what the viewer sees and hears before handing control back to the rep. Start by confirming whether the rep shares the whole screen or just the demo application. Next, scan for visible private information that might remain on the desktop. Then test the audio to ensure the rep’s voice is clear and notification sounds are muted. Finally, review who can control the slides. These checks help you catch issues before they reach a live customer. Keep the focus on the specific tool your team already uses. Do not compare vendors or assume every product hides notifications automatically. The distinction between sharing a whole screen and sharing a single application is critical for privacy. Your goal is a clean, professional demo experience where the viewer’s attention stays on the product. By running these checks consistently, you build a reliable rehearsal process. You can schedule the habit with Recurring sales practice: 5 checks to schedule. This supports your team’s coaching goals and ensures reps are prepared for live interactions. Review that rehearsal on the Sales One-on-One Agenda for Coaching Software Sellers. The primary next action is to close sensitive windows and mute notifications before the next session. Write down the single application the rep should share to maintain focus. This simple step reduces the risk of exposing unrelated windows or notifications. It also clarifies the scope of the share for both the rep and the viewer. Use this section as a quick reference before each rehearsal. The checks are designed to be fast and practical. They fit into your existing workflow without adding significant overhead. Focus on the viewer’s perspective to identify potential issues. If the viewer sees something they should not, the rep needs to adjust their setup. This feedback loop improves the quality of the demo over time. Keep the process simple and consistent for your team. The goal is to reduce anxiety and errors during live demos. By addressing these five areas, you create a safer and more professional environment. This supports your role as a front-line manager in a B2B software sales team. The checks are specific to the task of running a recurring software-demo rehearsal. They are not a general guide to screen sharing. Stick to the scope of your team’s current tools and practices. This ensures the advice is relevant and actionable. Use the checks to prepare the rep for the specific demo they will run. See Sales rep practice goals: 5 checks to write today before the rep writes the practice aim. This targeted approach helps the rep focus on the product message. It also prevents distractions from unrelated windows or notifications. The viewer’s experience is the ultimate measure of success. If the viewer is distracted by a pop-up or a personal document, the demo fails. By checking these five areas, you minimize the risk of such distractions. This allows the rep to deliver a clear and focused presentation. The process is simple but effective. It requires only a few minutes of preparation before each rehearsal. This small investment of time can significantly improve the quality of your team’s demos. Use the checks as a standard part of your rehearsal routine. This consistency helps reps build good habits. It also makes it easier to identify and fix issues quickly. The goal is to create a smooth and professional demo experience. This supports your team’s sales goals and customer relationships. By focusing on the viewer’s perspective, you ensure the demo is engaging and effective. The checks are designed to be easy to implement and maintain. They do not require any new tools or software. They simply require attention to detail and a clear process. Use them to prepare your reps for success. This is a practical and effective way to improve your team’s demo quality.
Choose the application and check private windows or notifications
For the first two checks, decide whether the rep shares the whole screen or a single application, then scan for visible private information. These choices determine what the viewer sees during the rehearsal.
Whole screen or application The core difference is visibility. When you share a specific application, others can't see anything other than the shared application, according to Cisco. This limit applies to Cisco. For a software demo, sharing the specific application keeps the focus on the product interface. It prevents accidental exposure of unrelated work items. The rep should select the demo application before starting the share.
Visible private information Your audience won't see the chat window in your shared screen, according to Microsoft. This rule applies to Microsoft Teams. However, this does not mean all private information is hidden. Notifications, pop-ups, or other windows outside the shared application may still appear if the rep shares the full screen. The manager should instruct the rep to close sensitive windows before the rehearsal. This includes email clients, personal documents, or unrelated project files. The check is simple: look at the screen as the viewer would see it. If any private data is visible, the rep must close it or switch to application-only sharing.
Editorial Recommendation Treat these as standard rehearsal steps. Do not assume every platform hides notifications or private windows. The screen and application distinction is critical. A full screen share exposes everything on the desktop. An application share limits visibility to that specific program. Use the viewer's perspective to verify what is actually visible. Close sensitive windows and mute notifications before starting the share. This practice reduces the risk of exposing unrelated information. It keeps the demo focused on the software being presented. The manager should confirm this step with the rep before the live rehearsal begins.
Test audio and understand who can share or control slides
Audio routing depends on how you start the share. If you present a Chrome tab, it shares that tab's audio by default, according to Google. For video content that plays from a file or application rather than a browser tab, check the Share your computer audio box so that the video sound comes directly through the audio conference, according to Cisco. During your rehearsal, have the rep play the demo video with the audio box checked, then listen from your side to confirm the sound travels through the conference channel instead of staying local to the rep’s machine. If the viewer hears only silence while the video plays, the audio is not routing through the call, and the rep should adjust the setting before the next run.
Control limits vary by the tool the rep uses. In Microsoft Teams meetings, you can easily transition during a presentation by sharing control of PowerPoint slides with up to 20 people, according to Microsoft. However, slide control is only available during presentations started from Teams for desktop, according to Microsoft. In Slack huddles, up to two people can share their screen at a time, according to Slack.
Reference table of screen-sharing rules by publisher
The following table lists five documented vendor rules: a Google 10-presentation ceiling, Teams slide control, and three Cisco rules. Each row summarizes a documented rule or capability, providing a concrete reference for the specific aspect of the screen share you are verifying. These entries are documented vendor rules, not vendor comparisons or rankings.
| publisher | documented rule or capability | qualification | use in today's practice |
|---|---|---|---|
| A maximum of 10 simultaneous presentations can occur in a meeting at a time. | This limit applies to the number of concurrent presentations, not the total participant count. | Suggest checking if multiple reps are presenting simultaneously to avoid exceeding this ceiling. | |
| Microsoft | You can share control of PowerPoint slides with up to 20 people. | This limit applies specifically to PowerPoint slide control during a presentation. | Suggest limiting the number of people with slide control to maintain order during the demo. |
| Cisco | Check the Share your computer audio box so that the video sound comes directly through the audio conference. | This setting routes video audio through the conference audio channel. | Suggest enabling this box to ensure the demo video audio is heard by all participants. |
| Cisco | When you share a specific application, others can't see anything other than the shared application. | This applies when a specific application is selected for sharing. | Suggest using application-specific sharing to isolate the demo software from other desktop windows. |
| Cisco | Before your meeting, mute notifications and close any personal or sensitive documents. | This is a preparatory step recommended before starting a share. | Suggest making this a mandatory pre-check for the rep before the rehearsal begins. |
Use this table to verify the specific constraints of the tool your team uses. If your software is not listed, apply the same editorial logic: check the scope of the share, the audio routing, and the control permissions before the rep begins.
Run the 5 checks from the viewer’s perspective
The final check asks you to sit where the buyer sits. You are not watching the rep’s cursor; you are watching the image the viewer receives. In a recurring rehearsal, the viewer is often you, the manager, or a peer rep observing the demo. Your job is to confirm that the visual feed matches the intended narrative. If the rep shares the entire desktop, the viewer sees everything on that desktop. For a single application, use Cisco’s application-share rule instead of assuming every tool hides other windows. You must verify which mode is active before the rep begins speaking.
According to Google, your screen zooms to 80% within the presentation. This specific behavior applies to the screen zoom feature in Google Meet. It is not a general quality threshold for all video calls. It is not a guarantee that the image will be sharp enough for every monitor size. It is a documented setting for how the shared screen scales inside the presentation view. When you run this check, look at the shared screen in your own client. Does the text remain readable? Does the layout distort? If the rep’s demo relies on small text, this zoom level may make it difficult for the viewer to read.
Illustrative example of a five-check pass
You and the rep run five checks before a practice demo. You name one application to share and close two other windows. You mute notifications, then play a short clip and listen for sound on the call. You leave slide control with one person. You watch the shared image and confirm the text is readable. You write the application name in your notes and stop. The pass stays inside these five checks.
Choose one demo application and close sensitive windows today
This direct action prevents the exposure of unrelated content during the live session. According to Cisco, before your meeting, mute notifications and close any personal or sensitive documents. This recommendation applies specifically to the "Share content in meetings and webinars" context.
Mute all non-essential notifications on the shared device. This includes email alerts, chat messages, and system updates. These interruptions can distract the viewer and potentially reveal private information. Muting them ensures that the audio and visual experience remains focused on the demonstration.
FAQ: sales demo screen-sharing rehearsals
Should a rep share the full screen or just an application?
Share a specific application to hide other windows, as Cisco notes that others can't see anything other than the shared application. Google also advises sharing a new window or a specific tab instead of the meeting window to prevent mirroring. This approach keeps the viewer's focus on the demo content.
Can viewers hear notification sounds?
Yes, computer audio including notifications is audible in Microsoft Teams, where all sound from your computer will be heard in the meeting. In Google Meet, if you present a Chrome tab, it shares that tab's audio by default. Mute notifications before sharing to avoid unintended audio.
Can two people share screens at the same time?
Yes, up to two people in a huddle can share their screen at a time, according to Slack. Google Meet supports a maximum of 10 simultaneous presentations in a meeting at a time. Check your specific platform's limits before planning multi-presenter segments.
Can I let another person control the slides?
Yes, Microsoft Teams allows sharing control of PowerPoint slides with up to 20 people, but this feature is only available during presentations started from Teams for desktop. This is distinct from remote desktop control. Verify your desktop version supports this before relying on it.
How can I check what a viewer is actually seeing?
Avoid sharing the meeting window itself, as Google recommends sharing a new window or specific tab to prevent mirroring. Your screen zooms to 80% within the presentation in Google Meet, which affects how content appears to viewers. Test the viewer's perspective before the rehearsal to confirm clarity.
Reading references
Found an error on this page? Corrections explains how to report it.