
On October 28 a Jefferies analyst asked ServiceNow's CFO how to model the engineers the company had started putting into its biggest AI deals. Gina Mastantuono's answer ran about a minute. One sentence in it is the most honest thing a software executive has said about forward deployed engineers this year: "We do not expect to include this delivery expertise over the long term."
Include. Not sell.
ServiceNow isn't charging for those engineers. It's folding them into the deal, and the accounting then carves their value out of subscription revenue and books it as professional services. Her sizing, from earlier on the call: "about 25 bps in Q3 and expecting it to have approximately 50 bps in Q4."
Same afternoon, Microsoft. Amy Hood on the call, explaining what the $2.5 billion Frontier Company is for: "we want them to utilize both the Copilot license to its fullest, and understand when the consumption meter is delivering value to them."
So here's the headline for every software exec who reorganized around a forward deployed model this year with a services line penciled in to pay for it. Your customers are not paying for your FDEs. The biggest vendors in the market already know, and two of them told investors on the same day.
This is part 16 of The FDE Transition, part of The Product OS.
The short version
- Customers are not paying for forward deployed engineers as a line item, and the largest software vendors have stopped pretending they will.
- Microsoft put $2.5 billion and 6,000 people into the Frontier Company and its CFO ties the spend to Copilot licenses and the consumption meter.
- ServiceNow includes the engineers in select large deals and expects a 50 bps hit to Q4 subscription revenue because their value gets booked as professional services. Salesforce's FDE program is free to select customers. AWS prices on outcomes.
- That sets the market price of a vendor's engineer at zero, and a services fee on top of a subscription is now priced against free. The move isn't to fight that.
- Book the field team as acquisition cost with a clock on it, charge for the outcome or the platform, and make every deployment cheaper than the last by shipping what the field learned. That last part only works when the field reports to product.
Four companies, one price
Microsoft first, because it's the largest. The Frontier Company launched in July with, in Mary Jo Foley's report at Directions on Microsoft, "6,000 engineers and salespeople and a budget of $2.5 billion." There's no price list. Her colleague Lane Shelton, who advises enterprises on Microsoft licensing and contract negotiations, explained why there doesn't need to be one: "Free deployment is the customer acquisition cost and the consumption meters are the payback." Three months later Hood said the same thing to investors in CFO language. She also said, about how fast that payback arrives, "it will be a slower move outside of coding."
AWS put $1 billion behind its FDE organization in June. Larry Dignan's report at Constellation Research has the two details that matter: the work is priced on fixed outcomes, not billable hours, and the billion covers market development funds and cash and credit investments along with the engineers. Part of the FDE budget isn't engineers at all. It's credits.
ServiceNow is the one that put a number on it, and I'd give them credit for that. Delivery expertise included in "select large deals," 25 bps, then 50.
50 bps
Salesforce said it earliest and plainest. Its own blog on the role, from November 2025: customers "must be nominated by their account executive to be in the Momentum program, offered to select customers for free." Paige Elia, who works on the program: "It's an investment by Salesforce in our customers." The same piece says that some time in the next year customers "will also have the option to purchase FDE services." That was a year ago next week. Jason Lemkin wrote this summer that Marc Benioff told him he wished every customer had a forward deployed engineer "and didn't have to pay until they were deployed."
That's the man who built Salesforce on the subscription, wishing the engineer were free.
Add Google Cloud, Workday, NICE, and Atlassian, all covered in earlier parts, and you have most of enterprise software reorganizing around the field this year. Nasser Ghanemzadeh checked the pages of 34 companies selling forward deployed engineers in October. 25 publish no price, including every large vendor.
One caveat, because this site doesn't do invented numbers. None of these companies discloses FDE revenue, attach rate, or the share of engagements that are free. "Not paying" is my read of the pricing structure and of what two CFOs said out loud. It's a strong read. It isn't a reported figure.
Why the price is zero
Alan Paris wrote the cleanest map of this two weeks ago. His question for a buyer: "Does the engineer show up as a bill, as a drag on the vendor's margin, or as a subsidy funded by future consumption?" Three models. Consulting firms run the first, and he files Microsoft there too. ServiceNow is his example of the second. The labs, AWS, and Salesforce are the third. I'd move Microsoft to the third, on Hood's own words.
Now sit in the seat of a software company with a hundredth of Microsoft's revenue. You built an FDE team this year. The plan says services revenue covers some of it. Your buyer's procurement team has read the same announcements you have, and their Microsoft rep just offered embedded engineers with no invoice attached.
You're pricing against free. And free has a $2.5 billion budget.
Rocio Wu at F-Prime Capital laid out the other half of the trap in February. Bill time and materials and "customers anchor on hourly rates rather than product value," and the services revenue drags the multiple. Bundle the cost into the subscription and it "obscures the true drivers of CAC and gross margin." Both doors are bad. Most companies walk through the second one and stop measuring.
The buyers who do get a bill aren't happy either. Gartner, in a brief by Mukul Saha, estimates FDE consulting fees "could top $200,000 quarterly per use case," as Matt Ashare reported, and it predicts 70 percent of enterprises will abandon agentic AI built by vendor FDEs by 2028. The customers paying for the engineer are the ones Gartner expects to walk.
So who does get paid? Palantir, where Alex Karp's contracts are $25 million to start and nobody sends an invoice for an engineer, because the engineer is inside the platform price. The consulting firms, who've always sold hours and don't have a software multiple to protect. And the companies that sell a result. What I can't find is a subscription software company getting paid, at a margin, for its own engineers as a line item on top of the subscription.
If that line is in your plan, it's the one to look at.
Now what
Four moves. None of them is "raise the day rate."
Call it acquisition cost, and put a clock on it. ServiceNow's version has everything a board needs. A scope: select large deals. A size: 25 bps, then 50. An end date, loosely: not "over the long term." And a reason, in Mastantuono's words, "that consumption flywheel." You can argue with the bet. You can't say it's hidden. If your FDE spend sits inside cost of revenue with no scope, no size, and no end date, you're in Wu's second door. Pull it out, name the payback you expect, and write down when the subsidy stops for a given account.
Charge for the outcome or the platform. Never the person. Every model where the customer demonstrably pays has this shape. Karp sells a $25 million platform. AWS quotes a fixed price for a result. The economics chapter has the math on why outcome pricing forces the discipline: when revenue sits behind the result, engineer hours are your cost to manage, not the customer's cost to question. The moment a person shows up on the invoice, the conversation is about the rate.
Run two paybacks, not one. This is the move I'd put the most weight on.
Consumption is the first payback. The customer goes live, the meter runs, the subsidy comes back. Fine. But consumption pays the bill once per customer, and you send the engineers again for the next one.
Product is the second. Every deployment should make the next one need fewer engineer hours, because what the field learned shipped for everyone. That's the generalization rate, and it's the only thing that turns a subsidy into an asset.
Go back to ServiceNow's call, because the best moment in it isn't the CFO's. Right after Mastantuono named the cost, another executive jumped in to name the exit: "we are also building using AI implementation agents. When we help our customers go live, a lot of the heavy lifting is done by AI." Then: "This is not a long-term engagement."
That was Amit Zavery. President, COO, and chief product officer.
Finance can tell you what the field costs. Only product can make it cost less next quarter. A field team that reports into sales or services has no route to the second payback, which is the whole argument of part 15 and of The CPO Transition. Atlassian's Mike Cannon-Brookes said the same thing from the CEO seat last week: "Our goal is not building a service business."
Gate it by what the meter can earn. ServiceNow said "select" twice. Salesforce requires a nomination. Free engineers are still rationed, and the ration is the account's ability to pay it back in consumption. Part 11 has the honest cases where the seat is the wrong hire. Add one line to the deal desk: no FDE without a consumption forecast that covers the cost inside a year, and a named product owner for what comes back. Wu's rule is the backstop: "If customers cannot graduate from FDEs, the product is not ready."
And if you're the FDE reading this: your seat is funded by a meter. Find out which one. If nobody can tell you, start writing down what your deployments consumed afterward and what they sent back to product. That document is your case when the subsidy gets reviewed. It will get reviewed.
Three predictions, labeled as mine
By the end of 2027 at least one public software company reports FDE payback as a metric, consumption per FDE-supported deal or something close. ServiceNow is the obvious candidate. It already disclosed the cost.
The paid FDE option at a major subscription vendor, when one finally ships, gets priced as an outcome or a package. Not a day rate.
And companies that kept the services line in the plan take it out quietly at the next planning cycle. The ones who replace it with a product number keep the team. The ones who replace it with nothing cut it.
One thing to try this week
Your last five FDE engagements. Three columns.
What the customer paid for the engineers. What the customer consumed, or paid in recurring revenue, 90 days after go-live against the 90 before. What came back into the product for everyone.
The first column is probably zeros. That's fine. That's the market. If the other two are blank, you don't have a forward deployed model. You have a cost center with a field title, and a competitor with $2.5 billion who can afford one longer than you can.
Sources: Microsoft, Fiscal Year 2027 First Quarter Earnings Conference Call, with Amy Hood (October 28, 2026) · ServiceNow, Q3 2026 earnings call, with Gina Mastantuono and Amit Zavery, transcript via Stock Analysis (October 28, 2026) · Mary Jo Foley, "Microsoft Launches Its Own Forward Deployed Engineering Unit, the 'Frontier Company'," Directions on Microsoft (July 2, 2026), with Lane Shelton quoted · Salesforce, "Today's Hottest Role: Forward Deployed Engineer" (November 19, 2025), a company blog with Paige Elia quoted · Larry Dignan, "AWS launches forward deployed engineering unit with $1 billion investment," Constellation Research (June 30, 2026) · Jason Lemkin, "Your Agents Should Beat Your Best Reps, Not Match Them," SaaStr (July 8, 2026), Marc Benioff as Lemkin reports him · Alan Paris, "Agentic AI Implementation: Who Pays for the Embedded Engineer?" (November 1, 2026) · Rocio Wu, "The Uncomfortable Truth About FDEs," F-Prime Capital (February 6, 2026) · Matt Ashare, "Are forward deployed engineers flirting with failure?," Channel Dive (October 1, 2026), with Mukul Saha quoted · Nasser Ghanemzadeh, "FDE as a service: who sells forward deployed engineers, and what it costs" (October 14, 2026), by the founder of a firm that sells FDE sprints
Part of the running argument on SaaS to AI Business Models: when the seat stops being the unit of value, the margin structure moves with the pricing, and the field team is the first line where that shows.
Related answer: Do customers pay for forward deployed engineers?
Frequently asked
Do customers pay for forward deployed engineers?+
Mostly not as a line item. Salesforce's FDE program is offered to select customers for free, ServiceNow includes delivery expertise in select large AI deals and books its value as professional services, AWS prices its FDE work on fixed outcomes and not billable hours, and Microsoft has published no price for its $2.5 billion Frontier Company. Customers do pay when the engineer is inside a platform contract, as at Palantir, when they buy an outcome, or when they hire a consulting firm that has always sold hours. None of these vendors discloses FDE revenue or the share of engagements that are free, so this is a read of pricing structure and of what their CFOs said, not a reported number.
What did ServiceNow say about paying for deployment engineers on its Q3 2026 call?+
On October 28, 2026, CFO Gina Mastantuono said ServiceNow made the strategic decision to invest in customer success by including delivery expertise with its platform for select large deals. For accounting, the value of those deployments is carved out of subscription revenue and included in professional services, about 25 basis points in Q3 and approximately 50 in Q4. She added that the company does not expect to include this delivery expertise over the long term. Amit Zavery, president, chief product officer, and COO, said ServiceNow is building AI implementation agents that do a lot of the heavy lifting and that this is not a long-term engagement.
What is Microsoft's Frontier Company for, according to Microsoft?+
On Microsoft's October 28, 2026 earnings call, CFO Amy Hood said the investment in the Frontier Company and new sales motions are both meant to get customers to use the Copilot license to its fullest and understand when the consumption meter is delivering value to them. She also said it will be a slower move outside of coding. Lane Shelton of Directions on Microsoft described the model as free deployment being the customer acquisition cost and the consumption meters being the payback. Microsoft has not published pricing for the unit.
Why won't customers pay for a software vendor's FDEs?+
Falk's read: the reference price is zero. When Microsoft funds 6,000 people with $2.5 billion and Salesforce calls its program an investment in customers, a smaller vendor asking for a services fee on top of a subscription is pricing against free. Rocio Wu of F-Prime Capital names the other half: billing time and materials makes customers anchor on hourly rates and not product value, and services revenue hurts valuation multiples, so vendors bundle. Gartner estimates FDE consulting fees above $200,000 a quarter per use case and predicts 70 percent of enterprises will abandon agentic AI built by vendor FDEs by 2028.
If customers won't pay for FDEs, how should a vendor fund them?+
Four moves. Book the field team as customer acquisition cost with a size, a scope, and an end date, the way ServiceNow disclosed it. Charge for the outcome or the platform and never for the person. Run two paybacks: consumption after go-live, and product, meaning each deployment makes the next one need fewer engineer hours because what the field learned shipped for everyone. And gate the engineers by what the account's meter can earn. The second payback only happens when the field reports to the function that owns the roadmap, which is the case for putting the FDE org under the CPO.
What is the three-column check for an FDE org?+
For the last five FDE engagements, write three columns: what the customer paid for the engineers, what the customer consumed or paid in recurring revenue 90 days after go-live compared with before, and what came back into the product for every customer. A zero in the first column is normal. A zero in the first column with blanks in the other two is a cost center with a field title.
What is The FDE Transition series?+
A weekly series on falkster.com, part of The Product OS, for forward deployed engineers and the leaders building around them. Part 1 is the thesis that the FDE is the Product Builder arriving from services. Part 15 argued the FDE org reports to the CPO. Part 16 covers who pays for the field team once the largest vendors price the engineer at zero.

Sign in with LinkedIn to leave a comment.
Sign in with LinkedIn