Creating Sandbox Demos

Steps

1. 1Step 1 of 4

   What and Why Sandbox Demos

   Sandbox demos simulate real product usage in a safe, controlled environment. They are best suited for complex products where guided demos alone don't fully convey flexibility or depth.

   • Tip: Focus on core workflows
   • Tip: Design for exploration with guardrails
   • Recommended: Pair sandboxes with a short guided intro
   • Recommended: Start narrow and expand over time
   • Pitfall: Exposing unstable or incomplete features
   • Pitfall: Assuming users know where to start
   

   Prefer to read? Expand to read the lesson

   What Are Sandbox Demos?

   Sandbox demos simulate real product usage in a safe, controlled environment. They give prospects and users a hands-on experience with your product without affecting live data or requiring account setup.

   When to Use Sandboxes

   Sandboxes are best suited for complex products where guided step-by-step demos alone don't fully convey the flexibility or depth of your platform. If buyers need to test real workflows, explore configurations, or evaluate technical capabilities, a sandbox delivers what static demos cannot.

   Designing for Exploration

   • Focus on core workflows that demonstrate the most value
   • Add guardrails to prevent users from getting lost or stuck
   • Pre-populate realistic data so the sandbox feels like a real environment
   • Include clear starting points and suggested paths through the product

   Common Mistakes

   The two biggest pitfalls are exposing unstable or incomplete features (which undermines confidence) and assuming users know where to start (which leads to confusion and abandonment). Always pair your sandbox with a brief guided introduction that sets context.

2. 2Step 2 of 4

   Tips for Sandbox Cloning

   Clone only what's necessary to demonstrate value: key screens, workflows, and realistic data states. Remove unrelated features to reduce cognitive load.

   • Tip: Limit scope to high-impact flows
   • Tip: Use realistic but anonymized data
   • Recommended: Optimize for clarity over completeness
   • Recommended: Validate sandbox flows with sales or SEs
   • Pitfall: Overbuilding the sandbox
   • Pitfall: Including edge-case functionality
   

   Prefer to read? Expand to read the lesson

   The Art of Selective Cloning

   When building a sandbox demo, resist the temptation to clone your entire product. Instead, clone only what is necessary to demonstrate value: the key screens, workflows, and data states that matter most to your audience.

   Scoping Your Sandbox

   • Identify the 3–5 most important workflows for your target audience
   • Clone only the screens and features needed to support those workflows
   • Remove or hide unrelated features to reduce cognitive load
   • Use realistic but anonymized data that matches your typical customer's setup

   Data Strategy

   The data in your sandbox should tell a story. Pre-populate dashboards, reports, and lists with realistic data that demonstrates the value of your product in action. Anonymize everything to avoid privacy concerns while keeping the data believable.

   Validation

   Before sharing a sandbox externally, validate the flows with your sales team or solutions engineers. They can identify gaps, confusing paths, or missing data that would trip up a prospect. Optimize for clarity over completeness. A focused sandbox beats a comprehensive but overwhelming one.

3. 3Step 3 of 4

   Editing and Maintenance

   Sandbox demos require ongoing upkeep to stay aligned with production. Assign clear ownership and review sandboxes regularly to avoid broken or outdated experiences.

   • Tip: Schedule quarterly reviews
   • Tip: Document sandbox-specific changes
   • Recommended: Tie sandbox updates to product releases
   • Recommended: Retire unused or outdated sandboxes
   • Pitfall: Forgetting to update after product changes
   • Pitfall: Losing track of sandbox versions
   

   Prefer to read? Expand to read the lesson

   Why Maintenance Matters

   Sandbox demos require ongoing upkeep to stay aligned with your production product. An outdated sandbox that shows old UI, missing features, or broken workflows actively undermines buyer confidence.

   Establishing Ownership

   Assign clear ownership for each sandbox. Without a designated owner, sandboxes drift out of date quickly. The owner is responsible for reviewing and updating the sandbox on a regular cadence.

   Maintenance Cadence

   • Schedule quarterly reviews to check that all workflows still function correctly
   • Tie sandbox updates to product releases. When the product ships changes, update the sandbox in the same cycle
   • Document sandbox-specific changes so team members can understand what was modified and why

   Version Management

   Keep track of sandbox versions and their corresponding product versions. When multiple sandboxes exist for different audiences or use cases, maintain a central record of which sandbox covers which workflows and when it was last updated.

   Retirement

   Retire unused or outdated sandboxes proactively. A stale sandbox that a prospect accidentally encounters does more harm than having no sandbox at all.

4. 4Step 4 of 4

   Sharing

   Share sandbox demos selectively with prospects, partners, or customers. Provide a clear starting point to prevent unstructured exploration or confusion.

   • Tip: Add a guided entry point
   • Tip: Set expectations for what to explore
   • Recommended: Pair sandboxes with a leave-behind demo
   • Recommended: Follow up based on engagement
   • Pitfall: Dropping users into an empty state
   • Pitfall: No contextual guidance
   

   Prefer to read? Expand to read the lesson

   Sharing Strategically

   Sandbox demos should be shared selectively, not broadcast widely. Target specific prospects, partners, or customers who will benefit from hands-on exploration.

   Setting Up for Success

   When sharing a sandbox, always provide context:

   • Include a guided entry point that shows users where to start
   • Set clear expectations for what they should explore and what value they will discover
   • Pair the sandbox with a short leave-behind demo that provides a guided overview before users explore freely

   Avoiding Empty States

   The worst experience is dropping a user into an empty or unfamiliar state with no guidance. Every sandbox share should include:

   1. A brief intro explaining what the sandbox contains
   2. A suggested starting point or workflow to follow
   3. Key areas to explore and what to look for

   Following Up

   Use engagement data to follow up intelligently. If a prospect spent significant time in specific areas of the sandbox, reference those areas in your follow-up conversation. This shows that you are paying attention and creates a more personalized buying experience.