Enterprise trust used to have a physical address. Quarterly business reviews in conference rooms. Dinners where the agency picked up the check. Golf, because golf has always been a proxy for seriousness. The underlying logic: time in the same room builds the kind of relationship that sustains a multi-year engagement through difficult decisions and missed deadlines and scope conversations nobody wants to have.
That model assumed a lot of things that no longer hold. It assumed clients and partners were near each other, or willing to travel. It assumed the relationship’s warmth came from its in-person texture: the small talk, the meal, the shared moment of boredom at 16,000 feet. Most of all, it assumed proximity was the thing, rather than what proximity was trying to produce.
Proximity was actually a delivery mechanism for something else: attention, transparency, and the confidence that the other party had your interests in mind. Those things can be delivered remotely. In some cases, they’re delivered better.
Presence as proxy
Modern Tribe has been fully remote since its founding. That’s not a recent accommodation or a pandemic response. It’s structural. Which means the question of how to build genuine trust with clients, the kind that lasts ten years, the kind that survives a hard conversation, has been in front of us for two decades.
What we’ve found is that the traditional relationship-building model wasn’t really about the golf. It was about signal. The client dinner signaled: we take this seriously, we’re investing in you, we’re not going to disappear. The quarterly business review signaled: we’re accountable, we have a system, we’re thinking about your business beyond the immediate deliverable.
Those signals can be sent without a tee time. They can be sent better, and more consistently, when you build the practices that actually produce them rather than relying on physical proximity to do the work by implication.
What replaces the golf outing
Two practices have made a real difference in how Modern Tribe builds client trust at a distance.
The first is asynchronous walkthroughs. When a complex deliverable is ready — an architecture decision, a design direction, a technical recommendation — a 3-minute Loom walkthrough is more useful than a live review call. Not because the call isn’t valuable, but because it respects how comprehension actually works. A client who watches a clear video explanation before a call comes into that call having already processed the work. They have better questions. The conversation is more productive. And the implicit message, “we thought about how you’d receive this, not just what we’d present,” is itself a trust signal.
The second is visible work. Shared Figma files, open Slack channels, Jira tickets the client can actually see. Letting clients into the process before the work is polished is counterintuitive for agencies trained on the big reveal. The reveal feels like a demonstration of competence. In practice, it’s a protection mechanism: if the client doesn’t see the work until it’s done, they can’t push back until it’s expensive to change. That’s not a service to the client. It’s a transfer of risk.
Transparency is different. When a client can see a design evolving, they’re part of the process rather than the audience for it. When they can watch a ticket move through a board, they’re not wondering what’s happening — they know. That visibility produces the same psychological effect as the quarterly business review: confidence that the other party is engaged and accountable. Except it happens continuously, not quarterly.
The trade-off worth naming
Radical transparency requires trust to flow both directions. Letting a client into the messy middle means they’ll see decisions that are still being made, paths that were explored and abandoned, the normal friction of complex work. Some clients aren’t ready for that. Some relationships need the polished reveal to function, because the client’s internal stakeholders need the presentation, not the process.
The practice doesn’t work for everyone. But for clients who are genuinely operating as partners — who have skin in the outcome and want to think alongside the team rather than receive a deliverable — it’s more honest about how good work actually gets made. And honesty, as it turns out, is a better foundation for a 10-year relationship than a dinner tab.
The actual point
The golf outing was never really about golf. It was about demonstrating that the relationship mattered enough to invest in. That the agency was paying attention. That there was continuity beyond the project.
A fully remote team can demonstrate all of that; if it builds the practices that actually produce those signals, rather than assuming a physical context will do it by default. The agencies that figure this out aren’t just adapting to a remote world. They’re building something more durable than geography ever was.