Five Products, One Pitch: What Three Portfolio Companies Taught Us About Selling a Platform

TL;DR: When a company starts selling a platform, the pitch breaks at the persona layer long before it breaks in the deck. Every product arrives with its own buyer, so reps can't tell who the platform is for and go back to the product they know. Diligent, Heartland, and Darktrace each started by mapping personas and jobs to be done across the whole portfolio, and only then built the pitch. I'd give any platform team the same advice: one job per persona, a pitch in three layers, and the persona map settled about three months before kickoff.

When Diligent brought us in, it had 14 sales forces. Each came from a company Diligent had acquired, and each had been hired to sell its own point solution to its own buyer. Diligent had also just changed its pricing and packaging and restructured sales around a single platform. Kickoff was the deadline for all of them to start telling the same story.

Diligent's VP of Product Marketing, Brittany Clark, described the goal as moving "from selling siloed point solutions to selling one cohesive platform."

Most companies that grow through acquisition, or through a roadmap that keeps adding products, end up at that same sentence. The homepage gets a new hero that says "platform," the CRO wants one pitch on the main stage, and somebody opens a new slide template.

That's usually where it goes wrong. In my experience, the deck is the last place a platform pitch breaks and the first place teams try to fix it.

The pitch breaks one layer down, at the question of who the platform is for and what each of those people needs done. No slide order can fix an answer the company hasn't agreed on yet.

We've worked through this with three portfolio companies in very different markets: Diligent after 14 acquisitions, Heartland across its small business portfolio, and Darktrace ahead of its annual sales kickoff. All three started in the same place, and the order they worked in is the part I'd copy.

Where the Platform Pitch Actually Breaks

A platform pitch is the story a company tells when it sells several products as one offer. It explains what the platform does, who it's for, and why buying the products together beats buying them separately.

Buyers are consolidating, but they don’t hand the win to platforms by default. In Futurum Group’s 2H 2026 survey, enterprise buyers who were consolidating split almost evenly: 47.3% were replacing point tools with platforms, and 44.7% were replacing them with new point solutions. A platform has to earn the consolidation deal, and the pitch is where it does.

Earning it is hard, because a platform pitch can break in four places, and each one depends on the one beneath it. It fails from the bottom up:

  • Personas - Each product arrived with its own buyer. One team sells to the general counsel, another to the CFO, another to IT, and a slide that lists all three makes the platform sound like it's for everyone in general and nobody in particular.

  • Jobs - Product teams describe what their own product does. A platform buyer wants to know what gets done across the products, and in most companies nobody owns that answer.

  • The talk track - With nothing agreed above it, each rep fills the gap with whatever already works in their own deals, which is usually the product they were hired to sell.

  • The deck - A redesign with a platform diagram on slide three can look finished while the layers under it are still unresolved. Reps notice within a week of kickoff, and they quietly go back to their old slides.

Here's how that shows up in front of a buyer. The products are the same in both columns, and the conversation is completely different:

Pitch built product by product Pitch built from the persona layer
Starts with The products and how they connect The buyers and the job each one needs done
First slide A platform diagram with every product logo The problem one persona is trying to solve
Other products show up At the end, as add-ons When the buyer's job calls for them
What reps lead with The product they know best The entry point for the persona in front of them
What the buyer hears A list of everything the company sells What the platform would do for them

What Diligent, Heartland, and Darktrace Had in Common

The three companies sell very different things: governance software for boards and leadership teams, payments and payroll for small businesses, and AI cybersecurity.

They came to us for different reasons, on different timelines, and asked for different deliverables. What they shared was the order of the work.

Diligent: 14 Acquisitions and One Platform Story

We started Diligent with leadership workshops on personas and buyer journeys, jobs to be done for each of its three new packages, and positioning and messaging.

The 14 acquired companies each had their own personas, so the first job was getting them onto one map. The platform pitch came after that, as a deck and talk track that brought all 14 acquisitions into one story, and it was rolled out to all 14 sales forces at kickoff.

Everything else was built on the same persona work: decks and two-pagers for ten industries, plus a library of product demo decks to help new reps ramp. The full engagement is in our Diligent case study.

Heartland: A Small Business Portfolio With Several Buyers

Heartland wanted to refresh the positioning and messaging for several core small business solutions in its portfolio.

Over six months, we mapped the key personas for each product, worked out the jobs each product's customers needed done, and ran workshops with stakeholders to align on ideal customer profiles and buyer motivations across several products at once.

New positioning came next, and then everything that used it: landing pages for each product, a new sales pitch deck, email outreach templates, customer-facing one-pagers, and copy for a demo video.

Every asset drew from the same persona and jobs work, so the website, the pitch, and the outreach could describe the same buyers in the same words. The full engagement is in our Heartland case study.

Darktrace: A Portfolio Heading Into Kickoff

Darktrace came to us ahead of its annual sales kickoff with a large portfolio and a request for sales enablement materials.

Over three months, we ran workshops with stakeholders across several products to align on ideal customers and buyer motivations, uncovered the key personas for each product, and worked out the jobs each persona needed done.

