Vibe Engines
YouTube

Vibe Engines is free, interactive AI engineering & system design — runs in your browser. Pick a learning path

~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.

The delta

What this claims against rung 1: the deployment work is worth paying for

Rung 1 establishes that the gap between capability and outcome is where value is lost. This rung is the argument that a company should deliberately spend its own margin to close that gap — take on services-heavy deployment work, accept a lower gross margin than a pure software business would report, and treat the resulting customer outcome as the defensible asset.

The reasoning against the orthodoxy is specific. Software businesses are valued on high gross margin because it signals that revenue scales without proportional cost. The counter-argument here is that in a market where the underlying capability is available to everyone, high margin is not a moat — a competitor can match the product. What a competitor cannot easily match is being embedded in a workflow that now works, with the integration built, the data flowing and the outcome measured. So margin is spent to buy switching costs, and the bet is that they are worth more than the margin was.

The arithmetic that decides whether the bet holds is the checkable part, and it is the reason to read this as an engineer rather than as an investor. It holds if the deployment work produces reusable product — if each engagement's custom work becomes a connector, a template, a feature, so the nth deployment is cheaper than the first and margin recovers as the business scales. It fails if every engagement is bespoke, because then cost scales with revenue forever, and what has been built is a consultancy carrying a software company's valuation and cost base. Same strategy, same early numbers, opposite ending — and the variable is whether anything is extracted from the custom work.

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.

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

How it works

How the a16z essay builds its argument

The essay is Trading Margin for Moat: Why the Forward Deployed Engineer Is the Hottest Job in Startups, by Andreessen Horowitz partner Joe Schmidt, posted on June 4, 2025. Its argument runs in six moves.

gross margin customers deployed software-like margin reuse: custom work becomes product no reuse: every deployment bespoke 1.0× 0.6× 0.4× 1.0× 1.0× ×: cost of a deployment vs the first
The thesis in one picture: margin given up early comes back only if deployment cost falls as customers are added. The essay's examples have this shape (ServiceNow 63.2% gross margin at IPO and 79% in 2024; Workday 54.1% and 75%); the multipliers are this page's illustrative arithmetic.
  1. Observe the market. Enterprise AI startups are reported to go from zero to $5 million, $10 million or more than $20 million in annual recurring revenue within two years, by selling into complex workflows rather than self-serve tools.
  2. Name the moat. The prize is becoming the system of work, the place where a company's valuable data is generated, captured and stored. Getting there takes deep implementation, and deep implementation is services work.
  3. Argue from the last cycle. Salesforce, ServiceNow and Workday were built on heavy implementation and are worth far more than the leading product-led companies, at the cited $254 billion, $194 billion and $63 billion. ServiceNow's gross margin at IPO was 63.2% and Workday's 54.1%, against a software ideal of about 80%; by 2024 they were at 79% and 75%. Salesforce reportedly burned more than $52 million to generate $22 million of revenue before building a partner ecosystem.
  4. Change the target. Rather than an 80% gross margin from the start, optimize for growing total gross profit as fast as possible.
  5. Describe the role that does the work. Forward deployed engineers, alongside solutions and implementation specialists, operationalize models, integrate systems and act as managers for the customer's AI agents. Decagon's agent product managers are the case study, and OpenAI's careers page is cited: 22 of its 311 open roles fell into these categories when the essay was written.
  6. Set operating rules. Start with a narrow ideal customer, pair services staff with account executives, sell services at cost, avoid putting quotas on implementation leads, build reusable libraries and documented APIs, automate onboarding, and keep tight feedback loops from the front line to product. AI itself, the essay argues, can automate much of the implementation, so margins should recover faster than they did last time.

What kind of evidence this is

It is an argument by analogy and example, with no sample, comparison group or measurement of its own, and some figures labelled as reported. It names the standard objections, that services cap scalability, that low margins signal a commodity product and that partners should do the services, and answers them.

Two things it leaves out

Palantir, the company most associated with the forward deployed engineer title, is the natural test of margin recovery, and the essay never mentions it. Palantir carried heavy on-site engineering for years before listing in 2020, with a gross margin of about 67% in 2019, and reached about 80% by 2024 while still running forward deployed teams. That fits the thesis without isolating why margins rose. Outcome-based pricing is the other gap: a vendor that charges per resolved support conversation, as Intercom does for its Fin agent, recovers deployment cost through the price of results instead of absorbing it as a margin discount.

The evidence

What the essay's evidence shows, and what it cannot

ClaimFigure citedWhat it cannot show
Implementation-heavy incumbents recovered marginServiceNow 63.2% at IPO, 79% in 2024; Workday 54.1%, then 75%how often the recovery fails, since only survivors are cited
Implementation-heavy firms end up worth moremarket caps of $254B, $194B and $63Bthat services strategy, rather than markets or products, drove the value
Early services cost is survivableSalesforce: over $52M burned to generate $22M of revenuemore than a reported figure; the essay flags it as such
Enterprise AI grows fast with services$5M, $10M or $20M+ ARR within two yearswhich companies, or how many
Labs hire the role22 of 311 open OpenAI rolesmore than one snapshot of one careers page

