Personalized demos at scale

We reviewed a number of customer interviews to look at how other sales and marketing practitioners are approaching personalized demos in their go-to-market processes. The broad categories of personalization they needed are as follows:

• A specific prospect: Company name, logo, and sample data
• A buyer persona group: The story and the features you show
• A partner/reseller: Branding and partner workflows
• Another language: Product text, guidance, and narration

A personalized demo should help a prospect judge whether your product will work for them. Sometimes an account name and a relevant dataset are enough, but comparatively a partner selling a different workflow will likely need more than a logo swap.

In a perfect world, you would spin up a staging environment for that specific prospect, configure it, and personalize it as necessary. Unfortunately, presales teams can't do that for every single deal, and in a lot of cases the product setup simply takes too long. So the aim is to find a balance and save that setup for high-value, late-stage opportunities. For the rest, you need a way to reuse what you've already built.

Personalized demos for multiple use cases

Live sales calls, leave-behinds, and RFP responses are just a few ways to use a personalized demo.

Live sales calls

On a call, you need room to follow the conversation. A sandbox lets you open with the workflow you planned to show, then jump to a different one when the buyer asks about it.

A captured sandbox uses a copy of your product, separate from your live application. You can personalize it without configuring a fresh product account for each prospect. If the buyer needs to test an integration with their own systems or run new data through your backend, that's when a staging environment earns its keep.

Try the Salesforce sandbox below. Click Opportunities to move from the home screen to the sales pipeline.

Leave-behinds buyers can share

If you've taken the time to add a prospect's branding and sample data, you might as well send them the demo after the call too. They can revisit what you showed them and share it with colleagues who weren't there.

A guided demo is usually the better fit here. Add instructions to explain what the viewer is seeing and how it relates to the problem you discussed. In some cases, you may want to skip over clunky steps in a workflow.

HowdyGo's branding settings also let you choose the annotation fonts and interactive control colors.

If several workflows came up on the call, Collections lets you send the buyer a set of demos under one link. They can pass it around internally, and colleagues can choose the walkthroughs relevant to them.

RFP responses

When an RFP asks about a workflow, a short guided demo can show the evaluator how it works alongside your written response. Use the requirement number in the demo title and match the roles and sample data to the scenario the buyer has described.

For an approval requirement, show who can make the decision and where it's recorded. Add guidance that explains how those screens address the question, so the evaluator can follow the answer without a sales call.

Link to the demo from the relevant written answer where the submission format allows. If there's a live presentation too, keep those workflows available in your sandbox so you can work through follow-up questions with the evaluation team.

How to personalize a demo

Start with a demo you've already recorded. You can edit the captured product directly, ask AI to help with a larger set of changes, or use variables for details that change from prospect to prospect.

Replace a company name or logo

For a simple account or partner version, swap in the company name and logo. Turn on Edit UI, click the text or image you want to change, and enter the new text or upload the logo. In the sandbox editor, find-and-replace can update repeated text and images across the screens, so you don't have to chase down the same logo each time it appears.

Personalize the data with Edit UI

The data should make the buyer's problem easy to recognize. For a few changes, Edit UI lets you click captured text and replace it, including the labels and figures in a chart. Update the records or report values that matter to the conversation.

Keep the example consistent across the screens you'll show. If a record appears in a list and then in a detail view, use the same name and values in both.

This editing walkthrough shows how to change text in a captured screen.

Ask AI to help with bigger edits

Use Howdy AI when you have a list of names or records to update. Paste the values or attach a CSV with the old and new text, tell it which replacements you want, and review the proposed edits. This helps when you're swapping a list of sample records and don't want to edit each row by hand.

AI can also tailor the headings and comments to the prospect's company, role, and pain points. Work on a copy for an account-specific rewrite so you keep the generic version intact.

The AI walkthrough shows how to open the assistant and give it instructions.

Variables for details that change every time

Use personalization variables when reps need to personalize the same demo for lots of prospects. An AE can fill in the company fields and share a personalized link, using the same sandbox for each account.

Replace a captured company name with `{{company | your company}}`, then pass the company value through the share link. The fallback keeps the demo readable when no value is supplied.

We have also seen companies use variables to cater to particular personas. For example, one customer sold a product to CFOs, and the regulatory body responsible for an aspect of the data varied by market. Rather than using two separate demos, they swapped the body's name with a variable instead.

Build a master sandbox your team can reuse

Start with the workflows your reps already show on sales calls. Capture the main path and its branches, then link the screens so the rep can move between them and return to a familiar starting point.

Keep that master approved, with notes on its source, product release, and roles shown. HowdyGo also lets you insert screens from other sandboxes, so you can reuse an existing capture when you need to add another workflow.

Our interactive demo benchmarks found that most HowdyGo demos were built the same day they were created. Nearly nine in ten received their first external view within a week.

Different personas can use the same sandbox

An operations lead may want to follow an exception through to assignment and reporting. An executive sponsor might ask to go straight to the finished report. If both routes are available in the sandbox, the rep can adapt the conversation using the same environment.

Assemble a tailored story from existing screens

Choose the screens that answer the buyer's question. In HowdyGo, you can copy one or several steps from another demo, reorder them, and append a new capture where the existing material stops answering that question.

For the recording steps, use the interactive walkthrough guide.

Create partner and language versions from your master

Make a separate sandbox version when it needs a different set of workflows or edits that must stay specific to a partner or language. A partner marketer can own the branding and sample-data edits, with an SE helping on new workflow captures.

Match the partner's branding and workflow

One team we spoke to needed demos with different partner colors and workflows. Reuse the screens partners have in common, then capture any different roles or approval steps.

Check which colors and layout elements the editor can change inside the product. If it can't reproduce a partner's theme or screen arrangement, capture the configured product.

Translate the UI and narration

A language version of a sandbox needs its captured product text reviewed, including dates, currencies, and labels that have grown too long to fit. Check the linked destinations too, so the buyer stays in the intended language as they move around.

For a guided demo, Howdy AI translation covers headings, comments, overlay button labels, opt-in text, and text in the captured product UI.

The docs recommend duplicating the demo before translation if you want to keep the original language. Assign a reviewer to each language copy. When the script changes, regenerate or revise its narration too; translating a tooltip doesn't update the audio that describes it.

Refresh only the screens that changed

When a release changes a screen, replace it in the master and in the partner or language versions that use it. Reapply any branding or translated text on the replacement and check its navigation links. You can keep the rest of each demo.

On Enterprise, you can save an approved version before editing and roll back with version history if needed.

Routine edits tend to be quick. Our interactive demo benchmarks found that 92.6% of maintenance editing sessions took less than 15 minutes. Those are individual editing sessions measured at least seven days after a demo was created.

Start with a sandbox for your next sales call

Choose a workflow you already show on sales calls and capture it as a HowdyGo sandbox. Add the other routes buyers commonly ask about, then personalize the company details with variables.

Have a rep use it on a call. For the leave-behind, put the key points into a short guided demo the buyer can share with colleagues. When a product update changes a screen, check every partner or language version that uses it, including the links into and out of that screen.

HowdyGo's sandbox add-on costs $99/month on top of a Pro or Enterprise plan, with a free trial available. Try a sandbox for your next sales conversation.