Works with your people
In your Slack or Teams, at your standups and planning, in your hours. One person who knows your product and answers for the team.
A team that works only on your software: our tech lead, senior engineers and QA, working US hours. You own the priorities; we own delivery. From $29,500 / month.
The difference between a managed team and a set of contractors is the tech lead. This is the job.
In your Slack or Teams, at your standups and planning, in your hours. One person who knows your product and answers for the team.
You decide what matters. The tech lead breaks it into work the team can ship in two-week sprints and tells you early when something won't fit.
Code review on every pull request, QA inside the sprint, and releases with a way back. Quality is the team's job, not yours.
Assigns the work, unblocks it, coaches, and handles replacements without a gap in delivery. Nobody on your side has to manage developers.
A sprint report: what shipped, what's next, risks, and the numbers behind them. Every month, an engineering health report signed off by our founder.
Our founder samples each team's pull requests, always including changes to money movement, authentication, data migrations and production infrastructure.
Per month, full-time (about 160 hours per person), billed monthly in advance in USD.
One product area, a portal or a new workstream.
$29,500 / month
Ask for the team sheetA roadmap line that needs steady output every sprint.
$44,500 / month
Ask for the team sheetSeveral workstreams, or a platform with many integrations.
$67,500 / month
Ask for the team sheet| Add to a managed team | Monthly price |
|---|---|
| Senior engineer | $10,900 / month |
| Mid-level engineer | $8,000 / month |
A managed team costs about 17% more than the same people as developers in your team. That pays for the tech lead's time with you, QA in every sprint, replacements without gaps, reporting and our founder's review. All prices are on the pricing page.
Founding clients. Our first 3 clients get 10% off for their first 6 months, in exchange for a public reference. The discount starts once the reference is delivered: a short case study published, your logo approved, and an occasional reference call.
| Compared on | Managed team | Developers in your team |
|---|---|---|
| Who directs the work | Our tech lead, from your priorities | Your engineering manager |
| Who owns delivery quality | Atom | You (we vet and replace) |
| Best when | Nobody on your side has time to run the work, or it is a new workstream | A strong engineering manager owns the backlog |
| Priced | Per team, per month | Per developer, per month |
For managed teams, yes. Sprint goals are agreed in writing at kickoff. If we don't deliver the first sprint's goals, you don't pay for that sprint. Developers in your team have a trial instead: if you end it within the first 10 business days, you pay nothing for that engineer.
In a managed team, our tech lead: every day in your Slack or Teams, in standups and in sprint reviews. Developers in your team report to your engineering manager like the rest of your team. For anything about the engagement itself, such as people, invoices or changes, you have one named contact at Atom.
A managed team costs about 17% more than the same people as developers in your team. That pays for the tech lead's time with you, QA inside every sprint, replacements without gaps, sprint and monthly reporting, and our founder's review of the work.
We replace them within 10 business days at no cost, and we don't bill for the gap. Work stays in your repositories and tickets, so nothing leaves with them. In a managed team, the tech lead keeps the work moving and hands it over to the new engineer.
A 3-month initial term. After that, a developer in your team needs 30 days' notice. A managed team needs 30 days' notice to remove one person and 60 days' notice to end the team.
You do, once it is paid for. Every engineer signs a confidentiality and IP assignment agreement with Atom before getting any access, and Atom assigns the work to you on payment. The work happens in your own repositories and accounts from day one.
Yes, where your policy allows it, and under the same code review as any other change. We tell you which tools would touch your code or data, and where your policy says no, they don't.
Tell us the work. We'll send the team plan, the monthly price and a sample sprint report, then you meet the tech lead.