SaaS

Why SaaS Growth Can Stall Around $1M ARR

Julian Marzouki and Rob Walling explain how founder approvals, competing priorities and gaps in sales data can hold back an established SaaS.

Listen to the audio analysis

Create your own

Written for builders and creators.

Scaling a SaaS from one million to three million in ARR isn't about doing more of what worked. It's actually about doing something fundamentally different.

Editor's note

Why this matters now

At Drip, Rob Walling reached a team of 10 and still found himself making every decision. “Let's see what Rob thinks” had become the default response. What felt like helping the team was keeping it dependent on him.

That experience anchors his conversation with Julian Marzouki, a coach at the TinySeed SaaS Institute, about founders trying to grow beyond roughly $1M in annual recurring revenue. They describe 6 patterns worth investigating when an established SaaS stalls, from repeated founder approvals to competing sales priorities. These are coaching observations, not a diagnosis of every company at that revenue level.

The source

What it says

Distilled from the original. The notes above and below are the editor's own.

1. The Founder Still Owns a Whole Function

Marzouki starts with a rough estimate of where the founder's week goes. He asks about business functions such as sales, product and marketing. If one consumes more than 40% of the founder's time, he treats it as a place to examine dependence on that person.

The percentage is his diagnostic prompt, not a staffing formula. Spending heavily on sales may be a deliberate choice. The problem appears when nobody else can carry the work and the founder has no time left to build that capacity.

This can be hardest in the function the founder does best. Handing it over means accepting that another person will approach it differently, while making the required outcome and quality clear.

2. Larger Deals Can Distract From Faster Ones

The interview's banking-software example makes the cost of scattered attention concrete. A client was pursuing national, regional and community banks at the same time. Regional deals were around $70,000, compared with $30,000 for community banks, but the reported sales cycles were about 7 months and 1 month respectively.

The larger contract was therefore only part of the choice. The team also needed to compare how many prospects it could reach and how many it could close. Marzouki uses sales velocity to bring pipeline size, conversion, deal value and sales-cycle length into the same decision.

The attraction of community banks was earlier revenue and a shorter wait to learn whether the sales approach worked. Sequencing gave that opportunity concentrated attention before the team pursued larger contracts.

3. Rescuing the Team Keeps Decisions With the Founder

A founder who repeatedly takes over difficult tasks may finish them faster that day. The team also learns that bringing a problem back is easier than resolving it.

Marzouki's 10-80-10 rule gives the founder a different role. At the start, set the purpose, scope and quality standard. Let the team member own the middle of the work. Return at the end to review the result. The percentages describe the shape of involvement, not a measured allocation of every project hour.

The useful distinction is between agreeing on the result and taking over its execution. Walling's Drip account shows the cost of leaving that distinction unclear: hiring more people did not remove him from the approval path.

4. More Leads Can Leave the Existing Problem Untouched

Marzouki argues that some companies asking for more leads first need to understand the customers and prospects they already have. Without channel-level conversion, cancellation reasons or a view of sales handoffs, a founder cannot tell whether more spending will address the constraint.

He describes a client whose lifetime-value-to-acquisition-cost ratio rose from the high 2s to around 4 over 6 months while the company addressed sales conversion and team turnover. This is a coaching account with several changes in play, rather than evidence that a dashboard alone caused the improvement.

Pricing can be part of the same investigation. The price-cut case discussed by Rob Walling examines how an apparently easier sale can bring customers who stay for less time.

5. Uncertainty Needs a Test Small Enough to Finish

The speakers describe founders who keep thinking about a decision because the next action feels uncomfortable. A technical founder, for example, may find another product improvement easier to start than a sales conversation.

Their response is a short learning cycle: choose an action that can answer the uncertainty, observe the response and decide what follows. That only helps when the action addresses the question. Shipping another feature cannot establish whether a different customer segment will buy.

Marzouki also proposes a weekly rhythm of 1 priority, 3 commitments and a scorecard. Its purpose is to connect the team's activity with a chosen objective and a way to see progress. It is one operating practice offered in the interview, with no claim that those counts suit every team.

6. AI Adds Another Initiative to Prioritize

The speakers' concern about AI is familiar from the rest of the conversation: a company can add activity before deciding which customer problem it needs to solve.

An agent project still needs a defined user, task and useful result. Without those, the team can spend time automating a process whose value it has not established. Walling's separate discussion of AI features that remove user work develops that product question through examples of ingestion, analysis and task execution.

Editor's note

What to do with this

The interview is most useful when a founder recognizes a specific dependency: every proposal needs their approval, every sales segment is a priority, or nobody can explain why customers leave. Each points to a different change. A rough time estimate can reveal where to look, but revenue alone cannot tell you which pattern applies.

The goal is a company that can make and carry out more decisions without waiting for its founder. Walling's experience shows why adding people is only part of that change. They also need the authority and context to act.

The original

  • SaaS

    Why a SaaS Price Cut Can Bring More Churn

    Rob Walling examines a founder’s price cut and shorter customer lifetimes, then separates testing a higher price from selling to a different buyer.

    4 min read7 min listen

All posts