Who actually signs
At a company between two hundred and two thousand people, the signer is the VP of data, the chief data officer, or the CTO, and increasingly the CFO when the driver is the cost of the legacy platform. The champion is the analytics engineering lead who has been living with the old warehouse and has already built the case internally. The person who can stop it is the infrastructure lead who owns the legacy system and its contract.
The buying reason is usually one of three: a new data leader with a mandate, a legacy contract renewal with a number on it, or an AI initiative that the current platform cannot serve. All three are visible from outside.
The one sentence version
Your buyer is a data leader in their first quarter, with a legacy renewal or an AI mandate forcing a platform decision, and a team that can do the migration in eighteen months alongside everything else.
The triggers, and where each one is visible
- Job posts naming the target stack. A posting for an engineer with experience on one of the cloud data platforms, at a company whose other postings still name a legacy warehouse, is a migration that has been decided and not yet started. The boards show both, and the combination is the signal.
- New data leaders. A VP of data, chief data officer or head of analytics arriving at a company is a platform decision inside a quarter. Job change alerts surface it the week it happens.
- Legacy platform end of life and renewal cycles. On premises appliances, older distributed processing platforms and long term licence agreements all have dates. A company on a platform that has announced end of support is on a clock, and the platform's own announcements tell you which companies are on it.
- Funding and acquisitions. A round funds the data team. An acquisition creates two warehouses that have to become one, and the integration is a migration by another name.
- AI initiatives announced. A company describing an AI product or an AI strategy in its investor update has a data platform question underneath it, because the models need data the legacy warehouse was not built to serve.
- Platform vendor partner announcements and case studies. When a vendor publishes a customer story, that customer has already migrated. Its competitors have not, and they read the same story.
- Open table format and lakehouse adoption. Companies announcing a move to open formats are re-platforming, and the announcement usually names the target.
The job posts and the new leaders are the two to build on. One tells you the decision has been made. The other tells you who is about to make it.
Qualify in sixty seconds
- Is there a legacy platform to leave? Job posts, technology detection tools and engineer profiles show what the company runs. A company already on a modern platform is a different engagement about cost or modeling, not a migration.
- Is there a data team of more than three? Below that, the company will not run a migration and may not need a warehouse. Above twenty, they may run it themselves with your team on the hard parts.
- Is there a leadership change or a contract date? Either sets the clock. Neither means the decision is a year away.
- Are you a partner of the target platform? If the company has chosen a platform you do not partner with, the vendor's program will route the deal elsewhere, and the honest move is to say so.
The angle that gets replies
Lead with the decision they are about to make and the mistake most companies make inside it. The reader knows they are migrating. What they do not know is which order to do it in and what the pricing model change will do to their bill in month four.
Three openers you can adapt
- On a new VP of data"Congratulations on the role. Most data leaders make the platform call in the first ninety days, and the decision that matters more than which platform is what to move first, because moving the reporting layer before the models are rebuilt is how migrations stall in month six. One page on the sequencing we use, attached to nothing."
- On a job post naming the new stack with the old one still in the requirements"Your analytics engineer posting asks for the new platform and still lists the legacy warehouse. That usually means the migration is decided and the team is being built to run it. The thing that catches teams at that stage is the shift from licence to consumption pricing, which rewrites the cost model in ways the business case did not. Happy to send the three controls we put in before the first workload moves."
- On an acquisition"Congratulations on the acquisition. Two warehouses becoming one is a migration with a deadline, and the deadline is usually the first combined board report. The decision to make in the first month is whether the target platform is either of the current ones or neither, and it is cheaper to make it now than after the first quarter of duplicate pipelines. Two paragraphs on how we frame it, attached."
Each one names the decision, names the mistake, and offers the framing. That is what a migration partner is for.
What not to send
- "Modern data stack" as the pitch. It is a category name, not a finding about their situation, and it identifies you as someone who has read the same blog posts they have.
- Vendor award language. "Partner of the year" is a credential the vendor gave you. The reader wants to know what you did for a company like theirs.
- A capabilities list of platforms and tools. Naming what you can migrate to is a menu. Naming what they are migrating from is a conversation.
- A generic cloud data platform services email that could go to any company. If it does not name their source system, it does not know who it is talking to.
The objection you will hit
We will use the platform vendor's professional services. The vendor's services move workloads to the vendor's platform, well, and at a rate that assumes an enterprise budget. They do not redesign the models, they do not own the source system's retirement, and they are not incentivized to reduce consumption. A partner is, and the vendor's own migration funding usually flows through partners. Say all three.
The second is our team can do it. They can, in eighteen months, alongside their day jobs, learning the platform's cost model by getting the bill. The question is what the business needs the data for during those eighteen months, and whether the team's time is better spent on that.
The third is we are not ready to decide on a platform. Then the assessment is the engagement: an inventory of the current workloads, a cost model on each candidate, and a sequencing plan that is the same regardless of the platform chosen. It is small, and it makes the decision easier, which is why they say yes to it.
Deal shape
- Migration assessment, including workload inventory, cost model and sequencing plan: commonly $15K to $50K, and the engagement that opens most relationships.
- Migration execution: $150K to well past $1M depending on the size of the estate, often partly offset by the platform vendor's migration funding.
- Ongoing platform engineering retainer: $10K to $40K a month, and the reason a client acquired at the assessment is a client for years.
- Cost optimization on an existing modern platform: $25K to $75K, and a second door into companies that have already migrated badly.
- Signer: VP Data, CDO, CTO or CFO. Champion: the analytics engineering lead. Cycle: one to four months from first contact to a signed assessment.
The assessment is the funnel. It is priced so a data leader signs it in their first quarter, it produces the sequencing plan and the cost model, and those two documents are the migration.
A cadence you can actually run
- Weekly, pull job posts naming the target platforms, and cross reference each company's other postings for the legacy system.
- Weekly, run the job change alert for data leadership titles and write inside sixty days of the start date.
- Monthly, pull funding, acquisitions and AI initiative announcements at companies with a data team.
- Quarterly, review the legacy platform end of support calendar and the companies known to be on each.
- Qualify against the four checks, with the partner status question first. One message per account, naming the decision and the mistake. Twenty accounts a week is a full program.
- Three touches over two weeks, then stop. The next leadership change or the next renewal date is a fresh reason to write.
The company posts the decision on its own job board and the new leader posts it on their own profile. The consultancies that grow are the ones writing inside the first ninety days.
The sending mechanics most people get wrong
Everything above is about who and what. This is about how, and it is where most outbound in this niche quietly dies. Seven rules. None of them are optional.
1.Three to five sentences. That is the whole email.
Your reader is on a phone between meetings. One observable fact about their company, one consequence they have not thought about, one specific thing you would do. Anything past five sentences is a memo, and memos get archived unread.
2.Lead with a technical differentiator that turns into a number.
The messages that work best name something concrete you do differently and translate it into time or money saved. In this niche the differentiator is the cost model. A consultancy that can say what its last dozen migrations cost the client per month on the new platform against the business case, and how many came in under it, has the number a CFO signs on. The second is sequencing: state how many migrations you have run without a stall, and what you move first.
Most services firms do not have a technical differentiator, and pretending to have one reads as exactly that. The substitute is a verticalized case study: a company like theirs, what you did, what happened, in one sentence. For this niche the line is: a 900 person insurance services company, new VP of data in March, assessment in four weeks, models rebuilt before the reporting layer moved, legacy appliance retired eight months after kickoff, monthly platform spend within the business case in month twelve, vendor migration funding covering a third of the fee. The month count and the spend against plan are what the reader will check.
3.Ten to twenty emails a day per mailbox. Not a hundred.
Sender reputation is scored per mailbox and per sending domain. One inbox pushing a hundred cold emails a day looks like exactly what it is, and the penalty lands on the domain, which means it lands on your client correspondence too.
If the math says you need more volume, the answer is more mailboxes on more warmed sending domains, separate from the domain you invoice from. It is never more volume per mailbox. Twenty accounts a week at three touches is about twelve emails a day, one warmed mailbox. Leadership changes cluster in January and September, and those are the months for the second mailbox.
4.Write ten versions of every step and test them.
Versions A through J, not A and B. Rotate subject lines and bodies. You learn which angle is actually working instead of guessing, and there is a second reason that matters more: identical bodies going out over and over is one of the patterns postmaster tools flag. Variation is a deliverability tool as much as a testing one.
Subject line seeds for this niche, each of which should become several variants: "your first ninety days", "the posting that names both platforms", "two warehouses after the acquisition". Lower case, no punctuation tricks, and nothing that would look odd in a reply from a colleague.
5.Stop at three.
Most replies arrive on the first and second email. The third is already thin. Every touch past that raises the odds the whole thread gets classified as spam, and that classification follows the mailbox to the next person you write to. The long cadence is over. Three touches, each with something new in it, then leave them alone for ninety days.
6.Know what good looks like.
A one percent reply rate with a quarter of those replies positive is a healthy trigger based program. Anyone quoting you double digit reply rates is counting out of office messages or selling a course.
7.LinkedIn Sales Navigator is not optional.
Every other data source tells you who held a title at some point. Sales Navigator tells you who holds it today, because the person maintains it themselves. That is the difference between a three percent bounce rate and a fifteen percent one, and bounces are scored against the mailbox the same way spam complaints are. Verify the name there before anything goes out.
It is also the cheapest trigger detector you will own. The job change filter surfaces people who arrived in a role in the last ninety days, which is the moment they have budget and no incumbent. The posted recently filter surfaces companies talking about the exact problem you solve. Account lists with headcount growth alerts tell you who is scaling before the press release does. For this niche the saved search is headcount 200 to 2,000 across industries, titles VP Data, Chief Data Officer, Head of Analytics, VP Engineering and CTO, with the job change alert on for data leadership titles specifically, and a keyword alert on the platform names and the legacy warehouse names across job listings. The job change alert is the trigger itself. The job boards supply the stack, and the vendors' own announcements supply the end of support dates.
Use it for the research and the verification, not for the message. InMail reply rates are a fraction of email, and the person who replies to a thoughtful email is the same person who ignores a connection request with a pitch attached. Pull the work email from a data provider once Navigator has confirmed the person is real and current.
None of this is specific to your niche. All of it is specific to whether anyone ever reads the angle you spent an hour getting right.
If you would rather not run it yourself
That is what we do. ExpertLayer runs this exact loop for expert led firms: the weekly job post and leadership change pull, the stack cross reference, the qualification with the partner question first, the angle per account naming the decision, the sending across warmed mailboxes, and the reply reading. You take the conversations and run the assessment.
The first step is free and it is the same research described above. Send us your website and we will come back with 10 companies that hit these triggers right now, with the posting or the new leader, the contact, and the opening line for each.
Questions from people running this
The platform vendors have partner programs that hand out leads. Why do outbound at all?+
Because the partner leads go to the largest partners first and arrive after the company has already chosen the platform. Outbound reaches the company while it is still deciding, which is when a migration partner can shape the architecture rather than inherit it. The two channels are complementary, and the outbound one is the one you control.
A new head of data is the trigger, but how quickly do I write?+
Inside the first sixty days. A new data leader arrives with a mandate and a budget window, and the platform decision is usually made in the first quarter. After that, you are writing to someone defending a choice rather than making one. The job change alert is the single most valuable thing in this playbook.
Should I mention the vendor's migration funding programs?+
Yes, in the first conversation rather than the first email. Both major platforms fund migrations through partners, the amounts are meaningful for a mid market company, and most prospects do not know the programs exist. Knowing how they work is a credential, and it changes the economics of saying yes.
How do I handle a company whose team says they can do it themselves?+
By agreeing that they can, in eighteen months, alongside their day jobs, without the vendor's migration credits, and then asking what the business needs the data for in the meantime. The honest pitch is not that the team is incapable. It is that a migration is a project with a schedule and the team already has one.