Skip to main content
A leave-behind should help someone revisit the value you discussed and share it with a colleague. Start with the buyer’s question, not a tour of every feature.

Build the story

Choose one outcome and use the planning brief. For example, if a buyer asked how a team handles an exception, show the exception, the action, and the result. Explain what changes for the team at each point. If stakeholders need different paths, offer clearly named choices and test each ending. Use approved sample data. If a personalized introduction helps, define a variable with a useful default and test both the default and the audience-specific value. Personalization should make the story relevant; it should not expose private information in a share URL. See Personalize a demo.

Example: answer one buyer question

If a buyer asks how their operations team handles an exception, show the exception queue, the action a teammate takes, and the resulting status. A guide can say “Assign this order to a teammate” followed by “The owner and status are visible to the team.” Finish with a next step the buyer can take, such as reviewing a related workflow. This is more useful than sending a generic tour that requires them to remember which feature answered their question. Before sharing, check the perspective of the colleague who was not on the call. Define unfamiliar terms in the demo, make the reason for the first action clear, and remove claims that rely on conversation context. If an account-specific value appears in one guide, check the rest of the captured screens for conflicting names or logos. A neutral demo is better than inconsistent personalization. Publish the reviewed draft, then create a named link under Share → Link. Where available and appropriate, set a password, expiration, or view limit. Open the link in a separate browser session and confirm the intended values, access, and ending before sending it. A link can be forwarded. Use restrictions appropriate to the material, and do not assume a private share link requires a workspace login. If the recipient needs a copy for a different audience, review the access and content again. Keep the link name meaningful to your team, for example by pairing an account or campaign with the workflow. Names help you distinguish links in ArcDemo; they do not prevent forwarding. If the link expires or reaches its view limit, the recipient needs a working replacement, so check access before an important meeting or follow-up.

Follow up with evidence

Use the named link and demo analytics to understand whether the experience was opened and where viewers interacted. A view does not by itself establish buying intent, identity, or agreement. Use the signal to prepare a useful question, then combine it with your conversation and other context. For a live call instead, see Present a demo live.