Struck on a Growth Plateau? You Don't Need More Tactics. You Need Fewer Priorities
It’s one of the most frustrating feelings in the startup journey. You hit $5k, $10k, or even $20k MRR, and then... everything stops.
You keep working 12-hour days. You try new marketing hacks, tweak the UI, test cold outreach, and jump on every new trend. Yet, the revenue line on your Stripe dashboard stays completely flat
When a startup hits a growth plateau, the default reaction for most founders is to do more. More features, more marketing channels, more growth tactics.
But here is the hard truth: You cannot fix a strategic problem with operational busyness. You aren’t stuck because you aren't doing enough. You are stuck because you are doing too many of the wrong things. Here is how to regain your focus and break through the ceiling
-
The "More Things" Illusion
When growth slows down, founders look for missing pieces. They think: "If we just add an affiliate program AND launch an AI feature AND start a newsletter, we will grow."
This is a trap. Every new initiative you add doesn't just take time — it divides your focus. Doing five things at 20% effort yields exactly 0% results.
• Action item: Growth doesn’t come from doing more things. It comes from doing 1 or 2 things with absolute, ruthless intensity -
Audit Your "Productive Procrastination"
Are you actually working on growth, or are you just staying busy to avoid hard strategic choices?
Fixing a minor bug, rewriting a landing page copy for the fifth time, or redesigning a dashboard feels productive. It gives you a quick hit of dopamine. But it doesn't move the needle. This is called productive procrastination.
• Action item: Look at your calendar for the last two weeks. Separate your tasks into two buckets: Keeping the lights on vs. True Growth Levers. If growth levers take up less than 50% of your time, you've found your plateau -
Find the "One Metric That Matters" (OMTM)
If you have 5 different goals for this quarter, you have no goals. You cannot optimize for user retention, new user acquisition, churn reduction, and higher LTV all at the same time.
• Action item: Identify the single bottleneck holding your business back right now.
- If you have traffic but no conversions, your OMTM is conversion rate.
- If users sign up but leave after 3 days, your OMTM is activation/retention.
-
The Power of the "Not-To-Do" List
Strategic focus is not about deciding what to do. It’s about deciding what not to do, even if it’s a good idea.
• Action item: Create a "Not-To-Do" list for the next 30 days. Write down all the features, marketing channels, and partnerships that sound exciting but distract from your primary bottleneck. Park them in a backlog and refuse to touch them -
Stop Building, Start Optimizing
For technical founders, code is comfort. When growth stalls, the instinct is to build a new feature. But product bloat actually kills growth because it confuses new users.
• Action item: Freeze all new feature development for 2-3 weeks. Spend that time talking to existing power users and optimizing the core loop that already works. Double down on your strongest acquisition channel instead of building a weak new one
The Bottom Line
A growth plateau is a sign that the strategy that got you to this point is no longer enough to get you to the next level. To break through, you don't need a longer to-do list; you need a sharper knife to cut away the noise
One thing I've learned from working with founders and executives is that the hardest decisions rarely require more information—they require better thinking. If you're currently navigating a significant leadership challenge or strategic decision, feel free to send me a direct message. I'd be glad to continue the conversation
Agreed on killing the busywork, but I'd push on the diagnosis. Most plateaus I've seen (including at my own companies) aren't a focus problem, they're a saturation problem: you've maxed out the segment your current price and positioning fit, and no amount of ruthless focus on the same pond grows the pond. Before you freeze features and optimize the funnel, check whether the ceiling is the market you're selling to, because sometimes the unlock is charging more or moving to a bigger buyer, not doing fewer things.
I completely agree that not every plateau is caused by poor prioritization. Sometimes the bottleneck is the market itself, and in that case the right move is changing your positioning, pricing, or target customer—not simply focusing harder. My point was more about avoiding the instinct to chase ten different solutions before identifying the real constraint
The "kill 3 features" advice is gold, but most founders cannot pick which 3 to kill because they are emotionally attached. We use a brutal 1-question filter: "If we deleted this tomorrow, would any paying user notice within 30 days?" If no, kill it. Cuts through the noise. We pruned 11 features in Q1 this way and grew MRR 28% from the focus alone.
I like that filter. It forces you to think from the customer's perspective instead of your own attachment to the feature. Thanks for sharing it
The "not-to-do list" hits hard at early stage. When you have zero traction the temptation is to ship more features, fix the UI, set up analytics, improve SEO all at once. But none of that is a growth lever. The only thing that moves the needle before product-market fit is getting someone to pay. Everything else feels productive but it's just maintenance in disguise.
This hit home. I went through a period of trying every SEO tactic on every site at once -- new content, title changes, internal links, indexing pushes, all simultaneously across a dozen properties. Zero signal on what actually moved anything. The plateau broke when I picked one lever per site per week and actually tracked it. Fewer priorities is not just about focus -- it is about finally running a controlled experiment instead of random noise.
That's a great point. Focusing on one lever at a time doesn't just improve execution—it also makes it much easier to learn what actually works. If everything changes at once, it's almost impossible to separate signal from noise. That's a perspective I should have included in the article
This is exactly the stage I’m at right now while building my first SaaS.
The “productive procrastination” part really hit me—especially how easy it is to feel busy while not actually moving the growth needle. I’ve definitely fallen into the loop of tweaking landing pages, thinking about new features, and exploring different acquisition ideas all at once.
What stood out most is the idea of choosing a single bottleneck (OMTM) and letting everything else take a backseat. In theory it sounds simple, but in practice it feels really hard when you don’t yet have clear data.
In the early stage, how do you personally identify the right OMTM when:
you don’t have meaningful traffic yet,
user behavior signals are still weak,
and everything feels like it could be “the problem”?
Also curious about the “Not-To-Do list” — do you define that based on experiments you’ve already tried and failed, or do you proactively block ideas before testing them?
Great questions. I think the early stage is actually different.
If you don't have enough traffic or user data yet, your OMTM is usually generating more learning, not optimizing a metric. At that stage, your priority is to gather enough information to understand where the real bottleneck is. That could mean talking to more potential customers, getting more people to try the product, or understanding why they don't come back.
As for the Not-To-Do list, I use it more proactively. New ideas never stop coming, and most of them aren't bad—they're just not the most important thing right now. I write them down, but unless they directly help solve the current bottleneck, they stay in the backlog
That framing—“OMTM = generating learning instead of optimizing a metric”—makes a lot of sense.
It also clarifies something I was struggling with: at the very early stage, you’re not really choosing between metrics, you’re choosing between sources of truth. Either you’re learning from user conversations, activation attempts, or usage behavior—but the goal is the same: reduce uncertainty around what actually matters.
On the Not-To-Do list side, I like the idea of treating it as a proactive constraint rather than a reactive cleanup. That feels harder in practice because new ideas often feel urgent even when they aren’t aligned with the current bottleneck.
One follow-up I’m curious about:
When you say “wait until you identify the real bottleneck,” how do you personally avoid spending too long in that discovery phase before committing to a direction? Is there a signal you look for that tells you “enough learning, now focus execution,” even if the data is still incomplete?
I don't think there's ever a point where you have complete certainty. For me, it's less about having enough data and more about seeing the same pattern repeatedly. When different conversations, user behavior, or feedback all point to the same bottleneck, that's usually enough to commit. At some point, collecting more information has diminishing returns. That's when it's better to choose a direction, execute, and let the next round of results teach you whether your assumption was right
Productive procrastination is such an accurate name for it because the work genuinely feels meaningful while you're doing it. Polishing a dashboard or rewriting copy gives you the same dopamine as real progress without any of the risk that comes from actually testing something new.
The counter-question about market ceiling versus prioritization is worth sitting with though. A Not-To-Do list only helps if the remaining priorities are actually the right ones. Cutting from five mediocre bets down to one mediocre bet still leaves you with a mediocre bet.
My point wasn't that focus magically fixes every plateau. First you need to figure out what's actually holding the business back. Then you put most of your energy into solving that one thing. If you focus on the wrong problem, you'll just get better at doing the wrong thing
Productive procrastination is the killer. Most founders mistake busyness for progress. The not-to-do list matters more than the to-do list.
The part that stayed with me wasn't the advice about doing fewer things.
It was the assumption that the plateau is fundamentally a prioritization problem.
Reading this, I found myself wondering whether different explanations for the same plateau could justify completely different priorities while still making every recommendation here feel reasonable.
I'd be curious how you think about that.
That's a great point. I don't think every plateau is caused by poor prioritization. A plateau can come from product-market fit issues, market saturation, pricing, distribution, or even macro conditions. My point was that, regardless of the root cause, founders often respond by adding more initiatives instead of identifying the actual bottleneck first. That's where prioritization becomes critical. In other words, I see prioritization less as the cause of the plateau and more as the discipline that helps you diagnose and solve the real cause
That's exactly the distinction I was thinking about.
I don't think the interesting part is whether prioritization matters.
It's the business decision that quietly follows once you decide what the plateau actually represents—and I don't think I can unpack that properly in a thread without oversimplifying it.
Happy to explain what I mean if it's useful. What's the best email to reach you on?
Happy to continue the conversation. You can reach me at: alex.foundry.exec [at] gmail.com
Just sent it over.
Looking forward to hearing your thoughts once you've had a chance to read it.