Interactive Demos for Agencies: Separate Clients, Not Processes

The onboarding tour is approved. Then the client asks whether its customer success team can update it, your freelance producer finishes their contract, and someone notices that follow-up messages still come from an agency employee. The demo works. The operating model doesn’t.

To manage interactive demos for agencies, give each client a separate workspace and agree on access, content ownership and follow-up responsibility before publishing. Reuse your production process across accounts, not client assets or viewer records. Make maintenance and handoff part of the original scope.

I’d settle those questions before polishing another tooltip. They’re harder to fix once customers are using the experience.

How should agencies organize demos for multiple clients?

Start with one workspace per client, then organize the content inside it around audience needs and tasks. Create additional workspaces only when there’s a real separation in brands, teams or responsibilities, not because a new campaign needs a home.

A client workspace is an operating boundary: it keeps a client’s demos, content, contacts and workflows together, with the appropriate branding and user access. A folder alone doesn’t do that job.

Dale, the demo automation platform, supports separate workspaces containing demos, contacts, Pages, Walkthroughs, Segments and Campaigns. Each workspace has its own logo and colors, applied automatically to new demos. Users can belong to several workspaces, with custom roles and permissions within each.

That suits an agency producer working across accounts while client teams work within their own workspace. But the structure still needs an owner. Name the person who approves access changes, the person who approves content and the person responsible for viewer follow-up. Those may be different people.

The agency demo management use case gives you the platform context. Your delivery agreement should supply the missing operational detail: whose account you work in, who pays for ongoing use and what access remains after the project.

What can agencies reuse without mixing client work?

Reuse methods across clients and content within a client’s workspace. Keep screenshots, recordings, attachments, viewer records and follow-up workflows specific to the client they belong to.

Consider two reporting products that both need a “connect your data source” tour. The teaching pattern might be identical: explain prerequisites, show the connection steps, then confirm success. That doesn’t make the screenshots or customer examples interchangeable.

This is where “we’ll just duplicate the last project” becomes expensive. A copied script can carry the wrong support address. An attachment can contain another client’s commercial terms. A screenshot can expose an actual customer’s email.

Use sanitized data before capture, not as an afterthought during review. Workspace separation cannot protect information that you’ve already placed inside a visible recording.

I’d also keep the agency’s reusable templates outside any one client’s delivery package. Label what is a general production template and what is a commissioned asset. The software’s boundaries and the contract’s ownership terms should agree.

How do you give producers and clients the right access?

Assign access by task rather than job title, and test the resulting permissions before inviting the wider team. Being the senior stakeholder doesn’t automatically require administrative access.

A producer might need to work on Pages and Walkthroughs but have no responsibility for Campaigns. A client’s customer success lead may need contact activity to investigate onboarding questions. Write those needs down, then map them to the available workspace permissions.

1. Name the accountable administrator. Someone must approve changes when agency staff rotate or client responsibilities shift.
2. List the required tasks. Separate content creation, contact handling, outreach and administration rather than assigning broad access for convenience.
3. Test a restricted user. Check what that user can see and change, including whether other client workspaces are accessible.
4. Inspect outgoing communication. Confirm which inbox sends invitations and follow-ups, and who monitors replies.
5. Set an access review trigger. A contractor leaving, a launch finishing or a retainer ending should prompt a review.

Don’t confuse access with ownership. A client may have permission to view contacts without that resolving who can export, retain or use those records after the engagement. Put those terms in the agreement.

For an agency evaluating interactive demo software, this is a trial task, not a question to leave until procurement. Test the permissions you actually need, with the people who will use them.

How should agencies build training content that stays maintainable?

Build around a user task, not a tour of every screen. Separate topics so a change to one workflow doesn’t force you to remake the entire onboarding experience.

For an illustrative reporting SaaS project, “connect a source,” “configure a report” and “share the result” are useful units. “Everything you need to know about the dashboard” is not. It’s too broad to maintain and too vague to help someone who is stuck.

What belongs in Pages and Walkthroughs?

Pages hold topic-specific media, links and attachments. Walkthroughs provide screenshot-based steps with tooltips and highlighted areas, so viewers can click through the product experience.

Give each format a job. A video can explain why a permission setting matters. A product tour can show where to find it. An attached reference can document which roles should receive it. Don’t make viewers watch a long explanation just to locate a button.

