Forward-deployed engineering for manufacturers and distributors
We put engineers on your floor.
Neutron Technologies puts engineers on your floor. They learn how your business runs, build the software it is missing around the ERP you already have, and hand the digital work to AI agents one step at a time.
- 1 An engineer sits with the order desk.
- 2 An engineer stands at the scheduling board.
- Both walk the warehouse.
01 The work around your ERP
The real work happens around your ERP
Your ERP holds the transactions. Getting them in, checked and out again happens in spreadsheets, shared inboxes, phone calls and people's heads. That is the work our engineers go and find.
Shared inbox
The purchase order PDF someone re-keys
A customer emails a purchase order. Someone at the order desk types every line into the ERP, then checks the prices against a spreadsheet.
Excel
The quote built from an old quote
A request for quote comes in. The quote gets built in Excel from past quotes and a price list, and reaches the ERP only if the customer says yes.
Spreadsheet
The open-order list your buyers keep
Purchasing tracks late purchase orders in a spreadsheet of its own, and chases suppliers by email and phone.
Paper
The supplier invoice that does not match
Accounts payable holds each invoice against the purchase order and the receipt by hand, then walks the mismatches down the hall.
Whiteboard
The schedule the floor really follows
The ERP has a production schedule. The one that runs the plant is on a board, kept current by the one person who knows every job.
Phone
The call asking where an order is
Customer service looks in the ERP, the shipping log and somebody's memory before they can answer.
02 How an engagement works
Three stages. You can stop after any.
It starts with a fixed-fee Discovery Sprint. You keep everything it produces, whether or not you continue.
-
Stage 01
Discovery Sprint
Two engineers spend two weeks on your floor and in your front office. They map how the work really gets done and show the first automation working on your own data.
$25,000 fixed fee
- Duration
- 2 weeks on site
- Team
- 2 forward-deployed engineers
You get
- Operations Map
- Systems and Data Audit
- Automation Backlog, ranked
- Working Prototype of the top workflow, on your real data
-
Stage 02
Embedded Build
Engineers work alongside your team and ship working software every week, starting from the top of the Automation Backlog.
$32,000 per engineer per month
- Duration
- Typically 3 to 6 months, with a 3-month minimum
- Team
- Typically 2 forward-deployed engineers
You get
- Software built around your workflows and attached to your ERP
- A release to the people who use it, every week
- Agents introduced workflow by workflow, starting at the lower levels of the autonomy ladder
-
Stage 03
Operate & Automate
We run, monitor and support the software and the agents, and move each workflow up the autonomy ladder as it earns it.
From $9,000 per month
- Duration
- Monthly, after the build
- Team
- Your engineers stay on call, with one on-site week per quarter
You get
- Monitoring and support for the software and agents
- Promotion reviews that move workflows up the autonomy ladder
- One on-site week per quarter
Other terms
- Travel is billed at cost.
- AI model usage is billed at cost.
- You own the custom code and the data built for you. We keep our reusable tooling, and you keep the right to run and change the copy inside your software.
03 The engineers
In the first week they learn how you work
Our forward-deployed engineers do not work from a requirements document. They 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.
-
Walk the floor and the front office
They see where orders arrive, where material moves and where the paper piles up.
-
Shadow the people who do the work
The order desk, purchasing, accounts payable, scheduling and customer service, one desk at a time.
-
Map how orders, materials and money move
Step by step, with the spreadsheets, inboxes and workarounds that nobody wrote down.
-
List every system and spreadsheet
What data each one holds, how to get it in and out, and how clean it is.
-
Get read access to your ERP data
So that the second week can measure where the hours go and build a prototype on real data.
04 What we build
Software around the ERP you already run
Your ERP stays the system of record. We build what it does not cover, around it. Nobody has to replace their ERP to work with us.
-
Agent layer
AI agents that work the queues in the operations layer, under the autonomy ladder.
-
Operations layer
Software built for you around your workflows: screens, queues, rules and integrations. This is where your people handle exceptions.
-
System of record
Your ERP and other core systems. It stays the source of truth. We read from it and write to it only through interfaces it supports.
The software attaches to the ERP you already run, such as SAP Business One, Oracle NetSuite, Microsoft Dynamics 365 Business Central, Epicor, Infor, Sage, Acumatica, SYSPRO, QuickBooks Enterprise, or whatever you run. Where there is no usable ERP, the operations layer includes an ERP-like core that you own.
05 The autonomy ladder
Agents earn autonomy one level at a time
An agent starts by helping your employees. A workflow moves up only after it has shown it can be trusted, and it can always be moved back down.
-
Level 0 Recorded
People do the work. The software captures it as structured data.
-
Level 1 Assisted
People do the work. Agents draft, summarize and answer questions.
-
Level 2 Prepared
Agents prepare each transaction in full. A person approves every one.
-
Level 3 Supervised
Agents complete the work within set limits. People handle exceptions and spot-check.
-
Level 4 Autonomous
Agents run the workflow end to end. People set policy and audit.
- A workflow moves up one level at a time, and only after a promotion review.
- The workflow owner can move it down a level at once.
Where it stops
Not every workflow should reach Level 4 (Autonomous). Some stay at Level 2 (Prepared) or Level 3 (Supervised) for good, and that is a fine result.
The ladder applies to fully digital work: emails, documents and ERP transactions. Agents do not do physical work and do not operate machinery.
06 Workflows
The workflows we take on, today and after
Each of these is fully digital work that sits around an ERP at a manufacturer or a distributor. The After line on each card names the level it describes.
Illustrative example
Each card describes a typical case, not a specific client.
-
Manufacturing
Sales order entry
- Today
The order desk re-keys emailed purchase orders into the ERP, line by line.
- After
At Level 2, an agent reads the purchase order and builds the sales order. The order desk approves it.
-
Manufacturing
Quoting
- Today
A request for quote waits in an inbox while someone digs out costs and old quotes.
- After
At Level 1 (Assisted), an agent drafts the quote from your price list and past quotes. Your estimator checks it and sends it.
-
Manufacturing
Purchasing and supplier follow-up
- Today
Buyers chase late purchase orders by email and phone, from a spreadsheet they keep themselves.
- After
At Level 3, an agent asks suppliers for confirmed dates, updates the purchase order and flags the ones that will be late.
-
Manufacturing
Production scheduling support
- Today
The scheduler rebuilds the plan in a spreadsheet each time a job slips or material runs late.
- After
At Level 3, an agent keeps the shortage list and the late-job list current. A schedule change stays at Level 2: the scheduler approves every one.
-
Manufacturing and distribution
AP invoice matching
- Today
Accounts payable matches every supplier invoice to its purchase order and receipt by hand.
- After
At Level 2, an agent matches the three documents and prepares the clean ones for approval. Mismatches go to a person.
-
Distribution
Replenishment
- Today
A buyer reads stock reports and reorder points, then types up purchase orders one by one.
- After
At Level 2, an agent proposes the purchase orders from stock, demand and lead times. The buyer reviews and releases them.
-
Distribution
Returns
- Today
A return means a chain of emails, a hand-keyed authorization and a credit somebody has to remember.
- After
At Level 2, an agent prepares the return authorization and the credit, with the original order attached, for a person to approve.
-
Manufacturing and distribution
Order-status questions
- Today
Customer service looks in three places before they can say where an order is.
- After
At Level 3, an agent answers emailed status questions from ERP and shipment data. Anything unusual goes to customer service.
07 How we compare
Not a consultancy, not a software vendor
We do not hand you a report or a login. Our engineers build working software on your floor and stay to run it.
| Compared with | What they do | What we do |
|---|---|---|
| Management consultants | They deliver a report. | We deliver working software and stay to run 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. |
| Custom development shops | They build to a specification you write. | Our engineers write it themselves by sitting with your people. |
| AI tools | A general tool your team has to adapt to. | Our agents are built on your data, your rules and your exceptions. |
| Hiring in-house | Slow, and hard to recruit for. | We start in weeks and can hand over to an in-house team later. |
08 Questions
Questions to ask us first
Do we have to replace our ERP?
No. Your ERP stays the system of record, and we build what it does not cover, around it. We read from it and write to it only through interfaces it supports.
Where there is no usable ERP, our engineers build an ERP-like core that you own.
What happens to the people who do this work today?
The digital work does get automated, step by step. The people who do it today decide how it should work, approve what agents prepare, handle the exceptions and audit the results.
Their knowledge is what the software is built from. Each workflow has a workflow owner: one of your employees, who decides how it should work and signs off changes.
The hours that keying took are measured and shown to you, and what your team does with them is your decision.
How soon is something running?
The Discovery Sprint is 2 weeks on site. By the end of it, a Working Prototype of your top workflow runs on your real data. It is a prototype: it shows what the workflow can look like on your data, and it is not yet software to run a desk on.
In the Embedded Build, our engineers release working software to the people who use it every week.
Who owns the software?
You own the custom code and the data built for you. We keep our reusable tooling, and you keep the right to run and change the copy inside your software.
What if we stop?
You can stop after any stage. The four Discovery Sprint deliverables are yours whether or not you continue: the Operations Map, the Systems and Data Audit, the Automation Backlog and the Working Prototype.
If you stop later, the custom code and the data built for you stay with you, and an in-house team can take over. Where that software includes parts of our reusable tooling, your contract gives you the right to keep running and changing them after we leave, with no license fee.
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.