Every example is a company that made the trade and survived to be cited. None is a company that took the margin hit and stayed a services business, which is the failure the thesis has to rule out, so the evidence shows the strategy can work, not how often it does. The strongest figures are the margin trajectories: two firms that began about 17 and 26 points below the 80% ideal and closed most of the gap. The weakest claim is the forecast that AI will automate implementation enough to make the recovery faster this time, which no figure in the essay supports. The outside case of Palantir, about 67% gross margin in 2019 and about 80% in 2024 with forward deployed engineers still in place, is consistent with the thesis but does not test it, because pricing and product changed over the same years.

By the numbers

Worked example: margin gaps and gross profit, from the essay's figures

This is arithmetic on the figures the essay cites, plus the Palantir case this page adds from outside it. The software ideal is about 80 percent gross margin.

CompanyEarly gross marginGap to 80%2024 gross marginGap leftShare of the gap closed
ServiceNow63.2% at IPO16.8 points79%1 point94.0%
Workday54.1% at IPO25.9 points75%5 points80.7%
Palantir (not in the essay)about 67% in 2019about 13 pointsabout 80%about 0about all of it

The other figures divide just as simply. Salesforce's reported $52 million burned to generate $22 million of revenue is $2.36 spent per dollar earned before it built a partner ecosystem. The OpenAI careers snapshot, 22 of 311 open roles, is 7.1 percent of openings at one moment.

The essay's change of target is easiest to see with two illustrative companies. A product-led one books $10 million of revenue at an 80 percent margin: $8 million of gross profit. A services-heavy one books $20 million at 60 percent: $12 million. The second has the worse margin and 50 percent more gross profit, which is the trade the title names. The thesis then needs the margin to climb afterwards, as the rows above show it did for the companies cited. What the arithmetic cannot supply is the missing row: a company that took the same margin hit and never recovered, which is the case the evidence would need in order to say how often the trade works.

In the wild

Where the margin-for-moat trade shows up in real-world engineering

The thesis is decided by whether custom work becomes product. That happens, or fails to, in ordinary engineering decisions made during a deployment.

  • One codebase, configured per customer

    The services trap usually begins as a fork. The pattern that keeps reuse possible is a single product codebase with customer differences held in configuration, integrations behind one shared connector interface, and any truly bespoke logic isolated in a plugin that can be deleted or promoted later.

  • Delivery metrics that measure reuse

    Teams that manage the trade track it like any other system metric: calendar days per deployment, how many connectors or templates each engagement reused, and how much of its code was merged into the shared product. A flat line across four deployments is the warning, long before it reaches gross margin.

  • Partners as the other answer

    The incumbents the essay cites did not keep all implementation in-house: Salesforce, ServiceNow and Workday rollouts are widely delivered by systems-integrator partners, which moves services cost off the vendor's own books. An AI company choosing embedded engineers instead is choosing to keep that cost, and the learning that comes with it.

  • In forward deployed engineer interviews

    A common prompt: you built a workflow for one customer, and a second wants something similar but not identical. The strong answer separates what is customer-specific from what is product, proposes the shared abstraction and its cost, and says what you would ship first so the second customer is not blocked.

Since then

What kind of claim this is, and what it means for your work

This is an investor thesis, not a finding. It is an argument about where value will accrue, published by a party whose interests are served by the argument being believed, and it should be read with that in the frame — not dismissed for it, since the reasoning stands or falls on its own, but not mistaken for evidence either. No sample, no measurement, no counterfactual.

What makes it worth a rung is that its central claim is falsifiable on a timescale you can observe, and the test is the arithmetic above. Watch whether a services-led company's gross margin rises as it adds customers. If it does, custom work is being converted into product and the thesis is working. If it stays flat while headcount tracks revenue, the moat is not compounding and the discount was simply a discount.

For a career the implication is direct and worth stating plainly. In an organisation of this shape, the work that is visibly valued is shipping a customer outcome, and the work that compounds is turning the fourth version of the same integration into something the fifth customer gets for free. Those are not the same activity, and only the second one is what the thesis depends on. Doing only the first is how a good engineer ends up indistinguishable from a contractor while believing they are building a platform.

Questions

Questions people ask about Trading Margin for Moat

What does a16z's Trading Margin for Moat essay argue?

Joe Schmidt's June 2025 essay for Andreessen Horowitz argues that AI startups selling into complex enterprise workflows should accept lower gross margins early and spend them on hands-on implementation, led by forward deployed engineers. The payoff is becoming the customer's system of work, where its data is generated and stored, which is hard for a competitor to displace. It points to Salesforce, ServiceNow and Workday, which were built on heavy implementation and later reached high margins: ServiceNow went from 63.2% gross margin at IPO to 79% in 2024, Workday from 54.1% to 75%. The metric to optimize, it says, is total gross profit growth, not gross margin.

