We send engineers in.
They automate the work.
Voho's forward deployed engineers work inside your organisation, find the work worth automating, build AI into the systems you already run, and stay until it runs on real work. Not a report. Not a login and good luck.
On site now
Our delivery team is on site at Aramco, taking an AI call centre live.
A smart-city call centre for 100,000 residents, delivered to Aramco's procurement and security bar, by the same forward deployed model described on this page.
What an FDE is
An engineer on your side of the table.
A forward deployed engineer writes and ships production code, but does it inside your operation: next to the people whose work is being automated, against your systems rather than a demo. The value of AI is in the rules nobody wrote down, and those are found by being there.
| Consultant | Systems integrator | Voho forward deployed engineer | |
|---|---|---|---|
| Main deliverable | Strategy and roadmap | System built to specification | Automation running on real work |
| Who builds | Someone else, later | Delivery team, mostly remote | The engineer who did discovery |
| Unwritten rules | Documents some | Only if specified | Discovered on site and built in |
| Ends at | Report delivered | Acceptance | Measured results on live work |
What they automate
Wherever work arrives as a request, a document or a record.
The rule is simple: automate what is high-volume, rule-bound and already recorded; keep a person on anything that needs judgement; make every automated step visible and reversible.
Contact centre
Calls answered and resolved in the caller's dialect; tickets and bookings written into the real system; warm handover with the transcript.
IT and facilities service desk
Requests by phone, chat or email, classified and raised in ServiceNow, Maximo or Archibus without re-keying.
Back office
Invoices, claims, applications and contracts read, checked against the record and routed.
HR
Policy questions answered from the handbook; leave, letters and onboarding raised and tracked.
Field and plant operations
Work orders drafted from alarms and inspections; shift handovers from the log; manuals answerable with citations.
Management reporting
Recurring reports assembled from the systems that hold the numbers, with the sources attached.
How an engagement runs
One workflow, proven on real work, then the next.
Start where the volume is real and the result is easy to measure. Give an engineer access in the first week. Judge it on real work.
- 01
Find
Sit with the team, read the tickets, listen to the calls, walk the systems with whoever owns them. Rank the work by volume and by how automatable it really is.
A ranked list of what to automate first, and what to leave alone.
- 02
Build
Build the agents and automations on the Voho platform against your live systems, in your language and vocabulary, with the permissions your people already have.
Working automations, tested on your own past cases.
- 03
Prove
Replay past cases, then run a slice of real work with approvals on. Fix what breaks the same day, next to the people who found it.
Measured results on real work.
- 04
Widen
Move to the next workflow. Connectors, permissions and evaluations are already in place, so each one is faster than the last.
One governed platform, not a pile of pilots.
On every engagement
Fast on site. Strict about control.
Forward deployment is how the work gets done quickly. These are the lines it never crosses, whichever team or industry the engineer is working in.
- Data stays where your policy says: in-Kingdom hosting or your own servers, air-gapped included.
- Agents inherit the access of the person using them.
- Every action waits for the approval your process requires.
- Every step is logged: request, sources, action and approver.
- Arabic is first-class: Najdi, Hijazi, Gulf Arabic and English, mid-sentence switching included.
- Read-only to control and safety systems, always.
When you do not need one
We will tell you at the start.
If you have an in-house team that wants to own the build, or the use case is one task behind a clean API, you do not need engineers on site. Voho is self-serve for that: an account comes with credit, and an agent can be built in the browser without a sales conversation.
Further reading
How we think about forward deployment.
- Forward deployed engineers: how Voho puts AI to work across the whole enterprise
- What a forward deployed engineer automates, department by department
- Forward deployed engineers vs consultants vs systems integrators
- Forward deployed engineers in oil and gas
- Why we send an engineer to sit in your contact centre
- المهندسون الميدانيون: كيف يضع Voho الذكاء الاصطناعي في العمل
What teams ask before an engineer arrives.
If your question is not here, book a working session and ask the engineer.
01What is a forward deployed engineer (FDE)?
A software engineer from Voho who works inside your organisation, next to the people whose work is being automated, building against your real systems and staying until the automation runs on real work. Unlike a consultant, an FDE writes production code; unlike a remote integrator, an FDE discovers the unwritten requirements on site and builds them in.
02What 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. Judgement, liability and rare cases stay with a person.
03Where do Voho's forward deployed engineers work?
From the customer's own site. Our delivery team is on site at Aramco in the Eastern Province today, taking an AI call centre live, and works across Saudi Arabia and the Gulf.
04Does our data leave our network?
Not unless you want it to. The platform and the models can run in a Saudi cloud region or on your own servers, including sites with no outbound internet.
05When do we not need an FDE?
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: an account comes with credit and an agent can be built in the browser.
06What do we need to provide?
Access to the systems the workflow touches in the first week, real examples of the work including the difficult ones, one person who knows how the work is really done, and a decision-maker for what the automation must never attempt.