Skip to content

The forward-deployed engineer

A forward-deployed engineer is an engineer who works on site at your business, learns it first-hand and builds for it. This page covers what the role is, the skills it takes, why our engineers come in pairs and what they are not.

The engineers are the product. The software and the AI agents are what they build and leave running. An engineer does four things, in this order:

  1. Goes on site and learns how your business really runs.
  2. Builds custom software around that work, attached to the ERP you already run. Where there is no usable ERP, the engineer builds an ERP-like core that you own.
  3. Adds AI agents that work for your employees first, then take over more of the digital work as each workflow earns it.
  4. Keeps going until fully digital work runs itself, with people setting the rules and checking the results.

The person who sat at your order desk on Tuesday is the person who writes the code on Wednesday. Nobody stands between the people who do the work and the people who build for it, and nothing gets rewritten into a requirements document on the way.

Engineers are on site by default in the Discovery Sprint and the Embedded Build, and they come back for one week each quarter in Operate & Automate. The work has to be seen where it is done: beside the person keying the order, not in a description of it.

Skill What it looks like on your floor
Building software end to end One engineer can take a workflow from a sketch to software the order desk uses: the screens, the queues, the rules, the connection to the ERP and the agent.
Reading an operation Following an order from the customer’s purchase order to the shipment and the invoice. Knowing what a price list, a credit limit, a lead time and a cycle count are for.
Shadowing without getting in the way Sitting beside a buyer for a morning, asking why at each step and writing down what happens, not what the procedure says.
Working inside someone else’s systems Reading ERP data through the interfaces the ERP supports. Following your IT team’s rules and your change control.
Judging what not to automate Saying when a workflow should stay at Level 2 (Prepared), with a person approving every transaction. Saying when a piece of work is not fully digital at all.
Writing plainly The Operations Map has to make sense to the people it describes.

The Discovery Sprint has two engineers, and an Embedded Build typically has two. There are four reasons.

  1. Two desks at once. While one engineer sits at the order desk, the other sits with purchasing. Five desks in one week do not fit one person.
  2. A second pair of eyes on everything. One asks the questions while the other writes down the steps and the screens. Each checks the other’s part of the Operations Map and, later, the other’s code.
  3. Nothing lives in one head. You already know what it costs when one person holds all the knowledge. If one engineer is away, the other knows your workflows.
  4. Release day needs both. One stays at the desk with the people using the change. The other watches the queue and the write-backs to the ERP.
They are not Because
Consultants who deliver slides The Discovery Sprint ends with a Working Prototype on your real data, not only with documents. The engineers who mapped the work stay to build it and run it.
Contract staff who take tickets They do not wait for a specification. They write it themselves by sitting with your people. The workflow owner decides how the workflow should work and signs off changes.
Your ERP partner They do not configure the modules your ERP ships with. They build what the ERP does not cover, around it, and work alongside your partner.
Your IT team They do not administer your network, your accounts or your ERP. They work under your IT team’s rules.
Operators They do not run machines or move material. They watch physical work to understand the digital work around it.