SaaS Demo Script Example
Intro
For a head of operations or IT sponsor evaluating a horizontal B2B SaaS after a trial—project delivery, workflow, or collaboration; substitute your category.
Leadership wants justification for paid seats and SSO; security asked about audit log and data residency. You demo one client project from kickoff to sign-off with admin, member, and guest roles.
Success: they believe the product scales from pilot to department without admin overhead exploding, and client collaboration stays controlled.
Common problems
- Tool sprawl: tasks in one app, files in another, client updates in email—nobody can reconstruct what happened.
- Guest access fear: legal worries about what clients can see, download, or forward.
- Admin scalability dread: SSO, groups, and permissions feel like a second job at two hundred users.
- Trial trap: power users love shortcuts the rest of the team will never adopt.
Demo script
Talk track you can lift into a call. Swap product names, proof points, and the exact scenario you confirmed in discovery.
Opening
“You’ve been in trial—I want to connect what worked for individuals to how a whole team and your clients would run day to day.”
“I’ll use one client project, ‘Acme redesign,’ from kickoff to delivery sign-off. Stop me when something does not match how you work.”
“Order: workspace and roles, work breakdown, files and versions, guest access, portfolio roll-up for leadership, then admin and security at a sane level of depth.”
Problem framing
“The failure mode we see after trial is everyone loves their personal workflow, but there is no shared spine—so delivery still lives in email under pressure.”
“I’m going to show one spine: project, tasks, files, and client visibility scoped so CS and legal can sleep.”
Walkthrough
- Create the project from a template: your standard phases and tasks copy in; members inherit access from a group like ‘Delivery East’; guests are not added yet.
- Execute work: tasks with owners, due dates, dependencies; comments stay on the task so decisions are searchable; show timeline view for the steering-committee date.
- Files live on the deliverable task with version history—who uploaded when—so ‘final_final’ naming stops being the system of record.
- Invite the client as a guest to this project only: they cannot browse other clients; comments and approvals in a limited portal; disable download per policy if required.
- Portfolio view for leadership: active projects, RAG status, at-risk tasks—director-level answer without a status meeting.
- Admin and security teaser: SSO with your IdP, SCIM for groups, audit log of logins and exports; data region for residency requirements.
Value reinforcement
“Delivery, files, and client visibility stayed on one project record—no parallel thread in email for the same outcome.”
“Guests were scoped to one workspace; audit and export controls are where security questionnaires usually start.”
“Templates and groups mean you are not hand-building every project at scale.”
Close
“Suggested next step: paid pilot with one business unit—cap seats, include SSO sandbox.”
“Mid-pilot we run a one-hour admin workshop so IT is confident before you expand; I’ll send draft success criteria you can share internally.”
Example scenario
Example: Chris, Head of Ops, and Sam, IT lead, post-trial
Chris piloted with five power users; the CEO wants ROI before company-wide seats. Sam needs SSO, group provisioning, and an audit story for procurement. They need to see one client engagement end-to-end with a guest, plus proof that scaling does not mean Chris becomes full-time admin. This script gives them that arc in one sitting.
Why this script works
- Project thread beats feature buckets—buyers map to how they deliver work, not your roadmap sections.
- Guest and portfolio beats address the two gates that usually block expansion: legal and leadership reporting.
- Pilot plus admin workshop in the close turns evaluation into a plan with dates, not a vague “let us think.”
Call to action
Turn this talk track into a reusable outline and prep checklist.
More category scripts
FAQ
What if they want pricing and packaging in the same session?
Let your AE own a tight commercial block at the end or schedule immediately after. Keep your presales narrative on value delivered in the pilot scope—do not negotiate discount on the architecture whiteboard.
How technical should the security section get?
Answer questionnaire-level topics: SSO, SCIM, audit, retention, regions. Deep pen-test detail belongs in a security review, not in the first value demo.
How do I reuse this script for a different vertical?
Keep the spine (workspace, tasks, files, guest, portfolio, admin) and swap the template and vocabulary in the Software Demo Script Template. Track vertical-specific proof in the Demo Checklist Generator.