Skip to content

Forward-deployed engineers

The engineers are the product

A forward-deployed engineer works on site at your plant, warehouse and front office, learns the work first-hand and builds for it. Software and AI agents are what our engineers build and leave running.

01 Who shows up

Who walks in on day one

The person who sits at your order desk on Tuesday 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.

What an engineer does, in 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.
  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.

Why they come in pairs

Discovery Sprint
2 forward-deployed engineers
Embedded Build
Typically 2 forward-deployed engineers
  • Two desks at once. One sits at the order desk while the other sits with purchasing.
  • A second pair of eyes. One asks the questions while the other writes down the steps and the screens. Later, each checks the other's code.
  • Nothing lives in one head. If one engineer is away, the other knows your workflows.
  • Release day needs both. One stays at the desk. The other watches the queue and the write-backs to the ERP.

What each engineer can do

  • 01

    Builds software end to end

    One engineer takes a workflow from a sketch to software your order desk uses: the screens, the queues, the rules, the connection to the ERP and the agent.

  • 02

    Reads an operation

    Follows an order from the customer's purchase order to the shipment and the invoice. Knows what a price list, a credit limit, a lead time and a cycle count are for.

  • 03

    Shadows without getting in the way

    Sits beside a buyer for a morning, asks why at each step and writes down what happens, not what the procedure says.

  • 04

    Works inside your systems

    Reads ERP data through the interfaces the ERP supports. Follows your IT team's rules and your change control.

  • 05

    Judges what not to automate

    Says when a workflow should stay at Level 2 (Prepared), with a person approving every transaction. Says when a piece of work is not fully digital at all.

  • 06

    Writes plainly

    The Operations Map has to make sense to the people it describes. They are the ones who check it.

02 Why on site

The work is not in a requirements document

We do not work from one. Our engineers sit with the order desk, walk the warehouse and stand at the scheduling board, because that is the only way to see the work as it is.

  • 1 Someone interviews the people who do the work and takes notes.
  • 2 The notes are written up as a requirements document.
  • 3 Developers who never saw the desk build from the document.
  • Our engineers sit at the desk and write the code. What the desk corrects goes into the next weekly release.
Fig. 1 Two routes from the work at the desk to the code.

What you only see from the desk

  • Second monitor

    The spreadsheet beside the ERP

    The part number cross-reference, the open-order list, the price exceptions. None of them is in a system diagram. All of them are open on the desk.

  • Someone's head

    The exception nobody wrote down

    Which customer always writes the wrong unit of measure. Which ship-to address needs a liftgate. The person who knows tells you while they fix it.

  • Phone

    The call about the late order

    Our engineers sit within earshot of the front office to hear it. A conference room on another floor defeats the purpose.

  • Order screen

    The correction, as it happens

    When your order desk changes a draft, the engineer is beside them to ask why. The corrections that repeat become next week's plan.

Engineers are on site by default in the Discovery Sprint and the Embedded Build. For a build, the on-site schedule is agreed before it starts. In Operate & Automate they come back for one on-site week per quarter.

03 The first week

Week one on your floor, day by day

This is week one of a Discovery Sprint, as the default plan has it. Before day one we move days to fit your shifts, your month-end close and the people who need to be in the room.

  1. Day 1

    Orientation, kickoff and one order end to end

    They take your safety orientation before anyone enters the floor, then hold a kickoff with the sponsor. Then they walk the floor and the front office, following one order from the customer's purchase order to the shipment and the invoice.

    They need The sponsor, your safety contact and someone to guide the walk.

  2. Day 2

    The order desk and customer service

    They shadow the people who take orders by email, EDI and phone, then the order-status questions that follow. The engineers split up, so both desks are covered at the same time.

    They need The people at those desks, doing their normal work.

  3. Day 3

    Purchasing and accounts payable

    They shadow your buyers as they release purchase orders and chase suppliers, and accounts payable as invoices are matched to purchase orders and receipts.

    They need Your buyers and accounts payable.

  4. Day 4

    Scheduling

    In a plant that is the scheduling board. At a distributor it is replenishment, receiving and returns.

    They need The scheduler or the warehouse lead.

  5. Day 5

    Systems, read access and the map walked back

    They list every system and spreadsheet with your IT manager or ERP administrator, and confirm that read access to the ERP data works. Then they walk the draft Operations Map back to the people they shadowed, who say where it is wrong.

    They need Your IT manager or ERP administrator, and the people who were shadowed.

