The FDE Buyer’s Guide
Hire the FDE. Keep the value.
Every AI vendor now wants to send you an engineer. This free 38-page guide shows enterprise leaders how to choose the right one, contract for outcomes and ownership, and make sure what gets built stays with your company when they leave.
Know whose scorecard your FDE is on.
In 2026 Microsoft, AWS, Google Cloud, OpenAI, Anthropic, Salesforce and the big systems integrators all launched or expanded forward deployed engineering units, often offered at little or no charge. Those engineers are measured on their employer's targets: consumption, renewals and features they can take back into their own product. That can be a real opportunity for your company or a slow handover of your business logic. Almost every FDE playbook so far was written for the vendor or the engineer. This one is written for the buyer.
- 95%
- of enterprise generative AI pilots showed no measurable P&L impact. MIT NANDA, The GenAI Divide, 2025
- ~6,000
- engineers in Microsoft's new $2.5B Frontier Company, built to embed inside customers. Company announcement, July 2026
- $1B
- committed by AWS to a forward deployed engineering unit running 45-day customer pods. Reported June 2026
Are you ready to bring one in?
Most FDE engagements that stall do so for reasons on the client's side: no sponsor, blocked data, a three-month security review. Score your company on the guide's eight-point readiness check before you talk to any provider.
Day 0 to Day 120, from the client's chair.
The FDE drives the work. You supply access, decisions and people, and you sign every gate. Here is what the guide asks of you at each step, and what you should own when it ends.
-
Before you buy
Get ready, then write the brief
The readiness check, a one-page FDE brief every provider answers against, and your own internal lead named to pair with the FDE.
Gate: sponsor named, readiness 10 of 16 or better
-
Weeks −6 to 0
Choose the source and vet the people
Five ways to get an FDE, a weighted provider scorecard, questions for the firm and for the named engineers, red flags, and a paid discovery sprint before any big commitment.
Gate: provider chosen on evidence, not a demo
-
Contracting
Contract for outcomes and ownership
Commercial models from discovery sprint to outcome pricing, and a clause checklist for work product, business logic, data use, portability and exit help.
Gate: ownership and exit terms signed while you have leverage
-
Weeks 1 to 6
Discovery, lighthouse and business case
What to give your FDE on day one, what must stay in your repositories, how to pick the first use case, and payback math your finance team co-owns.
Gate: success sentence, lighthouse and baseline signed
-
Weeks 4 to 10
Set the non-negotiables, own the evals
Seven architecture requirements including model portability and your own identity, the autonomy ladder, and an evaluation harness your experts build and you keep.
Gate: risk sign-off and KPI threshold met
-
Weeks 8 to 16
Go live and transfer the capability
Hypercare, then a shadow, pair and lead plan that moves the work to your engineers, with evidence at every stage.
Gate: your team ships and fixes unaided
-
Day 120
Rehearse the exit, then hand off
Two weeks running the system without the provider, a handoff acceptance checklist, finance-signed value, and a review that scores the provider for next time.
Gate: you own it, and the next use case is funded
20 chapters, five parts, written for the buyer.
Every chapter ends in something you can use on Monday: a scorecard, a checklist, a contract position, a template or a talk track for your CFO.
Part I · The 2026 FDE market
- What an FDE is, and what it isn't
- Why every vendor now wants to send you one
- Whose scorecard is your FDE on?
- When your company actually needs an FDE
Part II · Choosing your FDE
- Five ways to get an FDE
- Get ready before you buy
- How to vet an FDE and an FDE provider
- Contracting for outcomes and ownership
Part III · Running the engagement from the client's chair
- Your 120-day map
- Discovery: what to give your FDE, and what to keep
- Choosing the lighthouse and building the business case
- Architecture and governance: your non-negotiables
- The pilot and the evaluation harness you own
- Production, hypercare and capability transfer
- Measuring value, and measuring your FDE
Part IV · Building your own FDE capability
- The internal FDE team
- Hiring and developing FDEs
- Buyer anti-patterns
Part V · Field kit for buyers
- Templates: RFP question bank, weekly status, eval rubric, executive readout
- The sponsor's first 90 days and the CFO talk track
Plus a glossary and 19 cited sources, current to October 2026.
Written for the people who sign for it.
| If you are… | Start with | You'll leave with |
|---|---|---|
| A CIO, CTO, COO or head of AI | Chapters 2, 3 and 5, then Part III | A sourcing decision, a provider scorecard and the terms to insist on |
| A business sponsor funding an AI initiative | Chapters 3, 6 and 9 | What you must provide, what to demand and how to measure the result |
| Procurement, legal or vendor management | Chapters 7 and 8, then the field kit | An RFP question bank and a contract checklist built for FDE work |
| An AI center of excellence building its own team | Part IV | An operating model, a hiring loop and metrics for internal FDEs |
| An FDE, or a firm that provides them | Parts III and V | What your best clients will expect from you, and how to earn their trust |
Written by Qexa Technology's Chief AI Architect.
Before you sign
Read it before the vendor’s engineer arrives.
Enter your name and email and the PDF is yours on the next screen. Free, 38 pages, October 2026.
Questions
Is it really free?
Yes. No trial, no paywall. You get the full 38-page PDF right after you enter your name and email.
What will you do with my email?
Qexa keeps it to know who downloaded the guide. You'll only get occasional notes on deploying AI if you tick the box, and you can unsubscribe at any time.
Can I share the guide with my team?
Please do. Send them to fde.qexa.com so they get the latest edition.
Is it tied to one AI vendor?
No. It compares vendor, lab, systems integrator, boutique and in-house options side by side, and its architecture rules are written to keep you free to switch models and providers.
Is this the same as the original FDE Playbook?
No. It replaces it. The first edition was written for practitioners; this October 2026 guide is written for the enterprise that hires them, with new chapters on sourcing, vetting, contracts, ownership and building your own team.
Can Qexa help with a deployment?
Yes. Qexa Technology works vendor-neutral, builds in your environment and hands over what it builds. It can also review a provider proposal against the guide. Book a conversation with Alex.