peopleanalyst

Reference implementation · the communication engine

One engine, three grammars.

A presentation is a surface composed from the connective substrate — not a document we author. Three deck grammars share one StoryBrand skeleton; only the object in the hero slot changes. The client-insight grammar is already running: it projects a complete data-story (DS-7+1) into a decision-ready readout. Charter: docs/strategy/COMMUNICATION-CAPABILITY-CHARTER.md; the engine’s canonical home will be the toolbox.

Investor

10 roles

Object: equity in a future company · Works with: thesis · traction · market · team (mostly authored) · Close: meeting / diligence / term sheet

What this isWhy nowWhy it can be bigThe wedgeThe unique insightProofScaling logicMoatTeamRound logic

Customer

8 roles

Object: a product that solves their problem · Works with: situations · brandscripts · proof cards · Close: trial / pilot / purchase

Your situationThe problem & its costWhy the old way is breakingThe better futureHow we get you thereProofRisk reversalNext step

Client-insight

8 roles

Object: a decision to make from their own data · Works with: their data · analytics recipes/models · the story-card shelf · behavioral priors · Close: decide + act + the priced next step (certainty upsell)

Who this is forThe decision on the tableWhat we believed walking inWhat the data showsWhat it means for youThe moveAct / don't actThe honest close

Authored decks (investor / customer)

These grammars are authored: a deck spec supplies content per grammar role and the engine orders it by the spine. Same engine as the readouts below — second path. Confidential (investor room); drafts still carry [bracketed] figures for Mike to fill.

Customer decks (derived from brandscripts)

The customer grammar is derived, not authored: each persona’s SB7 brandscript assembles into a customer deck with zero re-authoring — the engine fanned across every live persona. Same renderer as the investor decks above. Drafts; the proof slide attaches its paired situation.

Client-insight readouts (assembled, not authored)

Each readout below is projected from the story database into the DS-7+1 grammar by the engine. The charts are designed canonical scenes— the platonic form a confirmed story presents as — not any client’s data.