The harness, sold.
Almost no public SaaS company cracks $500K per contract — Palantir averages $4M. The difference is a motion: loan the customer engineers who assemble your platform’s primitives into their outcome. Once every platform went agentic, that once-niche motion became everyone’s problem.
click a piece to inspect it
The chain of limitations — 6 sheets
- 01The 2×2Two axes decide the whole go-to-market: how technical the thing you sell is, and how technical the buyer is. Three quadrants have well-worn motions — DevRel, self-serve, sales-led. The fourth, a deeply technical platform sold to a non-technical buyer, is where forward deployed engineering lives.
The quadrant tells you a sales deck can't carry the product and the customer can't carry it either. It doesn't tell you what you're selling instead of software.
- 02Selling the OutcomeNot a product, not a service — the thing in between. You loan the customer engineers who learn their business and build them a working solution on your platform. What the customer buys is neither software nor someone's time. It's the outcome.
Loaning out engineers sounds like a cost center wearing a sales badge. The motion only makes sense if it lands contracts nothing else can reach — so the numbers have to say so.
- 03The Half-Million GapMeasure public SaaS by average contract value and almost nobody cracks $500K. Palantir sits at $4M — with a few thousand employees. The gap between configure-it-yourself software and delivered outcomes is where the business case for FDE lives.
Big contracts for custom-built outcomes — a dev shop can claim the same. And a dev shop's P&L gets eaten alive by maintenance. What separates the two is what the engineers build on.
- 04The Platform of PrimitivesFDEs never write software from scratch. They assemble shared primitives into solutions arbitrarily valuable to each customer. Bespoke work stays scoped to its customer; anything generalizable flows back into the platform — and the field becomes the product team's scouts.
A platform makes the motion sustainable — it doesn't make it yours. FDE is in vogue, and it's easy to want what's in vogue. Two questions separate need from want.
- 05The Two QuestionsDo you have to sell something technically complicated to a non-technical buyer? And do you have a platform — or the will to invest in one? Two honest answers route you to FDE, DevRel, or sales-led growth. Then the hiring profile: an FDE is nothing more than a customer-facing software engineer.
For twenty years those questions filtered nearly everyone out, and FDE stayed a Palantir curiosity. Then AI made building easy — and the filter started catching everybody.
- 06When Every Platform Went AgenticWhat changed isn't that the world decided Palantir was right. The nature of software changed: nearly every platform is now agentic, which means customizable, which means your customers no longer fully understand what they bought. The niche motion is moving to the center of how software gets sold.
Look at what an FDE actually deploys: instructions shaped to one customer's business, tools wired into their systems, procedures, verification — primitives assembled around a problem. That's a harness with a go-to-market. The chain closes where it began.
Two axes, four motions
Three quadrants have well-worn playbooks. Forward deployed engineering exists for the fourth.