What shadowing means

An engineer sits beside the person doing the work and watches the real thing: the purchase order PDF that lands in the customer service inbox, the screen it is keyed into, the spreadsheet that gets updated afterward.

The engineer asks why at each step. They measure the work, not the person.

What exists by Friday

  • A draft Operations Map, checked by the people it describes
  • A list of every system and spreadsheet the work runs through
  • Read access to your ERP data, confirmed to work

Then week two

They measure where the hours go and rank the workflows. Then they build a Working Prototype of the top one on your real data, run it beside the person who does that work today and present the findings at the readout on day 10.

04 What they need from you

What they need on day one

Seven things need arranging before the first morning. Everything else our engineers find out by sitting with your people.

Have ready

  • A sponsor with time on day 1, day 7 and day 10: the kickoff, the backlog review and the readout.
  • A shadowing schedule. Named people at the order desk, in purchasing, in accounts payable, in scheduling and in customer service, each told in advance who is coming and why.
  • Read access to your ERP data, with a named account for each engineer. It has to work by day 5, because week two counts from that data.
  • Real documents. Access to the shared inboxes and spreadsheets the work runs through, or copies of recent documents from them.
  • A place to sit in or next to the front office, with power and a network connection.
  • A safety orientation booked for the first morning, with a list of the protective equipment each area requires.
  • A written agreement on AI and data, made with your IT manager before day one: which AI model provider the Working Prototype may use and on what terms, and where our engineers' working copies and the prototype run. No document of yours reaches an AI model before that.

Not needed

  • A requirements document
  • A new ERP, an upgrade or a data cleanup first
  • Write access on day one. The Discovery Sprint runs on read access.
  • A full-time project team
  • AI expertise on your side
  • A commitment to all three stages

On your floor, under your rules

Our engineers follow your site rules the way any contractor does. They do not touch machines, material or product, and they take no photo without permission.

They work under named accounts that your IT team creates and can disable at any time, without asking us.

05 How this differs

Five alternatives, and how this differs

Each alternative does one part of this. Our engineers do all of it: they map the work, build the software and stay to run it.

How forward-deployed engineers compare, by category
Compared with What they do What our engineers do
Management consultants They deliver a report. We deliver working software and stay to run it. The Discovery Sprint ends with a Working Prototype on your real data, and the engineers who mapped the work are the ones who build it.
ERP resellers and implementation partners They configure the modules the ERP ships with. We build what the ERP does not cover, around it, and work alongside your partner. A change inside the ERP still goes through your change control, and your ERP administrator or your partner makes it.
Custom development shops They build to a specification you write. Our engineers write it themselves by sitting with your people. Nobody on your side writes a requirements document. Your workflow owner decides how the workflow should work and signs off each change.
AI tools A general tool your team has to adapt to. Our agents are built on your data, your rules and your exceptions. Each agent works one workflow, inside limits your workflow owner sets, in software built for that desk.
Hiring in-house Slow, and hard to recruit for. We start in weeks and can hand over to an in-house team later. You own the custom code, and a handover comes with documentation and runbooks. Where the software includes parts of our reusable tooling, your contract gives you the right to keep running and changing them after we leave.

What they are not

They are not your IT team. They do not administer your network, your accounts or your ERP, and they work under your IT team's rules.

They are not operators. They do not run machines or move material. They watch physical work to understand the digital work around it.

06 After the first week

Where the work goes from there

The first week is the start of a longer job. Each of these pages covers one part of it.

Next step

Start with a call with an engineer.

Tell us which ERP you run and the three workflows that hurt most. That is the whole first conversation.