Own the priorities
Decide what matters and accept what ships. In a developers model, your engineering manager also directs the day-to-day work.
Usually 4 to 6 weeks, most of it the 10 to 15 business days between signature and the first day. Here is every step, who does it, and what you get.
Day 1 · 30 minutes
What you need built, the team you have, your timeline and your budget. We tell you whether a managed team or developers in your team fits, or whether to start with a two-week Blueprint because nothing is written down yet.
Week 1
For a managed team: the people, the first milestones and the fixed monthly price. For developers in your team: profiles of engineers who fit the role, each with the scorecard from their recorded technical session.
Weeks 1-2
You meet the tech lead and every engineer before anyone starts. If someone isn't right, we send another profile.
Week 2
A mutual NDA, one master services agreement, and one statement of work per team or developer, naming the people, rates, start date, term and reporting. The first month is paid before the start.
10-15 business days after signature
Accounts you create in your repositories, ticket tracker and chat. The tech lead runs a kickoff, agrees the first sprint's goal with you, and the team starts.
Every two weeks, every month
A sprint review and a written sprint report every two weeks: shipped, next, risks and metrics. Every month, an engineering health report and the invoice. At day 90 the initial term ends and notice periods apply.
| What | How often | What it contains |
|---|---|---|
| Standup | Daily, in your hours | Progress and blockers, in your chat or call |
| Sprint review | Every two weeks | A demo of what shipped, and the next sprint's goal |
| Sprint report | Every two weeks | Shipped, next, risks, and the metrics behind them |
| Engineering health report | Monthly | Lead time, deploy frequency, change-failure rate, escaped defects and tests on critical paths, signed off by our founder |
Developers in your team follow your own rituals and report to your engineering manager.
Decide what matters and accept what ships. In a developers model, your engineering manager also directs the day-to-day work.
In a managed team: the plan, the engineers, code review, quality and releases, and your daily contact.
Reviews every engineer before they are presented, each team's launch plan, sampled pull requests on sensitive changes, the monthly health reports and every serious incident review.
Our hub is Panama City, on UTC-5 all year (no daylight saving): US Eastern time in winter and US Central in summer. Engineers work US business hours.
Engineers start 10-15 business days after signature. From a first call to day one usually takes 4 to 6 weeks: a plan or profiles, your interviews, the contract, then the start date.
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.
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 mutual NDA, one master services agreement, and one statement of work per team or developer. The first month is paid before the start; after that, invoices are monthly in advance, net 15, in USD. Rates are locked for 12 months, then rise with CPI, capped at 4% a year.
Bring the work you have in mind. We'll tell you which model fits and what it costs.