Use cases and value propositions for every product came out of that, followed by a personas and jobs alignment deck, a guide reps could work from, and finally battlecards and two-pagers on competitors and key differentiators.

Darktrace’s CMO, Chris Kozup, said the work gave his team a complete toolkit for communicating its offerings. The full engagement is in our Darktrace case study.

The Order Is the Lesson

Three industries and three timelines, and the same sequence every time. Personas and jobs came first, across the whole portfolio.

Positioning came second, the pitch third, and the assets reps carry into deals last. In every case, product, sales, and leadership were in the room when the personas were agreed, and nobody opened a slide template until they were.

Company Starting point First step What came after
Diligent 14 acquired point solutions, new packaging, and a sales kickoff Workshops on personas, buyer journeys, and jobs to be done per package Platform pitch and talk track, industry decks, and demo decks
Heartland Several core small business solutions due for a refresh Personas and jobs to be done for each product, aligned across products Positioning, landing pages, pitch deck, and outreach
Darktrace A large portfolio and an annual sales kickoff Workshops on ideal customers, personas, and jobs across products Use cases, value propositions, battlecards, and two-pagers

Start With One Job per Persona, Across the Whole Portfolio

Almost every portfolio company already has persona documents. The trouble is that each one was written for a single product, so the same buyer shows up under three names with three different priorities. The platform story inherits all of that confusion, and reps feel it first.

My rule for this stage is one primary job per persona, across the whole portfolio. A persona with four jobs pulls the pitch straight back into a tour of every feature.

A persona with one job gives a rep one problem to open on and a clear reason to bring in the next product, and the secondary jobs still have a home in discovery questions and product detail.

Getting there takes five steps, and it’s the same process we run in our B2B buyer persona development work. The first four are desk work, and the last one is where most of the value sits:

1. List every buyer every product sells to - Pull persona documents, win notes, and CRM job titles from each product team, and put them in one place.

2. Merge the duplicates - The CFO in one product's deck and the finance leader in another's are usually the same person. Keep one entry with the most specific description.

3. Give each persona one primary job - Write it in the buyer's words, as something they're trying to get done that more than one of your products touches.

4. Map products to jobs - For each job, note which products help, and which one a buyer would reach for first.

5. Get the room to agree - Review the map with product, sales, and leadership together. Reps use the personas their own leaders signed off on, and they ignore the rest.

To show what that looks like on paper, here's an illustration for a hypothetical platform selling payroll, expense management, and benefits software to mid-size companies. The real maps we build are longer, and the shape is the same:

Persona Primary job Entry product Products that follow
CFO Get one accurate view of people costs every month Payroll Expense management and benefits
Head of HR Run benefits enrollment without chasing spreadsheets Benefits Payroll
Controller Close the books without reconciling three systems Expense management Payroll

One more thing to settle here: keep the ICP and the personas separate. The ICP decides which companies the platform is for, and personas decide which people inside those companies the rep is talking to. Teams blur the two at this stage all the time, and our guide to ICP vs. buyer persona pulls them apart.

How to Build a Platform Pitch in Three Layers

Once the persona map is agreed, the pitch finally has something to stand on. We build it in three layers, each with its own job and its own owner.

The three-layer pitch: a platform story every rep tells the same way, one entry point per persona, and product proof underneath.

Layer What it answers How often it changes Usually owned by
Platform story What the platform does, for whom, and why buy it together Once or twice a year Product marketing, with leadership
Entry point per persona Which job and which product a rep opens with for this buyer When personas or packaging change Product marketing, with sales
Product proof How each product delivers, with demos, customer stories, and competitive detail Every release Each product team, with product marketing

The platform story is the top layer, and it should be short enough that every rep tells it the same way. It names the outcome the platform delivers across the persona jobs, the type of company it's for, and the reason to buy together.

Your CEO should be able to say it on stage, and a rep should be able to say it in the first two minutes of a call. It comes straight out of your positioning and messaging, which is why positioning sat before the pitch in all three engagements.

The middle layer is the one most platform pitches skip, and it's the one I'd spend the most time on. For each persona, it names the job to open on, the product that solves it first, the discovery question that surfaces the job, and the signal to bring in the next product.

This is where reps from different product teams finally start telling the same story, because each persona has one way in.

The bottom layer holds the detail each product team already owns: demos, customer stories, specs, and battlecards.

It changes with every release, so it lives in modular assets reps pull in when a buyer reaches evaluation. Diligent's version paired the platform pitch with industry decks for ten verticals and a library of product demo decks underneath.

How to Retrain Reps Who Used to Sell One Product

A rep hired to sell one product knows one buyer very well and the rest of the portfolio barely. The platform pitch asks them to open conversations with people they've never sold to and to talk about products they've never demoed. I'd treat that as a bigger change than any new deck, and plan for it separately.

