Appendix B — Messaging Lines, Demo Lines, and Objection Handling
This appendix is for practical commercial language.
It is not the place for vague slogans, inflated hype, or generic legal-tech buzzwords. It is meant to give SUMMA a reusable set of serious lines for demos, conversations, and internal alignment.
1. Core positioning lines
Short line
SUMMA is for criminal files that have crossed the point where folders, PDFs, notes, search, and memory are no longer enough.
Slightly fuller line
SUMMA is a serious criminal-review system built for disclosure-heavy, structurally punishing files where ordinary tools stop composing into a survivable review environment.
Structural line
SUMMA does not mainly try to make law firms more “modern.” It tries to make ugly criminal files more structurally survivable.
Human-burden line
SUMMA is built for the point where the problem is no longer opening the documents. The problem is knowing what matters, what changed, and how to re-enter the file without rebuilding it from scratch.
2. What SUMMA is not
SUMMA is not generic legal AI.
SUMMA is not mainly practice-management software.
SUMMA is not mainly a prettier document repository.
SUMMA is not a magic machine that replaces counsel judgment.
SUMMA is not mainly for the easiest, lowest-burden files.
3. What SUMMA changes
SUMMA changes the structure of review.
It preserves source more carefully. It concentrates issues more honestly. It makes re-entry less punishing. It improves handoff. It helps surface where the real pressure in the file appears to live.
Strong short line
SUMMA does not make a monster file magically simple. It makes serious review more survivable.
Another short line
SUMMA reduces reconstruction cost so judgment can be spent on the case instead of on rebuilding context.
4. Demo opening lines
Demo opening — plain version
The point of this demo is not to show flashy AI tricks. The point is to show what happens when a criminal file becomes ugly enough that ordinary tools stop being enough.
Demo opening — pain-first version
Most lawyers do not lose cases because they cannot open documents. They lose time, continuity, and strategic clarity because the file becomes too big, too messy, and too unstable to inhabit properly. That is the problem SUMMA is built for.
Demo opening — wedge version
If the file is small and sleepy, you can survive with ordinary tools. This demo is about the threshold where that stops being true.
5. Demo progression lines
Step 1 — source layer
We start at the bottom. If source is weak, everything above it drifts.
Step 2 — issue layer
The file becomes more survivable once it stops being just mass and starts becoming grouped problems.
Step 3 — workbench layer
The workbench matters because the reviewer has to move through the case without repeatedly losing the thread.
Step 4 — pressure layer
Once the structure is real, the next question is not just “what is here?” It is “what matters most now?”
Step 5 — Level 9 line
This is not automatic legal strategy. This is strategic pressure support: helping surface what changed posture, what is loud versus what is dangerous, and where counsel may need to look next.
6. Level 9 phrasing
Safe Level 9 line
Level 9 is the strategic pressure layer. It helps rank where the real strain in the file appears to live.
Counsel-support line
Level 9 does not replace judgment. It strengthens the environment in which judgment happens.
Premium line
The premium promise is not “the machine wins the case.” The premium promise is that the machine helps serious counsel stop wasting strategic attention on the wrong parts of the file.
Sharp line
Level 9 is about distinguishing what is merely loud from what is actually dangerous.
7. Objection handling
Objection: “We already have folders, PDFs, and search.”
That may be enough for lower-burden files. SUMMA is for the point where those tools stop composing into a survivable review environment.
Objection: “We already use practice-management software.”
That is fine. SUMMA is not trying to replace broad practice management. It is trying to solve the structural review pain that still remains inside severe files.
Objection: “We already use review software.”
That may solve retrieval, coding, and large-scale review. SUMMA’s claim is narrower and harsher: source-linked issue concentration, re-entry continuity, workbench posture, and pressure-aware review in ugly criminal files.
Objection: “This sounds like AI hype.”
Then the right test is not whether the language sounds exciting. The right test is whether the system reduces real pain: re-entry loss, issue rediscovery, weak handoff, source drift, and poor prioritization.
Objection: “This sounds expensive.”
The real comparison is not against a cheaper tool in isolation. It is against the cost already being paid through lost time, repeated reconstruction, weak continuity, and mis-ranked attention.
Objection: “Our files are not that big.”
Then SUMMA may not be urgent for every matter. The product becomes strongest when the file crosses the threshold into structural pain.
Objection: “Does this tell the lawyer how to argue the case?”
No. SUMMA is not a substitute for counsel. It is a stronger review environment for counsel.
8. Short sales lines
SUMMA is for the file that has become too ugly for ordinary tools.
SUMMA helps preserve source, structure issues, and reduce re-entry pain in serious criminal files.
SUMMA is built for the moment when the review environment starts failing the reviewer.
SUMMA helps the file become inhabitable again.
SUMMA is not about storing more. It is about losing less structure.
9. Longer pitch lines
Version 1
SUMMA is a criminal-review system designed for disclosure-heavy, structurally punishing files where the main problem is no longer access to the material, but the loss of structure, continuity, and ranked understanding inside the material.
Version 2
SUMMA helps lawyers and review teams working serious criminal files preserve source, concentrate issues, reduce re-entry pain, and surface where the real pressure in the file appears to live.
Version 3
SUMMA is for the threshold where folders, PDFs, notes, search, and memory stop being enough, and where serious review needs a stronger environment than ordinary tools usually provide.
10. Internal alignment lines
We do not sell magic. We sell stronger structure.
We do not pretend every file needs SUMMA equally. We focus on the threshold where the pain is already real.
We do not market Level 9 as automatic strategy. We market it as strategic pressure support.
We do not compete by being louder. We compete by being more exact about the actual failure mode of ugly files.
11. Final takeaway
The best SUMMA language is:
- pain-first
- threshold-based
- serious in tone
- specific about what changes
- careful with Level 9
- honest about what the system does not do
That is the voice this appendix is meant to protect.