Factory Doubling Revenue Month over Month

This kind of growth signals that Factory was not selling a simple coding copilot, it was landing as a new budget line for automated software delivery. The jump from $5M annualized revenue at the end of 2025 to $60M by March 2026 lines up with a product that can take real work off engineering teams, from bug fixes and migrations to testing, review, and incidents, and then expand quickly inside large enterprises once one team proves it works.1

• Factory’s Droids do more than suggest code. They explore repositories, make plans, edit files, run tests, inspect failures, and submit pull requests. That makes monetization closer to paying for completed engineering work than paying for seats in an editor, which helps explain why usage can compound faster than headcount growth.1
• The company’s enterprise motion appears to have stacked bottom up adoption with top down rollout. In April 2026 it cited daily use by hundreds of thousands of developers at firms like NVIDIA, Adobe, EY, Palo Alto Networks, and Adyen, and by September 2026 EY and Royal Bank of Canada had moved to broader internal deployments.1
• Comparable platforms show why this pace mattered strategically. Blitzy sold autonomous code delivery into large enterprises with contracts starting around $500K annually, while Factory positioned more broadly across coding, QA, security review, and incidents. In practice, that widens the spend pool from developer tooling into software transformation and operations budgets.3

The next phase is likely less about proving developer demand and more about turning isolated wins into an enterprise control plane for autonomous work. If Factory keeps expanding from code generation into review, testing, security, and non engineering workflows, revenue growth should increasingly come from company wide standardization rather than from individual developers experimenting with agents.1