Key Takeaways

  • Quinn Slack split Sourcegraph into two separate entities, moving 20 people to AMP while leaving the remaining team on core code search.
  • Every Sourcegraph investor and employee received equity in both companies, mirroring David Sacks spinning Yammer out of Geni in 2009.
  • AI agents eliminate the need to hire specialized support staff, allowing teams to hire only people with high agency and broad skills.
  • Hiring dedicated product managers and marketing staff too early creates an overhead trap where 90% of headcount manages internal coordination.

The Return of the 20-Person SWAT Team

Most founders believe scaling means adding headcount. Quinn Slack did the opposite. After building Sourcegraph into a 200-person company, he orchestrated a clean split: a tight group of 20 people left to build AMP, while the rest stayed on the core code search product.

“We decided along with the board and my co-founder Bang where we had these two products in Sourcegraph,” Slack explained. “We had the code search product and we had AMP, and we decided to spin off, which has not been done really in startups and software since David Sacks spun off Yammer from Geni in like 2009.”

To make the split fair, Slack ensured that every existing investor and employee received shares in both entities. That structure gave the new company a clean cap table while protecting everyone who helped build the original business.

The Death of the Middle-Management Tax

Large engineering teams spend most of their week talking to each other. Once an organization passes 50 or 100 people, founders start hiring project managers, product managers, and internal coordinators just to route information between silos.

Slack stepped down from running a 200-person company because the coordination tax drained his energy. In a 20-person team, every engineer talks directly to customers, writes code, and deploys updates.

“I don't think I was nearly as good at being CEO of a 200-person company, and I get a lot more energy from this,” Slack noted. “Now we have this team of 20 people where everyone can be trusted with everything.”

When every person on the team possesses high agency, you do not need intermediate managers to translate requirements. You need builders who can talk to users in the morning, fix the bug by lunch, and ship the feature before dinner.

Why Agents Kill Traditional Hiring Plans

The standard startup playbook says that as soon as you find product-market fit, you should hire specialized marketers, dedicated QA engineers, and junior PMs. Slack argues that AI agents make that entire hiring sequence obsolete.

“Compared to a few years ago, you do not have the need to go and hire people that you do not trust have high agency or the right skills, because you can use an agent to do those things,” Slack said. “I see some other companies that are around our size starting to go hire a PM or a marketer, and that just feels like the old way of building a software business. Ultimately that's going to lead to something where 10% of the people are thinking about how to make a great product and the other 90% are thinking about the overhead.”

Agents handle the mechanical work that junior staff used to do: summarizing customer calls, drafting initial documentation, running test suites, and formatting release notes. If a task does not require exceptional judgment, give it to an agent instead of opening a job requisition.

What to Do With This

Audit your hiring pipeline this week. Take every open non-engineering role on your board (junior marketing generalists, project managers, and product operations) and test whether an automated AI workflow can do 70% of the job. If it can, cancel the requisition and assign the remaining judgment calls directly to a high-agency engineer.