Make the whole make sense, featuring blue and white 3D imagery from Spin’s Microsoft Copilot in Viva project.

A platform narrative explains who your platform serves, the problem it solves, and why its products are more useful together. It gives each product a role in a larger customer story, without making every product sound the same.

Your portfolio can make perfect sense inside the company and still feel like a collection of unrelated offers outside it. Each product has its own deck, demo, launch plan, and vocabulary. The buyer is left to do the connecting.

That connection is the work. Before commissioning another overview video or rewriting the homepage, decide what the whole makes possible.

Start with the value between the products

“One platform” describes how you want to be perceived. It does not explain why someone should care. The useful question is more specific: what becomes easier, clearer, or possible when these capabilities work together?

Look for a customer task that crosses product boundaries. It might be moving from a signal to a decision, from an approved asset to a consistent campaign, or from a skills gap to a development plan. Choose a task your offering can demonstrably support today.

Then describe the connection in ordinary language. If the answer depends on words such as seamless, unified, or end-to-end, ask the team to explain the actual handoff. What information moves? What work disappears? What can the customer see or do that they could not before?

Build the story in four parts

1. What changed for the customer?

Name the pressure that makes the old approach less useful. That could be growing complexity, a new expectation, or a bottleneck the customer already recognizes. A credible opening begins with their situation, not the history of your company.

2. What is getting in the way?

Describe one central problem with a visible consequence. “Disconnected tools” is a category description. “The team cannot tell whether the approved campaign assets are the ones being used” is a problem someone can recognize.

3. What does the platform make possible?

Explain how the relevant capabilities work together to change that situation. Every product mentioned should advance the same customer task. A capability that does not help explain the main promise can wait for a deeper conversation.

4. What makes the promise believable?

Match each claim to evidence: a product demonstration, a documented integration, a customer-approved example, or a substantiated result. If the connection exists only on the roadmap, say so. A story should clarify the product reality, not disguise its gaps.

Use a message house to organize the central promise and its supporting points once the platform logic is clear. The narrative explains why the portfolio belongs together; the message house helps teams communicate that explanation consistently.

THE PLATFORM NARRATIVE

Four parts.
One reason to care.

Build the story around the customer, then support it with proof.

Customer change

What makes the old approach less useful? Name the pressure your customer already recognizes.

Central problem

What is getting in the way? Describe one problem and its visible consequence.

Platform promise

What becomes possible when the capabilities work together? Give each product a role.

Proof

What makes the promise believable? Use a demonstration, documented connection or substantiated example.

Lead with the customer. Earn the promise.Describe the experience that exists today, not an unqualified roadmap claim.
Use the four parts to build a narrative, not a catalog of capabilities.

A practical example: turn a catalog into a customer journey

Consider a fictional software company with tools for asset storage, approval, and campaign distribution. This is an illustrative example, not a Spin client result.

Its product-led introduction might read: “Our platform combines a digital asset library, approval workflows, and multichannel publishing.” That tells the buyer what is included. It leaves them to infer the value.

A more useful opening is: “Keep every campaign connected to the work your team approved.” The story can then show an asset moving from review to the library to distribution, with its approval status and version intact.

That promise only works if the products actually preserve those connections. If a manual export breaks the chain, either narrow the claim or explain the limitation. The strongest story is the one the experience can support.

Notice that no product has disappeared. Each now has a clear role in a sequence the customer understands.

FROM PRODUCT LIST TO CUSTOMER JOURNEY

Give the connections a job.

Keep every campaign connected
to the work your team approved.The customer promise in this illustrative software example.
Review

Approve the right asset.
Establish the version and approval status.

Library

Keep the approved work accessible.
Preserve its status and version.

Distribution

Put the approved work into use.
Carry that connection into each channel.

Review → Library → Distribution
Approval status and version stay intact across every handoff.

Fictional example. Only make this promise if the product experience actually supports it.

