Appendix M — User Personas and Buyer Types by Pain Level
This appendix explains who different SUMMA people actually are.
That sounds simple, but it matters.
A serious company should not confuse: - the person who uses the product - the person who buys the product - the person who influences the purchase - the person who benefits from the product indirectly - the person who understands the company strategically
If these roles blur together, messaging gets weaker, demos get messier, and sales conversations become less precise.
This appendix separates them properly.
1. The core distinction
The first rule is:
The user is not always the buyer. The buyer is not always the operator. The operator is not always the economic decision-maker. The investor or partner is not the same as the first-fit customer.
That distinction should stay sharp.
2. Main persona categories
A clean SUMMA persona map has five major categories:
- end user
- operator / reviewer
- buyer / decision-maker
- internal champion
- strategic audience
Those categories are explained below.
3. End user
The end user is the person who directly lives inside the file.
This person feels the pain most physically.
Typical end users may include: - criminal defence lawyers - associates - articling students - litigation-support staff - analysts - junior reviewers - anyone doing direct file handling in a severe-review environment
Their pain is usually operational and immediate: - re-entry pain - issue sprawl - source drift - mixed-format burden - contradiction confusion - difficulty holding posture across sessions
They care less about corporate narrative and more about: - does this actually help me survive the file?
That is the end-user lens.
4. Operator / reviewer
The operator is the person responsible for keeping the review process alive and usable.
Sometimes the operator and end user are the same person. Sometimes not.
Operators usually care about: - how the file is being worked - whether structure is preserved - whether handoff is survivable - whether the system improves continuity - whether the review environment is stable enough to support others
This persona tends to value: - workbench logic - issue concentration - source-linked review - continuity - pressure visibility
The operator often becomes one of the strongest internal champions if the product lands.
5. Buyer / decision-maker
The buyer is the person who can say yes economically or organizationally.
This may be: - a partner - a firm owner - a practice lead - a senior lawyer - an operations head - a procurement or innovation stakeholder in larger environments
The buyer’s pain is still real, but it is usually framed differently.
The buyer tends to care about: - whether the pain is frequent enough to justify change - whether the product is credible - whether the team will actually use it - whether handoff, continuity, and review quality improve - whether the workflow benefit is real enough to justify cost
The buyer is usually asking: - is this worth introducing? - is the pain severe enough? - is the company serious enough? - will this reduce expensive structural waste?
That is different from the end-user lens.
6. Internal champion
The internal champion is the person who helps the product survive inside the organization after the first conversation.
This may be: - an associate who feels the pain sharply - a senior reviewer who understands workflow failure - a partner who sees the structural problem clearly - an operations-minded lawyer who knows current tools are not enough
The champion is critical because they translate pain into urgency inside the organization.
They usually say things like: - yes, this is our problem - yes, we keep losing time here - yes, our current setup is searchable but not inhabitable - yes, this is worth piloting
Champions matter because not every buyer feels the pain directly enough to speak that way without help.
7. Strategic audience
The strategic audience includes: - investors - strategic partners - future senior hires - major connectors - platform or ecosystem partners
These people are not usually asking: does this help me on today’s file?
They are asking: - is the market real? - is the wedge sharp? - is the engine broader than the wedge? - is the expansion path believable? - is the moat real? - is the company disciplined?
That is why they need a different narrative.
This is the audience for the broader company-story appendices, not the operational demo alone.
8. Pain-level bands
Another useful way to map personas is by pain level.
Band 1 — Low pain
Typical characteristics: - smaller files - lower issue density - less mixed evidence - weak need for deep continuity support - current folders/search/notes still broadly enough
These users may understand the product intellectually but not feel urgency yet.
Band 2 — Moderate pain
Typical characteristics: - some disclosure burden - some re-entry pain - some issue sprawl - some continuity problems - current tools are “mostly okay” until they suddenly are not
These buyers may be educable, but fit can still be inconsistent.
Band 3 — High pain
Typical characteristics: - repeated disclosure - mixed-format burden - contradiction-heavy or witness-heavy files - serious re-entry loss - significant handoff pain - current tools clearly straining
This is strong SUMMA territory.
Band 4 — Extreme pain
Typical characteristics: - monster files - intense evidence burden - timeline instability - large review surfaces - weak continuity becoming operationally expensive - strong need for issue concentration and pressure ranking
This is the clearest wedge territory.
The more the pain rises, the more the product becomes obvious.
9. Strong-fit buyer types
Strong-fit buyer types usually include:
Type A — The buried criminal reviewer
This person is personally living inside ugly files and feels the pain directly.
Type B — The workflow-aware partner
This person sees that the team is losing time and judgment to structural disorder.
Type C — The continuity-minded operator
This person knows handoff, re-entry, and structure are breaking under real load.
Type D — The severe-file specialist
This person may not use the product every minute, but they know the file class is punishing enough to justify real review infrastructure.
These are the best early buyers.
10. Weak-fit buyer types
Weak-fit buyer types usually include:
Type W1 — The low-burden generalist
Mostly simple files. Mostly admin problems. Not much structural pain yet.
Type W2 — The generic-AI tourist
Interested in hype, not in serious workflow pain.
Type W3 — The pure admin buyer
Main problem is billing, intake, contacts, or broad practice management.
Type W4 — The too-early believer
Understands the concept, but current file pain is not yet acute enough to justify adoption.
These are not bad people. They are just not the first battlefield.
11. What different personas need to hear
End user
Does this make the file easier to inhabit?
Operator
Does this preserve structure and continuity?
Buyer
Is this pain real enough and expensive enough to justify change?
Champion
Can I explain internally why this matters now?
Strategic audience
Is this company building something real, scalable, and defensible?
That is the cleanest persona-to-message map.
12. Why this matters commercially
If the company uses the same language for all personas, it weakens itself.
For example: - investor language can sound too broad for an operator - operator language can sound too tactical for an investor - end-user pain language can be too narrow for a strategic partner - premium Level 9 language can sound too abstract if the user has not first felt the lower-layer pain
That is why persona discipline matters.
It makes the whole commercial system more precise.
13. Clean summary lines
If this appendix needs to be explained simply, the cleanest lines are:
The user is not always the buyer.
The buyer is not always the person who feels the pain most directly.
The strongest early SUMMA fits are people living at high or extreme structural pain levels.
As pain rises, the wedge becomes clearer.
Those are the right summary lines.
14. Final takeaway
SUMMA should not think in one generic “customer” blob.
It should think clearly about: - who uses - who buys - who champions - who evaluates strategically - and what pain level the file environment is actually at
That is how the company avoids vague selling and keeps its wedge honest.