Skip to content

Appendix F — Founder Sales Playbook

This appendix is the operating playbook for founder-led SUMMA sales.

Its purpose is not to create a polished fantasy of selling. Its purpose is to create a serious, repeatable, honest commercial motion.

SUMMA should not be sold like a generic SaaS toy. It should be sold like a wedge product with a narrow, painful, high-value lane.

That is the spirit of this playbook.

1. Core commercial truth

SUMMA is not for every file equally.

It is strongest where the file has crossed from ordinary inconvenience into structural review pain: - disclosure-heavy - mixed-format - contradiction-heavy - hard to re-enter - hard to hand off - hard to prioritize honestly

That is the wedge. Every sales conversation should stay anchored to it.

2. What the founder is really doing

In early sales, the founder is not just selling.

The founder is: - testing the wedge - sharpening the language - identifying real pain - rejecting weak-fit buyers - learning which proof points actually land - learning which objections are real - protecting the product from fake positioning

That means every sales conversation is also product learning.

3. The founder sales sequence

A serious founder-led motion should run in this order:

  1. identify prospect
  2. run discovery call
  3. decide if fit is real
  4. run focused demo
  5. decide if pilot is justified
  6. run structured pilot
  7. evaluate outcomes honestly
  8. expand, refine, or walk away

That is the full sequence.

Do not collapse it. Do not skip straight to pitch. Do not force a pilot before real pain is visible.

4. Target prospect profile

Strong early prospects usually have some combination of:

  • serious criminal defence work
  • disclosure-heavy files
  • mixed media / video / audio burden
  • issue sprawl
  • contradiction pressure
  • painful re-entry
  • weak handoff
  • a sense that current tools are searchable but not inhabitable

Weak early prospects usually have:

  • mostly low-burden files
  • mainly administrative pain
  • mostly simple workflow problems
  • a desire for generic AI help
  • no real continuity or structure pain
  • little reason to change current habits

The founder should get comfortable distinguishing these quickly.

5. What to say first

The founder should begin with pain, not with features.

Good starting frame:

SUMMA is for the point where a criminal file gets ugly enough that folders, PDFs, notes, search, and memory stop being enough.

Or:

The problem is usually not opening the documents. The problem is preserving the structure of the file well enough to think inside it.

That is the right opening temperature.

6. What not to say first

Do not lead with: - generic AI language - Level 9 - “strategy generation” - dashboards - fancy summaries - everything the product can eventually do

That weakens trust.

The early conversation should feel like: we understand the pain, we know where current tools break, and we have a system built for that threshold.

7. Discovery call rules

The discovery call should answer one question:

Is this prospect living inside the kind of pain SUMMA is actually built to reduce?

If yes, continue. If maybe, keep warm. If no, do not fake the fit.

Good discovery calls feel diagnostic, not performative.

8. Demo rules

A strong SUMMA demo should move in this order:

  • pain
  • source
  • issue concentration
  • workbench
  • continuity
  • pressure
  • Level 9
  • proof-oriented close

The founder should not let the demo turn into feature tourism.

The buyer should leave feeling: - understood - structurally relieved - clear on what changes - clear on what SUMMA does not claim to do

9. Level 9 rules

Level 9 should be sold carefully.

It should be described as: - strategic pressure support - attention ranking support - help surfacing what changed posture - help distinguishing what is loud from what is dangerous

It should not be sold as: - automatic legal strategy - machine-generated defence truth - replacement for counsel judgment

The founder should treat Level 9 as premium credibility, not cheap excitement.

10. Pilot rules

A pilot should only happen if: - the pain is real - the file is severe enough - the buyer understands what is being tested - success criteria are explicit

A SUMMA pilot is not a vague free trial.

It is a focused test of whether the system reduces: - re-entry loss - issue rediscovery - weak handoff - source drift - poor pressure visibility

That is what the founder should keep bringing the pilot back to.

11. Close / no-close rules

Move forward when:

  • the buyer clearly feels the pain
  • the demo lands against real workflow problems
  • the file is severe enough to justify change
  • the pilot shows real structural relief

Slow down when:

  • the fit is interesting but still early
  • the buyer has some pain but not enough urgency
  • the workflow does not yet justify a serious switch

Walk away when:

  • the buyer mainly wants broad admin convenience
  • the buyer wants fake AI magic
  • the file burden is too low
  • the product would have to be misrepresented to sound like a fit

This is a serious playbook, so “no” is part of the system.

12. Core proof points to keep repeating

The founder should keep the proof simple and operational:

  • less re-entry loss
  • less issue rediscovery
  • stronger source return
  • cleaner handoff
  • better issue concentration
  • better visibility into where the real pressure lives

These are much stronger than dramatic claims.

13. Core founder lines

Strong opener

SUMMA is for the threshold where criminal files stop being administratively annoying and start becoming structurally painful.

Strong demo frame

This is not a demo about flashy AI. It is a demo about what happens when the file becomes too ugly for ordinary tools to hold together properly.

Strong Level 9 line

Level 9 is not automatic strategy. It is strategic pressure support.

Strong pilot line

We are not testing whether the product is impressive. We are testing whether it reduces real structural pain.

Strong honest close

If the pain is not strong enough yet, SUMMA may not be urgent. If it is, the next step is to test whether the system actually makes the file more survivable.

14. Founder discipline rules

The founder should always remember:

  • do not oversell
  • do not universalize
  • do not rush to pilot
  • do not fake urgency
  • do not use generic legal-tech language when specific pain is present
  • do not sound bigger than the proof
  • do not let excitement outrun clarity

That discipline is part of the moat.

15. Final takeaway

The founder sales playbook is simple:

Find real pain. Qualify honestly. Demo in the right order. Introduce Level 9 late. Pilot against real burden. Measure operational relief. Move forward only when the fit is real.

That is how SUMMA should be sold.