AI Operations (FDE) insight

Forward Deployed Engineer vs Professional Services: Which One Do You Actually Buy

Hayat Amin · Updated 2026-09-05

Forward deployed engineer vs professional services, settled from the filings rather than the job titles. Salesforce books its forward deployed engineers inside professional services and UiPath books them beside it, so the label tells you nothing. Here is the test that does, what each model costs in the United States, and where professional services is still the right purchase.

Buy professional services when the specification already exists. Buy a forward deployed engineer when nobody can write it yet. Professional services is a delivery organisation that executes a defined scope against a statement of work and is measured on hours delivered and projects closed. A forward deployed engineer is a builder embedded inside one operation who works out what to build by watching the work, then owns whether the system runs. The two look identical on the site visit. They diverge on the only three things that matter: who holds the specification, what gets measured, and who carries the outcome.

The hard part in 2026 is that the label has stopped telling you which one you are buying. Salesforce files its forward deployed engineers inside the professional services section of its annual report. UiPath lists them beside its professional services organisation as a separate function. Both documents went to the United States Securities and Exchange Commission within twenty three days of each other in March 2026. Same phrase, opposite org chart. Hayat Amin, who takes the forward deployment engagements at Beyond Elevation, argues that the only test left is economic, and that buyers should stop reading job titles and start reading how the seller gets paid.

What Professional Services and Forward Deployment Actually Sell

Professional services sells the execution of a decided outcome. Forward deployment sells the finding of one and the building of it in the same motion. That is the whole distinction, and it survives every rebrand laid on top of it, because it is a statement about where the specification comes from rather than about where the engineer sits.

Salesforce defines the category in its own filing. Professional services revenue, it tells investors, covers professional and advisory services for process mapping, project management and implementation services and training services. Read that list again. Process mapping, project management, implementation, training. Every item presumes somebody has already decided what is being mapped, managed, implemented and taught.

Now read how Palantir described the other model when it first put the term in front of investors. Its forward deployed engineers, the company wrote, had travelled to bases in Afghanistan and factories in the industrial Midwest to deploy its platforms, and as they helped customers they observed users' challenges firsthand. The risk factors were blunter: the business depended on those engineers identifying new use cases. A statement of work cannot contain a use case nobody has identified yet, which is exactly why the model exists.

The Label Stopped Working in 2026

Full text search of the Securities and Exchange Commission's filing archive returns eighty seven documents containing the phrase forward deployed engineers. The earliest is Palantir's draft registration statement of 6 July 2020. Six years on, the filers using it are overwhelmingly the professional services industry the term was coined against.

IBM told investors on 22 July 2026 that as AI adoption moves from experimentation to enterprise scale deployment it is investing in more specialised technical and client facing talent, including Forward Deployed Engineers. Cognizant filed on 29 April 2026 that under a new Google Cloud practice it plans to deploy forward deployed engineers, senior engineering talent embedded directly within client environments. Wipro's annual report describes a dedicated AI Native unit supported by forward deployed engineering teams, and gives its consulting subsidiary Capco the job of owning those capabilities. Deloitte sells Forward Deployed Engineering as a service page inside its consulting practice.

The most useful moment came on an Infosys call filed on 28 July 2026. A reporter asked the chief executive how difficult it is for a services company to plug forward deployed engineers into existing workflows, and noted that several were struggling with it. Salil Parekh named the Infosys version, Frontier Engineers, an objective of six thousand of them, and a definition worth keeping: the capability is really the engineering plus the business context. That definition is correct. It is also an admission that the capability had to be built rather than renamed.

Forward Deployed Engineer vs Professional Services, Side by Side

Where Professional Services Wins

Professional services wins whenever the scope is real and written. If you can hand a stranger a document and they can execute it, and you will know on delivery whether they did, you are buying execution. A forward deployed engineer is an expensive and slightly insulting way to buy execution, and any honest firm will tell you so before taking the money.

It wins a second time on price, for a reason most buyers never see. Salesforce's professional services line brought in 2,137 million dollars of revenue in the year to 31 January 2026 and cost 2,474 million dollars to deliver, losing roughly 337 million dollars. It lost 229 million the year before and 44 million the year before that. No company runs a loss making line for three straight years by accident. It runs it because that line protects 39,388 million dollars of subscription revenue carrying a gross margin near 83 percent. For a buyer that is good news: if your problem is getting more out of a product you already own, the vendor's own team is subsidised, knows the product to the metal, and is paid to keep you renewing.

It wins a third time on scale and recourse. A systems integrator can put forty people on a programme, carry an indemnity, hold a clearance and still be there in three years. One embedded engineer can do none of that. Regulated, multi year, multi country programmes are professional services work, and dressing that up as forward deployment helps nobody.

What the Economics Tell You to Ask

Ask how the seller books your engagement, because the answer predicts the behaviour you get for the next six months. Utilization businesses are paid for hours. Outcome businesses are paid for systems. The same engineer, sold two ways, becomes two different colleagues.