Give every product a job in the story

Build a simple map before writing channel copy. For each product, identify the customer task it supports, the capability that matters, its connection to the other products, and the proof available. Any product that cannot be placed deserves a discussion.

Some portfolios share a buyer or a brand without sharing a workflow. That can still be valuable. You do not need to claim technical integration to explain a coherent offer. Be precise about whether the connection is shared data, connected actions, a consistent experience, or complementary expertise.

If products serve fundamentally different needs, several related narratives may be more credible than one oversized promise. Consistency should help customers understand the differences.

Keep the promise consistent. Change the entry point.

An executive, a practitioner, and a technical evaluator may need different reasons to keep listening. Maintain the same central promise while changing the opening question, level of detail, and evidence.

For an executive, lead with the operational consequence. For a practitioner, show the task getting easier. For a technical evaluator, explain how the connections work and where the limits are. All three versions should remain true to the same product reality.

Give each format a specific role, too. The homepage establishes the promise. An overview film makes the relationship between capabilities easy to grasp. A product demo shows what changes in a real workflow. Product pages supply the detail needed to evaluate individual capabilities.

Visual consistency helps carry that connection. Shared hierarchy, diagrams, motion behavior, and terminology can make a complex portfolio easier to navigate. Our approach to building brand systems connects those decisions across the work.

Test whether the story survives outside the workshop

Put the draft in front of people who did not help write it. Ask them to explain who it is for, what gets better, why the products belong together, and what evidence they would need next. Listen for the meaning they repeat, not whether they remember your preferred phrasing.

Then give a marketer or seller a specific task: introduce one product using the platform narrative. If they need to invent a new company story to make the product relevant, revisit the connection. If every version becomes the same generic paragraph, make the product roles more specific.

Record the questions people cannot answer. Those questions are more useful than a round of comments about whether the copy feels exciting.

A one-page brief your team can use

Capture the working narrative under these six prompts:

  • Audience: Who needs to understand the platform, and what are they trying to accomplish?

  • Pressure: What makes their current approach difficult or insufficient?

  • Promise: What meaningful improvement can the platform support?

  • Connection: How do the products contribute to that improvement together?

  • Proof: What can you demonstrate or substantiate today?

  • Boundaries: What should the story avoid implying?

Give the brief an owner and a revision date. Revisit it when a product launches, an acquisition changes the portfolio, or the promised experience changes. Use it to guide the homepage, sales story, and creative brief before those teams produce separate interpretations.

A WORKING BRIEF

One page your team can use.

Six prompts to resolve before the next homepage, film or sales deck.

Customer

Who are we helping, and what are they trying to do?

Problem

What is getting in their way?

Promise

What does the platform make possible?

Product roles

How does each capability contribute to that promise?

Connections

What actually links the products or experiences?

Proof

What evidence supports the promise?

Give the brief an owner and a revision date.Revisit it when the offer, portfolio or promised experience changes.
A useful brief helps the team decide what to lead with, what to show and what to leave for later.

Make the whole make sense

A platform narrative earns its place when it makes the next creative decision easier: what to lead with, what to show, what to leave for later, and how each product contributes.

At Spin, we connect strategy, design, and storytelling so the idea holds from the first explanation through the final execution. Explore our branding capabilities or how we work alongside marketing teams.

Common questions

How is a platform narrative different from product messaging?

Product messaging explains the value of an individual offer. A platform narrative explains the value of the relationship between offers. It gives product messaging a shared context while preserving the details that make each product useful.

Does a platform narrative require integrated software?

No. A portfolio may be connected by a shared customer problem, experience, or expertise. The narrative must accurately describe that relationship and avoid implying shared data or automated workflows that do not exist.

How long should a platform narrative be?

Start with a one-page working brief that covers the customer, problem, promise, product connections, and proof. Add supporting detail where teams need it. Length matters less than whether someone can use it to make a clear, accurate communication.