Demo Guide
How to deliver compelling Olympus Cloud product demonstrations that win deals.
Demo Environment Access
URLs
| Environment | URL | Purpose |
|---|---|---|
| Sales Demo | demo.olympuscloud.ai | Customer-facing demos |
| Dev | dev.api.olympuscloud.ai | Hands-on trials and development |
| Training | training.olympuscloud.ai | Internal practice |
Credentials
Contact Sales Ops for demo credentials: sales-ops@nebusai.com
| Account | Role | Use For |
|---|---|---|
| demo@olympus.demo | Owner | Full feature showcase |
| manager@olympus.demo | Manager | Scheduling, reporting |
| staff@olympus.demo | Employee | Mobile app, clock-in |
Pre-Demo Checklist
24 Hours Before
- Confirm meeting time and attendees
- Research the prospect's business (size, cuisine, locations)
- Check their current tech stack (from discovery call)
- Prepare custom talking points for their pain points
- Test demo environment and reset data if needed
- Test screen sharing and audio
30 Minutes Before
- Open demo environment and log in
- Have backup demo (screenshots/video) ready
- Close unnecessary browser tabs and apps
- Test internet connection
- Have discovery notes visible
During Demo
- Ask permission to record (if applicable)
- Confirm attendee roles at the start
- Focus on their stated pain points
- Leave time for Q&A
Demo Structure (45 minutes)
Opening (5 minutes)
Goal: Build rapport and confirm agenda
"Thanks for joining today. Before I show you the platform, I want to
make sure we focus on what matters most to you.
From our last conversation, I understand your main challenges are:
[recap their pain points]
Is there anything else you'd like to see today?"
Discovery Recap (3 minutes)
Confirm their situation:
- Current POS/systems
- Number of locations
- Staff count
- Key pain points
- Decision timeline
Platform Overview (5 minutes)
Show: Dashboard with key metrics
"Let me give you a quick tour of the command center. Everything
your team needs is accessible from one dashboard..."
Key Points:
- Real-time sales and labor data
- Multi-location view (if relevant)
- Mobile-first design
- Intuitive navigation
Feature Deep Dives (25 minutes)
Choose 3-4 features based on their pain points:
Voice AI (if drive-thru or phone orders)
Demo Path: Settings > Voice AI > Live Demo
"Let me show you something that usually surprises people..."
[Activate voice demo]
"Hey Maximus, I'd like to order a large pepperoni pizza with
extra cheese and a side of garlic bread."
Key Points:
- Natural language understanding
- Handles modifications and special requests
- Integrates directly with POS
- Works in noisy environments
ROI Statement:
"Restaurants using our drive-thru AI see 15-20% faster order
times and save 1-2 labor hours per day. For a busy drive-thru,
that's $30,000+ in annual labor savings."
Offline Mode (if reliability is a concern)
Demo Path: Toggle airplane mode on device
"Now I'm going to do something that would crash most POS systems..."
[Enable airplane mode]
"Let me take an order, send it to the kitchen, and process a payment."
[Complete full transaction]
"Everything works. When connectivity returns, it syncs automatically."
Key Points:
- Full functionality offline
- Credit card processing works (store & forward)
- Kitchen tickets print immediately
- No lost sales during outages
ROI Statement:
"One internet outage during a Friday dinner rush can cost
$2,000-5,000 in lost sales. Our customers never worry about that."
Kitchen Display System (if kitchen efficiency matters)
Demo Path: Open KDS view on second screen/tab
"Let's see what your kitchen staff experiences..."
[Enter orders from POS]
"Notice how tickets are color-coded by timing and the AI
prioritizes based on cooking times."
Key Points:
- Color-coded urgency
- Automatic cook time management
- Bump bar or touch interface
- Connected to prep stations
Scheduling (if labor is a pain point)
Demo Path: Workforce > Scheduling
"Creating a schedule used to take managers hours. Watch this..."
[Click Auto-Schedule]
"The AI considers availability, skills, labor laws, and your
forecast to create an optimized schedule in seconds."
Key Points:
- AI-powered auto-scheduling
- Availability and time-off requests
- Shift swapping
- Labor cost forecasting
Reservations (if they use OpenTable)
Demo Path: Front of House > Reservations
"How much do you pay per cover with OpenTable?
[Wait for answer - usually $0.50-$1.50]
Let me show you our reservation system..."
[Walk through guest booking flow]
"Zero per-cover fees. You own the guest data. Same functionality."
Cost Savings Calculation:
"At [X] covers per month × $[Y] per cover = $[Z] per month.
That's $[annual] per year going to OpenTable instead of your business."
Reporting & Analytics (if they mention needing insights)
Demo Path: Reports > Dashboard
"Let's look at what this week's data is telling us..."
[Show labor vs sales chart]
"See this spike? The AI would have recommended adding a
server during this period."
Key Points:
- Real-time dashboards
- Labor cost percentage
- Sales trends and forecasting
- Employee performance
Competitive Differentiation (3 minutes)
Address their current system:
If they use Toast:
"Unlike Toast, you're not locked into proprietary hardware.
Any iPad, any Android tablet works. And our voice AI is
actually intelligent—it understands context, not just scripts."
If they use Square:
"Square is great for retail, but it wasn't built for restaurants.
Our KDS, table management, and kitchen workflows are purpose-built
for how restaurants actually operate."
If they use OpenTable:
"We integrate with Google Reserve for discovery, but we never
charge you when a guest sits down. Your regulars book directly,
your new guests find you on Google—all at zero per-cover cost."
Pricing Preview (2 minutes)
"Based on what you've shared—[X locations, Y employees]—you'd
likely be looking at our [tier] plan.
I'll send over a detailed proposal, but you're looking at
approximately $[range] per month, which includes:
[list included features]
Compared to what you're paying now for [current systems],
most restaurants in your situation see [X%] savings."
Next Steps (2 minutes)
Always end with clear action items:
"What questions do you have about what you've seen today?
[Answer questions]
It sounds like [summarize their interest areas] really resonated.
Here's what I suggest for next steps:
1. I'll send you a recap and custom proposal by [day]
2. Would you like to do a hands-on trial with your actual menu?
3. [If multi-location] Should we schedule a call with your [other stakeholders]?
What works better for a follow-up: [offer two specific times]?"
Feature-Specific Demo Scripts
Voice AI Deep Dive (10 min)
-
Introduction
"Our voice AI, Maximus, handles phone orders and drive-thru
without pulling your staff away from guests." -
Phone Demo
- Call the demo restaurant number
- Place a complex order with modifications
- Show how it appears in POS
-
Drive-Thru Demo
- Switch to drive-thru mode
- Demonstrate background noise handling
- Show order confirmation flow
-
Show AI Learning
- Menu updates sync automatically
- Handles 86'd items gracefully
- Remembers customer preferences
Offline Mode Deep Dive (5 min)
- Show full POS functionality
- Enable airplane mode on device
- Take complete order
- Process credit card payment
- Send to KDS/kitchen printer
- Re-enable connection
- Show automatic sync
Multi-Location Demo (10 min)
- Dashboard overview with all locations
- Drill into individual location
- Compare performance metrics
- Show consolidated reporting
- Demonstrate role-based access
Handling Demo Failures
Internet Goes Down
"Actually, this is a perfect opportunity to show you
something—watch what happens to our system..."
[Continue demo in offline mode]
"Unlike other systems, we keep running."
Feature Doesn't Work
"That's not behaving as expected—let me show you the same
functionality a different way..."
[Use backup approach or screenshot]
"I'll have our team look into this and send you a video
of it working properly."
Unexpected Questions
"That's a great question and I want to make sure I give you
an accurate answer. Let me note that down and get back to
you within 24 hours."
Post-Demo Checklist
Immediately After
- Send thank-you email with:
- Recap of their requirements
- Features they were most interested in
- Answers to questions you couldn't answer live
- Next steps and timeline
Within 24 Hours
- Send formal proposal
- Schedule follow-up call
- Update CRM with demo notes
- Loop in Sales Engineering if technical questions
Within 1 Week
- Follow up if no response
- Offer hands-on trial
- Connect them with customer reference
Demo Resources
Sales Engineering Support
For complex demos or technical deep dives, request SE support:
- Email: se@nebusai.com
- Slack: #sales-engineering
Demo Videos
Pre-recorded demos for specific features:
- Voice AI Overview - Contact SE team for latest recording
- Offline Mode - Contact SE team for latest recording
- Kitchen Display - Contact SE team for latest recording
- Scheduling - Contact SE team for latest recording
Customer Stories
Reference customers for similar prospects:
- Pizza: Mario's Pizzeria (Chicago)
- Fine Dining: The Riverside (Seattle)
- Fast Casual: Green Bowl (Multi-location)
- Drive-Thru: Burger Joint (Texas)
For NebusAI Internal Use Only