33 — Who SUMMA Is For

One of the fastest ways to weaken a serious product is to pretend it is equally for everyone.

SUMMA should not make that mistake.

A strong product begins by knowing where its value is most real. In the SUMMA worldview, the product is not mainly for the smallest, thinnest, sleepiest file. It is not mainly for the matter that can already survive inside ordinary folders, PDFs, search, and private memory. SUMMA becomes most valuable when the record crosses a threshold and starts punishing the people inside it.

That threshold is the real target zone.

SUMMA is for lawyers and review teams working files that have become structurally difficult. The file may be disclosure-heavy, mixed-format, witness-pressure-heavy, timeline-sensitive, contradiction-rich, forensics-heavy, or procedurally unstable. It may contain many productions, corrected productions, large media bodies, or issue clusters whose significance changes as the record evolves. The core commonality is not one charge label. The core commonality is burden. The file has crossed the point where ordinary tools no longer solve the main problem.

That is the first truth about the target user.

The second truth is that the target user is not defined only by role title. It is defined by pain.

A criminal defence lawyer may be the target user in one matter and not in another. A public defender may be the target user on one file and not on a lower-burden one. A litigation-support professional, articling student, associate, or senior trial lawyer may all become target users if the record is severe enough that structure, re-entry, issue concentration, source discipline, and pressure ranking become operationally valuable. In that sense, SUMMA is less a product for one job title than a product for one class of problem.

That class of problem is the monstrous file.

These are the kinds of files where disclosure arrives in waves, where mixed evidence types collide, where witness pressure forms contradiction zones, where timelines matter more than people expected, where later productions change the meaning of earlier ones, and where the reviewer starts paying a serious tax every time they return to the case. In that environment, the difference between storing the file and inhabiting the file becomes brutal. SUMMA is built for that difference.

This means the first beachhead user is not “all lawyers.”

It is closer to this: criminal defence lawyers and teams handling disclosure-heavy, structurally punishing matters in which ordinary tools stop composing into a survivable review environment. The product may later expand outward, but the wedge becomes strongest where the burden is already severe enough that the architecture immediately makes sense.

A useful way to say it plainly is this:

SUMMA is for the file that has crossed the point where folders, PDFs, notes, and memory are no longer enough.

That is the right level of honesty.

It also explains why the product should not be positioned mainly as generic legal AI. The market already contains strong practice-management tools, chronology tools, eDiscovery tools, transcript tools, and digital-evidence tools. Those products are useful, and many of them are mature. SUMMA’s sharpest value is not that it also stores things or also uses AI language. Its sharpest value is that it is built around the threshold where the file becomes cognitively punishing and structurally unstable.

That is a narrower target than “legal tech” in general, but it is a much more serious one.

It also means the product should not apologize for being stronger on ugly files than on easy ones. That is not a weakness. It is part of the identity. The file that ordinary systems can already handle gracefully is not where SUMMA proves itself best. SUMMA proves itself where issue sprawl, source drift, re-entry pain, contradiction pressure, and mixed-format burden start defeating ordinary review habits.

The reader should leave this chapter with one central understanding: SUMMA is for lawyers and teams facing files that have crossed from ordinary inconvenience into structural review pain, where the record is difficult enough that better source discipline, issue concentration, continuity, and pressure-aware review become genuinely valuable.