What we need from you
An engagement depends on seven things from you: a sponsor, workflow owners, access to the floor and the offices, read access to the ERP and its data, a place to sit, a safety orientation and decisions within a week. This page explains each one, then lists what we do not need.
At a glance
Section titled “At a glance”| What we need | Needed by | Who provides it |
|---|---|---|
| A sponsor | Before the Discovery Sprint is scheduled | The owner, CEO, COO or VP of operations |
| Workflow owners | Before the Embedded Build starts | Named by the sponsor |
| Floor and office access | Day 1 of the Discovery Sprint | Plant manager or warehouse manager |
| Read access to the ERP and its data | Requested before day 1, working by day 5 | IT manager or ERP administrator |
| A place to sit | Day 1 | Whoever runs the front office |
| A safety orientation | The first morning, before anyone enters the floor | Your safety contact |
| Decisions within a week | Throughout | Workflow owners and the sponsor |
A sponsor
Section titled “A sponsor”The sponsor is one executive who owns operations and wants the work done. In most companies that is the COO or VP of operations. In a smaller one it is the owner or CEO. The sponsor:
- Names the workflow owners.
- Sets the order of the Automation Backlog.
- Clears access with IT and with the plant or warehouse.
- Settles decisions that cross departments, such as who releases an order on credit hold.
During the Discovery Sprint the sponsor attends the kickoff, the backlog review and the readout. During the build the sponsor reads the weekly update and acts on the decisions it lists.
Workflow owners
Section titled “Workflow owners”Each workflow gets one workflow owner: a named employee of yours who decides how the workflow should work and signs off changes to it. Pick the person who knows the work, not the person with the most free time. It is often the manager of the desk and sometimes its most experienced member.
| Workflow | A typical workflow owner |
|---|---|
| Sales order entry | Customer service manager, or the senior person at the order desk |
| Purchasing and supplier follow-up | Purchasing manager |
| AP invoice matching | Controller or accounts payable lead |
| Production scheduling support | Production scheduler or plant manager |
A workflow owner plans with our forward-deployed engineers each Monday, answers questions during the week and signs off each release. Later the same person signs off promotion reviews.
Floor and office access
Section titled “Floor and office access”Our engineers need to walk the plant or warehouse and to sit where the work is done: at the order desk, in purchasing, in accounts payable, at the scheduling board, with customer service. The people at those desks need to know in advance who is coming and why. Site conduct and safety covers how our engineers behave once they are there.
Read access to the ERP and its data
Section titled “Read access to the ERP and its data”Each engineer needs a named, read-only account that reaches the ERP data: orders, items, customers, suppliers, purchase orders, invoices. They also need to see the spreadsheets and shared inboxes the work runs through.
Read access is enough for the whole Discovery Sprint. Write access is requested later, one workflow at a time. Access and credentials covers how.
Before day one we also agree in writing with your IT manager on two things: 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.
A place to sit
Section titled “A place to sit”A desk or a table within earshot of the front office, with power and a network connection. A conference room on another floor defeats the purpose. The engineers are on site to hear the phone call about the late order.
A safety orientation
Section titled “A safety orientation”The same orientation you give any contractor, before the first walk on the floor. Send us the list of protective equipment each area requires ahead of time.
Decisions within a week
Section titled “Decisions within a week”When our engineers bring a question that needs a decision, they need the answer within a week. The build releases every week, so a question that waits longer holds up a release. Typical questions:
- Should an order be held when the purchase order price is below the price list?
- Which suppliers may an agent email without a buyer reading the message first?
The workflow owner decides what sits inside the workflow. The sponsor decides what crosses departments. Open decisions are listed in the weekly update with the date they were asked.
What we do not need
Section titled “What we do not need”- A requirements document. Our engineers write down how the work runs by sitting with the people who do it.
- A new ERP, an upgrade or a data cleanup first. The ERP you already run stays the system of record. The Systems and Data Audit records how clean the data is, and the plan starts from there.
- Write access on day one. The Discovery Sprint runs on read access.
- A full-time project team. Shadowing happens while the work is being done, and a workflow owner does the role alongside their normal job.
- AI expertise. Nobody on your side needs to know how an AI model works. A workflow owner needs to know the workflow.
- A commitment to all three stages. You can stop after any stage.