Frameworks, core principles and top case studies for SaaS pricing, learnt and refined over 28+ years of SaaS-monetization experience.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
.png)
Devin sells to three groups, and the groups themselves are sound. First are curious developers or small teams who want to test whether autonomous coding works for them. Second are scaling teams who want more engineering capacity without hiring. Third are large enterprises rolling Devin out across many teams.
Each group needs something different. The first needs enough room to run a real test on actual tickets, not a toy demo. The second needs Devin handling daily work (bugs, small features, tests, migrations) wired into their existing pipeline. The third needs custom deployment, security, volume, and support.
Devin’s packages are Core, Team, and Enterprise, and the problem is the fit. Core includes about 9 ACUs (Agent Compute Units), which is enough for only a handful of tasks. But the first group’s whole goal is to evaluate Devin, and you cannot judge it in three or four tries. By the time someone burns through Core, they have barely started, and the next plan is a 25x jump.
Team does serve the second group’s need for steady daily use. But there is a real group stuck in the middle: small teams of three to ten engineers, or serious solo users, who run Devin on a few tickets a week. They are past testing but nowhere near a full team deployment. Devin has no plan for them.
Cognition may have done this on purpose, using Core as a free sample to push serious users toward Team. But if that middle group is left unserved, rivals who do package for it (Claude Code, Copilot’s agent mode, Windsurf) will pick those users up.
Join companies like Zoom, DocuSign, and Twilio using our systematic pricing approach to increase revenue by 12-40% year-over-year.