Start
Question 1 of 4
Does this customer have any presence on AWS?
Even a small footprint counts — dev environments, a single workload, any active AWS account.
Question 2 of 4
What's the situation with AWS adoption?
Are they heading toward AWS on their own terms, under external pressure, or not interested at all?
Question 2 of 4
What's their approximate monthly AWS spend?
~$40K/mo is the threshold where cost optimization conversations become most impactful.
Question 3 of 4
Is there any migration conversation happening?
Looking to expand their AWS footprint, exit a datacenter, or move off VMware — even at a smaller scale?
Question 3 of 4
Any active migration conversation alongside the AWS spend?
Are they also looking to move workloads, exit a datacenter, or get off VMware — or is this purely an existing AWS environment?
Question 3 of 4
What's the primary migration driver?
Cost optimization lead
Good candidate — introduce Mission Cloud's FinOps team
Significant AWS spend with no active migration — strong cost optimization play. Mission Cloud's FinOps team finds savings fast, often identifying $100K+ in unoptimized spend at this level.
To:[customer contact]
CC:srys@missioncloud.com
Subject:Introducing Mission Cloud — AWS cost optimization
[Name], Wanted to make a quick introduction. Sky Rys is an account executive at Mission Cloud — CDW's dedicated AWS practice — and I think it's worth a conversation. Mission Cloud specializes in helping financial services companies get more out of their AWS environments. One thing they do really well is find cost savings that teams don't have the bandwidth to track down themselves — they've helped FSI customers save hundreds of thousands of dollars on AWS without disrupting anything in production. Sky can walk you through what that looks like and whether there's an opportunity. I'll let you two take it from here. [Your name]
Copied!
VMware migration lead
Strong candidate — AWS-funded assessment can change the economics
VMware renewal events create hard deadlines. Mission Cloud has executed multiple VMware exits — including mapping 4,000+ app dependencies for a major mortgage company — and AWS MAP funding can reduce out-of-pocket cost dramatically.
To:[customer contact]
CC:srys@missioncloud.com
Subject:Introducing Mission Cloud — AWS migration
[Name], Wanted to introduce you to Sky Rys, an account executive at Mission Cloud — CDW's dedicated AWS practice. Mission Cloud works with a lot of financial services companies navigating VMware decisions, and one thing that tends to change the conversation is their AWS-funded migration assessment. It maps your full environment — dependencies, costs, target architecture — before you commit to anything. In some engagements, AWS funding has covered the majority of the project cost. Given what's likely on your plate around VMware, I thought it was worth a conversation. Sky can tell you more about what that process looks like. [Your name]
Copied!
Migration lead
Good candidate — introduce Mission Cloud's AWS-funded assessment
Datacenter exits, legacy hosting migrations, and planned AWS adoptions are Mission Cloud's core motion. An AWS-funded MAP Assessment maps every dependency and de-risks the full migration before the customer commits.
To:[customer contact]
CC:srys@missioncloud.com
Subject:Introducing Mission Cloud — AWS migration
[Name], Wanted to introduce you to Sky Rys, an account executive at Mission Cloud — CDW's dedicated AWS practice. Mission Cloud helps financial services companies move to AWS, and they have a process that takes a lot of the risk out of the decision. They offer an AWS-funded migration assessment that produces a full dependency map, cost model, and migration plan before you commit to anything — so you understand the full picture before any work begins. They've done this across insurance, banking, lending, and fintech — and the AWS funding often covers a significant portion of the engagement cost. Worth a quick conversation with Sky to see how it applies to your situation. [Your name]
Copied!
Warm but early
Smaller footprint — keep warm, share FSI materials
Promising profile but spend isn't at a level where a full introduction makes sense yet. Keep the relationship warm and plant the seed for when their AWS usage grows.
To:[customer contact]
Subject:A resource for your AWS environment — Mission Cloud
[Name], Wanted to share a quick resource. Mission Cloud is CDW's dedicated AWS practice, and they do a lot of work specifically in financial services — compliance-ready environments, cost optimization, migrations, and AI on AWS. As your AWS footprint grows, they're worth knowing. More about their FSI work here: https://www.missioncloud.com/industry/finance Happy to make a formal introduction when the timing makes sense. [Your name]
Copied!
Not a fit — no follow-up
No signal, no forcing event, no plan — move on
No AWS presence, no migration pressure, no expressed interest. Not worth pursuing right now. No email, no intro — save the time for customers where there's a real signal.