Service Performance Insight's 2026 Professional Services Maturity Benchmark, built from 509 organisations, found billable utilization falling to 66.4 percent in 2025, the lowest in the firm's surveying history, with average earnings before interest, taxes, depreciation and amortisation at 9.9 percent. Sit with the first number. Your rate has to carry the third of the time your consultant is not billing anybody, and revenue arrives by the hour, so finishing early costs the firm money. That is not a moral failing. It is the arithmetic of the model, and you are inside it the moment you sign.

The forward deployed model was built to get out of that arithmetic. Joe Schmidt at Andreessen Horowitz called it trading margin for moat in June 2025, noting that ServiceNow went from a 63.2 percent gross margin at its initial public offering to 79 percent in 2024, and Workday from 54.1 percent to 75 percent. Palantir, which coined the term, reported an 82 percent gross margin and 3.7 billion dollars of gross profit across 954 customers for 2025. The services work never disappeared from these companies. It stopped being sold by the hour.

What Each One Costs in the United States

The American full time price of the role is public. Anthropic is running 595 open postings today, six of them forward deployed. Its Forward Deployed Engineer role for New York City, San Francisco and Seattle is posted at 280,000 to 320,000 dollars in annual salary, on the Applied AI team, embedding with strategic customers to ship production applications. The manager of that practice in New York City is posted at 320,000 to 405,000 dollars. That is base salary, before equity.

Professional services is priced the other way, by the hour or the phase, off a rate card built to hold utilization near two thirds. Which is cheaper depends entirely on whether the scope is known. With a known scope, hours are the efficient purchase and you should take them. With an unknown scope, hours are how a pilot dies: you buy a discovery phase, receive an excellent document, and arrive back where you started with less money in the bank.

The Question That Settles It

Hayat Amin's Specification Test is one exercise, done before you call anybody. Sit down and try to write the statement of work yourself. Not the goals. The scope: what gets built, in which system, touching which data, and the test that says it worked.

If you can write it, buy professional services and buy it hard. If you cannot, notice that no procurement process will produce the missing document, because the information you are short of lives in your operation rather than in a vendor's proposal. That is the forward deployed engineer's job, and the one thing professional services structurally cannot do: get the specification out of the business by working in it.

The failure mode is predictable and expensive. A company that cannot write the scope signs a six figure statement of work to have the scope written, then treats the resulting document as progress. Nothing is running. Hayat Amin's rule for founders is shorter: if ninety days from now the deck has improved and nothing is in production, you bought the wrong model.

How Beyond Elevation Fits This Decision

Beyond Elevation places forward deployed engineer leaders into companies that cannot yet write the specification: operators with fifteen or more years in the C-suite and at least one exit behind them, named and accountable, not a bench of juniors billing hours. Because the firm sells engagements rather than time, there is no utilization number that finishing early would damage, and the scoping call starts by testing whether you already have a scope, in which case Beyond Elevation will tell you to buy professional services instead. Fractional engagements start from 5,800 dollars a month and projects from 30,000 dollars, with no salary, no equity and no notice period, and the first system goes live within eight weeks. Smaller companies can start with a two week AI audit at a fixed 3,000 dollars. The model is set out at beyondelevation.com/fde, the neighbouring comparisons are forward deployed engineer vs software engineer and forward deployed engineer vs product manager, and the smaller company version is forward deployed engineer for startups. The rest of the firm's work sits at beyondelevation.com. Hayat Amin, a chief financial officer across three exits before moving into forward deployment, takes the scoping calls himself at meethayat.com/services/fde.

FAQ

Forward deployed engineer vs professional services: what is the actual difference?

Professional services executes a specification you supply, priced by the hour and measured on utilization and milestones. A forward deployed engineer works inside your operation to produce the specification nobody could write, then builds it and answers for whether it runs. If the scope exists, the difference is cost. If it does not, only one of the two can help.

Is a forward deployed engineer just professional services with a new name?

Sometimes, yes, and the filings prove it. Salesforce describes its forward deployed engineers inside the professional services part of its annual report, while UiPath lists them separately from its professional services organisation. The name is not evidence. Ask how the engagement is priced and what number the seller reports internally: hours billed, or systems live.

Do the big consulting firms have forward deployed engineers?

They do now. Deloitte sells Forward Deployed Engineering as a consulting service line. IBM told investors in July 2026 it is hiring Forward Deployed Engineers. Cognizant is placing them inside client environments under a Google Cloud practice, Wipro has built them into a dedicated AI Native unit, and Infosys is scaling its own version, Frontier Engineers, toward a stated objective of six thousand people.

Forward deployed engineer vs technical consultant: is there a difference?

Yes, and it is visible in the deliverable. A technical consultant advises and hands back a recommendation. A forward deployed engineer commits production code into your systems and stays until it runs. If the engagement ends with a document rather than something running in your stack, you hired a consultant, whatever the invoice says.

Should I hire a forward deployed engineer or buy my software vendor's professional services?

Buy the vendor's professional services if the goal is getting more out of that vendor's product. It is deep, it is subsidised, and Salesforce's own numbers show the line runs at a loss to defend subscription revenue. Hire a forward deployed engineer when the problem crosses systems the vendor does not sell, or when nobody can yet say what success would look like.