Unifying messaging and GTM across a fragmented SaaS portfolio

Twice in my product marketing career, I've been in charge of a fragmented SaaS portfolio.

One portfolio got messy by acquisition: a few companies stitched into one, multiple product lines the market already knew by name.

The other got messy organically: one brand, one name, but new product lines bolted on every quarter as we tested what would stick.

We got there two different ways, but from the outside I was in the same situation both times. Too many products with no clear story. Ask three people inside the company what we did and you'd get three different answers, and none of them would have matched what our customers said they bought us for.

In both cases, the fragmented portfolio wasn't flagged as a problem by anyone in the business. What I got wrong as the PMM was letting it drift until it became one, then scrambling to realign messaging after the fact, when staying on top of it all along would have been far easier.

Whether fragmentation is actually hurting you comes down to one thing: whether the portfolio, and the way you message it, serve your business strategy. The number of products has nothing to do with it.

Faced with a sprawling portfolio, the instinct is to reach straight for the messaging: consolidate the decks, simplify the site, tidy the names. But I want to push you to treat messaging as the last move, not the first.

Before you touch a single positioning framework, you have to know where the business is actually trying to go, because that's the only thing that tells you whether messaging sprawl is a problem at all.

Take Stripe. When most people think of Stripe, they think of payment processing, even though they know it does far more.

Nobody calls Stripe fragmented, and if they did, it would hardly be a criticism, because its product lines all point in the same direction the business is going. The portfolio and the strategy agree. Sprawl only becomes a problem when the two disagree. When they do, the fix has an order to it, and messaging comes last. I'll get to that sequence at the end.

I’m going to lead this piece with the 2 cases I have dealt with in my career, because the framework came out of them. The move that worked was the same at its core in both companies: lead with your single strongest asset (not groundbreaking, I know), and let everything else earn its place behind it.

What changed was the shape of that asset, and that difference is what I want you to take away from this. In one company, leading with our strength meant running exactly the Stripe play. In the other, that same move would have sunk us. Here's how each played out.

Case one: acquired sprawl

Here's what fragmented looked like day to day. We had two ICPs, one set of brands built for SMBs and one for enterprise, with some light overlap.

We had tools with names the market recognized but new customers couldn't parse. And we did so much that customers kept telling us they didn't need all of it. They'd point at a competitor selling the single thing they wanted at a lower price and ask why they should buy thirty things from us to get the one.

We'd tried to fix it before, and the attempt is worth a short detour because it taught me something separate from the portfolio problem itself. We'd decided to push harder into enterprise, since some of our tools could clearly be priced higher there.

Reasonable on paper. In practice, it meant shifting from a product-led motion to a sales-led one, split across two teams. I ran one of them. Both teams hit their targets. The initiative still got labeled a failure because nobody had aligned those targets to each other, or to the actual business goal, before we started. We found that out deep into the test, too late to fix.

Because I hit my number, the blame didn't land on me. I hated it anyway. Burning company resources and my own time because the alignment work didn't happen upfront is exactly the kind of avoidable failure that sticks with you. I now force that stakeholder alignment before a test kicks off, while there's still time to shape it.

That detour aside, the real diagnosis underneath the failed enterprise push was this: we had no single leading thing anymore. We used to. But newer divisions had grown more profitable, so what the market knew us for wasn't what we wanted them thinking about. We were trying to borrow the strength of our old flagship to sell newer lines, and customers didn't buy it. The trust didn't transfer.

So the first real move was to find what actually connected everything. In this case, it was the data that powered everything the business did. That through-line made every sub-brand strong, so I made it the message and aligned the portfolio around it.

That meant retiring the standalone name of the line we were now pushing hardest, and letting it borrow the parent company's brand equity instead of growing a small name from scratch.

It meant killing a new brand name that was about to launch internally. And it meant deprioritizing our most popular, most recognized tools on the homepage, in email, in offers. We still had to promote them; they were the base, but they moved to the background.

That last part had a lot of people ready to stand their ground. The people who'd built those popular lines had watched them grow from nothing, and into an incredibly successful business.

If I'd walked in and said "we're not focused on that anymore," it would have gone badly, and deserved to. So I didn't frame it as taking anything away. I framed it as leverage: here's why we're focusing on something else, and here's how we're using the strength of the lines we're deprioritizing to power it. Nothing was being cut, and I made that clear. The resistance stopped once the team saw their work as the foundation rather than the casualty.

What got better: engagement with our marketing climbed, and conversion went up. Nothing in the lineup changed. We just stopped trying to convince the market of something new and anchored on a strength customers already believed, and the selling got easier.

The counterintuitive part was the email data. Because we were saying fewer things, we sent fewer marketing emails. Open rates went up, and unsubscribes went down. 

Less marketing, but better marketing.

Managing a large product portfolio with limited team members

Discover how product marketers can manage large portfolios with limited resources - key metrics, prioritization, tools, and scaling strategies.

Product Marketing AllianceCharley Gale

Case two: organic sprawl

Different company, similar mess, opposite origin.

This one was all one brand, one name. We started with a single product; it worked, and we kept expanding into new lines. We tested constantly to see what the market wanted, and what stuck was often not what I'd have bet on. So the portfolio grew sideways, fast.

Day to day, the confusion this time was about how each line fit into the overall business and each person’s role. The same people were managing multiple personas across projects, and it wasn't obvious to the whole org who the ICP was for each line. We were growing so fast the documentation couldn't keep up. Sales felt it most, juggling products without a clear sense of who each one was for.

