The Role of Advisors in AI Engineering
A Forward Deployed Advisor is a senior practitioner who runs a solo consultancy and sells FDE work without performing it.
Where the Name and the Work Part Ways
Engineering vocabulary is full of titles that suggest more than they deliver. The label Forward Deployed Advisor is one of them. At first glance it seems to describe someone who sits inside a customer's organization and ships working software. The source material describes a different reality: the label has spread beyond the core of the industry and has been attached to a role that works at a distance from the engineering itself. Understanding this role starts with noticing where the name and the work part ways.
What do you think happens?
What does a Forward Deployed Advisor deploy into the customer's production environment?
Reveal answer
Nothing. The Advisor does not sell shipping code in the customer's production environment.
The title is borrowed from hands-on delivery work, but the Advisor is not doing that work. The source names the expectation that an Advisor will deploy production code as a misconception, and a buyer who treats the title as a promise of deployment has misread the engagement before it starts.
Who the Advisor Is
A Forward Deployed Advisor is a senior practitioner who runs a solo consultancy and sells FDE work without performing it.
The definition has two features that matter. First, the Advisor is senior. The value sold rests on experience and judgment rather than on a team of engineers executing a build. Second, the consultancy is solo, so the person selling the engagement is the same person delivering its advisory output. The model is one practitioner whose knowledge is packaged into services.
The role is structured around a single practitioner. The Advisor sells the engagement and provides its advisory output, but the hands-on FDE work that the title evokes is sold by the Advisor without being performed by the Advisor.
The Advisor's Catalogue of Services
The Advisor's catalogue is specific and limited. The source lists four categories of offering. Each one stays on the advisory side of the line between thinking about a system and building it.
- Strategy
- Diagnostics
- Executive coaching
- In some cases, high-quality intellectual property such as frameworks and playbooks
Every item on that list produces guidance, assessment, or reusable material. None produces running code in a live system. That shared character is what the rest of the article depends on. Notice the qualifier on the last item: intellectual property is sold only in some cases, so a buyer should not assume every engagement includes frameworks or playbooks.
The One Thing Not Sold
The clearest way to see the distinction is to place the Advisor's sales next to the hands-on work the role is named after. The source describes FDE work as the engagement the Advisor sells without performing it. The comparison below sets the two sides against each other, using only what the source states.
Tracing a Request Through the Filter
The following scenario is an illustration written for this article. It is not drawn from the source. Its purpose is to show how the distinction plays out when a real request arrives. Follow the request through the decisions in the flowchart, then read the worked example.
A buyer asks for a production deployment
A company writes: 'We need a Forward Deployed Advisor to ship our retrieval service into our production environment next month, and also review our data strategy.' Decide what fits the Advisor role.
- 1Split the request into parts
The request contains two asks: shipping a service into production, and reviewing data strategy.
- 2Test the strategy part
Reviewing data strategy is strategy, one of the four advisory categories. It is within the Advisor's catalogue, so it is in scope.
- 3Test the production part
Shipping a service into the customer's production environment is shipping code in production. The source states the Advisor does not sell this, so that part must be declined.
- 4Respond to the buyer
The Advisor accepts the strategy review and states clearly that deployment into production is not part of this engagement. The buyer is not left expecting a deployment that will not happen.
The data strategy review fits the Advisor role and can be accepted. The production shipping request does not fit and must be declined, so the buyer should not assume the title promises deployment.
Mistakes When Reading the Title
Common mistake Reading the title as a job description
What it looks likeAssuming a Forward Deployed Advisor will sit inside the customer's organization and ship working software because the name evokes hands-on delivery.
Why it failsThe title is borrowed from hands-on delivery work, but the Advisor is not doing that work. The source describes the role as working at a distance from the engineering itself.
Do this insteadCheck the scope of the engagement directly against the four advisory categories instead of inferring it from the name.
Common mistake Assuming every engagement includes intellectual property
What it looks likeExpecting frameworks and playbooks to be included in every Advisor engagement.
Why it failsThe source says high-quality intellectual property is sold in some cases, not in all of them.
Do this insteadConfirm whether frameworks or playbooks are part of the specific engagement.
Common mistake Treating the Advisor as a team of engineers
What it looks likeExpecting a build team to appear once the Advisor is hired.
Why it failsThe model is a solo consultancy. The value sold rests on the experience and judgment of one senior practitioner, not on a team executing a build.
Do this insteadEvaluate the Advisor's offering as advisory output from one senior person.
Sorting Incoming Requests
Three requests arrive at a solo Forward Deployed Advisor. For each, decide whether the request is within the advisory catalogue, asks for the excluded item, or needs its scope checked directly: (1) an executive coaching program for a new head of AI; (2) a diagnostic review of why a model pipeline is underperforming; (3) a commitment to deploy code into the client's live production system. Explain your decision for each using the two tests from the flowchart.
Hints
- Ask first whether the request covers strategy, diagnostics, executive coaching, or intellectual property.
- If it does not, ask whether it asks for shipping code in the customer's production environment.
- A request that fits neither test, or is vague, needs its scope checked directly rather than assumed from the title.
Key Takeaways
- A Forward Deployed Advisor is a senior practitioner who runs a solo consultancy and sells FDE work without performing it.
- The Advisor sells strategy, diagnostics, executive coaching, and in some cases frameworks and playbooks, all of which produce guidance, assessment, or reusable material.
- The Advisor does not sell shipping code in the customer's production environment, and the title should not be read as a promise of deployment.
- To evaluate a request, first test whether it falls within the advisory catalogue, then test whether it asks for production code, and check unclear scope directly.