Every seller on a small team ends up with their own demo. One recorded last quarter, one with a prospect's name still in it, one that skips the feature the buyer asked about. A shared library gives every seller the same set of current demos to send.
For more on this topic, read How Product-Led Teams Can Use an Interactive Demo Before the Trial.
Short Answer
Keep one shared set of short demos, organized by use case, with one owner and a clear rule for what sellers may change.
- List the flows buyers ask about most.
- Record one short demo per flow in a shared workspace.
- Let sellers make their own buyer-specific versions, and keep the library versions clean.
Why a Library Is Harder than It Looks
- Sellers record their own because the shared one is out of date.
- Nobody knows which version is current.
- Buyer-specific edits leak into the shared version.
Organize by Use Case
| Use case | Demo | Owner |
|---|---|---|
| Core result | Homepage demo | Marketing |
| Most-asked feature | Feature demo | Product marketing |
| Common objection | Flow that answers it | Sales lead |
| Setup and onboarding | Setup demo | Support |
Keep the library small. A seller should find the right demo in seconds.
Set the Rules
- Library demos are edited only by their owner.
- Sellers make their own demos for buyer-specific versions. See personalizing a demo without a sandbox.
- Every library demo uses the shared brand kit.
- Every library demo is reviewed at each release. See keeping demos up to date.
Share Access Inside the Team
In a Proovyt Team workspace, owners and admins see every demo. Members see their own and ones shared with them. A demo's owner can share it with a teammate and take access back. Admins can turn member demo creation on or off.
An Illustrative Worked Example
This example is hypothetical. A four-person sales team has a dozen personal demos between them.
- The sales lead lists the five flows buyers ask about most.
- Product marketing records one demo per flow in the Team workspace and shares them with every seller.
- Sellers record their own versions for specific buyers.
- Personal demos that duplicate the library are retired.
- At each release, owners check their library demos.
The Old Way Versus a Better Way
| Old way | Better way |
|---|---|
| Each seller records their own demos | One shared library, one owner per demo |
| Prospect names left in reused demos | Library demos stay on neutral data |
| Nobody knows which version is current | The library holds the current version only |
| Old demos stay live forever | Retired demos are unpublished |
| Demos sent on open links | Buyer-specific demos on protected links |
What Goes in Each Library Entry
A seller choosing a demo needs to know a few things at a glance. Keep a short note with each library demo.
- The flow it shows, in one line.
- Which buyers it suits.
- The link to send.
- When it was last checked against the product.
- Its owner.
A 30-Day Rollout Plan
Week 1. Collect. Ask each seller for the demos they send most. Note which flows come up again and again.
Week 2. Choose. Pick the five or so flows that cover most conversations. Assign an owner to each.
Week 3. Build. Owners record each flow on neutral test data, apply the brand kit and the agreed callout style, and share the demo with every seller in the workspace.
Week 4. Switch. Sellers start sending library links. Personal demos that duplicate the library are unpublished. Add a library check to your release routine.
How Sellers Personalize Without Breaking the Library
When a deal needs the buyer's name or numbers, the seller records the flow again as their own demo and edits that. The library stays clean, and the buyer-specific version is shared on a password-protected or expiring link.
Questions to Ask Before You Start
Answer these before recording. They take a few minutes and prevent most rework.
- Which flows come up on almost every call?
- Who will own each library demo, and who checks it at each release?
- Where will sellers find the library, and how will they know a demo is current?
- When may a seller make their own version, and how should they share it?
- Which old personal demos should be unpublished once the library is live?
Where Proovyt Fits (Full Disclosure)
Proovyt is an interactive demo tool, and this is our blog.
- Team is priced per seat, from 2 seats. Everyone in the workspace takes a seat, admins included.
- One owner, any number of admins and members, invited by email.
- A workspace activity log with CSV export.
- Every seat has everything in Pro, including password and expiring links and lead capture.
Proovyt has no custom roles or CRM integrations yet. See pricing and the FAQ.
Common Mistakes
- A library so large nobody can find anything.
- Sellers editing the shared version for one buyer.
- No owner per demo.
- Not retiring old personal demos.
The Bottom Line
A small, owned library keeps every seller sending a current demo. Let sellers personalize their own versions, and keep the shared ones clean.
Frequently Asked Questions
How many demos should the library have? One per flow buyers ask about most. Start small.
Can members create their own demos? Yes, when an admin allows it.
Can I share a demo with one teammate? Yes. The demo's owner can share it with a teammate and take access back.
Do two people need Team? If both make demos and want a shared workspace, yes. Team starts at 2 seats.
How is Team priced? Per seat. See pricing.