There’s a sentence I hear at conferences that makes me twitch: “You can’t build culture remotely.”
It’s usually said by someone who has an office lease to justify and a middle management layer that exists primarily to observe people sitting at desks. But it gets repeated so often, by enough credible people, that I used to half-believe it myself.
PipelineRoad has been fully remote since day one. Not “remote-first” with an optional office. Not “hybrid” with mandatory Tuesdays and Thursdays. Fully remote. Five people across multiple time zones, with no physical space that belongs to the company.
And we have a culture. A strong one. I know this not because we have a values poster — we don’t — but because when we onboarded Alfredo last year, he told me after his first month: “I’ve never worked somewhere where everyone actually knows what the standards are without being told.”
That’s culture. Not ping-pong tables and free lunch. The invisible agreement about what “good” looks like and how people treat each other when nobody’s watching.
Here’s how we built it without a building.
The Anti-Culture Deck
The first thing we did was explicitly reject the idea of a culture deck.
I’ve seen too many culture decks. They all say the same things. “We value transparency.” “We move fast and break things.” “We’re a family.” They’re written by founders who want to signal culture to investors and candidates, not by teams that have actually negotiated what their norms are.
Culture isn’t a document. It’s a set of behaviors that get reinforced through repetition and consequences. You can write “we value honesty” on a slide, but if the team sees someone get punished for honest feedback, the real culture is: don’t be honest.
So instead of writing values, we wrote behaviors. Specific, observable, testable behaviors.
“We respond to client messages within four hours during business hours.” Not “we value responsiveness.”
“We flag scope creep within 24 hours of noticing it, even if the client will be unhappy.” Not “we value proactive communication.”
“We share drafts at 70% quality for feedback, rather than polishing to 95% in isolation.” Not “we value collaboration.”
These behavioral norms emerged from real situations — most of them situations where something went wrong. The four-hour response time became a norm after a client escalated because a message sat unanswered for two days. The scope creep rule became a norm after we ate $8,000 of unrequested work because nobody wanted to have the awkward conversation. The 70% draft rule became a norm after Andre spent three days perfecting a design concept that turned out to be based on a misunderstanding of the brief.
Each norm was born from a specific failure. That’s what gives them weight. They’re not aspirational. They’re scar tissue.
The Rituals That Actually Matter
Remote work strips away the ambient interactions that in-office teams take for granted. The hallway conversation. The lunch table brainstorm. The “hey, got a second?” that catches a problem before it becomes a crisis.
You can’t replicate those digitally. I’ve seen companies try — virtual watercoolers, Slack channels for random chat, scheduled “social time” on Zoom. Most of it feels forced, and forced social interaction is worse than no social interaction.
What you can do is create rituals with genuine purpose that also build connection as a side effect.
Monday kickoff. Every Monday at 10 AM, all five of us are on a video call for thirty minutes. Not a status meeting — I hate status meetings. Each person shares one thing: their most important focus for the week. Not a list of tasks. One thing. The constraint forces prioritization and gives everyone visibility into what matters most across the team.
The call is thirty minutes. The first five minutes are always personal. What happened this weekend. How you’re feeling. Not mandated — nobody forces anyone to share. But the space exists, and because I start with something personal, others follow. Last Monday, Mikael told us about a documentary he watched about deep-sea photography. We talked about it for six minutes. Nobody complained about the “wasted” time.
Thursday review. Thursday afternoon, asynchronous. Everyone posts a short Loom video — three to five minutes — showing what they worked on. Not explaining it. Showing it. Andre walks through a design. Alfredo walks through a content calendar. Bruno walks through campaign metrics. I walk through strategy updates.
This ritual does two things. It creates accountability without surveillance — you know your work will be seen, so you ship with care. And it creates cross-pollination — Andre sees what Alfredo is writing and designs assets that match. Alfredo sees Andre’s design direction and adjusts his content tone. The whole team stays in sync without a single sync meeting beyond Monday.
Monthly retro. Once a month, an hour. What worked, what didn’t, what we’re changing. This is where behavioral norms get created, updated, or retired. It’s the most important hour of the month, and we protect it absolutely.
The Communication Constitution
The single most important decision we made about remote culture was establishing explicit communication norms. Not “be responsive” — actual rules about which channels are for what and what response times are expected.
Slack: Asynchronous by default. Response expected within four hours during business hours. Use threads. Don’t send “hey” by itself — always include the context so the other person can respond without a back-and-forth setup.
Loom: For anything that would take more than three paragraphs to type. Tone carries in video. It doesn’t carry in text. When in doubt, record.
Call: For urgent issues, sensitive feedback, or strategic decisions. If it’s emotional or complicated, it’s a call. Never try to resolve conflict over text.
Email: Client-facing communication only. We don’t email each other internally. Ever.
These aren’t suggestions. They’re norms, and we enforce them. When someone sends a three-paragraph Slack message about a strategic concern, I’ll respond: “This is a call conversation. When are you free?” Not because I’m being rigid, but because I’ve seen what happens when strategic conversations happen in text — they get misread, feelings get hurt, and what should have been a ten-minute call becomes a two-day Slack thread.
Identity Without a Space
The hardest part of remote culture is identity. In an office, identity is partially physical. You walk into a space that looks like your company, surrounded by people who work at your company, and that physical context reinforces who you are and what you’re building.
Remote teams don’t have that. So you have to build identity through other means.
For us, identity comes from three sources.
Shared standards. When everyone on the team knows what excellent looks like — not approximately, but specifically — there’s a pride that comes from meeting that standard. Our quality bar is our identity. When Andre talks to friends about his work, he doesn’t say “I work at a remote agency.” He says “I work at an agency where everything ships at this level.” The standard is the brand.
Shared language. Every team develops its own vocabulary over time. We have phrases that mean specific things to us. “Is this a 70 or a 95?” means “should I share this now for feedback or polish it first?” “This is a Hassan situation” — a reference to a Marrakech market story I told once — means “the client is being sold something they don’t need and we need to intervene.” These shared references create an in-group, and in-groups create belonging.
Shared wins. We celebrate client results publicly within the team. When a client’s organic traffic hits a milestone, when a campaign outperforms benchmarks, when a piece of content gets praised by the client’s CEO — we share it. Not in a performative way. In a “look what we built together” way. The wins are the proof that what we’re doing matters, and proof matters more when you can’t see each other working.
What We Haven’t Figured Out
I want to be honest about the gaps, because pretending remote culture is a solved problem would be dishonest.
Onboarding is harder remotely. When Alfredo joined, it took about twice as long as it would have in an office for him to fully absorb the team’s norms. In an office, you pick up culture through osmosis — you overhear conversations, you see how people interact, you absorb the rhythm. Remotely, all of that has to be made explicit, which means someone has to think about it and document it. We’ve gotten better at this, but it’s still our weakest point.
Spontaneous collaboration is rare. The best creative ideas often come from unplanned collisions — two people who aren’t working on the same project having a conversation that sparks something unexpected. This happens naturally in offices. It almost never happens remotely unless you engineer it. Our Thursday review helps, but it’s not the same as walking past someone’s desk and saying “what are you working on?”
Isolation is real. Some weeks, some people feel alone. That’s not a solvable problem — it’s a manageable one. We check in. We notice when someone’s Loom videos get shorter or their Slack presence drops. We ask. Not in a surveillance way. In a “I see you and I care about how you’re doing” way. But I won’t pretend we catch it every time.
The timezone challenge. With team members in different regions, there are windows of the day when everyone is online and windows when only some of us are. This creates information asymmetries. Someone posts an important update during another person’s night, and by morning, the conversation has moved on. We mitigate this with asynchronous communication, but it’s an ongoing friction.
The Uncomfortable Advantage
Here’s what I don’t hear enough remote advocates admit: remote culture has advantages that office culture doesn’t.
Remote culture is explicit. Because nothing happens by osmosis, everything has to be articulated. This means our norms are clearer, more specific, and more consistently applied than they would be in an office, where unspoken rules create confusion and exclusion.
Remote culture selects for self-starters. People who thrive remotely tend to be self-directed, communicative, and comfortable with ambiguity. The remote structure acts as a filter, and the people who make it through are exactly the kind of people you want on a small, high-performance team.
Remote culture respects autonomy. Nobody at PipelineRoad has to pretend to be busy. There’s no performative work — the staying-late-to-look-dedicated theater that office culture breeds. When work is done, it’s done. The output speaks for itself. This is more honest, more humane, and more productive than any open-plan office I’ve ever worked in.
Culture Is a Verb
The biggest misconception about culture is that it’s something you build once. Culture isn’t a structure. It’s a practice. It’s rebuilt every day through the small decisions that people make when nobody’s telling them what to do.
Do you respond to that message now or let it wait? Do you flag the problem or hope it resolves itself? Do you share the imperfect draft or keep polishing? Do you ask the uncomfortable question or let the meeting end without it?
Those micro-decisions, made independently by five people across multiple time zones, are our culture. And the only reason they’re consistent is because we’ve invested time — real time, valuable time — in defining what good looks like and reinforcing it through conversation, not documentation.
You can absolutely build culture without an office.
But you can’t build it without intention.