Hi, I’m James. Thanks for checking out Building Momentum: a newsletter to help startup founders and marketers accelerate SaaS growth through product marketing.
I’ve been thinking about this a lot recently, due to my work and things my friends are also working on. I’ve helped create, rollout, and scale second and third products.
There definitely is a right and wrong way to build your second product. I actually think that in an ideal world, your second product should be a product you acquire, rather than build yourself – I’ll explain why later.
But first, let’s look at the usual way a second product comes about, and then how I think it should be done.
In this post:
A typical second product story
I’m talking about a second actual product, not just a major feature of an existing product. A second product that should have it’s own dedicated product/engineering teams and a separate go-to-market.
What usually happens is this: your founder or someone in the exec team spots an adjacent problem that your company should solve. They either suggest – or dictate – that the second product is something that must be done – it’s critical to the future success of the business and NOW is the time to branch out, to build upon the traction you’re experiencing.
So it’s assigned to a product manager, with an exec sponsor. The PM goes away and starts thinking about the product.
As most PMs are prone to do, they’re closer to the delivery of features than the development of a proposition. So they come back with a plan to build the thing and get it going. The exec sponsor goes back and gets the green light – this is a huge money-making opportunity!
Maybe a product marketer gets involved. As we are prone to do, we ask hard questions about the customer, the opportunity, the proposition.
“We just need to build the thing!” they say. “We’ll find customers who care about this when we’ve built it!”
Dutifully, the PMM carries on, supporting the proposition development and planning the GTM. Launch comes, and… the reaction isn’t quite as hoped.
“But the first, original product is a success! How could this happen?”
Well, it was different back then.
- The founder started the company probably because they experienced the pain firsthand
- They had unique wisdom that gave them shortcuts to pinpoint pains and develop the proposition
- They were probably working closely with customers to develop the product from day 1
- The gap between the interpretation of the problem and the execution was more narrow – maybe a CEO, a CTO, and a few engineers.
Now – with best intentions – the second product is a bit more difficult.
- The founder may not have experienced the second problem as deeply as the first problem
- They may not have as deep unique insight, or it’s based on outdated context
- Survivorship bias means the founder underestimates the amount of constant iteration and rethinking they did the first time round
- The interpretation gap is wider – understanding and context has to filter through a PM, an exec sponsor, and a founder both ways
So, through no fault of their own, the founders expectations and the reality of what the PM can deliver is out of sync. That misalignment – of the market opportunity, of the requirements to compete, of the deep context to be understood – is painful.
Building a second product (the right way)
Here’s how I think – and have seen – second products built the right way.
Firstly, an adjacent problem is identified from several sources including existing customer interviews, sales conversations, and the objective synthesization of market opportunities from the exec team.
It’s handed to a product marketer and product manager, who – as a team – are tasked with validating and quantifying the opportunity. A research sprint is undertaken: desk research for current solutions to the problem, existing customer interviews, and new market interviews too.
A business case is developed, detailing customer segments, the market landscape, and an initial draft of a competitive proposition. Opportunities are highlighted: what could the first next step be? What customer segment would make an easy first target? Where are the underserved needs in the market today?
This is reviewed and receives sign-off, empowering the product team to start building an MVP. At the same time, the product marketer works to iterate the go-to-market package: drafting and testing messaging, researching a distribution strategy, working with a sales/marketing ‘tiger team’ to start defining the GTM.
In constant contact with interested customers and prospects, the product team begin to ship product that’s tested by real hands. Quick feedback loops enable users to provide feedback on workflows and screens that the engineering team can pick up to improve without a longwinded selection process.
At some point, momentum starts snowballing – users begin to love it, issues decrease, and your initial sales/marketing results are exceeding expectations. Product/market fit has been achieved.
Of course, it never really happens like this – there’s usually a few more hiccups along the road. But hopefully you’ll recognise some of the smoothness, the natural pull and eagerness from the market, and the ‘start with the customer’ approach.
Or, could you acquire a product?
I think that, more than ever, acquiring a company as your ‘second product’ makes a ton of sense.
Not only are you acquiring the technology – which, with a well-resourced plan, can be integrated into your own stack – but you’re acquiring customers. They already had the pain, and they searched for a solution to solve it.
You’re acquiring expertise. Those founders, the product managers, the engineers all have more context on the customer problem to be solved than your team can learn quickly – even though the problem is adjacent.
And you’re buying experience. What worked? What didn’t work? What does the market want, need, what are competitors doing, how does selling and marketing work best?
These shortcuts – hopefully – would make it easier to build momentum with a second product. You can learn where the overlap are between your existing product customer base and your acquired base so you can figure out the cross-sell motion. You’ve already got revenue, a baseline for growth, and tactical plans to start optimizing from.
Regardless, look for focus + confidence
As longtime Building Momentum readers will know, momentum is the output of confidence + focus. If you have focus (in the customer, the problem, the product) and confidence (that reality will match expectations) – you will build momentum.
Whether you’re acquiring your second product, aspiring to build it “the right way”, or struggling through a mess, finding ways to increase focus and confidence will serve you well.
Thanks for reading! Let me know what you thought – find me on Twitter and LinkedIn.
P.S. If you’ve found value in Building Momentum, could you buy me a coffee? Here’s my tip jar – any support is gratefully appreciated!
P.P.S: If you enjoyed this post, will you share Building Momentum with your network?