Everyone is a builder now

When a natural disaster hits or a political crisis breaks out, you need to know where your employees are and reach them fast. We were paying $60,000 a year for a third-party tool to handle that. It didn’t fully work. So someone on our people team built a replacement. Using Claude Code connected to Remote’s employment data, she put it together in three hours and 17 minutes for $216. That kind of tool used to require a specialist vendor, a procurement process, and months of setup. She’s not an engineer. She just knew the problem better than anyone and had the tools to act on it. I didn’t ask her to do that. Nobody assigned it. She just built it. She’s not an exception. Over the last year I’ve watched our HR and finance teams handle significantly more volume and complexity than before, with the same number of people. That’s only possible because they work differently now. They’re not waiting for someone else to build the tools they need. They’re building the tools themselves. For most of history, “builder” was a specific job title. You were an engineer or a developer. Everyone else was a user. AI has changed that. Anyone who understands a problem can now take a real shot at solving it. To be clear: Engineers are still as valuable as they’ve always been. What’s changed is that they’re no longer the only ones who can build. That’s actually pretty new. EVERYWHERE, ALL AT ONCE According to Deloitte’s 2026 State of AI report, worker access to AI tools grew 50% in 2025 alone. The org chart that’s been standard in tech for decades, where product writes specs, design mocks it up, and engineering builds it, is changing. We’ve watched the same thing happen at Remote. We built an internal platform where anyone can build and deploy tools, and people have run with it. A localization specialist built a pipeline tool to manage content workflows across 24 languages. A product manager