Proximity Isn't Nostalgia, It's Our Operating Model

Ask anyone who has worked both ways and they will tell you the same thing before you finish the question: a hard problem gets solved faster in a room than in a thread. Not because the people are smarter in person. Because the friction of typing, waiting, and re-explaining disappears, and what is left is just two people looking at the same screen until it works. At ETAPX, on the campus we built Whistlr Live Studio from, that is not a management preference dressed up as culture. It is a bet we keep making, on purpose, against a decade of industry consensus that said the office was optional and the calendar was the only thing that mattered.

The Room Beats the Roadmap Doc

Remote-first became the default position in tech not because someone proved it produced better products, but because it was cheaper, it scaled hiring past any single zip code, and it was hard to argue with during a period when showing up anywhere felt like a risk. Those were real reasons. They just were not reasons about the work itself. Once distributed teams became normal, the industry backfilled the argument afterward: async is more inclusive, deep work needs quiet, meetings are where good ideas go to die. Some of that is true in specific cases. None of it is true as a blanket rule for a company shipping a live product against a clock, with creators waiting on the other end of every decision. What remote-first optimizes for extremely well is the individual contributor's own calendar: control over hours, noise level, commute. What it does not optimize for is the thing that happens between two people who do not yet agree on what to build. Worked out over Slack threads and async video, that disagreement takes days. Worked out at a whiteboard, it takes twenty minutes and a marker. We have watched both versions happen inside the same company, on the same class of problem, and the gap in speed is not subtle.

Not a New Idea, Just a Deeper Commitment

We have made versions of this argument before, and we are not walking any of it back here. Being a Bay Area company was never incidental to what ETAPX does, and neither was the choice to treat culture as something built, not something that accumulates on its own if you leave people alone long enough. Campus community is that same conviction taken one level more specific. It is not enough to be headquartered somewhere real. The people building Whistlr, Influxx, Ocsidian, and GLSRM have to actually occupy the same physical space often enough that the culture has somewhere to happen.

What a Tuesday on Campus Actually Looks Like

None of this is a nostalgia trip for open-plan offices circa 2015. The Bay Area campus ETAPX works from is not there to be a perk on a recruiting page or a backdrop for photos. It is there because certain things about building Whistlr only happen when the people building it are near each other for enough hours that the unplanned parts of the day start doing real work. A single ordinary week produces a handful of moments like these, and none of them show up on a roadmap:

• A Creator Studio design review that starts as a scheduled meeting and turns into forty-five minutes at a monitor, three people redlining a WTC tab layout in real time.
• Someone from the payments side overhearing a Gems payout conversation in the kitchen and correcting a wrong assumption before it ever reaches a sprint planning doc.
• A new hire's first week spent sitting next to the person who actually owns the code they are about to touch, instead of reading a wiki page about it.
• Bug reports reproduced on someone's own desk in the time it would have taken just to write up the steps to reproduce them remotely.
• The realization, mid-lunch, that two teams are quietly building the same feature under two different names, caught before either one ships.

Why Proximity Compounds

Every one of those moments looks small on its own. A hallway correction here, a faster bug repro there. The case for campus culture is not that any single instance changes an outcome. It is that these moments compound the way interest does: quietly, constantly, and only visible when you look back over months instead of days. A team that runs into each other by accident twenty times a week accumulates a shared, unspoken understanding of the product that no documentation system replicates, no matter how well it is maintained. That understanding shows up later as speed: fewer meetings needed to align, fewer misreads of what a feature is actually for, fewer times a decision has to be quietly unmade because two teams built past each other without knowing it.

You can hire remote-first and still build a good product. What you cannot do remote-first is build the kind of shared instinct for the product that lets a team move without a meeting. That instinct is built in rooms, not in docs.

AJ, ETAPX

The Tradeoff We're Not Going to Pretend Away

Naming this honestly means naming what it costs. A campus-centered culture narrows the hiring pool to people who can be in the Bay Area, or who are willing to relocate for it, which is a real ask in a market where cost of living is its own kind of gatekeeping, not a footnote. It means the company absorbs the cost of a physical space instead of pocketing the savings a fully distributed team offers on paper. It means some strong engineers ETAPX has talked with over the years simply were not a fit, not for lack of skill, but because they had already built a life somewhere a campus culture could not reach, and asking them to uproot it was never going to be the right call for either side. We do not think that tradeoff is free, and we are not going to describe it as one just because it worked out for the people already here.

Who This Actually Rules Out

It rules out the fully async operator who does their best work at 2am in a timezone six hours off from everyone else. It rules out someone who needs total control over their physical environment to think clearly, door closed, notifications off, for the good work to happen at all. Both of those are legitimate ways to work, and ETAPX is honestly not the right home for either of them. What campus culture is built for is a specific kind of person: someone who does their best thinking out loud, who would rather be corrected in the room in real time than in a comment thread a day later, and who finds that being around the product team all day sharpens their sense of what the product actually needs, rather than draining it out of them by the end of the week.

Why the App Built by This Culture Looks the Way It Does

This is where the campus argument stops being a culture story and starts being a product one. Circuits and Flow, the close-circle and feed surfaces inside Whistlr, exist because the team that built them spends its own days in exactly the kind of proximity those features are trying to give creators and viewers: small, real, in-the-room connection, not broadcast to everyone at once regardless of who actually cares. A team that only ever worked at a physical remove from each other would have a harder time building software that bets on closeness being worth more than reach. We are not claiming you have to work on a campus to understand that instinct. We are saying it is not a coincidence that a company betting on in-person culture keeps shipping features that reward closeness over scale, on Whistlr and across the rest of what ETAPX builds.

Campus community is not a slogan on this team, and it is not a rule enforced for its own sake or defended out of habit. It is a bet that the extra friction of getting people into the same building, on the same days, pays for itself in speed and shared judgment that a distributed team has to work much harder to replicate, and sometimes never does. Some weeks that bet looks expensive: a lease payment, a commute someone would rather skip, a candidate who was otherwise perfect and still said no. Most weeks, it looks like a bug fixed late at night because nobody wanted to leave first, or a WTC tab redesign that took forty-five minutes instead of four days of back-and-forth that never quite lands the same way in writing. That is the difference we are actually chasing. Not the room for its own sake. What the room makes possible. We didn't set out to prove that offices beat remote work in the abstract. We set out to build Whistlr as fast and as well as we could, and proximity kept winning the argument on its own merits.