How to Build Company Culture in a Startup: A Founder’s Operational Guide

11–17 minutes
Founder building company culture in an Indian startup through deliberate operational decisions

Most founder advice on company culture is written by people who have either never built one from zero or have built one so long ago that the texture of it has faded. The gap between what founders actually do in their first few years and what shows up in articles, books, and podcasts is wide.

I have been running Marpu Foundation for seven years. We started as one person and a small group of volunteers in Hyderabad, and we now work across 23 Indian states with hundreds of paid team members and volunteers passing through our programmes every year. Along the way, OurVolunteer.com and KRV Group came in as separate organisations with their own cultures to think about. The cultures of these three organisations are similar but not identical, and the differences between them are operational decisions, not accidents.

This article is about how to actually build company culture as a founder in the early years. Not the slogans. Not the values posters. The operational decisions you make every week that, accumulated over time, become what your culture is.

It is written for founders, CEOs, and early team leaders who are building something from scratch and want to understand what culture really is, where it comes from, and how to shape it deliberately rather than wait for it to take whatever shape it falls into.

Culture Is the Sum of What You Tolerate

The single most useful sentence I have ever read about company culture, and the one I keep returning to in my own work, is this. Your culture is not what you say. Your culture is what you tolerate.

What you tolerate is what people see. If you say excellence is a value but tolerate sloppy work because the person doing it is your friend, the culture is sloppy work tolerated for friends. If you say transparency matters but tolerate decisions made in private channels, the culture is private decisions. If you say you respect people’s time but tolerate meetings that start late and run long, the culture is late meetings.

This works in the other direction too. If you say excellence is a value and consistently send back work that is not at the bar, even gently, even from people you like, the culture starts to be excellence. If you make decisions in public, write them down, share the logic, the culture becomes transparency. If you start meetings on time and end them on time even when senior people are late, the culture becomes respect for time.

For a founder building from zero, this is the lever that actually matters. You are not setting culture by writing a values document. You are setting culture by what you let pass and what you do not. Every quiet correction, every delayed praise, every uncomfortable feedback conversation is shaping the culture more than any all-hands speech you give.

The First Five Hires Set the Culture for the Next Five Hundred

The other founder lesson I would offer early is that the people you hire in the first year are setting the operating standard for everyone who joins after them.

I learned this slowly. In Marpu’s first two years, I made hiring decisions that I would not make today. People joined who were close to me, or available, or willing, but who were not aligned with how I wanted the work to be done. They became the de facto reference point for what was acceptable. New people coming in observed how the older ones behaved and concluded that this was how Marpu operated. By the time I tried to course correct, the patterns had set hard.

The same lesson plays out in startup after startup. The first five hires define the bar. The next twenty calibrate to that bar. By the time you have a hundred people, the original five have shaped how everyone works, even if they themselves are no longer in the company.

The implication for founders is to slow down on the first five hires considerably. Hire people who do the work the way you want it done, not just people who can do the work. The difference between these two is the difference between a culture you can scale and a culture you have to apologise for later.

What Culture Actually Comes From

Founders often think culture comes from values statements, all-hands speeches, town halls, or HR-led culture programmes. In practice, culture comes from four operational sources that founders control directly.

Source 1: How decisions get made and communicated. If decisions are made in private and announced as fait accompli, the culture becomes top-down and quiet. If decisions are made in writing, with reasoning, in a place everyone can see, the culture becomes transparent and intellectual. The founder’s choice of how to communicate decisions is the strongest culture signal in the early years.

Source 2: How disagreement is handled. Every founder will face moments where someone disagrees with a decision, a priority, a direction. How you respond to that first instance of disagreement teaches everyone whether disagreement is welcome. If you punish it, even subtly, the culture becomes silent agreement. If you welcome it, engage with it, sometimes change your mind because of it, the culture becomes intellectual honesty.

Source 3: How mistakes are treated. The first time a team member makes a real mistake, the founder’s reaction sets the standard for how mistakes will be treated forever. If the reaction is anger, blame, or visible disappointment, the culture becomes risk-averse and hidden. If the reaction is curious problem-solving without blame, with focus on what to learn and what to change, the culture becomes one where people surface problems early instead of hiding them.

