Forward deployed engineering works because it collapses the distance between the people with the problem and the people building the solution. But embedding engineers is not enough on its own. Successful FDE engagements follow a disciplined rhythm. Here is the playbook we use.
Before day one: scope the outcome, not the solution
- Agree a single business outcome and how it will be measured (for example, “reduce claim review time by a measurable amount”).
- Name an executive sponsor and a day-to-day product owner from the business.
- Secure access early — systems, data, environments and security approvals often take longer than building.
Week 1: embed and observe
FDEs spend most of the first week with users: shadowing work, mapping the workflow, collecting real examples and understanding the edge cases that never appear in requirements documents. The output is a shared problem statement, a baseline measurement and a short list of solution hypotheses.
Weeks 2–3: prototype with real users
- Build the thinnest version that touches real data and real workflows.
- Put it in front of users within days and iterate daily.
- For AI solutions, build an evaluation set from real cases from the start.
- Kill ideas quickly when they don’t work — speed of learning matters more than code volume.
Weeks 4–8: harden and deploy
Once the approach is proven, shift from speed to robustness: integration with production systems, authentication and authorisation, error handling, monitoring, automated tests, CI/CD and a security review. Release gradually — pilot group first, then wider rollout.
Handover or scale
- Handover: pair with the client’s engineers, document architecture and runbooks, and transfer ownership deliberately.
- Scale: package what worked as reusable components and repeat the playbook with the next team.
Rituals that keep FDE engagements on track
- Daily check-ins with the product owner.
- Weekly demos to users and the sponsor — working software only, no slides.
- A visible metric dashboard from week one.
- A risk log covering access, data, security and adoption.
Common failure modes
- No empowered product owner on the client side.
- Waiting weeks for data or system access.
- Building for a demo instead of for production.
- Skipping handover, leaving the client unable to maintain the solution.
Learn more about our Forward Deployed Engineering services.
Frequently asked questions
How long does a forward deployed engineering engagement take?
A typical engagement reaches production in roughly 6 to 12 weeks, depending on access, integrations and complexity, followed by handover or expansion.
What does the client need to provide for an FDE engagement?
An executive sponsor, an empowered day-to-day product owner, access to users, data and systems, and timely security approvals.
What is the most common reason FDE engagements fail?
Lack of access and ownership on the client side — no empowered product owner, or long delays getting data and system access.