I’ve seen the same mistake kill dozens of remote teams. It’s not about the tools, the timezones, or the pay. It’s about trust. Or rather, the complete lack of it, replaced by a clumsy, misguided attempt at AI-powered surveillance.
Over the last decade, I’ve managed more than $8M in payroll for remote teams. I’ve built and sold two companies, RemoteTeam and MovieLaLa, that were built on the backs of incredible people working from all corners of the globe. I’ve also invested in over 200 companies, including some of the biggest names in AI like Anthropic, OpenAI, and Scale AI. I’ve seen what works and what crashes and burns. And the biggest predictor of failure? Treating your team like a bunch of untrustworthy robots.
The Allure of the Digital Panopticon
When the world went remote, a panic set in. Managers, used to seeing butts in seats, suddenly felt a loss of control. How could they know if people were really working? The solution seemed obvious: AI-powered monitoring tools. Keystroke logging, screenshot captures, activity trackers—a digital panopticon to ensure productivity.
I get the temptation. I really do. When you have deadlines to hit and investors to please, the idea of a tool that guarantees everyone is at their desk, typing away, is seductive. But it’s a trap. And it’s a trap that I’ve seen company after company fall into.
Here’s the problem: the moment you install that kind of software, you’ve sent a clear message. “I don’t trust you.” All the talk about culture, autonomy, and empowerment goes right out the window. You’ve created an adversarial relationship. It’s you versus them. And in that game, nobody wins.
The Counterintuitive Secret of 6 Successful Companies
I got obsessed with this problem. I spent months analyzing six different, highly successful, fully remote companies. I’m talking about companies with insane retention rates, off-the-charts productivity, and products that were dominating their markets. I wanted to know their secret.
Did they have some super-advanced, custom-built AI coworking platform? Nope.
Did they have an army of managers watching every move? The opposite.
They all had one thing in common, and it was shockingly simple. They trusted their people, completely and utterly.
Instead of monitoring activity, they focused on outcomes. They set clear goals, defined what success looked like, and then got out of the way. They used AI not as a whip, but as a partner.
Here’s what that looked like in practice:
- AI for Communication, Not Surveillance: They used AI tools to summarize long Slack threads, transcribe meetings, and make information more accessible. The goal was to reduce noise and improve clarity, not to check if someone was online at 9:05 AM.
- AI for Performance, Not Presence: Instead of tracking hours, they used data to understand team performance. They looked at things like cycle time in software development or customer satisfaction scores in support. They used AI to find bottlenecks and identify areas for improvement, not to punish people for taking a long lunch.
- AI for Connection, Not Control: Some of the smartest companies I saw used tools to foster human connection. One company had a bot that would randomly pair two people for a virtual coffee chat each week. Another used an AI-powered system to suggest collaborations between people in different departments based on their skills and current projects.
My 6-Year Journey: From Skeptic to Believer
I didn’t get here overnight. When I started RemoteTeam, I was a data-driven founder. I wanted to measure everything. I experimented with every productivity and monitoring tool on the market. For six years, I tweaked, I tested, I A/B tested. I had dashboards for my dashboards.
And you know what I found? The more we tracked activity, the more creative people became at gaming the system. We had people writing scripts to move their mouse. We had others who would just sit in a Google Doc with their cursor blinking to show they were "active." It was a complete waste of time and energy.
The turning point came when we were acquired by Gusto. Gusto has a deeply ingrained culture of trust. They hire great people and empower them to do their best work. It was a culture shock, but it was also a revelation.
We ripped out all the monitoring software. We stopped caring about when people worked and focused on what they produced. And guess what happened? Productivity went up. Morale skyrocketed. People started taking ownership of their work in a way I had never seen before.
The Truth About AI Coworking
So here’s the truth I’ve learned after all these years. AI can be an incredible tool for remote teams. But it’s not a replacement for good management and a strong culture. You can’t automate trust.
If you’re a founder or a manager of a remote team, I challenge you to do this: for one month, turn off all the activity monitoring. All of it. Instead, spend that time setting crystal-clear goals for your team. Define what success looks like for each person. Have open, honest conversations about their progress.
Focus on the what, not the how. I promise you, the results will surprise you.
You hired smart, capable adults. Treat them that way. The best AI coworking tool isn’t a piece of software. It’s a culture of trust. It’s the belief that your team will do the right thing, even when no one is watching. That’s the secret. That’s what separates the companies that thrive from the ones that just survive.
The Day I Realized We Were Measuring the Wrong Thing
I remember one specific incident at RemoteTeam that really drove this point home. We had a brilliant engineer, let's call him Alex. His output was incredible. He was solving problems nobody else could touch. But his activity score was consistently in the bottom 10%. He wasn't a big talker on Slack, and his commit history was sporadic. He'd disappear for two days and then, in a flurry of activity, commit a massive, elegant solution.
According to our tracking software, Alex was a slacker. My co-founder was getting nervous. He’d point to the dashboard and say, “Sahin, this guy is barely online. What are we paying him for?” I defended Alex, pointing to his results. But the data was a constant source of friction.
One day, I sat down with Alex. I didn't mention the tracking. I just asked him about his process. He told me he spent most of his time thinking. He’d walk around his neighborhood, turning the problem over and over in his head. He’d fill notebooks with diagrams. Then, when the solution was clear in his mind, he’d sit down and code it all out in a single, focused burst.
That was the lightbulb moment. We were trying to measure the process of work—the typing, the clicking, the online status—when all that mattered was the outcome. Alex was one of our most valuable team members, and our system was telling us he was a problem employee. We were on the verge of burning out a top performer because we were obsessed with the wrong metrics. We scrapped the activity tracker the next day.
Case Study: How “Project Phoenix” Rose from the Ashes
Let me give you a more concrete example from one of the six companies I studied. Let's call them Acme Corp. They had a critical project, codenamed "Project Phoenix," that was failing. It was over budget, behind schedule, and the team was completely demoralized. The team was spread across three continents, and the previous manager had implemented a strict, top-down, heavily monitored workflow.
The new manager who came in did something radical. She held a single all-hands meeting and said, “The old way isn’t working. I’m deleting all the tracking software. Your only job is to deliver Project Phoenix by the end of the quarter. I don’t care how you do it. I’m here to support you and remove roadblocks. That’s it.”
The first week was chaos. People were so used to being told what to do that they didn’t know how to function. But then, something amazing happened. The senior engineers started stepping up, organizing the work, and mentoring the junior developers. The team in Europe realized they could hand off their work to the team in North America at the end of their day, creating a 24-hour development cycle. They self-organized. They started communicating more, not less, because they needed each other to succeed.
They used AI, but they chose the tools themselves. They set up a shared AI assistant to summarize their daily progress, so everyone stayed in the loop without needing endless meetings. They used another AI tool to help them refactor old code, speeding up their development process immensely. They delivered Project Phoenix two weeks ahead of schedule. It was a massive success, and it was all because one leader had the courage to choose trust over control.
How to Build a High-Trust AI-Powered Remote Team: My Playbook
This isn't just a philosophical argument. You can put this into practice today. Here is my playbook, refined over a decade of building and investing in remote companies.
1. Hire for Autonomy: During the interview process, you need to screen for people who are self-starters. Ask them about a time they had to complete a project with minimal supervision. Ask them how they organize their day. Look for people who are proactive and don’t need their hand held.
2. Onboard for Clarity: The first 30 days are critical. Your onboarding process should be a firehose of information, but it needs to be organized. Set up a clear "source of truth" in a tool like Notion or Confluence. Document everything: your mission, your values, your processes, your goals. The goal is to give every new hire the context they need to make good decisions independently.
3. Set OKRs (Objectives and Key Results), Not Tasks: Don't give people a to-do list. Give them a mission. An objective is the ambitious goal (e.g., "Launch the V2 of our product"). The key results are the measurable outcomes that tell you if you’ve achieved it (e.g., "Achieve a 50% adoption rate within 60 days," "Reduce bug reports by 25%"). This focuses everyone on the results, not the activity.
4. Default to Transparency: Share everything. Your financials (if you can), your strategy, your failures. When people have the full picture, they make better decisions. They feel like owners, not employees. Use tools that facilitate this, like public Slack channels and shared documents.
5. Provide AI "Power Tools," Don't Mandate Them: Curate a list of recommended, helpful AI tools for things like writing assistance (like Jasper or Copy.ai), code completion (like GitHub Copilot), or meeting summaries (like Fireflies.ai). Frame them as resources to make their lives easier, not as requirements. Let them choose what works for them. The best tools will spread organically.
This Is Not the Easy Path
I need to be clear. This is harder than just buying some software. It requires you to be a better leader. It requires you to be comfortable with a certain level of ambiguity. It requires you to have tough conversations when people aren’t meeting their goals.
But the payoff is immense. You build a team of A-players who are deeply engaged and committed to the mission. You create a culture that attracts and retains the best talent in the world. You build a company that can out-innovate and out-execute the competition because you’re not wasting energy on internal battles of mistrust.
I’ve made my bet. I’m all in on trust. I’ve invested my own money in over 200 companies, and the ones I see succeeding on a massive scale are the ones that get this right. The future of work isn’t about better AI surveillance. It’s about more human leadership.
Stop counting keystrokes. Start counting what actually matters. Your team, and your bottom line, will thank you for it.
Frequently Asked Questions
How has this view evolved over time?
My thinking on most topics has changed significantly over the years. Early in my career, I held many conventional views that experience proved wrong. I try to update my beliefs when the evidence changes.
What experience informs this perspective?
This perspective comes from over a decade of building companies in Silicon Valley, two successful exits (RemoteTeam to Gusto, MovieLaLa to Gfycat), and investing in 200+ startups including Anthropic, OpenAI, and Scale AI. I write about what I've lived.
Do all experts agree with this view?
No, and that's fine. The best ideas in business are often contrarian. I share my perspective based on my experience and data, but I encourage you to seek out opposing viewpoints and form your own conclusions.
How can I apply this thinking to my own situation?
Start by identifying the core principle behind the opinion, not the specific example. Then ask yourself: does this principle apply to my context? If yes, test it in a small, low-risk way before going all in.