For a stretch of years I hosted RemotePreneurs, a YouTube interview series with founders and operators building companies without a traditional office as the center of gravity. After more than a hundred conversations, the patterns stopped being anecdotes and started looking like an operating system.
This is not a highlight reel of famous guests. It is what kept showing up when people who actually run remote-first companies talked about what works, what breaks and what they would do earlier next time.
I later founded and scaled a fully remote software consultancy myself, and as a partner I had already helped grow a consulting firm from about $6M to $60M. The interviews did not replace that experience. They sharpened it. Below are the lessons I still use.
Remote-First Is a Design Choice, Not a Perk
The strongest guests did not treat remote as "office culture over Zoom." They designed the company as if co-location were the exception.
That sounds obvious. In practice it means writing down how decisions get made, how work is handed off and how performance is judged, instead of hoping people absorb it by sitting near the right hallway. Guests who skipped that design phase often described the same failure: a few people became human routers for every question, and growth stalled at the bandwidth of those people.
Remote-first is not the absence of an office. It is the presence of an operating system that works when nobody shares a room.
Trust Is Built With Cadence, Not Slogans
Almost every durable remote company had a rhythm: weekly priorities, clear owners, visible progress and a small number of meetings that existed for decisions rather than status theater.
Trust was not "we hired adults, so leave them alone." Trust was "we made expectations legible, so people can succeed without guessing." The interviews that stuck with me were rarely about ping-pong tables or home-office stipends. They were about how a team knows what good looks like on Friday when nobody watched them on Tuesday.
Async Is a Skill, Not a Default Setting
Many guests said they were "async first," then admitted their Slack was still a second job. The ones who made async work treated writing as a core competency.
They wrote proposals before meetings. They recorded short updates instead of booking thirty minutes for a monologue. They accepted that a thoughtful reply tomorrow beats a half-baked reply in two minutes. And they protected overlap hours for the few conversations that truly need back-and-forth: conflict, ambiguity, and relationship repair.
Async fails when it is used to avoid hard talks. It works when it is used to prepare for them.
Hire for Ownership, Then Give People Something Real to Own
Remote companies that scaled well hired people who could create clarity, not just consume it. Job descriptions sounded less like task lists and more like outcomes.
Several founders described the same early mistake: hiring for skills they could supervise closely, then wondering why remote felt harder than an office. Supervision does not travel well across time zones. Ownership does. The follow-on lesson was just as important: ownership without authority is theater. If you want someone to own a result, give them the decision rights that match it.
Culture Is What You Tolerate in Writing
In an office, culture leaks through tone of voice and who gets interrupted. Remote, culture shows up in docs, pull requests, issue threads and how leaders respond when something goes wrong.
Guests who were honest about culture talked less about values posters and more about examples: what happened the last time a deadline slipped, a customer was upset or a hire was wrong. Remote teams copy what leaders do in public channels. If leaders only praise speed, people hide quality problems. If leaders reward clear updates and early escalation, people tell the truth sooner.
Daily Rituals That Kept Showing Up
Across very different industries, a handful of practices repeated:
- A written weekly plan with a single owner per outcome.
- A short daily or near-daily update in a shared channel (not a meeting).
- Documented decisions, including the "why," in a place new hires can find.
- Deliberate overlap windows across time zones, treated as scarce and valuable.
- Regular one-on-ones focused on blockers and growth, not status regurgitation.
- A playbook that grows whenever the same question is asked three times.
None of these are glamorous. Together they are how remote companies avoid becoming a pile of private chats and forgotten promises.
What Remote Does Not Fix
Remote work does not fix a fuzzy strategy, a weak manager or a product nobody wants. Several interviews were cautionary for that reason. Founders who went remote to escape hard management problems usually recreated those problems in a chat app.
Remote also does not mean zero in-person time for every company. Some guests used occasional on-sites for planning or bonding. The point was never purity. The point was that the default system still worked on the fifty-one weeks nobody flew anywhere.
How I Use This Now
When I look at a remote team, I ask a short set of questions I stole from those conversations:
- Can a new hire find how work gets done without asking the same three veterans?
- Are outcomes owned by names, or by group chat?
- Do people know what "good" looks like without watching someone do it?
- Is writing valued enough that meetings shrink?
- When something breaks, does the truth surface early?
If the answers are weak, no tool migration will save the culture.
The Short Version
After 100+ RemotePreneurs interviews, my conviction is simple. Remote-first companies win when they design for clarity: written expectations, real ownership, async skill, a steady cadence and leaders who model the behavior they want copied. The office was never the real operating system. The habits were.
I took a firm from $6M to $60M in under three years.
If you are building or scaling a remote services team and want to compare notes, you can find me at https://tdzpro.com.
Ashkan Rajaee is the founder of TDZ Pro. As a partner, he helped grow a software consulting company from about $6M to $60M in under three years, and he founded and scaled a fully remote software consultancy.
Top comments (1)
The playbook rule is my favorite detail here, a question asked three times earning its own written answer feels like a clean way to stop repeat explanations.