Source 4: What gets celebrated and what gets ignored. Founders signal what matters by what they celebrate publicly. If you celebrate revenue numbers but never celebrate the quiet work of someone fixing a process, the culture becomes about visible wins. If you celebrate the quiet work alongside the visible wins, the culture becomes about substance. If you celebrate effort without outcomes, the culture becomes about looking busy. If you celebrate outcomes without acknowledging effort, the culture becomes burnout-prone.

These four sources operate every single day, regardless of whether the founder is paying attention to them. The choice founders have is to be deliberate about all four, or to let the four shape the culture by accident.

The Documents Every Early Founder Should Write Themselves

Before you have an HR team, before you have a People Operations function, there are three documents that founders should write themselves rather than delegate. Each of them ends up shaping culture more than any later policy ever will.

Document 1: The hiring philosophy. A short document that explains how you hire, what you look for, what disqualifies someone, and what you will not compromise on. It is not a job description. It is a values document expressed through hiring criteria. Writing it forces the founder to articulate what kind of company they are actually trying to build. Most founders never write this document. The ones who do hire considerably better.

Document 2: The decision-making framework. A short document that explains how decisions get made in the company. Who decides what. When the founder is the decision-maker and when they are not. How disagreements get resolved. How decisions get communicated. Without this document, every decision creates ambiguity. With it, the company runs on a shared understanding of authority.

Document 3: The first-year operating note. A short document, written for the team, that captures what the early years feel like and what is expected. Not aspirational. Operational. In year one, we will be slow. In year one, we will be unclear about many things. In year one, we will ask everyone to do work outside their roles. Here is why and here is how we will get to year two. This document sets expectations honestly and prevents the resentment that builds when early-stage chaos goes unnamed.

These three documents are short. None of them needs to be longer than two pages. But the founder who writes them spends time clarifying what they actually believe, which is the prerequisite for shaping culture deliberately.

The Culture Mistakes Founders Make in the First Two Years

Across founders I have watched closely, including my own first two years, six recurring mistakes show up.

Mistake 1: Trying to be everyone’s friend. In the early years, the founder is often close in age, background, and life stage to the team. The temptation is to be a peer rather than a leader. This works for a while, until a hard decision is needed. By the time the founder tries to switch into the leadership role, the relationship dynamics make it harder than it should have been.

Mistake 2: Avoiding hard feedback because the team is small. Hard feedback in a small team feels intimate and risky. The instinct is to soften, defer, or skip it. But the founder who avoids hard feedback in the first ten hires is the founder who will face the same conversations with a hundred hires, when the cost of fixing patterns has multiplied.

Mistake 3: Letting one bad hire stay too long. Every founder knows the experience of hiring someone who turned out to be a poor fit and waiting too long to act on it. The cost is visible after the fact. The culture pays the price during the wait. Acting fast on bad hires, while painful, is the kindest thing a founder can do for the rest of the team.

Mistake 4: Building culture around the founder’s personality. Some founders create cultures that work because of their specific energy, charisma, or work style. The problem is that this culture cannot scale beyond the founder. As the company grows, the founder cannot be in every room, and the culture starts to fragment because nobody else can replicate the founder’s specific way of being. Culture should be designed to work without the founder in the room.

Mistake 5: Ignoring exit interviews. The most useful culture signal in any company is what departing people say in their exit conversations. Founders who avoid these conversations or run them perfunctorily lose the most valuable feedback they will ever get about their own culture. Founders who run them honestly, with curiosity instead of defensiveness, learn things they cannot learn any other way.

Mistake 6: Not separating personal preferences from cultural standards. A founder who likes early mornings sometimes builds a culture that punishes people who work late. A founder who likes formality sometimes builds a culture that rejects casual conversation. These are personal preferences, not cultural standards. Mixing them creates cultures that exclude good people for the wrong reasons. The discipline is to be honest about which of your preferences are values and which are just preferences.

How Culture Shifts as You Scale

