The case for killing the process
Software teams spend more time on process than product. We think agents can fix that.
The average software engineer spends less than 40% of their time writing code. The rest goes to meetings, ticket management, code review, deployment coordination, and documentation. We think that ratio is backwards.
The process tax
Every team we've talked to has the same complaint: too much process, not enough building. Standups, sprint planning, grooming, retros, design reviews, architecture reviews, security reviews. Each one exists for a reason. Together, they consume most of the week.
The agent opportunity
AI agents can handle process. They can generate PRDs from briefs, plan sprints from backlogs, review code with reasoning, run test suites, and manage deployments. Not someday — today.
What changes
When agents handle process, engineers focus on the work that actually requires human judgment: product decisions, architecture trade-offs, user experience, and the creative aspects of building software that no model can replicate.
The name
kill9 is the Unix signal for immediate, unconditional termination. SIGKILL. It's what you send when a process won't die gracefully. We chose it because that's what we're doing to the overhead that kills engineering velocity.