Why would a software company deliberately accept a lower gross margin?

Because gross margin is a ratio and gross profit is the money. A company at 55% margin on $20 million of revenue makes more gross profit than one at 80% on $10 million, and if the services behind the lower margin win larger, stickier contracts, the trade can pay. The a16z essay argues that deep implementation makes a vendor the customer's system of work and creates switching costs a competitor cannot easily copy. The bet only works if margin recovers as the business grows, which depends on custom work turning into reusable product. If every deployment stays bespoke, the company has become a services firm with a software valuation.

Is Palantir evidence that trading margin for moat works?

It is the obvious test case, though the a16z essay never mentions it. Palantir popularized the forward deployed engineer, embedding engineers with customers for years before its 2020 listing, and its gross margin was about 67% in 2019. By 2024 it was about 80%, a software-like level, while Palantir still ran forward deployed teams. That trajectory is what the thesis predicts. It is not proof, because pricing, product and customer mix changed over the same years, so the recovery cannot be attributed to turning custom work into product alone. It shows the path is possible for a company of that kind, not how often it succeeds.

How does outcome-based pricing compare with trading margin for moat?

They are two answers to the same problem: enterprise AI only pays off after expensive deployment work. Trading margin for moat absorbs that cost up front as a lower gross margin and bets on recovering it through retention and reuse. Outcome-based pricing charges for results instead, for example per support conversation an AI agent resolves, the model Intercom uses for its Fin agent, so the vendor is paid only when the deployment works and recovers its costs through the price of outcomes. The a16z essay does not discuss it. The two can be combined, and outcome pricing makes the vendor carry the risk that the deployment never delivers.

How much evidence supports the a16z margin-for-moat thesis?

Less than its confident tone suggests. The essay offers examples rather than a study: three incumbents built on heavy implementation, their margin trajectories and market capitalizations, one startup case in Decagon, and a count of 22 forward-deployed-style roles among 311 open OpenAI jobs. There is no sample of companies that tried the strategy, no comparison group and no account of the ones that stayed services businesses, so it shows the strategy can work, not how often. Its central claim can still be checked from outside, by following a services-led company's gross margin as its customer count grows and seeing whether it rises or stays flat.

Check yourself

4 questions to test what you just read

Work each one out before you open it — a number, a prediction or a reason, not a definition. Producing the answer is what makes it stick. Your progress is kept on this device.

ServiceNow went from 63.2% gross margin at IPO to 79% in 2024. On $1 billion of revenue, how much more gross profit does the later margin produce?

Show answer

0.79 × $1B − 0.632 × $1B = $158 million more gross profit on the same revenue. That difference is what the essay asks founders to forgo early, betting that the revenue base it buys will make the trade worthwhile.

The essay says to optimize total gross profit, not gross margin. Which is better on that metric: $10M of revenue at 80% margin or $20M at 55%?

Show answer

$10M × 0.80 = $8.0M against $20M × 0.55 = $11.0M of gross profit, so the lower-margin business wins on the essay's metric, provided the extra revenue is retained and the margin does not stay at 55% forever.

Why is a list of successful implementation-heavy companies weak evidence that trading margin for moat works?

Show answer

It samples only survivors. A fair test would also count the companies that accepted low margins, never turned custom work into product and remained services businesses; without them, the examples show the strategy can work, not how often it does.

Using this page's illustrative numbers, a $100k deployment whose cost falls to 0.6× and then 0.4× with reuse, what do the first three deployments cost with and without reuse?

Show answer

With reuse: $100k + $60k + $40k = $200k. Without: 3 × $100k = $300k. The third deployment alone costs 60% less, which is the compounding the thesis needs; flat costs mean margin never recovers.

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 Company — openai.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 customers — www.ciodive.com/news/microsoft-25b-embed-engineers/824392/
  4. a16z — Services-Led Growth (Joe Schmidt, 4 Jun 2025) — 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 — report dated July 2025, available as a PDF; the figure here is cited via later press coverage (TechCrunch, 30 Jul 2026), which is what this link points to. 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
Where this sits

The industry numbers

Not research papers: a consultancy census, a VC essay and a job-posting analysis. Included because their figures get quoted as if they were, and read here for their method.

  1. 1The 95% Number, Examined2026
  2. 2Trading Margin for Moat2026
  3. 31,000 FDE Jobs, Analysed2026

All 110 papers, in 19 ladders →

Trading Margin for Moat · part of the FDE track · Vibe Engines · 2026
Finished this one? 0 / 110 Paper Breakdowns done
Next1,000 FDE Jobs, Analysed Next on the “The industry numbers” ladder · rung 3 of 3

Explore the topic

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

More Paper Breakdowns