The hardest culture lesson I have learned is that the culture that works at 10 people does not work at 50. The culture that works at 50 does not work at 200. Founders often resist this because the culture that worked at 10 was the one they built carefully and feel proud of.

At 10 people, culture is mostly transmitted by daily proximity. Everyone sees everyone. The founder’s behaviour is observable in real time. Decisions can be informal because everyone is in the room.

At 50 people, daily proximity breaks. The founder is no longer visible to everyone. Decisions need to be written down because not everyone is in the room. The informal culture that worked at 10 starts to feel arbitrary because it depends on context that not everyone has.

At 200 people, the founder is largely invisible to most of the company. Culture has to be carried by middle management, by written documents, by repeatable processes. The founder’s job shifts from being the culture to making sure the systems that carry the culture work without them.

The founder who recognises these shifts and adapts deliberately keeps their culture strong through scale. The founder who insists on the 10-person culture at 200 people watches the culture become accidental, fragmented, and eventually unrecognisable.

The Culture Habits That Have Mattered Most for Marpu

If I were to name the specific habits that have shaped Marpu’s culture more than anything else, four come to mind.

Habit 1: Writing decisions down. Every significant decision at Marpu gets documented, including the reasoning. This single habit has compounded harder than any other. New people joining can read the history. Old people reviewing decisions have a reference. Disagreements about what was decided become impossible because the record exists.

Habit 2: Slow hiring, fast firing. We have always taken time to hire. We have also been willing, when needed, to acknowledge a hire that did not work and act on it. This combination has protected the culture more than any single recruitment policy. Slow hiring keeps the bar high. Fast acting on bad hires keeps the bar from being lowered by people who do not belong.

Habit 3: Public credit, private feedback. Praise happens publicly. Hard feedback happens privately. This rule sounds simple but it shapes everything. Public praise makes people feel seen by the whole team. Private feedback preserves dignity. Reversing this, public criticism with private credit, is the fastest way to destroy a culture, and it is more common than founders admit.

Habit 4: The reverse-the-decision check. Before any major decision, I ask myself one question. If this decision turns out to be wrong, can it be reversed? If yes, decide quickly and move on. If no, slow down and think harder. This single habit has saved Marpu from several decisions that would have been painful to undo.

These four habits are not unique to Marpu. They are not proprietary frameworks. They are the operational expressions of values that other strong companies also live by. What matters is not their novelty but their consistency. Founders who do these four things every week, for years, build cultures that hold.

What Founders Should Stop Worrying About

Three things founders worry about more than they should.

Worry 1: Whether the culture is fun enough. Founders sometimes confuse fun with culture. They invest in offsites, parties, perks, and celebration rituals, hoping these will create culture. They will not. Fun is the byproduct of a strong culture, not the cause of one. People in companies with strong cultures often have fun, but they have fun because the work is substantive and the team is good, not because the offsite was well-organised.

Worry 2: Whether the values document is well-written. Values documents are largely irrelevant. Every company has them, almost no employee remembers what they say, and the words on the document rarely shape behaviour. The behaviour is shaped by what gets tolerated and what gets celebrated, not by what the values document says.

Worry 3: Whether other companies have a better culture. The grass is always greener. Founders often look at companies that have been written up for their culture and feel inadequate. The truth is that most celebrated cultures are also imperfect from inside, and most quiet companies have stronger cultures than they get credit for. Build your own thoughtfully and stop comparing.

A Final Note for Founders Building From Zero

The single biggest thing I have learned about culture in seven years is that it is built one decision at a time, and the small decisions matter more than the big ones.

The decision to send back a piece of work that was not at the bar. The decision to credit someone publicly even when they did not ask. The decision to write down a hard conversation rather than have it in passing. The decision to hold a meeting on time even when the senior person is late.

None of these decisions feels significant in the moment. Cumulatively, they become what your company is.

If you are a founder reading this in your first or second year, do not wait for a big culture moment. There will not be one. There will only be the next decision. Make it deliberately. Make the next one deliberately. Keep going. In two years you will look back and see the culture you built without ever having a single big culture meeting.

That is how it actually happens.


Write to me. My email is raghu@marpu.org.

Leave a comment