The Open Source CEO: What Happens When AI Takes Over Judgment?

The short answer

No, AI cannot replace product managers, and the reason has nothing to do with whether it can write a spec. Every serious test of the question comes back to the same finding: AI is closing in fast on the tasks of the job, but the job itself is judgment under uncertainty, and that part hasn't moved.¹²

That distinction is now showing up in an unlikely place: open source repositories built as a joke.

The joke that isn't really a joke

A few weeks ago, a group of developers who'd been laid off as part of an "AI transformation" built something called Open Executive, a free multi-agent system meant to replace a company's CEO and executive team. It runs eight specialist agents, a CFO, a CHRO, a COO, a CMO, and others, backed by an LLM, styled as "turnabout is fair play."³ Within weeks it had over a thousand GitHub stars.

The premise is funny because it inverts the usual direction of the threat. Executives replace headcount with AI, so engineers build AI that can, in theory, replace the executive. But strip away the punchline and the project reveals something real about where AI capability actually sits today. Feed a model a company's numbers, and it can draft a budget, flag a hiring freeze, write a termination memo. Feeding it a strategy is different. The model doesn't know what the company is for. It has no skin in the outcome, no relationship with the customer who'll be furious, no memory of the promise made in the board meeting six months ago. It can simulate the form of judgment. It cannot originate it.

This is the same gap that shows up, task by task, when researchers actually test AI against the people whose jobs it's supposedly coming for. And the closest job to the question "who decides what gets built" isn't the CEO. It's the product manager.

What the actual tests show

The most rigorous public test of this ran blind evaluations pitting GPT-4 against real human product managers on three hard PM tasks: developing a product strategy, defining KPIs, and estimating the ROI of a feature.¹ Voters didn't know which answer was AI. The results were split, and the split tells you exactly where the line sits.

AI won or tied on defining metrics and drafting a product strategy outline, tasks with a fairly explicit internal logic. Humans won on ROI estimation for a real product launch, the task that required knowing tradeoffs nobody had written down. The most common criticism of the AI's strategy answer wasn't that it was wrong. It was that it "felt like a list of features, rather than a true strategy."¹ That's the whole argument in one sentence. AI is very good at producing the artifacts of a decision. It is not yet good at making the decision the artifacts are supposed to represent.

Product leaders and practitioners keep landing on the same split when they break the job into its component parts. A widely shared breakdown from a working PM put it plainly: AI can write boilerplate PRDs, first drafts of research summaries, backlog housekeeping, and status updates. It cannot set context, choose among imperfect options when the data is thin and the stakes are high, earn trust with a skeptical exec, or read the room in a meeting that's about to fall apart.⁴ Those two lists are not close in size, but the second list is the job.

Why this matters more than the coding question

For two years the AI-and-jobs conversation has fixated on whether AI replaces developers. That question is close to settled: AI writes a huge share of code at plenty of companies now, and the bottleneck has quietly moved.⁵ It's moved to a different question entirely: given that anyone can now generate working software in an afternoon, who decides which afternoon's worth of software was worth generating?

That's the shadow AI problem in miniature. When a marketing analyst can vibe-code an internal tool over a weekend, the code was never really the constraint. Deciding whether that tool should exist, whether it duplicates something already owned, whether it creates a compliance liability, whether it's still needed in six months, that's a judgment call, and right now most companies have no one explicitly assigned to make it. MIT's Project NANDA looked at 300 enterprise AI deployments and 150 leadership interviews and found that roughly 95% of generative AI pilots deliver no measurable P&L impact.⁶ That's not a story about model quality. Researchers found the deployments that succeed almost always had a specific person driving procurement and workflow redesign, not a general mandate to "use more AI."⁶ Judgment about scope was the difference between the 5% and the 95%.

The same failure shows up at the individual level. One product person tracked a single vibe-coded prototype at 43 hours of work to reach "demo-ready," not production-ready, at a value of roughly $6,450 of billable time, before handing it to an actual engineering team to rebuild. The tool wasn't the expensive part. Deciding what to build, and building the wrong thing fast, was.

What the PM's job actually protects against

Read enough of the debate around this and a pattern emerges: nobody serious argues AI has no effect on product management. The argument is about which half of the job it touches. Reforge's research on how AI is changing the discipline lands on a version of this that most practitioners now accept: the tasks change, the role's center of gravity does not.²

What survives on the human side isn't mystical. It's accountability with consequences attached. Someone has to be the person a customer can be angry at, the person who tells an exec no and keeps their job, the person whose name is on the roadmap when it's wrong. An AI agent has no consequence to absorb. It can be swapped, retrained, or deleted with no cost to itself. That asymmetry is the actual moat, and it's also the reason the Open Executive joke lands: replacing a CEO with a model is funny precisely because everyone senses the model has nothing at stake.

The practical shift already happening

What's changing isn't the existence of the PM role. It's the shape of a good one. The routine share of the job, drafting, summarizing, formatting, generating first-cut KPI trees, is being absorbed fast, and PMs who resist that are burning hours an AI would do for pennies. What's left over, and what's becoming scarcer and more valuable, is exactly the judgment work: deciding what problem is actually worth solving before anyone writes a line of prompt. That's also the skill this publication keeps returning to under a different name: knowing what software your org should own outright versus rent from a vendor is the same judgment call as knowing what to build in the first place. Neither is a task an agent can be handed. Both require someone willing to be wrong in public.

The developers who built Open Executive as a prank were making a point about power, not capability. But the honest version of their prank isn't that AI can run a company. It's that AI can run the parts of a company that were already reducible to a checklist. The parts that were never a checklist, the calls made with incomplete information and a career on the line, are still waiting for a human to make them. That's true whether the title on the door says CEO or product manager.