INSIGHT · DIGITAL AND 3D

How to explain a complex technical product: an eight-minute narrative structure

In technical sales the most expensive loss is superiority that never appears in the decision. With the right narrative, the meeting starts with the application scenario rather than with “what does this do?”

Key takeaways

  • Start the narrative with the problem, not the product.
  • Technical superiority is invisible in the decision until translated into the customer's metric.
  • Eight minutes is a realistic ceiling for a decision-maker's attention budget.
  • Every claim needs proof beside it; an unproven claim falls at the first objection.

The eight-minute structure

The structure has five parts: the problem the customer lives with today (1 min), the measurable cost of that problem (1 min), how the solution works (3 min), translating the difference into the customer's metric (2 min) and the next step (1 min).

This does not ignore technical depth; it puts it in the right order. How something works only becomes meaningful after the problem and its cost are clear.

Translate technical superiority into the customer's metric

“12 percent higher efficiency” is an engineering statement. Translated into the decision-maker's metric it becomes: this much annual energy cost, this payback period.

Without that translation proposals get compared on price alone and technical superiority disappears from view.

The division of labour between text and visual

Text makes the claim, the visual carries the proof. Working principles go in animation, sections in a visual, comparisons in a table. Repeating the same information in text and image splits attention.

Each page of a presentation should carry one message. A page carrying two usually loses both.

Place the objections in advance

Experienced sales teams know the three most common objections: price, integration difficulty and lack of references. Placing them inside the narrative in advance increases trust.

A narrative that ignores an objection leaves a question already present in the decision-maker's mind unanswered.

Tags
WRITTEN BY

Avenra Digital and 3D team

This insight was prepared by the Avenra team running field projects in digital and 3d. Editorial responsibility sits with founder and chief strategist Taylan Yıldız; the material is based on applicable findings from client work.

03FAQ

Frequently asked questions

How many slides should the deck have?
Message count matters more than page count. For an eight-minute structure 10–14 pages is typical, provided each carries one message.
Should engineering or sales present?
Both. Engineering carries the proof, sales carries the frame. In meetings presented by engineering alone the narrative usually drifts to product features.
Does the same structure work for investor decks?
Largely yes, with market size and scalability sections added and the working-principle section shortened.
→Let's begin

Let's turn this insight
into practice.

If what you read is heading towards a decision, let's define an applicable first step.