Assured · Discovery Session · Monday
A facilitation framework. Go in as discovery; let the bigger play be the sky, never the script.
The one rule
Run it as A — listen, ringfence, scope. Let B — the agent-native asset play — stay the ceiling. Earn it with the listening. Offer it only once they reach for it.
The bridge sentence — in their language Technical superiority that lives in people's heads is a cost. Technical superiority codified into systems is an asset — defensible, scalable, and it shows up on the balance sheet.
The arc
Three movements. Frame, ringfence, synthesise. Each has one thing to protect against.
HYPRCORP deck. Ambition and worldview — why agent-native, why now. Pre-loads B at the level of philosophy without committing Assured to anything.
Watch: frame, then get out of the way. Over-anchor and they feel sold-to before they've been heard.
Pure listening. Build the org graph as you go — every problem you capture is a node. Don't solve. Don't pitch. Capture.
Watch: the urge to leap to the answer. The answer isn't earned yet.
Mirror the pattern back. Cluster into tracks. Test how high they want to climb — and read their posture on exit.
Watch: the buyout framing is optionality & enterprise value — never "getting you flipped."
Hour 2
One row per problem on the whiteboard. Five columns — and every row is also a node in Assured's org graph. You're drawing the agent-native substrate without ever saying the word.
| Process | Pain | Owner | What "good" looks like | How we'd measure it |
|---|---|---|---|---|
| the workflow today | where it hurts, breaks, costs | who holds it in their head | the target state, in their words | the metric that proves it |
The gold question finds the un-codified technical superiority — knowledge trapped in someone's head. That's exactly the IP that, systematised, moves from a cost (key-person risk) to a balance-sheet asset.
Hour 3 · A
Group rows into 3–5 candidate tracks. A track is a cluster that shares an owner or system boundary, shares an outcome, and could become one software surface.
Hour 3 · B
Ask in order. Stop escalating the moment the room cools.
"If we systematised these, what does Assured become?"
Tests whether they think in capability terms. Listen for "we could do X at scale."
"Who else in your world has this same problem — and what's it worth to them?"
Tests whether they see the systems as a product, not just internal tooling. This is the multiple-expansion door.
"Three years out — are you running a bigger version of this, or building something someone wants to acquire?"
Direct exit-posture read. If "acquire" lights them up → bring the analogue. If it cools them → hold it. You've still got clean tracks and lost nothing.
Only if Q2 / Q3 land
A sensor & measurement company that wrapped data + software around the physical capability — and the market re-rated it, because it now pays for the software layer, not just the boxes.
Assured is the sensor company in that story.
Keep it qualitative. Cite the pattern, not invented multiples. Transparent math or nothing — fabricated numbers in a client room destroy more trust than they buy.
The exit