Scale your demos across products, brands and teams

Overview

At first, one team builds a few demos for one product. Then the company adds products, sub-brands, partners, regions and more teams. Copying templates and restyling them by hand stops working, and demos go out of date.

Walnut handles that growth in one workspace. You don't need to copy templates or open separate accounts. Each part of a demo has its own tool, so you manage that part once and reuse it everywhere:

Layer	What it controls	Walnut tool
Screens	The product UI	Screens Library
Quality	What's ready to share	Approval
Look	Colors, fonts, buttons, avatar	Brand themes
Story	Customer name, logo, industry, sample data	Demo presets
Access	Which teams can see and edit what	Groups

Set up each layer once. After that, a new product, brand or partner is a few new labels, a theme and a preset rather than a new set of demos.

---

Step 1: Capture each screen once in the Screens Library

Make the Resource Hub → Screens library your single source of product UI.

• Capture with the Chrome extension, or Promote from template to move screens you already have into the library.
• Label every screen with a Product and a Feature. Labels let one library serve every product line, and shared screens such as login or settings are captured only once.
• Capture at one preset size (Desktop, Laptop or Mobile) so screens from different teams fit together.

When the product changes: edit the library screen and click Update in templates to push it to every template that uses it. Edits a template made to its own copy are kept.

👉 Screens Library: capture once, reuse across every product and brand

---

Step 2: Build master templates and require approval

Build a small number of master templates from library screens, for example one per product or per use case. These masters are what every team builds demos from, so protect them:

• Turn on Company Settings → Account settings → Content approval → Require approval before publishing. A template then needs approval before anyone can create demos from it or update demos to its latest version.
• Name your approvers in Company Settings → Users (Can approve content).
• Any edit to an approved template moves it to Needs re-approval, so changed content can't go out on an old approval. Updates sent from a template back to the Screens Library go through a reviewer too.

👉 Review and approve templates before they're published

---

Step 3: Give each brand its own theme

A theme is a named set of colors, fonts, buttons, avatar, dim and interactions. Create one per brand you show:

• Your core brand (the workspace default)
• Sub-brands or acquired companies
• Partner co-brands or white-label looks for resellers
• Campaign looks for a launch or an event

Point each template or demo at the right theme. One master template can go out under your brand, a sub-brand's or a partner's, with no copy to keep in sync.

👉 Brand themes: one workspace, multiple brands

---

Step 4: Personalize the story with presets

Themes change how a demo looks, and presets change what it says. A preset is a saved set of variable values, such as customer name, industry, currency, logo and sample data, that you can apply to a demo in one click.

• Create presets in Company Settings → Global variables → Presets, named by story ("FinServ — enterprise", "Retail — mid-market").
• Turn on the Pre-flight screen so presenters pick the preset before the buyer sees the demo.
• Library screens' variables bind to company-wide variables, so presets work on every template built from the library.

Put it together: a partner's SE opens a master demo with the partner's theme, picks the "Healthcare" preset, and presents a demo that looks like the partner's and speaks to a healthcare buyer. The demo was built once, from library screens, and approved once.

👉 Demo presets and the Pre-flight presenter screen

---

Step 5: Organize teams with groups

As more teams use the workspace, manage access by team, not person by person.

• Create groups in Company Settings → Groups for each team, product line or partner, for example Sales — Product A, SE, Partner — Acme.
• Grant access to templates and folders at the group level. New hires and partners get the right content as soon as they join a group.
• Use Manage group to see each team's usage and engagement.
• Keep most people on Presenter or Editor, and keep master templates in a folder where only collaborators have access.

👉 Scale your workspace: governance best practices

---

Keep it fresh

Once the layers are in place, routine changes take one edit each:

When...	Do this
The product UI changes	Edit the library screen → Update in templates
A master template changes	Get it approved → Update demos from the template's Create & share dialog
A brand refreshes its look	Edit its theme. Templates and demos that use it pick up the change; republish to refresh links shared earlier
You start selling to a new vertical	Duplicate the closest preset and change a few values
You add a new partner	Create their theme, a group and, if needed, a preset
A team reorganizes	Move people between groups

---

FAQ

Do I need separate workspaces for different brands or partners? No. Themes give each brand its look, groups control who sees what, and content and analytics stay in one workspace.

How many master templates should we have? As few as you can. Use themes and presets for variety instead of copying templates. Create a new master only when the flow is different, not just the look or the customer.

Who should own each layer? Usually admins own themes, presets, groups and approval settings. Product marketing or solutions engineering owns the Screens Library and master templates. Sales and partners present.

What's the difference between this playbook and "Scale your workspace"? This playbook is about getting one set of content to many audiences. Scale your workspace covers governance in depth: roles, collaborators, tags, folders, AI and API access.