Four things change for them at once. Each one deserves a round of practice before kickoff, with reps saying it out loud:

  • New personas - They now meet buyers that used to belong to another product team, and they need those buyers' jobs and language.

  • A new opening - They lead with the persona's job and its entry point, where they used to lead with their old product's top feature.

  • A trigger for the next product - They need to know which discovery answers mean it's time to bring in another product, and which mean it isn't.

  • New partners in the deal - Specialists from other product lines join some calls, so reps need to know when to bring them in and how to hand over.

Retrain in the same order you built the pitch. Teach personas and jobs first, then the platform story, then the entry points, and save product depth for last, when reps know which buyers they'll use it with.

My favorite test is simple: have every rep record a pitch for a persona they've never sold to, and certify it before kickoff.

Who builds that training depends on how your company splits the work, which we covered in sales enablement vs. product marketing.

Whoever owns it, listen to recorded calls a few weeks after kickoff and check whether reps open with the persona's job. Our guide to sales enablement training walks through that check.

One thing no deck can fix is compensation. If reps are still paid on quota for the product they were hired to sell, they’ll lead with that product no matter what the talk track says. Before kickoff, check that comp plans reward platform deals, or at least don’t penalize a rep for opening with another team’s entry product.

What to Settle Before Kickoff

The biggest lesson I take from these three engagements is about timing. A platform kickoff goes well when the hard decisions were made months earlier, and Darktrace's three-month runway is about right for most portfolio companies.

Persona work needs time for workshops and sign-off before anyone builds an asset, and every week you save there gets spent later fixing slides.

When What to settle Who owns it
About 12 weeks out Persona and jobs map across the whole portfolio, agreed in workshops Product marketing, with product, sales, and leadership
About 8 weeks out The platform story and the packaging it sells Product marketing and leadership
About 6 weeks out One entry point per persona, with discovery questions and next-product triggers Product marketing, with sales
About 4 weeks out Platform deck, talk track, and updated product proof Product marketing and product teams
2 to 3 weeks out Final materials and a pre-read sent to reps Enablement
Kickoff Practice by persona, in breakouts Enablement and sales managers
2 to 3 weeks after First call review on persona openings Sales managers, with product marketing

If your kickoff is closer than that, answer three questions before anyone touches a slide.

Who are the personas across the whole portfolio, and what is each one's primary job? What is the one-sentence platform story every rep will tell? Which product does each persona start with, and what signals the next one?

Get those agreed, and the deck, the talk track, and the training all have something solid to build on.

Work With Olivine on Your Platform Pitch

Selling a platform starts well before kickoff, with personas, jobs, and positioning that every product team agrees on.

Olivine's sales enablement agency work covers the full sequence we ran for Diligent, Heartland, and Darktrace, from persona and jobs workshops to platform pitch decks, talk tracks, battlecards, and kickoff preparation.

If your company is moving from products to a platform, or you have a kickoff on the calendar and a portfolio to explain, we'll help you build the pitch from the persona layer up.

Get in touch to plan your next kickoff with us.

Frequently Asked Questions (FAQs)

What is platform messaging? Platform messaging is the positioning and language a company uses to sell several products as one offer. It names the outcome the platform delivers, the type of company it’s for, and the job each buyer persona needs done, so every product team and rep describes the platform the same way.

What’s the difference between selling a platform and selling point solutions? A point solution sells one product to one buyer for one job. A platform sells several products as one offer, so the pitch has to start with the buyer’s job and show why buying together beats buying separately. Platform deals usually involve more personas and more stakeholders in the evaluation, which is why the persona map has to come first.

What is a platform pitch? A platform pitch is the story a company tells when it sells several products as one offer. It explains what the platform does, who it's for, and why buying the products together beats buying them separately. A strong platform pitch has three layers: a shared platform story, one entry point per persona, and product proof underneath.

How do you sell multiple products without confusing buyers? Sell multiple products by starting with the buyer's job and letting it set the order. Map personas and jobs across the whole portfolio, give each persona one entry product, and bring in other products only when discovery shows the buyer needs them. Buyers get confused when every product shows up at once, usually on the first slide.

Should each product keep its own pitch deck after a platform launch? Each product should keep its proof assets, and its standalone pitch should retire. After a platform launch, product decks become modular evaluation assets, with demos, customer stories, and competitive detail that reps pull in after the platform story and persona entry point. Keeping old standalone pitches in circulation gives reps an easy way back to selling one product.

How far ahead of sales kickoff should enablement materials be ready? Final enablement materials should be ready two to three weeks before sales kickoff, so reps can work through a pre-read and arrive ready to practice. For a platform kickoff, start about three months out, because personas, jobs, and the platform story need workshops and sign-off before anyone builds the deck or talk track.

How do you retrain reps who were hired to sell one product? Retrain reps who sold one product by teaching buyers before products. Start with the personas and jobs they haven't sold to, then the platform story, then the entry point for each persona. Have every rep record a pitch for an unfamiliar persona, certify it before kickoff, and review recorded calls a few weeks later.

Clayton Pritchard

Marketing leader with 11+ years of marketing experience including 6 years in product marketing across both B2B and B2C tech industries.

Next
Next

The B2B Rebranding Process: When to Rebrand, When to Refresh, and What to Keep