Forward deployed engineers: how Voho puts AI to work across the whole enterprise
A forward deployed engineer (FDE) is a Voho engineer who works inside your organisation, finds the work worth automating, builds the AI into your real systems and stays until it runs. What FDEs are, what they automate, how an engagement runs, and when you do not need one.
Most organisations do not have an AI problem. They have an implementation problem. The models are good enough. The pilots worked. What is missing is somebody who will sit inside the operation long enough to find the work that should be automated, connect the AI to the systems that work actually lives in, and stay until the people doing that work trust it.
That person is a forward deployed engineer. At Voho it is the core of how we sell and deliver: we do not hand you a platform and a login and wish you luck. We send engineers in, they automate things, and they stay until the automation runs on real work.
What a forward deployed engineer is
A forward deployed engineer, often shortened to FDE, is a software engineer who works from the customer's side of the table. Not a salesperson, not a project manager, not a consultant who writes a report. An engineer who writes and ships code, but who does it inside your organisation, next to the people whose work is being automated, against your systems rather than a demo environment.
The role was popularised by Palantir, which built its business on engineers embedded with customers rather than on software thrown over the wall. Over the last few years a number of AI companies have adopted the same model, for the same reason: a general-purpose model is only as useful as its connection to one organisation's data, rules and people, and that connection is built on site or not at all.
| Role | Writes production code | Works inside your operation | Owns the outcome after go-live |
|---|---|---|---|
| Forward deployed engineer | Yes | Yes | Yes, until it runs |
| Management consultant | No | Partly, for the study | No, the report is the deliverable |
| Systems integrator | Yes | Usually remote, to a specification | Until acceptance |
| Vendor support engineer | Rarely | No | Only the ticket |
| Solutions architect / pre-sales | Prototypes | For workshops | No |
Why AI needs forward deployment more than other software did
Traditional enterprise software encodes a process somebody already wrote down. AI is different: the value is almost entirely in the parts nobody wrote down. Which requests are really the high-volume ones. How customers actually phrase them, in which dialect. Which system is the real source of truth when two disagree. What the agent must never attempt. Which approvals are formal and which are a phone call to one person.
None of that survives a requirements document. All of it is obvious within a week of sitting in the building. That is the entire argument for forward deployment, and it is why AI projects run from a distance tend to demo well and then quietly stop being used. We set the three delivery models side by side in forward deployed engineers vs consultants vs systems integrators.
What Voho's forward deployed engineers automate
Voho started with Arabic voice: AI call centres that speak the dialect the caller speaks. That is still where we are deepest, and our delivery team is on site at Aramco today taking an AI call centre live. But the forward deployed model is not specific to voice. The same engineers, on the same platform, automate work wherever it arrives as a request, a document or a record.
| Function | What gets automated |
|---|---|
| Contact centre | Inbound calls answered and resolved in dialect; tickets and bookings written into the real system; warm handover with the transcript |
| IT and facilities service desk | Requests taken by phone, chat or email, classified, prioritised and raised in ServiceNow, Maximo or Archibus without re-keying |
| Back office | Documents read, checked against the record and routed: invoices, claims, applications, contracts |
| HR | Employee questions answered from policy; leave, letters and onboarding requests raised and tracked |
| Field and plant operations | Work orders drafted from alarms and inspections; shift handovers written from the log; manuals answerable with citations |
| Management reporting | Recurring reports assembled from the systems that hold the numbers, with the sources attached |
The rule an FDE works to is simple: automate what is high-volume, rule-bound and already recorded somewhere, keep a person on anything that needs judgement, and make every automated step visible and reversible. The full list, department by department, is in what a forward deployed engineer automates; what the first month looks like inside a contact centre is in why we send an engineer to sit in your contact centre.
How an engagement runs
| Phase | What the FDE does | What you have at the end |
|---|---|---|
| Find | Sits with the team, reads the tickets, listens to the calls, walks the systems with whoever owns them. Ranks the work by volume and by how automatable it really is. | A ranked list of what to automate first, with the reason for each, and what to leave alone. |
| Build | Builds the agents and automations on the Voho platform against your live systems, in your language and your vocabulary, with the permissions your people already have. | Working automations for the first workflows, tested on your own historical cases rather than invented ones. |
| Prove | Replays past cases and runs a slice of real work with approvals on. Fixes what breaks the same day, next to the people who found it. | Measured results on real work, and a team that has watched it improve rather than had it imposed. |
| Widen | Moves to the next workflow. Connectors, permissions and evaluations are already in place, so each one is faster than the last. | A growing set of automations on one governed platform, not a pile of disconnected pilots. |
What stays true on every engagement
- Your data stays where your policy says: in-Kingdom hosting, or on your own servers, including sites with no outbound internet.
- Agents inherit the access of the person using them. Nobody gets an answer they could not have looked up themselves.
- Every action waits for the approval you set. Nothing is raised, closed or paid without the step your process requires.
- Every step is logged: the request, the sources read, the action taken and who approved it.
- Arabic is first-class, not a translation layer. Engineers and callers can work in Najdi, Hijazi, Gulf Arabic or English, and switch mid-sentence.
When you do not need an FDE
Forward deployment earns its cost when the work spans several systems, the rules are partly unwritten, and there is a compliance function that will ask where the data lives. It is the wrong choice if you have an in-house engineering team that wants to own the build, or if the use case is a single task with a clean API behind it. For those, Voho is self-serve: an account comes with credit, and an agent can be built in the browser without a sales conversation.
We would rather say that at the start than bill for engineers you did not need.
Starting
Every engagement starts the same way: pick one workflow where the volume is real and the result is easy to measure, give an engineer access in the first week, and judge it on real work. If it works, the next workflow reuses everything the first one built. Book a working session and we will tell you honestly whether forward deployment is the right model for what you have in mind.
Frequently asked
- What is a forward deployed engineer (FDE)?
- A software engineer from the vendor who works inside the customer's organisation, next to the people whose work is being automated, building against the customer's real systems and staying until the system runs on real work. Unlike a consultant, an FDE writes production code; unlike a remote integrator, an FDE builds on site rather than to a specification.
- What do Voho's forward deployed engineers automate?
- Work that arrives as a request, a document or a record: contact-centre calls in Arabic dialect, IT and facilities service requests, back-office documents, HR requests, operational work orders and handovers, and recurring reports. They start with what is high-volume and rule-bound, and keep a person on anything that needs judgement.
- How is an FDE different from a systems integrator?
- A systems integrator usually builds remotely to a written specification and hands over at acceptance. An FDE works inside the operation, discovers the requirements that were never written down, and owns the outcome until it works on real traffic.
- Does Voho provide forward deployed engineers in Saudi Arabia?
- Yes. Voho's delivery team is on site at Aramco in the Eastern Province today, taking an AI call centre live, and forward deployed engineers work from the customer's own site across the Kingdom.
- When is an FDE not worth it?
- When you have an in-house team that wants to own the build, or the use case is a single task behind a clean API. Voho is self-serve for those cases.
Keep reading