How Notion Scaled to Series B With a Three-Person Growth Team

Teardown: How Notion Scaled to Series B With a Three-Person Growth Team

A founder told me recently: “We would love to scale but our hands are tied due to resourcing and headcount.”

I asked what his growth engine looked like and how many more people he needed to fix it.

“Isn’t the plan to just hire more people to generate more revenue?” he said.

That assumption is why most Series A companies stall before Series B. They treat growth as a headcount equation. They wait until the team is big enough to scale. By the time they realise the team is never big enough, the window has closed.

Notion closed its $50 million Series B at a $2 billion valuation in April 2020 with a growth team that was, at its core, two to three people. This article tears down what that team actually built, why it compounded without proportional hiring, and what you can take from it if you are running a Series A or B startup in Singapore or SEA today.


1. Notion Built Architecture, Not a Team

Camille Ricketts joined Notion as Head of Marketing as the 11th employee. Ben Lang became Head of Community when the company had around 12 total staff. Between them, they made one deliberate architectural choice: instead of hiring a team to push content out, they built systems that let users do the work.

The ambassador program grew to 300+ enthusiasts globally. The template gallery scaled to tens of thousands of templates. Each template was a piece of user education and use-case discovery that kept working after the team went offline.

That is not content marketing in the traditional sense. It is content as infrastructure. Every template is a conversion asset. Every ambassador is a distribution node. The team stayed small because they externalised the work into systems that ran without them.

💡 Key Takeaway: Notion did not scale by adding marketing staff. It scaled by turning users into the growth engine.


2. System Primitives Come Before Specialist Hiring

Notion is not the only example of this sequence. Lattice’s first marketing hire, Alex Kracov, joined as employee number three. Before Lattice hired any specialists, Kracov built the website as lead-capture infrastructure, set up early attribution, started SEO because it compounds over years, and tracked community members by uploading lists into Salesforce to map pipeline and revenue progression. Lattice then raised $15 million in its Series B in April 2019.

The pattern in both cases is identical:

  • Build the measurement foundation before adding budget
  • Build compounding assets before adding headcount
  • Let the system tell you where to hire next

Most founders do it in reverse. They hire the channel specialist before building the attribution model. They add headcount before they understand what the system actually needs. The result is a team that is expensive, busy, and unable to prove what is working.

💡 Key Takeaway: Attribution, content infrastructure, and product signals must come before team specialisation. Hiring into a broken system does not fix the system.


3. Product Signals Beat MQL Volume

Here is a data problem most founders do not know they have. Only 24% to 25% of product-led companies use product-qualified leads (PQLs). Yet free trials that use PQLs convert to paid at around 25% on average, versus a 9% median free-to-paid baseline. In the $1,000 to $10,000 ACV band, PQL conversion reaches 30% to 39%.

The same benchmark shows activation is tracked only 34% of the time. That means most SaaS teams are flying without the instrument that connects product behaviour to commercial action.

This is where a small team with the right system beats a large team chasing the wrong signals. If you are optimising for MQL volume, you are optimising for the wrong number. The right question is: which users hit the activation milestone, and what happened to their revenue trajectory after that point?

💡 Key Takeaway: PQLs outperform generic free-to-paid conversion by a wide margin. If your growth team cannot see activation data, you are making revenue decisions without the most important signal available.


4. The SEA Counterargument Is Valid, But It Does Not Change the Architecture

A sceptical SEA founder would say: “This is a US playbook. In SEA, enterprise buyers do not self-educate. Trust matters more. Each country needs its own story, its own channel habits, its own partners.”

That objection is fair. Singapore EDB’s guide to enterprise SaaS in Southeast Asia, drawing on 19 SaaS companies using Singapore as a base, confirms that SEA buyers are more conservative, that trust and familiarity matter, and that winning requires country-specific storytelling, strategic local partnerships, intensive market education, and channel-specific follow-up including WhatsApp and LINE.

But here is the point: all of that is architecture. Country-specific messaging, partner onboarding flows, localised content assets, WhatsApp follow-up sequences, these are system design decisions, not headcount decisions. You do not solve them by hiring more junior staff. You solve them by building the right frameworks, then executing at scale.

This is also where fractional senior expertise changes the equation for most Series A and B founders in SEA. The constraint is rarely junior execution capacity. It is the absence of senior judgment at the architecture level.

💡 Key Takeaway: A Fractional Chief Growth Officer (CGO) brings that judgment without the full-time hire, so you get the system built correctly before you scale the team around it.


Final Thoughts: Growth at Series B Is a Systems Problem, Not a Hiring Problem

Notion scaled to a $2 billion valuation with a growth team that most founders would consider understaffed. Lattice built its Series B foundation with a single marketing hire. What they shared was not a large team. It was a clear system: compounding content assets, product signals wired to commercial action, and measurement that told them where to press next.

Nansen, by contrast, raised $75 million in its Series B in December 2021. By May 2023, it laid off 30% of staff. The CEO said the cost base was too high relative to where the company was. Headcount had outrun the durable growth loops underneath it.

If you are a founder building toward or past Series B in Singapore or SEA, the question is not “how many more people do I need?” It is: “does my current system compound without me adding more headcount?”

If it does not, that is the problem to fix first.

Book a discovery call or connect with me on LinkedIn.


A note before you close this tab. The fact that you read this far tells me something. You already sense that the way you’ve been thinking about growth might be incomplete. That instinct is worth following.

Mervyn Chua is a growth-transformation consultant helping founders and CEOs build the strategic clarity and systems to grow in an AI-first world. If this raises questions worth exploring for your brand, let’s talk.

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.