Pages are reusable across multiple demos. That saves duplicate production within a client’s workspace, but it creates a maintenance obligation: check an updated Page wherever it’s used.

Keep a content register, even if it’s a spreadsheet. Record the topic, owner, source files, product area shown, demos using it and last review. For more context on this application, see product demos for training and onboarding.

When should training use a Linear Demo or Branched Demo?

Use a Linear Demo when viewers should choose which topics matter and how much detail they need. Use a Branched Demo when a role or use-case choice should route them to a different experience.

In a Linear Demo, viewers rate topics Important / Somewhat Important / Not Important. Pages can hold a longer video for Important and a shorter video for Somewhat Important; Not Important topics are skipped. One video can also serve both levels of interest.

That’s useful for optional learning. It’s not evidence that mandatory instruction was completed.

A Branched Demo could route administrators and end users to different training. Branching uses preset choices today, not free-text answers. Ask only questions that change what someone should see. A questionnaire that changes nothing is just another obstacle.

What should agencies report about training engagement?

Report engagement as evidence of interaction with training, not proof of product adoption. Verify task completion separately through the client’s application data or support process.

“The viewer completed the Walkthrough” and “the customer connected a data source” describe different events. Combining them into one success metric makes a report look cleaner, but it hides the question the client actually cares about.

Agree on the evidence before launch:

• Training engagement: Which topics did viewers choose, watch or replay?
• Possible friction: Which Walkthrough steps attracted repeated viewing or longer attention?
• Task completion: Can the client confirm that users performed the intended action in the product?
• Content changes: What should be clarified, shortened or recaptured?

Walkthrough heatmaps can tell you where to investigate. They cannot tell you why someone paused. The viewer might be confused, interrupted or carefully following along in another window. Use demo engagement analytics to choose the next question, not manufacture an answer.

The same caution applies to buying intent. Buying Intent Signals and Lead Scoring can inform acquisition workflows, but an existing customer replaying setup instructions isn’t automatically considering an expansion. Keep education follow-up distinct from sales outreach unless you have a reason to connect them.

Should an agency use workspaces or Partner Center?

Use workspaces to build and manage client experiences. Use Partner Center when the job is to distribute approved co-branded demos without editing them.

These are different relationships. An agency hired to produce onboarding content needs authoring access and a maintenance process. A reseller needs approved material it can share with prospects.

Partner Center lets invited partners share selected demos with their logo and contact details alongside the vendor’s branding. Partners have a dashboard showing their shared demos and engagement with the contacts they reached, but they cannot build or edit. The vendor owns partner-sourced contacts, and partner accounts don’t consume team seats.

That makes co-branded distribution through Partner Center relevant if your agency also acts as a referral or resale partner. It doesn’t replace a workspace for producing client content.

Ask during scoping: are we creating on the client’s behalf, distributing approved material, or doing both? If it’s both, document the two responsibilities separately.

What should you test before committing to a multi-client setup?

Test the operational edges, not just the polished viewer experience. Your trial should include restricted access, shared content updates, outgoing messages and the proposed handoff arrangement.

For example, create two fictional client brands using sanitized content. Give a producer access to both workspaces and a client user access to only the intended workspace. Then walk through an ordinary change request.

Short acceptance checklist:

• New demos receive the correct workspace branding.
• Each user has only the intended access.
• Content and viewer records are in the right workspace.
• An updated Page is checked in every demo using it.
• Invitations and follow-ups come from the intended sender.
• A named person can maintain the content after launch.

Multiple workspaces with separate branding are available on Advanced and above. Check Dale pricing for the features and limits your delivery model needs. Confirm how published demo, contact, storage and seat allowances apply to your account structure rather than assuming each workspace has an independent allowance.

Use the Dale interactive demo to assess the viewer experience. Evaluate administration separately.

What belongs in a client demo handoff?

Hand over the operating instructions alongside the published demos. The next owner needs to know where content appears, what can change and which messages are still active.

Include the content register, agreed source files, audience definitions, distribution locations and maintenance responsibilities. Document configured Segments and Campaigns so automated messages don’t outlive their purpose or their accountable sender.

Agree on account arrangements before promising a transfer. Don’t assume a workspace can move between accounts or that billing ownership can change through a self-service action.

For your next kickoff, add a workspace plan to the brief. Name the owner, list the users, define the first training task and write down the exit arrangement before capturing the first screen.