Papers  /  a16z · Trading margin for moat
Industry essay~11 min readRead Aug 2026
Breakdown

Why a software company
hires expensive engineers
to do customer work

Software companies are supposed to optimise gross margin. Hiring senior engineers to sit at customers is the opposite of that, and a16z’s services-led-growth argument is the case for doing it anyway: trade margin for depth, because depth is defensible.8 If you work in a forward deployed role, this essay is the reason your job exists — and the reason it can be taken away.

01

The thesis, in one paragraph

Services-led growth

Deliberately spend gross margin on deployment work — embedded engineers, integration, enablement — because the resulting integration is hard for a competitor to displace and the resulting outcome is provable. The margin hit is real and it is treated as an acquisition cost for defensibility rather than as an inefficiency to be optimised away.8

The context that makes it a live argument rather than a historical one: model capability is broadly available and enterprise outcomes are not, so the differentiator moves from what the model can do to what a specific customer got. That is exactly the gap the widely-reported finding about pilots without measurable P&L impact describes.17 The market has responded with money — OpenAI standing up a deployment organisation,5 Anthropic and Blackstone launching a $1.5B venture,6 Microsoft committing $2.5B to embed engineers with customers.7

→ The word that matters is “trade”

It is not a claim that services are good. It is a claim that a specific exchange is worth making — margin now for defensibility later. Trades have terms, and a trade only works if you get the thing you paid for. Most of what follows is about how to tell whether you did.

02

The arithmetic that decides it

Worth doing on a napkin, with your own numbers. The figures below are an illustrative worked example, not market data.

# worked example — substitute your real figures
loaded cost of one FDE                         ~$300k/yr  (salary + benefits + travel)
deployments per FDE per year                     3
  → deployment cost                            ~$100k each

# the ratio that decides whether the trade works
ACV $150k  → services eat 67% of year-one revenue   
ACV $600k  → services eat 17%, renews at ~95%      

# and the multiplier that actually saves you
reuse: work that ships as product  → next deployment 0.6×, then 0.4×
no reuse                              → every deployment 1.0× forever

Two variables carry the whole model. Contract value has to be large enough to absorb a person — which is why this thesis describes enterprise deals and not mid-market ones, and why an FDE org attached to small contracts is structurally unhappy regardless of who works in it. And reuse, which is the only term that improves over time. Without it the model is arithmetically a consultancy, whatever the company calls itself.

→ The diagnostic, in one question

Does deployment N take measurably less time than deployment N−1? If yes, the trade is working — margin is buying a compounding asset. If it is flat across four engagements, you are paying for a moat you are not receiving, and no retrospective will say so out loud.

03

The failure mode built into the thesis

The essay argues for the trade. The trap is paying the cost and not getting the moat — and it is gradual, so nobody decides on it.

The trade working

  • Deployment N takes measurably less time than N−1.
  • Work done for one customer ships as product for the rest.
  • Engineers rotate off accounts and the systems keep running.
  • The roadmap contains items whose origin was a customer engagement.
  • You can name what the last deployment contributed to the product.

The services trap

  • Every customer has a fork, a branch, or a private repository.
  • Nobody can leave an account without the account degrading.
  • The word “utilisation” appears in performance reviews.
  • “We’ll productise it later” has been said for four consecutive quarters.
  • Headcount grows linearly with customer count and nobody finds that alarming.

Nobody decides to be in the right-hand column. It arrives one reasonable exception at a time: this customer is strategic, that integration is one-off, we will generalise it next quarter. The reason the left-hand column is hard is that generalising is always less urgent than the deployment in front of you, and the cost of not doing it is invisible for about a year.

→ What one engineer can do about a company-level thesis

Write the generalisation memo at the end of every deployment: what we built, what was genuinely customer-specific, what should be product, and what it would cost to make it so. One page, one hour. It is the smallest unit of the thing this essay argues for, it is entirely within your control, and it is the best evidence you will have at promotion time — see the commercial layer.

04

What it means for your career

If your compensation is paid out of this trade, the terms of the trade are your working conditions. Three things follow, and all three are knowable before you accept a job.

