Remote work is now common enough that many founders assume building a remote company simply means allowing people to work from wherever they are, as though the location of the desks were the only variable. Companies that treat it this way, remote by default rather than by design, tend to get the worst of both worlds: the loss of the easy in-person coordination they gave up, without the gains that a genuinely remote-first company builds in its place. Remote-first is not the absence of an office; it is a specific and deliberate way of organising how a company communicates, decides, and remembers, and a company that does not make those deliberate choices does not get a neutral outcome, it gets a quietly dysfunctional one.
The distinction that matters is between a company that permits remote work and one that is actually built for it, because the two operate on completely different assumptions. A permitting company still runs on the habits of co-location, the hallway conversation, the quick meeting, the shared context that comes from being in the same room, and simply scatters the people who depended on those habits, leaving them to coordinate through channels that were never designed to carry the load. A built-for-remote company replaces those in-person mechanisms with deliberate ones suited to distance, and the difference in how well the two function is enormous, even though from the outside both just look like people working from home.
Writing things down as infrastructure
The foundational practice of a genuinely remote-first company is writing things down, not as a nice habit but as the core infrastructure that replaces the shared context an office provided for free. In a co-located company, an enormous amount of knowledge lives in the air, in conversations overheard, decisions witnessed, context absorbed by proximity, and none of that transfers to a distributed team unless it is deliberately written. A remote company that does not write things down does not have quiet, informal coordination; it has no coordination, because the informal channel that co-located teams rely on simply does not exist across distance, and nothing has been built to take its place.
This makes documentation a first-class activity rather than an afterthought, because the written record is how a distributed company knows what was decided, why, and what is expected, in place of the shared memory a physical office holds automatically. The decisions, the context, the reasoning, the state of things, all of it has to be captured in a form others can find and read, or it effectively does not exist for anyone who was not in the specific conversation. Companies that build this writing habit early develop a durable, searchable organisational memory that co-located companies often lack, turning a constraint of remote work into a genuine advantage, while companies that skip it operate in a permanent fog of who-knows-what.
Deciding asynchronously
The second deliberate choice is learning to decide asynchronously, without requiring everyone in the same place at the same time, because a remote company that tries to make every decision in a synchronous meeting recreates the coordination cost of an office without its ease. When people are distributed, possibly across time zones, insisting on real-time meetings for everything becomes a scheduling burden that slows the company and exhausts the team, and it wastes the main advantage of remote work, which is the freedom from needing everyone synchronised. Asynchronous decision-making, where proposals are written, considered, and resolved without a live gathering, is what lets a distributed company actually move.
A remote company that does not write things down does not have informal coordination. It has none, because the hallway channel that co-located teams rely on simply does not exist across distance.
Deciding asynchronously is a skill that has to be built, and it depends on the writing habit, because an asynchronous decision requires the context and the proposal to be captured well enough that people can engage with them on their own time and reach a resolution without a meeting. This is harder than gathering everyone in a room and hashing it out, which is why companies default away from it, but it is what makes remote-first genuinely work rather than merely function under strain. Reserving synchronous time for the things that truly need it, and handling the rest asynchronously, is the operating rhythm that distinguishes a company built for distance from one merely enduring it.
Deliberate by design, from the start
All of this is far easier to build from the beginning than to retrofit later, which is the real argument for deciding your remote approach deliberately from day one rather than drifting into it. A company that establishes the writing habit, the asynchronous decision-making, and the deliberate communication practices while it is small bakes them into its culture, so they grow naturally as the company does. A company that scatters first and tries to add these practices later has to change ingrained habits under the strain of a team already struggling to coordinate, which is much harder, and many never manage it, remaining permanently in the dysfunctional middle of remote-by-default.
The regional dimension can make remote-first especially valuable, since a distributed model lets a company draw on talent across a whole region rather than one city, and serve customers across markets without concentrating in one place, which for many founders is a real strategic advantage rather than merely a convenience. But the advantage only materialises if the company is actually built for distance rather than just permitting it, which comes back to the deliberate choices: write things down as core infrastructure, learn to decide without gathering everyone, and design the communication practices on purpose from the start. Do that, and remote-first becomes a genuine strength. Drift into it, and it becomes the quiet dysfunction that founders mistake for the nature of remote work itself.