The outcome you are walking toward
A clear picture of who institutional briefings are shaped for — not a downloadable talk-track pack, and not one generic deck for every senior room. This page lists personas and meeting jobs only. Full briefing kits stay internal / briefing-room material.
What this page is (and is not)
- Is: the role map that serious multi-location buyers actually need: Executive, Operations, Finance, Security/Risk, and IT/Integration.
- Is not: full talk tracks, leave-behind PDFs, ROI calculators, or sample filled evidence.
- Is not: a pricing page. Commercial structure stays pilot → cohort → network principles until a live briefing.
Deal-specific materials are shared through a diligence briefing or scheduled briefing when they exist. Until then, treat this leaf as orientation.
Why role-shaped briefings matter
Institutional deals tend to die from silent stakeholders more often than from technical failure. The buyer journey Stage 3 — Internal Coalition — is where Operations, Finance, IT/Security, and sponsors either align or quietly stall. We do not run one generic story when the audience is mixed and senior.
Who we brief (persona map)
Each row is a meeting job — not a public script. v1 personas are locked: Executive, Operations, Finance, Security/Risk, and IT/Integration.
- Executive / Sponsor — Create clarity, reduce perceived risk, and earn the right to a real pilot conversation. Desired outcome: they can explain the core idea to peers and name a sponsor path.
- Operations Leadership — Show we understand the real operational surface area and will not create more chaos than we remove. Desired outcome: suitable pilot locations and active participation.
- Finance / Commercial — Make economic and control logic clear; show financial guardrails are native. Desired outcome: credible path from pilot cost to network-scale economics — principles only on public surfaces; no invented dollar bands.
- Security / Risk / Compliance — Demonstrate authority, policy, offline behavior, evidence, and conformance are designed in. Desired outcome: early diligence asks, not late ambushes. Public conformance is LEVEL only; deep attestations stay on request.
- IT / Systems / Integration — Clarify what is replaced, integrated, or left alone, and how edge + kits land. Desired outcome: a practical site-readiness path. Start from the integration pattern family map. Physical composition lives under the STORE Solution — not a parallel product dump.
What each room is for (outline shapes)
These are public outline shapes — not the internal talk track. Leave-behinds in live briefings stay engagement-filled blanks, never invented results.
Executive / Sponsor
- Job: clarity and sponsor path — not a network buy on day one.
- Usually covers: organism idea · phased path · what Phase 1 proves · what we are not asking yet.
- Leave-behind shape: one-pager with qualitative “good,” Evidence Package categories, and a named next step — no logos theater, no invented returns.
Operations Leadership
- Job: prove we understand the floor and will not add chaos.
- Usually covers: vertical surface · day-in-the-life agent team · first weeks of a pilot · offline and exceptions · location shortlist.
- Leave-behind shape: scenario cards (recovery, near-miss, form, maintenance classes) with qualitative “good” and escalation paths.
Finance / Commercial
- Job: control model first; returns language only after operational proof.
- Usually covers: envelopes and spend authority · real-time vs lagging signals · phase map matched to commercial commitment · CapEx vs OpEx principles.
- Leave-behind shape: economics one-pager with no dollar cells — phase labels, control model, value categories only. Rate language waits for an approved source.
Security / Risk / Compliance
- Job: designed-in authority, offline, evidence, and LEVEL gates.
- Usually covers: authority model · offline contract · reconstructability · LEVEL honesty · diligence-ask capture.
- Leave-behind shape: empty diligence checklist they fill in their words — we do not pre-invent certifications. Start from diligence resources, the governed agent boundaries reference, and agent authority.
IT / Systems / Integration
- Job: integrate vs replace vs leave — with a site-readiness path.
- Usually covers: edge autonomy · identity / network · boundary workshop · STORE as Solution composition.
- Leave-behind shape: integration boundary table (system class · decision · owner · pilot note). Prefer system classes over vendor theater on anything that leaves the room.
How briefing sequences usually run
Executive clarity first, then Ops + Security depth, then Finance structuring, then IT architecture. The same scenario library is reused; emphasis changes by audience. Language discipline matters: if the story sounds like every other platform, experienced buyers leave.
Evidence at Phase 1 exit
When a Foundation Pilot closes, the exit instrument is an Evidence Package mapped to the Pilot Charter — categories first, filled packs stay briefing/NDA. See Know what a Phase 1 Evidence Package must contain. Public pages will not host fabricated sample results.
Requesting a role-shaped briefing
State your role on Request Access — operator, partner, or counsel — or start from the diligence reading path. Ask for the stakeholder kit that matches the room you are bringing. We will not publish internal talk tracks on this site.