What if the secret to building something big is refusing to be scalable at first?
Every founder wants an engine that hums on autopilot: viral loops, automated hiring, turnkey growth channels. Yet the rare startups that become enduring companies share a stubborn habit. In the earliest days the founders do things that do not scale. They personally recruit the first users. They personally recruit the first team members. They trade efficiency for craftsmanship. They substitute attention for automation.
This is not nostalgia for scrappy grind. It is a structural claim: the early decisions about people and users shape the company more than the early decisions about technology. Put another way: the two most important unscalable acts are selecting the human DNA of the company and handcrafting the initial user relationships that prove the product matters. Ignore either and the company will be fragile, no matter how clever the code is.
The paradox: scale is the enemy of the thing that creates value
Most founders think of scale as the goal and unscalable work as a temporary inconvenience. In reality, scale and fragility trade off in a way that is not obvious. When a company scales too early in the wrong dimensions it dilutes the signals and relationships that created its initial value.
Consider a small team of brilliant people working on a hard problem. When they are few and directly connected, the group contains feedback loops that are fast, intense, and creative. People reinforce each other. Everybody is trying to impress the rest. The organization behaves like a single organism: it moves quickly and pivots with low friction.
Now add layers: middle managers, HR pipelines, broad hiring panels, and meeting rituals intended to coordinate larger groups. The organization gains coordination capability, but it loses those dense interpersonal feedback loops. The founder becomes further removed from the day to day, and the company begins to grow in processes instead of outcomes. In this moment of transition the true risk is not the headcount number itself. The risk is the loss of direct founder involvement in recruiting and in shaping the early user experience.
Why is that so dangerous? Because both the first hires and the first users are not merely inputs to growth. They are instruments for learning about the product and the market. They teach the founder what the product must become. When the founder delegates recruiting of people and recruiting of users too early, the company loses its compass.
Two crafts that look unscalable but create scalable advantages
There are two crafts that every founder must learn and practice until they no longer can. They feel inefficient, and they are. Yet they seed the only features that can later be scaled without losing direction.
Curating the first people. Recruiting is an act of sculpting the company DNA. The early hires are not interchangeable. They determine culture, standards, and the social norms of what gets done and how. The right hires are not just high IQ and skill. They are low ego, self managing, and obsessed with the work rather than credit. A small, mutual admiration society in which everyone wants to impress each other is more productive than a larger collection of competent people who bicker and politick.
Consequence: founders should remain personally involved in hiring decisions until they can point to a team and say with confidence that any new candidate could walk in, pick someone at random, and be impressed. If you cannot say that, you have a person in the room preventing the team from reaching the necessary bar.
Recruiting the first users by hand. Early users are not a market statistic. They are conversational partners. When founders personally recruit the first customers they get a level of feedback that cannot be replicated by analytics or feedback forms. This is how you learn what users actually value, and what distinguishes token interest from a deep need. Recruiting users by hand is also how you create evangelists who will seed growth through referrals.
Consequence: founders must be willing to do tasks that seem beneath long term strategy: emailing, calling, attending meetups, and giving personal attention to each early user. Those small acts of service and solicitation produce insights into the product that would otherwise take months to appear in aggregated signals.
A framework you can apply today: The Curate and Cultivate Loop
Think of early company building as a loop with two hands. One hand curates people. The other hand cultivates users. Each hand informs the other. Do both by hand and the loop compounds. Automate too early and you create brittle systems.
Centerpiece concepts:
Curate: The deliberate, high bar selection of team members who will imprint the culture and craft.
Cultivate: The founder level work of recruiting, onboarding, and delighting the first users to learn what matters.
Smallness Principle: Break the organization into components small enough for intense focus and mutual accountability. Smallness is not an accident. It is a design choice that preserves signal quality.
Impress Test: When hiring, the criterion is not absolute credentials but whether each person on the team would impress a new candidate. If not, you are tolerating mediocrity.
Toehold Test: When finding users, ask whether you can get a critical mass in a niche quickly by recruiting manually. A toehold is a group of users who can sustain early growth through engagement and word of mouth.
How the loop works in practice:
Founders pick a small initial niche of users they understand and can access easily. They go recruit users personally to achieve a toehold. They do this by direct outreach, attending events, or solving their own problem and inviting peers.
The founders use those conversations to learn what users actually do and want. They use what they learn to refine the product rapidly.
The founders hire early teammates not based on process but based on whether these hires will accelerate the loop: can they talk to users? can they ship quickly? do they raise the impress bar?
These hires, being high bar and low ego, complement the founders by executing on the refined product and continuing the direct user relationships.
Repeat. Over time the product matures, the user base grows, and the team culture crystallizes. Only then does automation and process become less risky to introduce.
This loop explains why founders should resist the temptation to scale people with generic recruiting or to launch with a big broadcast expecting users to appear. Scale without a curated foundation is amplification of noise.
Concrete signals and tactics that differentiate craft from chaos
Below are actionable diagnostics and rituals that make the abstract framework operational.
Hiring diagnostics and rituals:
The Impress Test: Before extending an offer, imagine a new strong candidate walking into the room and choosing anyone on the team to interview. If the candidate would not be impressed by at least 80 percent of the team, postpone hiring and fix the weak links. This is a quick proxy for cultural signal strength.
Founders stay involved: Founders should have a veto on every early hire. This is not micromanagement. It is genetic control over the company.
Smallness design: Organize teams as small autonomous units where possible. If you need coordination, prefer that the coordinating artifact is a simple written document or a tight standing meeting rather than multiple layers of middle management.
Low ego checklist: During interviewing, probe for low ego with questions about past conflicts, how credit was shared, and how the candidate handled failure. Prefer those who emphasize craft and learning over title and recognition.
User recruitment diagnostics and rituals:
The Toehold Hunt: Identify the smallest definable group of users who will care deeply about what you are building and who are easy for you to reach. Then go recruit them, persisting until you have a meaningful cluster of engaged users.
Manual onboarding playbook: For the first hundred users, do onboarding by hand. Call them. Walk through the product. Use the conversations to decide what you will automate later.
Replace metrics with conversations: When you have fewer than a few hundred users, prioritize qualitative feedback over quantitative metrics. One conversation with a passionate user is worth dozens of passive analytic signals.
Organizational timing rules:
Do not institutionalize recruiting until you have a repeatable hiring bar and the founder can name five people who would impress any incoming candidate.
Do not automate user acquisition until you have proof that a toehold can spread without constant founder involvement. Manual methods should be used until they reveal the right lever to automate.
Concrete examples that illustrate the difference:
A team physically separated from the rest of the company prevents credit conflicts and allows focus to flourish. Physical and organizational smallness can preserve clarity of purpose.
Limiting meetings and encouraging people to walk out when meetings are unproductive reduces the politicking that scales with headcount. These cultural constraints keep the team focused on output rather than process.
Attending a niche conference or meetup to recruit the first users creates both customers and insights. That same act, repeated a few dozen times, reveals the patterns you will later productize.
Key Takeaways
Prioritize founder led recruiting of both people and users until the company has clear, repeatable signals. Early delegation is subtle company weakening.
Use the Impress Test when hiring: if an outside top candidate would not be impressed by your team, you are tolerating mediocrity. Do not wait for HR to fix that.
Hunt for a toehold niche of users you can reach by hand; cultivate them with high attention before attempting broad distribution.
Keep teams intentionally small and design for smallness. Small teams preserve high signal to noise ratios in feedback and culture.
Automate only after you have learned what to automate. Manual actions teach you what to build into systems later.
Conclusion: Honor the small acts that make scale meaningful
Scale feels like a destination: more customers, more hires, more markets. But scale without craftsmanship is expansion of mistakes. The durable companies are those whose founders refused to surrender two crafts: the craft of choosing people and the craft of courting users with their own hands. Those unscalable acts are not quaint. They are the kiln in which product insight and culture are forged.
If you are building something, treat the early period as an apprenticeship in human curation. Be willing to do the repetitive, slow work of recruiting both people and users personally. Not because it is romantic, but because it is diagnostic. The insights you extract from hand recruiting will determine what you can later scale. The point of being unscalable is not to avoid scale. It is to make scale worth having.
The question to ask is not whether the company can scale. The question is whether what you plan to scale is worth scaling.
When you answer that with the rigors of curation and cultivation, you will create a company that scales without losing the qualities that made it valuable in the first place.
The Unscalable Alchemy: How Founders Forge Product and People by Doing the Small Things | Glasp
