Forward Deployment Engineer
One workflow, running, on the system you already have.
For heads of finance, ops, or shared services whose people are still working around the ERP. This seat sits with those operators and leaves one workflow running in production.
The ERP is staying. The spreadsheet around it has to stop.
What the Forward Deployment Engineer owns
One workflow
A baseline for volume, cycle time, and cost, taken before the build.
The system of record
Automation on the ERP, finance stack, or ops stack that is live today. The system stays.
An operator
A named person on your side who can run the workflow after the milestone ends.
This is one person on a fixed milestone. The engagement ends. A systems integrator replacing the ERP is a different hire. So is a written plan that leaves the spreadsheet in place.
Where this seat sits
Business Process AI
Primary home. One workflow, a baseline, a running system.
ERP, on the system you run
The system of record stays. This seat is the person. The four situation pages stay the entry for the moment.
Product AI Engineer
A product the customer sells, and a feature in the path users hit, is the other seat.
Common questions
No. The ERP stays the system of record. This seat automates one workflow on it. A migration, a rip-and-replace, and custom ABAP or Apex are a different engagement.
No. During a freeze, a replacement quote, cutover data, and the work after go-live each have their own page. This seat is the person who does the work when the entry is the workflow rather than one of those four moments.
Then there is no engagement. The baseline needs the workflow and the data. A chatbot demo is not a substitute.
Leave one workflow running.
A 30-minute scoping call is enough to tell whether this seat is the entry, or whether Business Process AI should come with it.