BackOffice 🧿
Demo Script
Your step-by-step guide for tomorrow's pitch. Read through this once tonight, then trust yourself. You know this product — you helped build it.
⚡ Before you go in: Open both files in your browser and have them ready to switch between. Pitch deck first, then demo app. Keep it on your laptop, not your phone.
Pre-Demo Checklist
✓
Open pitch.html in browser — Tab 1
✓
Open app.html in browser — Tab 2
✓
Zoom browser to 90% so everything fits cleanly
✓
Make sure WiFi is on (weather loads live in the app)
✓
Read through this script once so it's fresh
✓
Relax — you know this better than anyone in that room
The Pitch
1
Open With
Lead with the pain — not the product
"Hey, I want to show you something I've been working on. Before I do — how much time do you think we spend every project just building out the submittal log and hunting for compliant products? Because I tracked it, and it's 1 to 3 days of PM time. Per project. I got tired of it, so I built something."
2
Show Pitch Deck
Quick walk through the slides — keep it moving
"This is BackOffice. The idea is simple — you drop in your drawings, your spec book, and your submittal list. The app reads the specs, searches a library of real US construction products, and hands you back a formatted submittal package. You just add the cover page and send it."
"The part that makes this different from everything else out there — it shows you how well each product matches your spec as a percentage. 96% match, here's why. 71% match, here's what's missing. Nobody has built that before."
"The part that makes this different from everything else out there — it shows you how well each product matches your spec as a percentage. 96% match, here's why. 71% match, here's what's missing. Nobody has built that before."
💡
Tip
Let them react before moving to the demo
After you explain the concept, pause and ask: "Does that sound like something that would be useful?" Let him feel the pain point before you show the solution. His reaction here will tell you how hard to push. If he leans in, go straight to the demo with energy. If he seems skeptical, slow down and ask what specifically about the submittal process bothers him most.
3
Demo — Switch to App Tab
Walk through the app live
1
Type a project name in the bar at the top — use a real job name if you want, makes it feel personal
2
Point at the three slots — "Drawings go here, spec book here, submittal list here. Three drops."
3
Click "Browse Files" on the Drawings slot and select any PDF from your computer (it doesn't have to be real drawings — it's a demo)
4
Do the same for the Spec Book slot
5
For the third slot — click "Auto-generate from spec" and say: "Or if we already have a log, we drop it in. If not, BackOffice reads the spec and generates it."
6
Hit the big Generate button and let the processing animation run — don't talk over it. Let him watch it work. "Reading spec book... searching product library... calculating compliance scores..." — that's the WOW moment.
7
When results appear, click on any submittal card to expand it and show the product matches with % scores
8
Click a different product to show the selection works — say: "If I want a different product, I just pick it. Done."
9
Show the single submittal feature — type "insulation" in the text box, hit generate, show it returns just that one item
4
Say
Land the key points after the demo
"What you just saw is the demo version. I built this in 48 hours. The real version — with actual AI reading your spec PDFs, a live database of every major US construction product, and generating real PDFs you can submit — is 4 to 6 weeks away with some budget behind it."
"We're not trying to be Procore. Procore costs $50K a year and still doesn't do this. We're $99 a month for a PM and it actually solves the problem."
"We're not trying to be Procore. Procore costs $50K a year and still doesn't do this. We're $99 a month for a PM and it actually solves the problem."
⏸
Pause
Let him talk — don't fill the silence
This is the most important moment of the pitch. After you land those lines, stop talking. Let him react. His questions and objections tell you exactly what he needs to hear next. Don't rush to fill silence with more features — just listen and respond to what he actually cares about.
Common reactions and how to handle them:
"How does it actually read the spec?" → "The AI parses the PDF and identifies every CSI section with a submittals requirement. We've already mapped the architecture — it's ready to build."
"What about our specific products we always use?" → "Great question — users can add their own products to the library. Your go-to products stay at the top."
"What would it cost to build the real version?" → "Honestly, not much. The architecture is lean by design. We built the demo for nothing. A few thousand dollars gets us v1.0."
Common reactions and how to handle them:
"How does it actually read the spec?" → "The AI parses the PDF and identifies every CSI section with a submittals requirement. We've already mapped the architecture — it's ready to build."
"What about our specific products we always use?" → "Great question — users can add their own products to the library. Your go-to products stay at the top."
"What would it cost to build the real version?" → "Honestly, not much. The architecture is lean by design. We built the demo for nothing. A few thousand dollars gets us v1.0."
5
The Close
Ask for what you want
"I'm not here asking you to write a check today. I just wanted to show you what we built and get your honest reaction. If this is something you'd actually use — or something you'd pay for — that tells me everything I need to know about whether to keep going."
Remember
Key Things to Remember
You know this industry better than anyone in the room — trust that
The demo doesn't have to be perfect — it has to be real
Lead with pain, not features
Don't oversell — let the product speak
You built this in 48 hours — that's the story
If he loves it — great. If he has questions — great. Either way you learn something.