By Touchbase Technologies · Published 2026-11-05

Prepare safe sample data for a public product demo

Before recording a public product demo, create a dedicated demo workspace with fictional records and disabled live actions. Prepare enough data to show one complete task, check everything the recording could reveal, then review the exported video before publishing. A blurred name on one screen is not a complete plan if the next click reveals a real address, private note or live campaign.

The goal is a believable walkthrough with a controlled outcome. This is a production checklist for founders making marketing footage, not a guarantee that a particular workspace or recording tool removes sensitive information automatically. Use your organization's own review requirements where they apply.

An original demo preparation illustration showing fictional records, disabled live sends, one controlled task and an export review before publication.

Define the task before creating records

Choose one action a viewer should understand by the end. “Create a targeted customer campaign and review the draft” is a useful task. “Show every tab in the platform” is likely to produce a long recording with little explanation of why any screen matters.

Write the starting state, the action and the visible result. For a fictional campaign demo, the starting state might be six sample contacts in a clearly labeled audience. The action is choosing a design and drafting an invitation. The result is a saved draft with a recipient preview. There is no need to send a real email to demonstrate that sequence.

Keep the example aligned with your product. If you sell a tool for equipment-rental teams, use sample equipment and return records. An empty account or a generic spreadsheet labeled “software” makes it harder for viewers to recognize the job your product does.

Build a small, coherent sample dataset

Create fictional people and businesses from scratch rather than replacing names in a customer export. Real exports can retain private text in notes, custom fields, attachments or activity histories. Changing the most visible name leaves those other fields untouched.

Use a sample-data label that remains visible when useful, such as “Demo workspace — fictional records.” If you show an email address, use a documentation domain such as example.com. IANA maintains example domains for illustrative use; they are not production infrastructure for sending or receiving demo messages. Keep the demo's live email actions disabled.

Sample record	Purpose in the walkthrough	What to prepare
A customer prospect	Show the intended campaign audience	Fictional name, role and relevant product context
An existing customer	Demonstrate an audience exclusion	A clearly different relationship label
An opted-out contact	Show that the preview excludes it	A visible exclusion state without a real address
A draft campaign	Show the editable output	A subject, body and safe example links

Give the records consistent dates and states. A contact created after the campaign was supposedly sent can distract a viewer and undermine an otherwise useful explanation. Do not display made-up revenue, customer logos or outcomes as if they were real traction. Label illustrative numbers where they appear.

Disable actions that could reach real systems

Review email sending, campaign schedules, social publishing, payment actions, outbound webhooks and CRM updates before recording. A demo account with a connected production mailbox can still send a message if you click the wrong control. Removing a recipient from the first screen does not prove all background actions are disabled.

For a simple marketing recording, show a saved draft or a preview instead of a live send. If the workflow requires an integration, use a permitted test environment and clearly explain what is simulated. Do not manufacture a successful delivery or integration result in the footage. A truthful “This is where you review the recipients before sending” is enough to explain the step.

Write a short reset checklist: restore the six contacts, remove the previous draft, return to the starting page and confirm schedules remain off. Repeating a recording should not accumulate duplicate campaigns or change the example halfway through your script.

Prepare the recording surface

Close unrelated tabs and documents. Check your browser profile, bookmarks bar, account menu, autofill suggestions, desktop notifications and password-manager overlays. A private detail can appear outside the app even when the app's sample records are clean.

Choose the smallest capture surface that demonstrates the task. MDN's screen-capture documentation describes a browser permission prompt for selecting a display or part of it, such as a window. Available choices and audio support vary by browser. Check the actual selected surface rather than assuming the recorder captures only the page you intended.

If you plan to narrate, record a short sample and listen before the full take. Chrome has separate camera and microphone permissions; a permission being allowed does not prove the correct microphone is selected or the sound is clear. Turn off notifications before recording and avoid opening account menus during the take.

Rehearse a useful 60-second sequence

For the fictional campaign example, use this sequence: show the audience label, explain why these prospects are relevant, open a new campaign, choose a design, edit the subject and preview the message. Finish at the saved-draft state. Spend more time explaining the customer's task than reading button labels aloud.

One natural line is: “These are sample contacts for a product-demo invitation. I'll choose the audience first, then review the message and recipients before anything sends.” It explains the outcome without promising that finding contacts guarantees a sale. Keep the recording honest when a step takes time; you can edit a wait, but do not make an asynchronous process appear instantaneous without context.

Review the exported file, not only the live screen

Watch the final video from start to finish at the size people will see it. Pause on account menus, tooltips, notifications and link previews. Check the opening frame and thumbnail as well as the main sequence. A private detail can be present for a fraction of a second and still be visible when paused.

Listen for unintended background audio and check that captions do not introduce a false product claim. Confirm the final call to action reaches the correct public page. If the video includes a share link, verify what a signed-out viewer can open. Correct the source data and re-record when practical rather than relying on a blur that might miss the next frame.

Use Touchbase with the same review discipline

Touchbase's screen demos help turn a recorded workflow into a demonstration you can share. Prepare your sample workspace first, then record the task and review the result. Free includes one short watermarked screen demo; paid plans and processing credits have their own allowances. Screen demos and whiteboard videos are different features: whiteboard rendering requires Business or an eligible higher plan.

Use the screen-demo script guide to plan the narration, or the whiteboard-versus-screen-demo comparison to choose the format. Check current plan details before a recording session so the intended processing fits your available usage. Credits do not remove the need to review the data and the final video.

Keep a reusable recording kit

Save the sample dataset, starting-state checklist, script, capture dimensions and review notes together. The next feature update then starts from a controlled workspace rather than a live customer account. A good demo kit makes repeat recordings easier while keeping the story focused on what the viewer can accomplish.

Prepared with AI assistance and checked against the sources linked in this guide.