Sep 07, 2026 · Tech Lead Journal · 5 min read

Kilo Code Acquisition and AI Engineering Strategy

Kilo Code co-founder Emily Shario discusses the strategic acquisition by Anaconda, the shift from code generation to review, and the new metric of spend per merged pull request. This analysis covers how AI-native organizations leverage agentic workflows to optimize ROI and redefine engineering leadership.

Technology Business Strategy Software Engineering

The takeaways

Spend per merged PR is key. Shift focus from raw AI spend to cost per merged pull request to accurately measure customer value and ROI. This metric aligns engineering output with business impact rather than just volume of code generated.
Engineers become agent team leads. Reframe the engineer role from individual contributor to manager of an agent team. This accelerates the transition to tech lead responsibilities and optimizes human oversight of automated workflows.
Discovery moves to post-ship testing. Leverage low-cost AI generation to ship features rapidly and validate them in production. Use real user adoption data to decide which features to keep or revert, replacing expensive pre-ship discovery.
Model agnosticism drives cost efficiency. Adopt model-agnostic platforms to route tasks to the most cost-effective models. This prevents vendor lock-in and allows dynamic optimization of inference costs based on specific task complexity.
Human judgment remains non-negotiable. Maintain strict human oversight for architecture, security, and billing logic. Do not outsource critical thinking to AI agents, ensuring that high-risk decisions remain under human control.
Automate code review with agents. Implement AI agents as first-pass reviewers to manage the increased volume of generated code. Use multi-agent review councils for high-risk changes to mitigate cognitive load and ensure quality.

Strategic Acquisition and Market Positioning

Kilo Code’s acquisition by Anaconda represents a pivotal consolidation in the AI engineering tooling market. By integrating Kilo’s agentic coding platform with Anaconda’s 50-million-user ecosystem, the combined entity targets the Fortune 500 with a secure, managed environment for AI-driven development. This move signals a shift from standalone developer tools to enterprise-grade infrastructure, emphasizing security and governance as primary differentiators. The acquisition validates the market demand for model-agnostic solutions that allow enterprises to optimize costs across multiple AI providers without vendor lock-in.

Redefining Engineering Metrics and ROI

A critical strategic shift identified is the move away from raw spend metrics toward "spend per merged pull request." This metric directly correlates AI investment with customer value delivery, providing CFOs and engineering leaders with a clear ROI framework. As AI lowers the cost of code generation, the bottleneck shifts from production to validation and integration. Organizations must now measure the efficiency of their review and deployment pipelines, not just the speed of code creation. This metric encourages a culture of high-impact, low-waste engineering where every dollar spent on AI must translate into shipped, valuable features.

The Evolution of the Engineer’s Role

The engineer’s role is transitioning from code generator to agent manager. Senior engineers are best positioned for this shift, as their existing skills in code review, architecture, and team leadership translate directly to managing autonomous agents. This evolution requires a new competency set focused on prompt engineering, agent orchestration, and rigorous review. Organizations must invest in training engineers to oversee agent teams, recognizing that human judgment remains essential for high-stakes decisions like security and billing. The "don't outsource your thinking" principle underscores the need for intentional human oversight in AI-native workflows.

Operational Implications for AI-Native Organizations

AI-native organizations are redefining discovery and development cycles. With the cost of prototyping near zero, teams are shipping features faster and relying on production data to validate value. This "ship and test" approach requires robust metrics infrastructure to track adoption and user feedback. Additionally, the rise of agentic workflows in non-engineering roles, such as marketing and operations, indicates a broader organizational shift. Knowledge workers are delegating routine tasks to agents, freeing up time for strategic thinking. Companies that fail to adapt their processes and metrics to this new reality risk falling behind in both speed and efficiency.

Key insights

The primary metric for AI engineering ROI is shifting from total spend to spend per merged pull request. This aligns AI investment with actual customer value delivery rather than code volume.

Financial Metrics →

Impact: Enables engineering leaders to justify AI budgets to finance teams by demonstrating direct correlation between spend and shipped value.
Engineers are evolving from individual contributors to managers of agent teams, accelerating the path to technical leadership. This role change emphasizes review and architecture over manual coding.

Workforce Strategy →

Impact: Requires new training programs and performance metrics to evaluate engineers based on their ability to orchestrate and review agent output.
Model-agnostic platforms are becoming essential for cost optimization, allowing teams to route tasks to the most efficient models. This reduces dependency on single vendors and lowers inference costs.

Technology Strategy →

Impact: Provides enterprises with greater control over AI spend and flexibility to adapt to rapid changes in the model landscape.
The discovery phase is moving from pre-ship research to post-ship production testing. Low-cost AI generation enables rapid prototyping, with real user data determining feature retention.

Product Development →

Impact: Accelerates time-to-market but requires robust analytics and feedback loops to avoid accumulating technical debt from unvalidated features.
Human judgment remains critical for high-risk areas like security and billing, necessitating a "don't outsource your thinking" approach. AI agents handle routine tasks, while humans focus on strategic oversight.

Risk Management →

Impact: Mitigates the risk of AI-generated errors in critical systems by maintaining clear boundaries for human decision-making.

Action items

Implement a tracking system to calculate spend per merged pull request for all AI-assisted development tasks. Use this metric to evaluate the ROI of AI tools and optimize budget allocation.

Impact: Provides a clear, defensible metric for AI investment that aligns engineering output with business value.
Train senior engineers to manage agent teams by focusing on prompt engineering, agent orchestration, and code review. Update job descriptions and performance criteria to reflect this new role.

Impact: Accelerates the transition to AI-native workflows and leverages existing leadership skills for agent management.
Adopt a model-agnostic AI platform to enable dynamic routing of tasks to cost-efficient models. Establish partnerships with multiple model providers to ensure flexibility and cost control.

Impact: Reduces inference costs and mitigates vendor lock-in risks, allowing for better optimization of AI spend.
Shift product discovery to post-ship testing by shipping features rapidly and using production data to validate value. Implement robust analytics to track adoption and user feedback for each feature.

Impact: Accelerates innovation cycles and ensures that only high-value features are retained, reducing technical debt.
Establish clear guidelines for human oversight in high-risk areas such as security, billing, and architecture. Require human review for all changes in these domains, regardless of AI agent recommendations.

Impact: Mitigates the risk of AI-generated errors in critical systems and maintains compliance with security and regulatory standards.

Quotes

“I think the number one rule, and if people only take this from the conversation, let it be this, is don't outsource your thinking.”

“A metric that I don't think we've circled around as an industry quite yet, but I do think we're going to see people push more and more is going to be spend per merged pull request.”

“The human role has changed from generation to reviewer.”