What Is a Forward Deployed Agent (FDA)?
The role that gets enterprise AI agents from demo to production. Less a consultant, more a code-and-ETL specialist who ships the Decision Graph end-to-end.
What an FDA is, in one paragraph
A Forward Deployed Agent (FDA) is the delivery model Naboo uses to ship a Decision Graph for an enterprise customer in 2-4 weeks. The FDA is not a project manager or a generalist consultant - they are a specialist in ETL, data science, and the customer's particular toolchain. They sit with the customer's tech lead for two to four hours of elicitation, then encode the resulting entity definitions and joins across code, tickets, PRs, Slack, and internal services. The output is a queryable graph exposed via GraphQL and MCP, ready for the customer's agents to call.
The job, week by week
Week 1: elicitation. Sit with the tech lead, walk through ten real questions an engineer asks today, record every implicit reference type (branch-name conventions, flag-key patterns, Slack thread habits). Week 2-3: encoding. Translate the elicited language into typed entities and live-ETL plumbing across the source systems. Week 4: verification. Run a blind benchmark on the ten elicitation questions, iterate the entity definitions until the agent returns the right chain. End of week 4: the GraphQL surface and MCP server are locked; the customer's agents can call against production.
Why this is a role, not a tool
The encoding step requires judgment a tool cannot make. 'What is a feature here, in your words?' has a different answer at every company. A naive automated mapper would either over-generalize (and lose precision) or over-fit (and lose generality). An FDA - a human who has done this twenty times - knows which questions to ask, which patterns transfer, and which to encode as customer-specific. The Decision Graph stops being a generic framework and becomes the customer's actual decision substrate.
FDA vs professional services vs solutions engineering
Professional services typically delivers a configured product within the vendor's existing object model. Solutions engineering supports pre-sale evaluation. A Forward Deployed Agent does the work that lives between: shipping production infrastructure that encodes the customer's specific reality. Palantir originated the model; it's the right shape for any platform whose value depends on capturing a customer's hidden vocabulary.
FAQ
Is the FDA a Naboo employee or a contractor?
Naboo employee. The role requires deep knowledge of the Naboo platform, the customer's tools, and the standard patterns of decision encoding. Contractor FDAs would have a learning curve that defeats the 2-4 week timeline.
Does the FDA stay involved after deployment?
An on-call relationship continues. The Decision Graph definitions evolve when the organization's vocabulary changes (typically once a quarter). The FDA owns those updates - it's a few hours of work, not weeks - and stays the customer's named contact for the platform.
How is the FDA different from a consultant?
A consultant produces a deliverable - a report, a slide deck, a recommendation - and leaves. An FDA produces working infrastructure that the customer's agents call against in production. Their KPI is the success rate of the agent on the customer's real questions, not a project completion checkbox.
What does FDA mean elsewhere?
Palantir uses Forward Deployed Engineer (FDE) for a similar role - engineers embedded in customer workflows to operationalize the platform. Naboo's FDA is the same model adapted to AI agent delivery: same proximity to the customer, same end-to-end accountability, focused on encoding the Decision Graph.
Related reading
Reasoning Layer for Enterprise AI Agents
Definition, architecture, and the two tiers - Topic Graph and Decision Graph.
Read moreDefinitionWhat is a Decision Graph for AI Agents?
Decisions as first-class nodes - owners, triggers, blockers, evidence. The primitive AI agents need to act.
Read moreHow-toHow to Build a Decision Graph
Seven concrete steps from elicitation to a queryable graph. Two to four weeks via Forward Deployed Agent.
Read moreCFO briefHow to Reduce LLM Token Costs
Don't meter the waste, cut the cause. Reasoning Layer vs observability and caching, compared.
Read moreGuideImprove AI Agent Accuracy
Accuracy is upstream of evals. Four causes of enterprise AI inaccuracy and how a Reasoning Layer fixes them.
Read moreArchitectureConnect Enterprise Data Sources
Live joins vs stale copies. Warehouse, ETL, knowledge graphs, and Reasoning Layer compared.
Read moreGuideOvercome GenAI Hallucinations
Hallucinations are a context-handoff problem, not a model problem. Four causes, one upstream fix.
Read moreROIHow Naboo Saves Cost
Five places Naboo cuts cost in enterprise AI deployments. Four-minute explainer video.
Read moreHubCompare Naboo
Every category enterprise AI buyers weigh against the Reasoning Layer - in one place.
Read moreComparisonNaboo vs Helicone
Reasoning Layer cuts the cause; Helicone measures the waste. Composable.
Read moreComparisonNaboo vs Langfuse
Different layers. Langfuse versions + traces; Naboo grounds the agent.
Read moreComparisonNaboo vs LlamaIndex
RAG framework vs Reasoning Layer. When to use each.
Read moreComparisonNaboo vs LangChain
Orchestration vs substrate. Compose them.
Read moreBackgroundWhy retrieval was the wrong foundation
How enterprise AI agents got built on RAG, why it falls short, and what a reasoning layer fixes.
Read moreComparisonNaboo vs RAG
Retrieval vs reasoning - head-to-head benchmarks, architecture, and when to use each.
Read moreComparisonNaboo vs Glean
Enterprise search vs reasoning layer - when each fits.
Read moreConceptAI Search vs Reasoning Layer
Search returns links; the reasoning layer returns the chain. When to use which.
Read moreCase studyGlobal-E case study
How Global-E (NASDAQ: GLBE) gave AI agents secure access to customer data.
Read moreComparisonCompare alternatives
Naboo vs other enterprise AI agent infrastructure platforms.
Read moreGo deeper
The full architecture and customer story live on the dedicated page.