Skip to content
Contents

1. Revenue systems

2. Builds

3. The operator

4. Writing

5. Journal

6. Resume

7. Appendix

166 wordsby CONNOR J. LAUGHLIN

Outcome-first narrative architecture.

A messaging architecture where every claim carries its proof and its approval state.

Outcome

Built a multi-business-unit messaging architecture with proof governance and outcome-first positioning.

Claim to approvalThe claim register lifecycle behind the messaging architecture: a buyer outcome, the claim made about it, the evidence, the tier that evidence earns, the approval reference that holds the claim until someone signs it, and the published message.BUYER OUTCOMECLAIMEVIDENCETIER ASSIGNMENTAPPROVAL REFERENCEPUBLISHED MESSAGE
FIG_016 [ Claim to approval ]A claim reaches the page only after someone has put their name to it.

The acquired brands were each saying something different, and some of it couldn't be defended if a buyer pushed. I built a messaging architecture that leads with buyer outcomes, attaches evidence to every claim, and records who approved it. Sales says things the company can stand behind.

The case

  1. 01The problem

    Decks led with service language. Sales had nothing quantified to anchor a conversation.

  2. 02What I built

    I mapped features to quantified outcomes across the business units, built sales talk tracks, a do and don't language guide, and a versioned messaging system.

  3. 03What changed

    Sales started leading with outcomes. Buyer conversations got tighter and shorter.

  4. 04What it proves

    A narrative rebuilt around proof, with every claim keeping its approval state.

Proof

Chapter figures

outcome-anchored talk tracks
Multi-unit. outcome-anchored talk tracks. Feature-to-outcome mapping across the business lines. The unit count is not published..
messaging system
Versioned. messaging system. claim owners, language rules, change control.

Systems built

  1. Feature-to-outcome mapping
  2. Do and don't language guide
  3. Versioned messaging system
  4. Sales talk tracks with proof anchors

Chapter details

Scope
  • Feature mapping
  • talk tracks
  • language rules
  • enablement.
Stack
  • Outcome mapping
  • Sales enablement
  • Brand governance
Governance
  • Language rules
  • claim owners
  • versioned messaging system

Governance notes

  • Language guide mandatory for legal-reviewed materials
  • Claim consistency tracked in the register

In the interview

I rebuilt the narrative around quantified outcomes. Service language was the easy part to delete.

Long form

A written walk-through of this one, in full.

Read it
Email Connor

Open to VP of Marketing & GTM, Head of GTM, VP Revenue Operations, and GTM engineering roles at AI-native B2B SaaS and PE-backed growth companies that build the tools of change. Chicago, hybrid or remote.