Presentation Playbook

deet caught on because every surface tells the same story: a proof you can run.

The proof loop

1. Show the command

deet check

2. Show the receipts

deet compile --target duckdb --out dist
deet contract --out contracts

3. Show the artifacts

• dist/sql/*.sql for the warehouse
• contracts/*.d.ts for app code
• dist/graph.rxg.json for lineage + diffs
• .deet for shareable context

The receipts we lead with

• No hidden steps: every claim is backed by a command
• Portable outputs: SQL and contracts run anywhere
• Fast proof: green check in under 2 minutes
• Shareable context: .deet and templates make it repeatable

Five-minute demo outline

deet init demo
cd demo
deet check
deet compile --target duckdb --out dist
deet contract --out contracts

What to show:

• The type error is actionable (file + line + fix hint).
• The SQL exists in dist/sql/ and runs in your warehouse.
• The contract exists in contracts/ and plugs into TypeScript.

Common objections

"Is this a platform lock-in?"
No. The outputs are plain SQL + contracts. You own the artifacts.

"Will this fit our workflow?"
Yes. deet is a compiler. It drops into existing CI + warehouse runs.

"Is the story consistent?"
Every page points to the same proof loop. No special-case demos.