Appendix C — Demo Script and Walkthrough Flow
This appendix is for running a serious SUMMA demo.
It is not a theatrical pitch deck. It is a practical walkthrough sequence for showing the product in the right order.
The main rule is simple:
Do not start with magic. Start with pain.
If the buyer does not first recognize the pain clearly, the rest of the demo becomes noise. If the buyer does recognize the pain, then the architecture starts making sense very quickly.
1. The purpose of the demo
The purpose of the demo is not to prove that SUMMA is flashy.
The purpose is to show what happens when a criminal file becomes ugly enough that ordinary tools stop composing into a survivable review environment, and then to show how SUMMA changes that environment.
That is the real job of the walkthrough.
2. Opening frame
A good opening should sound something like this:
This is not a demo about generic legal AI. This is a demo about what happens when a criminal file gets big enough, messy enough, or unstable enough that folders, PDFs, notes, search, and memory stop being enough.
Or:
Most lawyers do not lose time because they cannot open documents. They lose time because the file becomes too hard to inhabit. That is the problem SUMMA is built for.
The goal of the opening is to make the buyer feel seen before the product appears.
3. What to show first
Show the burden first.
Do not begin with the fanciest layer. Do not begin with Level 9. Do not begin with a big dashboard pretending the case is already solved.
Begin with the file as pain: - volume - mixed evidence - repeated disclosure - issue sprawl - contradiction pressure - re-entry pain - weak continuity - handoff pain
The buyer must first recognize the environment.
If they do not recognize the environment, they will misread the product as just another tool.
4. The correct demo order
Step 1 — The file as burden
Show the file as it normally feels: - too many parts - too much rediscovery - no stable posture - hard to tell what matters most
Step 2 — Source discipline
Show that the system preserves source and identity properly. Make clear that this is the bottom layer and that everything above it depends on it.
Step 3 — Issue concentration
Show how the file stops being only mass and starts becoming grouped problem zones. This is where the buyer should feel the first real structural relief.
Step 4 — Workbench view
Show how the reviewer can move through the case without constantly losing the thread. This is where the product begins to feel inhabitable.
Step 5 — Re-entry / continuity
Show what the system preserves across time. This matters more than many buyers realize at first, and once they see it, they usually understand the pain reduction immediately.
Step 6 — Pressure view
Now show how the product begins separating what is loud from what is dangerous. This is the bridge to premium value.
Step 7 — Level 9 / strategic pressure support
Only now should Level 9 appear. By this point, the buyer should already trust the lower layers. Then the Level 9 promise becomes credible: not automatic strategy, but stronger support for where serious attention should go next.
That is the right order.
5. What not to do
Do not start with generic AI claims.
Do not say the system knows how to win the case.
Do not flatten the file into a toy example so early that the buyer never feels the real burden.
Do not flood the demo with too many features at once.
Do not over-talk the product before the buyer has seen the pain.
Do not introduce Level 9 so early that it sounds like fake omniscience.
Do not confuse “summary” with “structure.”
6. Where Level 9 belongs
Level 9 belongs late in the walkthrough, not early.
It should be introduced as the strategic pressure layer: - what changed posture - what is loud versus dangerous - what deserves attention now - where the file’s real pressure appears to live
Good phrasing:
This is not the machine replacing counsel. This is the system helping serious counsel spend attention where it matters most.
Or:
Level 9 is not automatic legal strategy. It is strategic pressure support built on top of stronger file structure.
That keeps the claim premium but believable.
7. Demo questions to ask the buyer
A good demo is not only showing. It is diagnosing.
Useful questions include:
- What kind of file starts hurting your current workflow first?
- Where do you lose the most time on re-entry?
- What part of the case becomes hardest to hold together?
- How do you currently track issue drift?
- What happens when another person has to inherit the file?
- Where do contradictions or timeline instability usually live in your current setup?
- What do you wish your current tools preserved better?
These questions make the demo feel like a serious conversation instead of a performance.
8. What the buyer should feel at each stage
Early stage
This company understands the real pain.
Middle stage
This is more than storage.
Workbench stage
This would actually make the file easier to inhabit.
Pressure stage
This might help me stop wasting attention on the wrong thing.
Level 9 stage
This is premium, but it still sounds honest.
That emotional sequence matters.
9. How to close the demo
A bad close says: So, do you want to buy it?
A stronger close says something like:
The real question is not whether the product looks impressive. The real question is whether it reduces structural pain in the kinds of files that currently punish your team.
Or:
If this kind of file is not painful enough yet, SUMMA may not be urgent. If it is, then the next step is to test the system against a real burden and see whether it reduces re-entry loss, issue rediscovery, weak handoff, and poor pressure visibility.
That kind of close is calmer and more serious.
10. Best final lines
SUMMA does not make a monster file magically simple. It makes serious review more survivable.
Or:
SUMMA is not for every file equally. It is for the threshold where ordinary tools stop being enough.
Or:
The point of the system is not to replace judgment. It is to stop wasting judgment on reconstruction.
11. Final takeaway
A strong SUMMA demo should move in this order:
- pain
- source
- issue concentration
- workbench
- continuity
- pressure
- Level 9
- proof-oriented close
That order protects the product from sounding fake and helps the premium story become believable at the right moment.