How do you build company culture with five people?

At five people, your culture is already being set—by how you treat your first users, how you handle mistakes, and what you silently tolerate. The good news is that this is the only moment when one founder can shape culture completely and cheaply. The bad news is that most founders spend this window writing mission statements instead of doing the things that actually encode values into the company's DNA.

Culture is behavior, not belief

The most common mistake at the five-person stage is confusing culture with documentation. A Notion page listing your values does nothing. What actually builds culture is the repeated, visible behavior of the founders—especially in moments of pressure. When you stay on a call with a struggling user for two hours instead of moving on, your team watches. When you ship something you know is slightly broken and don't flag it honestly, your team watches that too.

Paul Graham's observation about early-stage customer attention is instructive here: when founders go out of their way to make initial users genuinely happy, that attentiveness eventually permeates the company's culture—not because it was mandated, but because it was modeled. The culture you want at 200 people has to be lived at 5. There's no later opportunity to retroactively install honesty, craftsmanship, or urgency. You either practice it now or you don't have it.

Practically, this means narrating your decisions out loud. When you decline a shortcut, say why. When you redo something that was good enough, explain the standard you're holding. Small teams absorb norms through observation, and the founder is the primary signal source. Your job at this stage isn't to write culture down—it's to perform it consistently enough that the other four people internalize it without being told.

Who you hire in the first five defines everything

At five people, each individual represents 20% of your culture. That's not a metaphor—it's arithmetic. One person who cuts ethical corners, blames others for failures, or treats users as obstacles will reshape the team's behavioral norms faster than any founder speech can correct. This is why the cofounder relationship is the first cultural test: if there's exploitation or dishonesty between founders, it will spread outward to every hire and every user interaction.

The standard for early hires should be: does this person make the people around them better, and do they do the right thing when no one's watching? Skills can be developed. The willingness to do tedious, unglamorous work without being asked—and to be honest about problems instead of hiding them—is much harder to install in someone who doesn't already have it.

One concrete filter: pay attention to how candidates talk about their previous employers and users. People who habitually frame themselves as smarter than the companies they worked for, or who describe past users dismissively, will bring that same contempt into your company. At five people you can't dilute it. You have to screen it out entirely.

Do the unscalable things that teach your team what you stand for

Early-stage founders often skip the deeply attentive, hands-on work with users because it feels inefficient at a company-building level. This is exactly backwards. The unscalable work—personally onboarding every user, hand-writing follow-ups, fixing individual problems that will never recur—isn't just product research. It's a live demonstration to your team of what the company values.

When your team sees you spend three hours helping one user succeed, they understand without any meeting or memo that users are not an abstraction here. When they see you iterate on something five times because it's not quite right yet, they understand the quality standard. You are the curriculum. The early months are the only time when the founding team can directly teach every employee what excellence looks like in this specific company, in this specific market.

The practical implication: resist the temptation to delegate user-facing work prematurely. Keep at least one founder in direct, frequent contact with real users until you have strong cultural transmission—meaning your early hires have internalized the standards well enough to model them for the next wave. That's when it becomes safe to step back, because by then the culture is self-replicating.

Make your standards explicit through real decisions, not hypotheticals

One of the most effective culture-building tools at five people costs nothing and takes ten minutes: the post-decision debrief. After you make a significant call—a hiring decision, a product tradeoff, a difficult conversation with a user—explain your reasoning to the team. Not in a lecture format, but as a real account of what you weighed and why you landed where you did.

This does two things. First, it makes your actual values legible. Most founders have strong intuitions about quality, honesty, and user care, but those intuitions are invisible until they're narrated. Second, it gives your team a reusable mental model. The next time they face a similar decision without you in the room, they have a reference point. Over dozens of these conversations, the team builds a shared decision-making vocabulary that will outlast any individual.

Avoid the opposite pattern: making decisions quietly and then announcing outcomes. That teaches your team that judgment is a black box held by founders, which produces either paralysis (waiting for founder approval on everything) or freelancing (making decisions with no shared framework). Neither scales. The goal is a team that can make the right call in your absence—and that only happens if they've seen your reasoning, repeatedly, in conditions that matter.

Protect the culture by naming violations quickly

Five-person cultures are fragile in a specific way: a single tolerated violation becomes the new norm almost immediately. If someone is consistently late to commitments and nothing is said, lateness becomes acceptable. If someone takes credit for a teammate's work and it passes without comment, that behavior becomes fair game. The smaller the team, the faster bad patterns propagate—because there's no institutional mass to absorb them.

This means founders have to name violations early and directly, while the team is still small enough that the conversation can happen without bureaucracy. This doesn't require drama. A quick, private conversation—'I noticed X happened; here's why that matters to me'—is usually enough, especially with people who were hired well and want to be good. The goal isn't punishment; it's calibration. You're helping them understand where the line is before they've drifted too far past it.

The harder case is when the violation comes from a cofounder or very early hire—someone with status in the group. This is where founders most often fail to act, because the relationship cost feels too high. But the cost of inaction is higher. One person with status modeling the wrong behavior will pull the entire team toward it. Addressing it early, when it's still a pattern and not yet an identity, is dramatically easier than trying to correct it after six months of institutional drift.

“Delighting customers will by then have permeated your culture.”

— Paul Graham, source

The one thing to do

Starting today, narrate one real decision out loud to your team—your reasoning, your tradeoffs, your standard—so that your values become legible rather than invisible.

Frequently asked questions

Should we write down our values at five people?

Only if the written version accurately reflects what you actually do—not what you aspire to. A values document that contradicts observable behavior is worse than no document, because it teaches your team that stated values are decorative. Write them down after you've lived them consistently, not before.

How do we maintain culture as we hire beyond five people?

Culture transmits through people, not documents. Your first five hires need to be strong enough cultural carriers that they can model and reinforce norms for the next wave. Prioritize hiring people who already embody the behaviors you want, then trust them to pass it on—while staying close enough to correct drift early.

What's the biggest culture mistake founders make at this stage?

Treating culture as a future problem. The behaviors normalized in the first three to six months are extremely hard to dislodge later. Founders who plan to 'get serious about culture' after they have traction usually find they've already built one—just not the one they wanted.

Can culture survive a bad early hire?

Sometimes, but only if the bad hire is addressed quickly. At five people, every individual has outsized influence on group norms. A mis-hire who stays for six months can reshape defaults that take years to correct. Move fast when you know someone is the wrong fit.

Sources

More playbook answers · Growth Prophet home