Discovery · Decision extraction

From war story to decision map in sixty seconds.

An instrument used in discovery with construction and specialty-trades estimators. The expert tells the story of a recent bid, and the system returns the decisions inside it, structured, ranked and tagged for what to encode and what to keep human.

Shipped to a client
DomainConstruction and trades estimating
TypeDiscovery instrument
StackClaude · Supabase Edge Functions
InputTyped story or a call transcript
5Layers per decision: trigger, frame, logic, move, echo
90 minCall transcripts processed in one pass
3–6Decisions from a short typed story
Encode or humanEvery decision tagged for what happens next
01
The problem

Experts can't list their decisions. They can only tell you stories.

Ask a senior estimator to list their judgment calls and you get generic answers. Ask about the job they almost walked away from, and every real decision is inside that story: unstructured, and about to be lost in someone's notes.

A story is not a spec. If the consultant reconstructs the logic later from memory, the AI ends up automating a generic idea of the work instead of the expert's actual decisions.

Pain pointWhat it costWhat the build does
Checklist interviews
The decisions that drive the number never come up.
Story-first capture: the expert tells a real bid; the system finds the decisions.
Notes lose the logic
Reasoning is rebuilt later from memory.
Each decision comes back in a five-layer structure, in the expert's words.
No ranking
A dozen decisions, no sense of which matter.
Every decision ranked for what to encode first.
Invented answers
A demo that makes things up when it fails destroys trust.
If it cannot extract, it says so. It never invents a result.
02
The approach

Three tools, one secure backend. Built for the room.

A sample tool that runs anywhere, a live tool for typed stories, and a transcript tool for a full recorded discovery call (recorded with consent). All three use the same server-side extraction, so the API key is never exposed.

The moment that lands: an estimator watches their own judgment come back structured, in their own words.

Each decision comes back with its trigger, its frame, the real criteria behind it, the move made, and what it leaves behind to learn from, plus a rank and a tag: encode (logic a system could apply) or human (judgment that is relational, political or contextual).

The tags across a whole call become the first draft of an engagement roadmap: what to build, what to leave alone, and in what order.

03
How it works

Story in. Ranked, tagged decision map out.

Four stages between a narrative and a plan an engagement can be scoped against. Click a stage.

Interactive

See a sample extraction

A short bid story and the decisions the instrument returns. A sample, not a live call.

The story, as told"We almost walked on the school reline. Soil report came back vague, and the GC on it has a habit of pushing schedule risk down to us. I bid it anyway, but I put twelve percent contingency on the excavation instead of my usual five, and I told them we'd only hold the price thirty days. Thing is, they're a repeat client, so I didn't add my usual premium for a new GC."
04
What it shows

What this work shows.

Discovery output becomes a build plan, not a pile of notes.

Stories beat checklists

Real decisions live in narratives. Capture the story, then extract the structure.

Rank before you build

The rank turns a list of decisions into a sequence.

Some decisions stay human

A process that marks everything as automatable is a sales document, not a diagnosis.

Fail honestly

It reports what it cannot do rather than inventing what it can.

05
See it working

Try something like it.

ClaudeSupabase Edge FunctionsCall recording with consentFive-layer decision schema

Whose judgment is your business one resignation away from losing?

The same pattern fits estimating, underwriting, claims triage and procurement. Bring a war story to the first conversation.

📅 Book a call