Partners Running an agency? Partner with us
The Graylemon Journal Build logs, teardowns and method, by email. Subscribe All resources
Follow the studio LinkedIn Instagram
Partner with usBook a call (opens in a new tab)
Framework · Sequence

The Narrative Spine

How should a product story run in a demo, a deck or a launch? In five beats, in this order: the problem, the stakes, the product moment, the proof, and the ask. The product arrives third, as the answer to something the audience already cares about.

  • Stage: Market
  • Discipline: Creativity
  • Graylemon original
The framework

Five beats, one direction.

The Narrative Spine: problem, stakes, product moment, proof, ask.
Fig. 02: The Narrative Spine, as a model · point at a partLoops while in view
Each beat

What each beat has to do

The same spine runs a sixty-second demo, a ten-slide deck and a launch page. Only the length of each beat changes.

Problem

One specific person, one thing that goes wrong for them today. The audience should recognise it before you explain it.

It's working when

Someone in the room says "that's us" before the product appears.

Stakes

What the problem costs if nothing changes: money, time, customers, trust. Stakes are what make the product moment matter.

It's working when

The cost is concrete enough to picture, and nobody has to take it on faith.

Product moment

Not the feature list: the single moment the product changes the outcome, shown rather than described. One moment, done well, beats a tour of the menu.

It's working when

The audience could describe the moment afterwards in one sentence.

Proof

Why they should believe it will happen for them: real screens, a customer's words, a result, a number with its source. Proof is labelled by where it comes from, and never invented.

It's working when

Every claim has something behind it the audience could check.

Ask

One next step, the right size for this audience: book a demo, start a pilot, try it free. Two asks split attention; none wastes the story.

It's working when

People take the step you asked for.

Worked example

A launch demo for the clinic assistant.

Illustrative example The clinic from Cut It, told the way we'd tell a real launch. Not client work.

  • Problem and stakes

    A receptionist phones tomorrow's patients one by one. Many don't pick up, and an empty chair is a lost appointment the clinic can't sell again.

  • Product moment

    A patient books a slot and pays for it in the chat they already use, on screen, in a few taps.

  • Proof

    In a real launch, the beta clinics' own words and their booking records. An illustration can't supply those, so it shows where they'd go.

  • Ask

    For clinic owners: start a pilot at your practice. One ask, for one audience.

Common misreads

Where it goes wrong

  1. Misread

    Opening with the product

    Why Without the problem and the stakes, the product moment answers a question nobody asked.

  2. Misread

    A feature tour instead of a moment

    Why Ten features shown quickly are remembered as none. One moment, shown well, is remembered.

  3. Misread

    Proof you can't stand behind

    Why A borrowed number or an unlabelled mock-up undoes the whole story the moment someone checks it.

Where this fits

AI Creative Build writes every demo, deck and launch on this spine.

AI Creative Build

In the Journal: Market: can we reach them repeatably? and Teardown: our old website

Published 28 September 2026. Graylemon original, approved September 2026.

Search Graylemon

↑↓ Move↵ OpenEsc Close