When people hear that Octopush grew from around €1M to €2.5M ARR while remaining fully bootstrapped, the first question is almost always the same:

“What growth strategy worked?”

They’re usually expecting an answer about SEO, Google Ads, content marketing or some acquisition hack.

The truth is much less exciting.

The biggest lesson I learned during those three years had very little to do with marketing. It completely changed how I think about growth, and it’s the reason I approach SaaS companies very differently today.

I joined to solve a small problem

I didn’t join Octopush as Head of Growth.

The founder hired me to improve the onboarding experience and build an activation campaign for new customers. It was a relatively small project, and looking back, I think it was the best possible way to start.

Instead of arriving with a grand strategy and a list of recommendations, I had the opportunity to solve one specific problem, understand how the business operated, and build trust with the founders. As that relationship grew, so did my responsibilities. Over time, I took ownership of larger parts of the business until eventually becoming Head of Growth.

That gradual progression taught me something I’ve carried throughout my career: before trying to change a company, you first need to understand how it actually works.

The business didn’t need more ideas

When I joined, Octopush had been operating for almost ten years. It was generating around €1M in annual recurring revenue, had a solid product and was solving a real problem for its customers.

Demand wasn’t the issue.

SEO was already bringing in traffic. Google Ads existed, although there was plenty of room for improvement. Customers were signing up, and the business had reached a respectable size without raising venture capital.

From the outside, it looked like there were dozens of opportunities to accelerate growth.

After spending some time inside the company, I realised that wasn’t the real challenge.

The company wasn’t running out of marketing ideas.

It was running out of execution capacity.

The CEO was responsible for almost every commercial function in the business. He handled sales, customer support, partnerships and many of the day-to-day commercial decisions. On top of that, he was also running another company.

None of this happened because he wanted to control everything.

It happened because he had built the business himself. He knew the customers better than anyone, understood the product inside out and naturally became involved in every important decision.

That approach had taken the company to €1M ARR.

It was also preventing it from going much further.

We didn’t start with growth

One thing that often surprises people is that my first initiatives weren’t focused on customer acquisition.

In fact, I deliberately avoided it.

Adding more traffic would have generated more leads. More leads would have generated more sales conversations. More customers would have generated more support requests.

Every one of those activities still depended on the founder.

Increasing demand without increasing the company’s ability to execute would simply have made the bottleneck worse.

So instead of asking how we could generate more customers, I asked a different question.

How could we free the founder’s time?

That became the real growth strategy.

Building the foundations

The first initiatives were operational rather than commercial.

We implemented a proper customer support CRM, created a knowledge base and documented the API (we served both, commercial customers and developers). We also hired a dedicated customer support person, first on a part-time basis and later full-time.

The important part wasn’t hiring someone.

It was building a system that allowed someone else to succeed.

Instead of every support ticket ending up with the founder, routine requests could now be resolved through documented processes, while more complex issues could still be escalated when necessary.

Knowledge slowly moved from people’s heads into documentation.

The founder was no longer required for every operational decision.

One thing I always admired about him was that, even after these systems were in place, he still spent time talking to customers. He genuinely cared about understanding their problems and staying connected to the product.

The difference was that he did it because he wanted to, not because the business couldn’t function without him.

The objective was never to remove the founder from customers.

The objective was to remove dependency on the founder.

Growth became repeatable

Once those foundations were in place, we started applying the same thinking across the rest of the business.

Google Ads was one of the first areas I looked at because I had previously run an agency. The campaigns already existed, but attribution was weak and there was significant room for improvement. We rebuilt the campaigns, improved tracking and made decisions based on data instead of assumptions.

SEO was another obvious opportunity.

The channel was already producing results, so instead of constantly chasing new acquisition channels, we invested more heavily in what was already working. We expanded our content strategy, produced educational articles, invested in guest blogging and focused on building high-quality backlinks.

Later we improved lead qualification, routing and sales processes before gradually expanding the commercial team.

Looking back, I realise there was a consistent pattern behind almost everything we did.

We didn’t try to reinvent the business.

We identified what was already working, improved it, documented it, turned it into a repeatable process and only then invested more resources into scaling it.

That mindset still influences how I approach growth today.

Experiments instead of opinions

One misconception about growth teams is that they’re constantly chasing shiny new ideas.

Our process was much more disciplined than that.

Ideas came from everywhere: founders, customers, sales conversations, support tickets and observations from the team. Rather than debating them endlessly, we captured every idea in an experimentation backlog.

Every couple of weeks we reviewed that backlog, wrote a short brief for each experiment and prioritised them using an ICE framework. We looked at expected impact, implementation effort and confidence before deciding what deserved our attention.

Some experiments worked immediately.

Others failed.

That wasn’t a problem.

The objective wasn’t to avoid failure.

The objective was to build a system that allowed us to learn faster than our competitors while remaining disciplined about where we invested our limited resources.

Being bootstrapped forces you to think that way.

You can’t afford to pursue every interesting opportunity.

One lesson I learned the hard way

One of our biggest ambitions was expanding internationally.

We looked at Spain and the UK and assumed that if our playbook worked in France, we simply needed to translate it.

We were wrong.

The challenge wasn’t language.

It was operational complexity.

Every new market multiplied the amount of work required.

SEO wasn’t one strategy anymore.

It became three.

API documentation wasn’t one documentation project.

It had to exist in multiple languages.

Campaigns weren’t simply translated; they had to be rewritten because buying behaviour, competitors and communication styles were different in every market.

As a relatively small team, that complexity became much harder to manage than we had anticipated.

It was one of the first times I truly understood that growth doesn’t just multiply revenue.

It multiplies operations.

If your internal systems aren’t ready, complexity grows faster than the business itself.

Bootstrapped companies play a different game

Another lesson that stayed with me was learning when to say no.

Like every growing company, we constantly looked at competitors.

Some had raised millions in venture funding and were investing aggressively in channels, partnerships and expansion.

It was tempting to copy them.

More than once, I found myself telling the founder that a particular strategy simply wasn’t right for us.

Not because it was a bad strategy.

Because it belonged to a different company with completely different constraints.

Bootstrapped businesses don’t have the luxury of making expensive mistakes.

Every decision competes for the same limited time, money and attention.

Those constraints forced us to become more disciplined.

In hindsight, I think they also made us better.

The lesson I still carry today

When I look back at those three years, I don’t think about Google Ads, SEO or content marketing first.

I think about the founder.

The company didn’t unlock because we discovered some magical acquisition channel.

It unlocked because we gradually built an organisation that could execute independently.

The founder could finally spend more time thinking about the future instead of responding to the present. Sales no longer depended entirely on him. Support no longer depended entirely on him. Knowledge no longer lived exclusively inside his head.

That experience completely changed how I think about growth.

I no longer believe that most B2B SaaS companies have a marketing problem.

I believe they have an execution problem.

Founder-led execution is the right operating model in the early stages of a company. In fact, I don’t think you can build a great SaaS business any other way. Founders understand the customer, the product and the market better than anyone else.

But there comes a point where the very thing that made the company successful becomes its biggest constraint.

Every decision waits for the founder.

Every process depends on the founder.

The company can only execute as fast as one person can work.

That’s the point where growth stops being about generating more demand.

It becomes about building systems that allow the business to grow beyond the founder.

That’s the most valuable lesson I learned at Octopush.

And more than anything else, it’s the lesson that shaped how I work today.