Why not have forward deployed engineers report to sales?

Because a bookings scorecard turns the FDE into a sales engineer within two quarters. The promise becomes whatever closed the deal, the scope becomes whatever the customer asked for, and the handback to product becomes a liability nobody has time for. NICE described its newly staffed FDE team on its November 4, 2026 call as a shift in go-to-market, with engagements as the number, which is exactly the output a sales reporting line asks for.

Why not services or engineering?

A services line measures utilization, which keeps the engineer on the account because the account pays, and at scale that is a support desk with a field title. Engineering is the harder case: it owns the harness and should hold the bar on what an FDE ships, but its scoreboard is the system, reliability and the cost of a change, and the field's output is not a system. It is a decision about what the system should become for everyone. An FDE who reports to engineering brings that finding to a function whose job is to build what product decided, and the finding waits for a roadmap it does not own.

What does the reporting line change in practice?

The number the team reports. In Milos Mandic's State of FDE 2026 survey, 24 respondents report into five different places. Antoine Buteau's May 2026 piece puts it in one line: org design decides what forward deployment becomes. Everything measurable about an FDE team from the outside is lagging, bookings, time to value, utilization. The one leading number, the generalization rate, the share of what came back from the field that shipped for every customer, only exists on a product scorecard.

What is the CPO's loop and where does the FDE sit in it?

Customer, spec, build, story, adoption, and back to the customer. The FDE sits at the customer end and the build end at once, design turns the customer's workflow into the spec, product marketing turns deployment proof into the story, and the CPO decides what gets built for everyone. When the four report to four executives, each reports its own number and the loop closes in quarters. Under one CPO there is one scorecard, and a field finding that arrives on Tuesday can be a roadmap decision by Thursday.

What should a leader decide this quarter?

Move the FDE org's reporting line to the CPO before the next planning cycle and change the scorecard in the same memo: generalization rate per pod, roadmap items that started in a deployment with dates, and days from a field finding to a roadmap decision. Keep dotted lines to sales for the promise and to engineering for the harness. The CPO has to name the product manager who reads every handback packet first, because a field team under a product org that does not read the field is only a different box on the chart.

Should Forward Deployed Engineers Report to the CPO?

Should forward deployed engineers report to the CPO?

THE SHORT ANSWER

Yes. The reporting line is the scorecard, and the scorecard decides what the field produces: bookings under sales, utilization under services, a clean harness under engineering. None of those is the reason to put an engineer inside a customer's building. The reason is that a deployment is the product's fastest signal about what to build next, and the FDE's real output at the end of one is a decision about the product, a workflow that should be a feature, an eval the roadmap should be held to, a customer's process that is the design spec. Only the function that owns the roadmap can act on that in hours instead of quarters. On the Q3 2026 earnings calls of NICE (November 4), ServiceNow (October 28), and Palantir (November 2), the FDE team appeared with engagements, time to value, and demand, and no number about what the field contributed to the product, which is the tell. Falk's rule: the FDE org reports to the CPO, with dotted lines to sales for the promise and to engineering for the harness, and a scorecard of generalization rate, roadmap items that started in a deployment, and days from field finding to roadmap decision.

Three earnings calls in eight days named their forward deployed engineering teams, and every number attached to the team was a sales number or a delivery number. NICE's Scott Russell on November 4: "Since the end of Q2, we have fully staffed our FDE team, and engagements are ramping significantly," described as a shift in go-to-market. ServiceNow's Gina Mastantuono on October 28: "accelerated time to value of 80% year-to-date." Palantir's Alex Karp on November 2: "we really cannot satiate demand." Not one reported what the field put into the product, and that is the tell about where the org sits.

The reporting line is the scorecard. An FDE's real output at the end of a deployment is a decision about the product, and only the function that owns the roadmap can act on it in hours. That is the CPO, with design, product marketing, and the field in one org, because a loop split across four reporting lines cannot close fast enough.

Part 15 of The FDE Transition makes the case in full, with Falk's predictions for 2027 and the scorecard to adopt. The handbook chapter on building the FDE team covers the hiring bar, pairing, and comp that go with it, and The CPO Transition makes the same case from the top.

Last reviewed 2026-11-05 · 2 min read

Should forward deployed engineers report to the CPO?

SOURCES

THE LONG VERSION

RELATED ANSWERS