Many founders think startup growth should begin with scale.
They want thousands of users, a broad target market, significant website traffic, and rapid adoption soon after launch.
Paul Graham believes early-stage founders should focus on almost the opposite.
“You’ve got to find people who want what you’re making A LOT.”
At the beginning, that may only be a handful of people. Graham argues that this is completely normal. Some of the largest companies in the world started with surprisingly small groups of highly engaged users.
The goal is not to make thousands of people slightly interested.
It is to make a small number of people care deeply.
For startup founders across Canada, this creates a much more achievable early-stage objective: identify exactly who needs the product most, find those people, and make them exceptionally happy.
That concentrated enthusiasm can become the “small, intense fire” from which much larger startup growth develops.
Big Companies Can Start Very Small
Graham points to Apple as an example.
Apple began by selling only around 500 Apple I computers. Compared with the scale Apple eventually reached, those first sales were tiny.
But the number was not the important part.
Those early customers cared enough about the product to buy it.
Graham’s point is reassuring for founders worried that their startup does not initially appeal to a huge audience:
“You don’t have to do any better than Apple and Facebook.”
Facebook followed a similar pattern. It began with a narrow group of Harvard students before expanding to other universities and eventually becoming a global platform.
Neither company needed the whole world on day one.
They needed a small group that found the product unusually valuable.
This is why founders should be careful about evaluating an early startup primarily by audience size.
A thousand users who barely care may tell you less than ten people who use the product constantly and would be upset if it disappeared.
Know Exactly Who Your First Users Are
Graham argues that founders should know who their earliest users will be and how they are going to reach them.
That sounds simple, but many startups begin with extremely broad customer definitions.
“Our product is for small businesses.”
“It’s for anyone who wants to be more productive.”
“It can help every university student.”
The broader the audience becomes, the harder it is to understand what the product should actually do.
A stronger starting point is much narrower.
Which small businesses?
Which type of student?
Which productivity problem?
What situation makes the product especially valuable?
The first users should ideally experience the problem frequently and care strongly about solving it.
Once the founders know who these people are, they can learn directly from them.
What are they currently using?
What frustrates them?
Why are existing solutions inadequate?
What would make the product dramatically better?
A clearly defined first customer makes product development much easier because founders know whose problems they are trying to solve.
Make Your First Few Users Extremely Happy
Once founders find those initial users, Graham recommends focusing intensely on them.
“You’re going to sit down and just have a party with those first few users.”
Early customers should receive a level of attention that would be impossible once the startup becomes larger.
Founders can personally onboard them.
They can respond to feedback immediately.
They can watch users interact with the product and fix problems quickly.
They can even build features specifically because one important early user needs them.
At this stage, efficiency is not necessarily the goal.
Learning is.
Every interaction helps founders understand what customers value, what frustrates them, and what makes the product worth continuing to use.
A small number of deeply engaged users can provide an enormous amount of information.
They can help reveal what the product should eventually become.
Sometimes One User Is Enough
Graham gives an extreme example from a Y Combinator startup building a new mobile email client.
Its beta group consisted of just one person: Sam Altman.
One user may sound like almost no market validation at all.
But Altman was a valuable early customer because he used email extensively while travelling and was familiar with competing mobile email products.
That made him demanding.
And demanding users can be extremely useful.
If the startup could build an email product that genuinely made Altman happier than the available alternatives, it would have learned something important about what serious email users valued.
The lesson is that the quality of an early customer can matter more than the quantity.
A good first user experiences the problem frequently, understands existing solutions, and cares enough to provide detailed feedback.
Rather than collecting hundreds of shallow opinions, founders can sometimes learn more by obsessing over one highly relevant user.
Act Like a Consultant for Your Early Users
Graham advises founders to act almost like consultants during this stage.
“Act like Sam has hired you to make an email app just for him.”
This means temporarily forgetting about whether every part of the product will scale.
If one important user needs something, build it.
If onboarding needs to be done manually, do it manually.
If the interface needs to be adjusted specifically around one person’s workflow, make the adjustment.
Graham even jokes that the product could say “Sam Altman” at the top of the screen.
That level of customization would obviously make little sense at scale.
But early-stage startups are not operating at scale yet.
They are trying to discover what creates value.
Founders sometimes make the mistake of designing everything for a hypothetical future where the company has millions of customers.
They automate onboarding before understanding what good onboarding requires. They build complex systems before they know whether customers care. They avoid customization because it feels “unscalable.”
This can make the startup efficient at doing the wrong things.
Manual work provides information.
Once founders understand which parts repeatedly create value, they can automate them later.
The Real Test: Would the User Miss the Product?
Graham offers a simple test for whether the startup is beginning to work:
“Just so long as Sam would feel bummed if you stopped working on it. That’s the test.”
This is much more demanding than asking whether someone likes the product.
Users often tell founders that an idea is interesting, useful, or promising. They may genuinely mean it.
But being positive about a product is different from needing it.
A stronger question is:
What would happen if the product disappeared tomorrow?
Would users look for an alternative immediately?
Would their workflow become noticeably more difficult?
Would they contact the founders and ask when the service was returning?
Would they actually care?
When the answer is yes, the startup may have discovered something important.
Customers who would genuinely miss a product are receiving real value from it.
That emotional attachment can become the foundation for retention, word of mouth, and future growth.
Intensity Before Scale
Graham’s approach suggests that founders should think about startup growth in stages.
The first stage is not maximum reach.
It is maximum intensity.
Find a narrow group.
Solve their problem extremely well.
Understand why they love the product.
Then look for more people who share those characteristics.
This creates a stronger path to growth than attracting a large audience before the product has become valuable enough.
If users are only mildly interested, spending more money on marketing may simply produce a larger group of mildly interested people.
If a small group loves the product, marketing can eventually help find more people like them.
The difference is important.
Growth should amplify product value—not compensate for the absence of it.
Your Earliest Users Can Become Your Growth Engine
Deeply satisfied early customers do more than help improve the product.
They can also become the startup’s first advocates.
People naturally talk about products that solve painful problems unusually well.
They recommend them to colleagues.
They invite friends.
They share them in industry communities.
They write reviews or testimonials.
This creates organic growth.
One passionate customer brings another customer with similar needs. That customer may introduce someone else.
The small fire begins spreading.
This kind of growth is particularly valuable because referrals come with built-in trust. A recommendation from someone who understands the customer’s problem often carries more weight than an advertisement.
This is why making early users “super super happy” is not separate from growth.
It can be the beginning of the growth strategy itself.
Do Things That Don’t Scale—For Now
The early stage of a startup provides an unusual opportunity.
Founders have very few customers.
That means they can do things established companies cannot.
They can spend an hour helping one user.
They can manually configure an account.
They can personally deliver the service.
They can change the product overnight after a conversation.
At a larger company, this would be expensive and inefficient.
At an early-stage startup, it can be one of the fastest ways to learn.
The goal is to understand the customer so deeply that the company knows which parts of the experience eventually need to become scalable.
Founders should therefore distinguish between work that can never become a business and temporary manual work that teaches them how to build the business.
The latter can be extremely valuable.
What Startup Founders Can Learn From Graham
For founders in Canada, Graham’s “small, intense fire” approach offers several practical lessons.
Choose a specific first customer
Do not begin by targeting everyone who could theoretically use the product.
Find the group that experiences the problem most intensely.
Know how you will reach them
Your first users should not be an abstract market segment.
Know which communities they participate in, where they work, what they read, and how you can contact them directly.
Give early users unusual attention
Personally onboard them, respond quickly, and learn from how they actually use the product.
Find demanding customers
Easy-to-please users may provide positive feedback without helping the product improve.
A demanding customer with a real need can reveal exactly where the product falls short.
Look for strong attachment
Do not measure only sign-ups or compliments.
Watch whether customers return, request improvements, recommend the product, and would genuinely miss it if it disappeared.
Delay unnecessary scaling
Do not invest heavily in infrastructure, automation, or broad marketing before understanding what your first customers actually value.
Use your founder network
A strong founder network in Canada can help startups identify early adopters, receive honest feedback, and connect with customers who experience the problem firsthand.
The best startup support for founders does not always mean helping them reach thousands of people. Sometimes it means helping them find the ten people who matter most.
Why This Matters to the Startup Ecosystem in Canada
Founders across Canada are building products in artificial intelligence, healthcare, financial technology, climate tech, consumer software, education, and many other sectors.
They often face pressure to demonstrate rapid growth.
User counts, revenue, media attention, and funding can make progress easier to communicate.
But before scale comes something more fundamental:
Does anyone really care?
A healthy startup ecosystem Canada can support should encourage founders to answer that question before chasing bigger numbers.
Starting with a narrow audience does not mean thinking small.
It means creating a strong foundation.
Apple’s first few hundred customers were not evidence that the company would remain small. They were the beginning of something much larger.
The same principle applies to modern startups.
Find a few people with a real problem.
Make the product indispensable to them.
Learn why they care.
Then find more people like them.
The biggest companies can begin with a surprisingly small fire.
What matters is how intensely it burns.
