Most outsourcing companies put a project manager between you and the developer. We don't. The standard explanation is "AI replaces what PMs used to do." That's true, but it's the surface answer.
The real reason is older and harder to admit.
The PM role exists because of an assumption baked into how we build software: developers are resources to be coordinated, not people who create value. You hand requirements to the PM. The PM breaks them into tickets. The developer executes. The system rewards predictability and execution, not judgment.
This isn't dishonest. It worked for decades. When a project needs 15 people for 3 months, somebody has to coordinate dependencies, manage scope, and translate between the client and the engineers. The PM filled that gap.
But it came with a cost. The developer never sees the client. Never understands why the feature matters. Never has to make a trade-off between speed and quality, because someone else already made it. The developer becomes a tool — an efficient one, but a tool.
Many developers prefer this. The PM handles business context. The developer focuses on code. It feels efficient. In high-volume body-shop outsourcing models, this preference is deeply embedded. It's not the developers' fault. The system rewards it.
But the cost is real. The developer never grows into someone who can make business judgments. The client never gets the developer's actual thinking — only what the PM filtered. And when something is wrong with the requirements, nobody catches it until it's expensive.
How AI changed the equation
A senior developer with the right tools can now do what used to require three roles: understand business context, write user stories, design architecture, ship code, and talk to the client directly. When one person can hold the full picture, the PM stops being a bridge and starts being a wall.
What we built at Core70
Our developers talk to your decision-makers directly. They understand your business priorities. They make product calls. They tell you when something isn't worth building — because they own the budget with you, not for you.
Account Owners handle commercial matters: contract health, scaling decisions, escalations. They don't gatekeep technical conversations.
We don't filter who works this way. Developers self-select. Some prefer the old model — fewer decisions, less ambiguity. They stay at traditional teams. Others want to participate in business decisions, learn from clients, build judgment. Those are the ones who come to us, and they earn more for it.
A note on Scrum Masters
A real Scrum Master is different from a PM. A good one serves the team — removes obstacles, protects rhythm, and observes more than directs. Like a good coach, they don't tell players how to play. They create conditions for players to figure it out themselves. That role has value. The PM-as-translator role doesn't.
The trade-offs are real
This model demands more from developers, and not everyone wants it. Clients who need three layers of procurement and two departmental reviews don't fit — there's no PM to manage that ceremony. We're slower to scale because we don't onboard developers who can't handle direct client contact.
The deeper question isn't whether AI replaces PMs. It's whether we still want to organize software development around the assumption that developers are resources.
We don't. That's why our structure looks the way it does.