When growth stalls, the instinct is to ship a new feature and push harder on existing marketing channels. This almost never works if those channels are already saturated. Before defaulting to 'more features plus more ad spend,' explicitly audit which of your acquisition channels still have room to grow and which have hit their ceiling. If you can't answer that question, assume all of them are saturated.
"Do you know right now which channels are saturated and which aren't? If the answer is no, I'm like, well, okay, maybe that's because the answer is all. You know, that needs to change how you think. Just adding one little feature and then hoping we can flog AdWords is not going to work. Even if the feature is great, not going to work. So there's different things that could work, but that's not one of them. And yet, that's probably what we're doing. Let's add another feature and marketing can flog it is often the answer. But if you're in this state, that isn't the answer."
The surprising advice from a founder who built 2 unicorns | Jason Cohen (WP Engine) at 1:11:26 · Featured in Growth Gems #143
How often do you get asked: “How many new subscribers / how much new revenue will this feature bring?” I hear this surprisingly often. Sadly, most of the time, a “killer” feature rarely becomes an antidote. So I start with a few very simple questions:
What are the different features for? What metrics do you expect them to move?
Are you building a new feature because otherwise you’re not at parity with the competition, and users expect you to be?
Or does it unlock a new segment or a market and, hence, can help you scale customer acquisition? E.g., if you’re adding localization, or yoga exercises to a workout app, or a new language that users can learn? This would be a case when it can help you capture the existing demand if you can compete for it.
Or is it supposed to improve retention and word of mouth by “delighting” users?
Or maybe your users will start upgrading more often and be willing to pay more for it?
Put your hypotheses and expectations in writing. It doesn’t have to be scientific, but it should be good enough for your team to understand the importance and the WHY behind building this vs that. I’d recommend having at least this section in your PRD docs, Pitches, or whatever you’re using internally.

A very simple yet powerful thinking and writing exercise