1

Ask how deployment work is paid for

Bundled into the licence means you will be measured on days-per-deployment. Time and materials means you will be measured on utilisation. Those are different jobs and both are called forward deployed engineer.

2

Ask what the last deployment contributed to the product

A confident, specific answer means the trade is being managed. A vague one means you would be joining the right-hand column, and the person interviewing you may not know it.

3

Understand where the biggest comp step comes from

Generalising, not delivering. Ten excellent bespoke deployments that produce nothing reusable keeps you a senior FDE; six that turn two patterns into product capability is what reaches staff.18

→ The honest reading

This is an investor’s argument for a company strategy, not a description of a career. It is correct about why the role exists and it says nothing about whether an individual engineer’s five years in it compound — that depends entirely on whether the org you joined is in the left-hand column. Is forward deployed engineering worth it covers that side properly.

The mechanics behind the thesis

Where the margin actually goes

Frequently asked

Quick answers

What is services-led growth?

The argument that a software company should deliberately spend gross margin on deployment work — embedded engineers, integration, enablement — because the resulting integration is hard for a competitor to displace and the resulting outcome is provable. The margin hit is treated as an acquisition cost for defensibility rather than as an inefficiency to optimise away.

Why would a software company deliberately lower its gross margin?

Because model capability is broadly available while enterprise outcomes are not, so the differentiator moves from what the model can do to what a specific customer actually got. Deployment work buys a defensible position and a provable outcome. The trade only pays off if the contract value is large enough to absorb the cost of a person and if the work produces reusable product rather than bespoke artefacts.

What is the services trap?

Paying the margin cost and not receiving the moat: deployment work grows, every engagement is bespoke, nothing is reused, and a software company becomes a consultancy with a software cost base — without ever deciding to. Nobody chooses it; it arrives one reasonable exception at a time. The diagnostic is whether deployment N takes measurably less time than deployment N-1.

How can one engineer act on a company-level thesis?

Write a generalisation memo at the end of every deployment: what was built, what was genuinely customer-specific, what should be product, and what that would cost, with an owner and a date. It is one page and about an hour, it is the smallest unit of the thing the thesis argues for, and it is also the strongest evidence available at promotion time — because the biggest compensation step in this career comes from generalising rather than delivering.

What should you ask a prospective employer about this?

Two questions. How is deployment work paid for — bundled into the licence means you are measured on days per deployment, time and materials means you are measured on utilisation. And what did the last deployment contribute back to the product — a confident, specific answer means the trade is being managed, a vague one means the org is drifting toward the services trap.

Receipts

Sources

Every number on this page traces to one of these. Where a figure is self-reported or crowd-sourced rather than first-party, it is labelled inline.

Cited on this page

  1. OpenAI — launching the Deployment Companyopenai.com/index/openai-launches-the-deployment-company/
  2. TechCrunch — Anthropic and Blackstone launch “Ode” ($1.5B)techcrunch.com/2026/07/15/anthropic-blackstone-ode/
  3. CIO Dive — Microsoft commits $2.5B to embed engineers with customerswww.ciodive.com/news/microsoft-25b-embed-engineers/824392/
  4. a16z — Services-Led Growth — the margin-for-moat thesis behind FDE hiring. a16z.com/services-led-growth/
  5. MIT NANDA “State of AI in Business” — 95% of pilots with no measurable P&L impact — widely reported; figure cited via press coverage rather than a public PDF. techcrunch.com/2026/07/30/forward-deployed-engineers-are-the-ai-industrys-latest-talent-obsession/
  6. Perspective — 2026 Forward Deployed Engineering compensation report (1,200 FDEs) — self-reported survey data; treat as medium confidence, not first-party. www.getperspective.ai/blog/2026-forward-deployed-engineering-compensation-report-1200-fdes
Trading Margin for Moat · part of the FDE track · Vibe Engines · 2026
Finished this one? 0 / 111 Paper Breakdowns done

Explore the topic

See this alongside everything else on the same subject — handbooks, system designs, challenges and tools, in one place.

More Paper Breakdowns