Who actually signs
At a company with more than a million dollars a year in cloud spend, the signer is the CFO or the VP of finance when the driver is margin, and the CTO or VP of infrastructure when the driver is an engineering mandate. The two increasingly sign together. The champion is the first FinOps analyst if one has been hired, and the person who can stop it is the platform engineering lead who owns the architecture and does not want a finance person in it.
The buying reason is a number the board has seen: gross margin compression, cost of revenue growing faster than revenue, or a single month's bill that nobody can explain. The reason arrives with a name attached, and the name is usually a new CFO.
The one sentence version
Your buyer is a finance leader with a cloud line that grew faster than revenue last quarter, a commitment renewal on the calendar, and an engineering team that says the bill is what it is.
The triggers, and where each one is visible
- Public filings. Registration statements and annual reports disclose hosting and infrastructure costs, and the trend against revenue is the whole business case. A company whose cost of revenue is growing faster than its top line has a margin problem with a cloud line inside it.
- New CFOs. A new finance leader reviews the largest vendor lines in the first quarter, and cloud is usually in the top three. Job change alerts surface the arrival.
- Commitment expiries. Enterprise agreements and three year reserved capacity commitments have dates, and the ones signed in the expansion years are expiring on a known schedule. The renewal negotiation is the single largest cost decision most companies make about cloud, and most have never run one.
- FinOps job posts. A company advertising for its first FinOps analyst or cloud economist has a mandate and no playbook. The role is new enough that the hire will need one on day one.
- Layoffs and cost programs. A reduction in force is a company with a cost mandate, and the cloud bill is the line that did not get reduced when the headcount did.
- Funding rounds with a path to profitability in the narrative. The press release names the margin target, and the cloud bill is between the company and it.
- Accelerated compute spend. A funding announcement with an AI narrative, or a job post for infrastructure engineers with accelerator experience, is a company that has added the most expensive line item in cloud without the commitment discipline it applied to the rest.
The new CFO and the commitment expiry are the two to build on. One tells you who is about to look. The other tells you the date they have to decide by.
Qualify in sixty seconds
- Is the spend above a million a year? Below that, the savings do not fund the engagement, and the honest answer is a tool. Above five million, the renewal negotiation alone justifies it.
- Is there a FinOps function in house? One analyst is a champion. A team of five is a client for the hard parts only. None is the whole program.
- Is there a margin signal? Filings, a funding narrative, a layoff, a new CFO. Without one, the engineering team has no reason to let finance in.
- Is there a commitment date inside a year? If yes, the engagement has a deadline and a number. If no, the assessment is still the right first step, but the urgency is lower.
The angle that gets replies
Lead with the renewal or the margin line, in the finance leader's numbers. Not rightsizing, not waste, not a percentage. The decision they are about to make, and what it costs to make it without preparation.
Three openers you can adapt
- On a new CFO at a cloud heavy company"Congratulations on the role. Cloud is usually in the top three vendor lines a new CFO reviews, and the question that matters more than the total is how much of it sits under a commitment that expires inside your first year. The renewal sets the next three years of unit economics and most companies walk into it with the account team's proposal as the only number. One page on how we prepare for that negotiation, attached to nothing."
- On a filing showing cost of revenue outpacing revenue"Your last two filings show cost of revenue growing faster than the top line, and at a company shaped like yours the hosting line is usually the reason. The number the board will ask for next is cost per customer, which most infrastructure teams cannot produce because the bill is not attributed. Attribution is about four weeks of work. Happy to send what it looks like."
- On a first FinOps analyst posting"Saw the FinOps analyst posting. The hire will arrive to a mandate and no playbook, and the three things that make their first quarter succeed are a tagging standard the engineers will actually follow, a commitment inventory with expiry dates, and a weekly report the CFO reads. All three can be in place before their start date. Two paragraphs on the sequence, attached."
Each one names a decision, a date and a deliverable, and none of them quotes a savings percentage. That is what separates a practice from a tool.
What not to send
- "Save thirty percent, guaranteed." The number is the tool vendor's number, the reader has heard it from four of them, and a guarantee before seeing the bill marks you as the fifth.
- "Cloud cost optimization" as the whole pitch. It is a category, the reader has a tool in it, and the tool shows the waste without removing it.
- Rightsizing as the lead. It is real, it is the least valuable lever, and it is what the tool already recommends. The commitment position and the architecture are where the money is.
- Shaming. "You are wasting money" is true of every company and is not how a finance leader wants to be addressed by a stranger.
The objection you will hit
We have a cost tool. The tool shows where the money went. It does not negotiate the renewal, it does not change the architecture that produced the bill, it does not get the engineering team to adopt a tagging standard, and it does not decide which recommendations are safe to act on. Visibility is the first ten percent of the work. Say so and ask what the tool's recommendations have actually saved so far.
The second is our engineers handle it. They handle their own services, in the time left after shipping, with no incentive to reduce a bill that does not appear in their goals. The FinOps practice is the incentive and the process, and it works with the engineers rather than around them.
The third is we are locked into a commitment. Which has an expiry date, which is the trigger, and which can often be restructured, exchanged or drawn down through the marketplace before it expires. A commitment is a negotiating position, not a sentence.
Deal shape
- Cost assessment, including commitment inventory, attribution gaps and the top levers: commonly $15K to $40K, and the engagement that opens most relationships.
- Optimization engagement: $50K to $150K as a fee, or a share of first year savings in the range of ten to twenty percent.
- Renewal and commitment negotiation support: $25K to $100K, or a share of the improvement against the vendor's opening proposal.
- FinOps practice build, including the tagging standard, the reporting and the operating cadence: $75K to $200K.
- Retainer for ongoing commitment management and reporting: $5K to $20K a month.
- Signer: CFO, VP Finance, CTO or VP Infrastructure. Champion: the FinOps analyst. Cycle: two to eight weeks, and driven by the renewal date when there is one.
The assessment is the funnel. It is small, it is about their actual bill, and it produces the commitment inventory with expiry dates, which is the calendar of every engagement after it.
A cadence you can actually run
- Quarterly, pull filings for companies in your segment and flag cost of revenue growing faster than revenue.
- Weekly, run job change alerts for CFOs and VPs of finance at companies with visible cloud spend, and pull FinOps job posts.
- Weekly, pull layoffs, cost programs and funding rounds with a profitability narrative.
- Monthly, maintain the commitment expiry calendar for prospects and clients, which is the single most valuable document in the practice.
- Qualify against the four checks, with the spend threshold first. One message per account, naming the decision and the date. Twenty accounts a week is a full program.
- Three touches over two weeks, then stop. The next renewal date or the next filing is a fresh reason to write, and the vendors' fiscal year ends make the renewal calendar predictable.
The company publishes its margin problem in a filing and its renewal date in a contract the CFO has on file. The consultancies that grow are the ones writing three months before the renewal, not three weeks.
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 renewal outcome. A consultancy that can say by how much its clients' final commitment terms improved on the vendor's opening proposal, across the last dozen negotiations, has the number a CFO cares about. The second is attribution: state how many companies you have taken from an unattributed bill to a cost per customer figure the board uses, and how long it took.
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 400 person software company, new CFO in February, assessment in three weeks, a commitment expiring in five months that nobody had inventoried, renewal negotiated at a stated improvement on the vendor's proposal, cost per customer in the board deck by the second quarter. The improvement on the opening proposal and the timeline to the board figure 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. The vendors' fiscal year ends cluster renewals, and the quarter before each is when a second mailbox earns its keep.
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: "the commitment expiring in your first year", "cost of revenue in the last two filings", "before your FinOps hire starts". 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 3,000 in software and technology enabled services, titles CFO, VP Finance, CTO, VP Infrastructure and FinOps Analyst, with the job change alert on for finance leadership specifically and a keyword alert on FinOps and cloud economist across job listings. The CFO arrival is the trigger itself. Navigator confirms the person. The filings and the commitment calendar are the source.
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 quarterly filing pull, the CFO and FinOps alerts, the commitment expiry calendar, the qualification with the spend threshold 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 filing, arrival or posting, the contact, and the opening line for each.
Questions from people running this
Every cloud cost vendor promises thirty percent savings. How do I not sound like them?+
By never quoting a percentage before you have seen a bill. The tools promise thirty percent because the number sells. A practice that says the savings depend on the commitment position and the architecture, and offers to look at the last three invoices before saying anything, is the only one in the inbox that sounds like it has done this.
Is the commitment renewal really the best trigger?+
It is the one with a date the CFO already knows. The three year commitments many companies signed in the cheap money years are expiring now, the renewal negotiation sets the next three years of unit economics, and most finance teams have never negotiated one. A note timed to the expiry is a note about a decision they are about to make badly.
Should I sell a percentage of savings or a fee?+
Both models work and the choice is a positioning one. A share of savings aligns incentives and closes faster with a skeptical CFO. A fee is cleaner and does not create an argument about attribution six months later. Many practices open with a fixed fee assessment and offer a share of savings on the implementation, which lets the client choose.
GPU spend is the new line item. Different playbook?+
Same playbook, sharper trigger. A company that has added accelerated compute to its bill has usually done so without reserved capacity, without utilization monitoring and without knowing which team is spending it. The AI narrative in a funding announcement is the signal, and the questions are the same ones as for the rest of the bill, with larger numbers.