Growth Is a Product Problem Before It's a Marketing Problem

When a SaaS product struggles to grow, the first conversation is often about marketing. More campaigns, better ads, a new landing page, a sharper headline. Sometimes that is exactly right. But just as often, the people being brought in are arriving at a product that cannot keep the promise the marketing made.

My argument is not that marketing matters less. It is that growth depends on two things working together: getting the right people to the door, and helping them find what they came for once they walk through it. The second part is a product problem, and product design has a lot to do with it.

Traffic is not growth

A spike in sign-ups feels like growth. But sign-ups are a measure of interest, not of value received. If a large share of new users never complete a meaningful action and never return, the business has paid to acquire attention it could not keep.

Sustainable growth looks different. It shows up as users who reach the product's core value, keep using it, bring others in, and eventually pay. Those outcomes depend heavily on what happens inside the product.

One system, not separate departments

A common way to describe the customer journey is a sequence: acquisition, activation, retention, referral, and revenue. It is a simplification, but a useful one, because it shows how each stage depends on the one before it.

• Acquisition brings people to the product.

• Activation is the moment they experience its value for the first time.

• Retention is whether that value holds up and brings them back.

• Referral happens when the value is strong enough to share.

• Revenue reflects whether the value is worth paying for.

Marketing has a strong influence on the first stage. Product experience has a strong influence on most of the rest. Treating growth as only a marketing concern means optimizing the stage you can see most easily while ignoring the stages where users actually decide whether to stay.

When the promise and the experience don't match

Marketing makes a promise: this tool will save you time, give you clarity, help your team close more deals. The product either delivers on that promise quickly or it doesn't.

When there is a gap, users feel it immediately. The landing page talked about instant insights; the product asks for a long configuration before showing anything. The ad described a simple tool; the first screen is a dense dashboard full of empty widgets. The user doesn't experience this as a design problem. They experience it as the product not being what they were told.

Better marketing can make that gap worse, because it brings in more people with higher expectations.

Where product experience creates adoption barriers

Some of the most common barriers sit squarely in the product experience:

• Unclear onboarding that explains the interface but not how to get the result the user wanted.

• Confusing navigation that makes the core workflow hard to find among secondary features.

• Excessive setup before any value is visible.

• Weak feedback, where users can't tell whether what they did worked or what to do next.

Each of these turns interest into hesitation. And hesitation, early in a product relationship, often becomes abandonment.

A hypothetical example: the analytics platform with quiet accounts

Imagine a B2B analytics platform for e-commerce teams. Marketing is doing its job: sign-ups are steady. But most new accounts never configure a dashboard, and very few return after the first session.

The easy conclusion is that the interface is confusing. It might be. But a careful team would look at several possible causes before deciding:

• Onboarding. Do new users understand what to do first, or are they dropped into an empty workspace?

• Initial setup. How many steps stand between sign-up and seeing a single useful chart?

• Data integration. Does connecting a store require technical access the person signing up doesn't have? That would be a constraint the interface alone can't solve.

• Time to value. How long does it take before the product shows the user something they didn't already know?

• Targeting. Is marketing attracting people who don't have the problem the product solves, or who aren't the ones who would use it?

• Value and pricing. Is the problem urgent enough for these users to invest effort, at this price?

The answer might involve the interface. It might involve the integration flow, the ideal customer profile, or the pricing model. The point is that "low retention" is a symptom that crosses team boundaries, and the investigation should too.

Retention problems are rarely marketing problems

When users leave, it is tempting to respond with re-engagement emails or win-back campaigns. Those can help at the margins. But if users leave because the product didn't deliver enough value, a reminder doesn't change that. It just reminds them.

Retention is mostly a reflection of whether the product keeps being useful. That makes it one of the clearest signals a product team has about whether its experience is working.

How designers can collaborate on growth

Designers don't need to own growth to contribute to it. Some practical ways to be useful:

• Read the marketing message and walk through the product as if you believed it. Where does the experience fall short of the promise?

• Ask the growth or product team where users drop off, and look at those moments in the interface.

• Share qualitative observations alongside quantitative data, so the team sees both what is happening and why.

• Propose small, testable changes rather than broad redesigns.

If you want to go deeper on the business side of this, I've written about it in Product Designers Should Understand the Business Behind the Interface.

Two halves of the same job

Marketing helps the right people discover a product. Product experience helps them understand it, realize its value, and keep coming back. Neither can do the other's job.

When growth stalls, it is worth asking both questions: are we reaching the right people, and are we helping them succeed once they arrive? I suspect the second question gets asked far less often than it should.