Skip to content
How to Make a Deck
How to Make a Deck
Teardowns/Solution

Explaining HOW before WHAT it does for the customer

PrincipleLead with outcome. Save architecture for the appendix.

1 annotation · click a dot

How it works

  • Proprietary transformer fine-tuned on 2.4B tokens of legal text
  • RAG pipeline over the client's document store
  • Custom vector DB with sub-100ms retrieval
  • Human-in-the-loop review interface
1Weakens
Weakens
Nobody at seed cares about your vector DB

At pre-seed/seed, technical architecture is table stakes. What matters is what the customer feels.

Fix
Lead with the outcome (time saved, dollars, error rate). Architecture goes in the appendix.
More solution teardowns
A feature firehose instead of a wedge

Show the one thing you do that changes the customer's day.