The account list for the next program
How Northwind Demand and Atlas regional sales will reach the buying committees at the selected accounts in the next program. It carries forward the 10 accounts selected this quarter and the one shared buying committee model Kira approved on Aug 27. Reflects research dated through Sep 19, 2026.
- Selected accounts
- 10: 6 supported, 4 returned to Atlas
- Initiative
- Cloud migration
- Sales owners
- Atlas regional owners under Rosa Delgado
- Program director
- Ben Ortiz, Northwind
- Current stage
- Proposal shared Sep 24
- Decision
- Oct 16, 2026
Why these accounts
Source linked research supports a cloud migration initiative at 6 of the 10 accounts, and sales accepted 6 cloud migration briefs this quarter, more than any other initiative. The other 4 accounts have one or two sources, the newest from June to August, so we returned them to you rather than write outreach on thin evidence.
| Returned account | Linked sources | Newest source | What we need from Atlas |
|---|---|---|---|
| Manufacturer | 1 | Jul 22 | Is a cloud program active? Keep or replace |
| Software vendor | 2 | Aug 5 | Confirm the initiative with the regional owner |
| City government | 1 | Jun 30 | Keep only if procurement timing fits H1 2027 |
| Telecom operator | 2 | Aug 19 | Confirm the initiative with the regional owner |
Buying committee, by role
- Security architectTechnical reviewer
Joined earlier than the plan assumed at 5 of 6 interviewed accounts.
- Cloud platform leadTechnical evaluator
Owns the migration timeline and the integration questions.
- CISO or security directorEconomic owner
Signs off on risk and budget for the security stack.
- Procurement and riskFinal terms
Enters at the end. Needs the security questionnaire early.
Messaging by role
| Role | What they care about | Message | Proof to use |
|---|---|---|---|
| Security architect | Control and visibility during the move | Atlas keeps policy and audit consistent across old and new environments | Technical webinar, Dec 10, and a reference architecture note |
| Cloud platform lead | Integration effort and timeline | Works with the current cloud tooling, no parallel stack | Solutions engineer session booked by the regional owner |
| CISO or security director | Risk reduced per dollar | One consistent control set through the migration | Account brief with the dated sources, reviewed by sales |
| Procurement and risk | A clean security review | Questionnaire answers ready before they ask | Atlas standard security pack |
Engagement sequence
| Step | Role | Action | Owner | Status |
|---|---|---|---|---|
| 1 | All roles | Account brief accepted by the regional sales owner | Ben Ortiz | Done at 6 accounts |
| 2 | Security architect | Track 2 content: reviewer questions first | Talia Green | In the proposal |
| 3 | Security architect, cloud platform lead | Invite to the Dec 10 webinar, consent based | Talia Green | Planned |
| 4 | CISO or security director | Sales led briefing with the brief and research | Atlas regional owner | Planned |
| 5 | Full committee | Follow up task within 5 business days of any request | Atlas regional owner | Pilot measures this |
Next steps
Before the Oct 16 decision
- Six briefs approved and accepted by salesdone
- Shared buying committee model approveddone
- Qualify or replace the 4 returned accounts (Kira, Sep 30)open
- Refresh stale sources before outreach wording is approvedopen
- Name a regional owner for every account before kickoffopen