The diagnosis here had nothing to do with politics. No separate camps, no founders guarding turf. The problem was that we were fast and reactive. When we launched a new line, we deliberately kept it separate from the brand, because we didn't know yet if it would work.

Smart at the time, and you'll still see many startups operating under this model. But for the lines that did work, we never went back and folded them into the brand. The reintegration step just never happened. It was nobody's fire to put out.

The fix was to slow down and run the Stripe play. We kept our most profitable, best-known line as the main offering and the front door. We brought customers in through it, cleaned up its messaging so it wasn't bogged down by offerings relevant to fewer people, then used sales reps to cross-sell the rest once customers were already in, with light marketing support like email behind them.

The other lines didn't disappear. They moved to the bottom of the homepage, findable but not fighting for the spotlight, and we rewrote our boilerplate, the one-line and one-paragraph company descriptions, to lead with our strength instead of listing everything.

The resistance this time came down to budget math. Nobody wanted the other lines promoted equally, but the instinct was to put half our top-of-funnel spend on the main product and spread the rest across the others.

I took the case to my manager: top-of-funnel investment in the smaller lines had worse ROI than acquiring customers through the flagship and cross-selling into them cheaply later. Keeping detailed reporting on everything the team had done up to that point made the case easy to build.

And here's the part I wish I had done differently. I did this much later than I should have, long after the winning lines had clearly proven themselves. Nobody pushed back on slowing down, but nobody pushed me to do it either.

The consolidation work had no owner and no deadline, so it sat there while we chased the next test, and the delay cost the business real money, call it a quarter of runway on the wrong spend. That's the trap with reactive growth: the cleanup is never urgent enough to beat the next shiny thing, so it rots quietly until someone owns it.

I now treat portfolio consolidation as a standing responsibility, something owned on purpose rather than a someday project for when things calm down. Things don't calm down.

What got better: the persona confusion cleared up, and the org could finally say who each line was for. Cross-sell worked; customers who came in through the flagship bought the other lines, which was the entire bet. And sales stopped being confused, which made their jobs easier and our funnel cleaner.

Horizontal or vertical: the shape of your strength decides the fix

Both stories ran on the same principle, and yet the right move in one would have been the wrong move in the other. The shape of the strength decided everything.

In the acquired portfolio, the strength was a capability sitting underneath all the products: the sheer amount of data the company held and what we could do with it. Every sub-brand was strong for the same underlying reason. So the unification ran horizontally. I took that shared capability and made it the connective tissue across the whole portfolio, then aligned every sub-brand's message to it.

In the organic portfolio, the strength was one product: our most profitable, best-known line, the thing we were actually famous for. So the unification ran vertically. We led with that one line as the front door, acquired customers through it, and cross-sold the rest behind it with light marketing support and a sales assist.

If I'd run the horizontal play on the organic portfolio, I'd have diluted the one product that was carrying us. If I'd run the vertical play on the acquired portfolio, I'd have crowned a single product when our real edge was the layer underneath all of them.

The shape of your strongest asset tells you which way to unify. That's the whole game.

The pattern underneath both

Strip away the specifics, and the same discipline shows up in both companies: a willingness to kill what doesn't earn its place. Sometimes that's a full sunset. Sometimes it's pulling a line off the site and cutting off new traffic while still supporting the customers already on it. That instinct isn't attachment to a product or a name. It's attachment to the strategy, and a refusal to let the portfolio drift away from it.

Both times, the sprawl was only a problem because the portfolio had stopped pointing where the business was going.

In the acquired company, the market knew us for the wrong thing. In the organic company, the winners never got folded back into the story. Neither was a "too many products" problem. Both were "the portfolio and the strategy have come apart" problems that happened to look like clutter.

Run the diagnosis in order

Before you touch a single positioning framework, work through these in sequence. Even if your business has an entirely different situation than either of my cases above, this should help you be in the right place to take action. 

You should be able to answer each of the following with enough conviction to defend it to your CEO. 

Strategy first

What does the business want to be known for, and where is it trying to go? Which lines pull in that direction, and which are just along for the ride? Fragmentation is only a problem when the portfolio pulls against where the business is headed. If it points the same way, leave it alone. Sometimes the sprawl is fine and consolidating would be the mistake.

Then your customers

Do the lines serve the same audience, or genuinely different ICPs? A shared audience means one story can stretch across the portfolio. Different audiences mean you're running distinct plays, whether you've admitted it yet or not.

Then where your strength sits

Is it concentrated in one product, or spread across many as a shared capability? That answer is the fork from the two stories above: concentrated sends you vertical, flagship as the front door, and shared sends you horizontal, that capability as the connective tissue. Check the economics here too.

Can the business handle a different CAC for a line you acquire on directly versus one you only cross-sell into?

If you don't know the numbers, you can't defend where the budget goes.

Only then do you touch the messaging. The diagnosis, not the mess, tells you the move.

Don't look at fragmentation as a failure

Most people look at a sprawling portfolio and ask, "How do I clean this up?" That's the wrong question. It sends you tidying symptoms while the real problem sits untouched.

The same sprawl can be healthy at one company and fatal at another. What decides which is whether the portfolio serves the strategy.

Stop asking how to clean up your portfolio. Ask whether it points where your business is going. If it does, leave it alone. If it doesn't, lead with your strongest asset and let everything else earn its place behind it.