Start with a repetitive process where a delay, or a wrong handoff, has a cost you can point to. Price updates, quoting, and order entry are useful candidates. Trace the data and the approvals. Set a baseline. Test one workflow with the people who do the work. Spej guidance: the best starting point depends on the business.
By Sean Blair, Co-Founder & Chief AI Officer, Spej | November 19, 2026
Pick the first workflow
| Workflow | Repetitive task | Required data | Human owner | Useful measure |
|---|---|---|---|---|
| Price updates | Find the products a component price change affects, and update those prices | Affected products and approved price records | The person who owns pricing | Time to finish an update, and pricing errors |
| Quoting | Prepare a quote from a request | Request details, current costs, and estimator approval | The estimator who approves the quote | Prep time and rework |
| Order entry | Enter customer orders | Customer orders, product records, and a path for exceptions | The person who owns order entry | Entry time and exceptions sent for review |
Spej guidance: choose a workflow that happens often, stays bounded, has a clear owner, and uses records the team can reach. Treat the rows as illustrations for a planning conversation. They are separate from the manufacturer case below.
Trace the handoffs and data
Find the records people trust
Map the route from the email or the spreadsheet into the business system. Name the price record or product record people already rely on. Check how fresh it is, and who is allowed to use it. Write down the exceptions. Systems the company already runs may be usable. Assess the integration and the quality of the data before you treat those systems as ready for the workflow.
Keep approval where it matters
Keep the work of preparing a draft separate from releasing a quote, changing a price, or entering an order. A person approves changes that affect a customer or a price. That person also handles missing information and records that conflict. Record the source and the person's disposition. Spej guidance: use this as a way to assign approval. Legal requirements belong with the company's own counsel.
NIST's February 1, 2025 summary of industrial AI research says available data should match real-world conditions and represent the full scope of the desired use cases. It lists incomplete data, inadequate data variation, and large gaps in data as common pitfalls. Use that as general guidance about industrial AI data. It does not describe the manufacturer case below. NIST on industrial AI data
The NIST AI RMF Core organizes AI risk management into govern, map, measure, and manage. It says processes for human oversight are defined, assessed, and documented. NIST describes the framework, and its playbook, as voluntary. NIST AI RMF Core
What happened in a manufacturer pricing workflow
A commercial plumbing and drainage manufacturer faced manual price updates after a component price change. Every component price change meant 3 to 5 weeks of manual updates. During that time, quotes and orders could carry outdated or incorrect prices. Spej built a system that identifies every affected product and updates its pricing using the manufacturer's existing business data. It was built around the systems the business already runs.
The case reports $300K+ returned so far. It reports 95% fewer pricing errors. Price updates went from 3 to 5 weeks to near real time. The case page states those results as published. This work was price updates. Quoting and order entry in the table above are illustrations, and they sit outside this case. Read the pricing case.
Test one workflow and measure the result
Spej guidance: baseline update time or prep time, along with errors, rework, and review effort. Test ordinary cases and exceptions against the approved records. Compare operating cost and the cost of keeping the workflow running. Agree what would lead you to continue, to change the workflow, or to stop. An existing tool can be enough when it meets the requirements. A custom build belongs in the plan when the gaps justify the cost and someone will own what gets built.
AI workflow redesign in manufacturing looks at mapping a process before a tool choice. AI implementation is the build work. Strategy and governance is where decision rights get written down.
Where AI falls short
- Outdated costs, incomplete product records, and unusual orders can produce a wrong output.
- Reviewers need current information, enough time, and the authority to send a draft back.
- Integrations and ongoing maintenance need an assessment of their own.
- One published case does not predict another company's savings.
FAQ
Where should a manufacturer or distributor start with AI?
Spej guidance: map a recurring process such as price updates, quoting, or order entry. Pick one with a clear owner, records the team can reach, and a baseline you can measure. Test representative work and exceptions with the people who do the job before you expand. The best starting point depends on the business.
Can AI help keep product prices current?
Spej built a system for a commercial plumbing and drainage manufacturer that identifies every affected product and updates its pricing using existing business data. The case reports 95% fewer pricing errors, and updates went from 3 to 5 weeks to near real time. Another business should assess its own data, rules, and approvals first.
Can AI prepare quotes or enter orders?
It may help extract request details and prepare a draft for a person to review. The team still needs current product and price records, a way to handle exceptions, and an authorized reviewer before a quote is released or an order is entered. Spej's cited case covers price updates. Quoting and order entry are separate illustrations.
Do we need to replace our ERP first?
The published manufacturer system used the manufacturer's existing business data, and it was built around the systems the business already runs. The case page does not name an ERP. Assess data access, interfaces, permissions, and maintenance for the specific workflow before you decide what to keep or change.
Bring one process to Spej
Bring a price update workflow, a quoting workflow, or an order-entry workflow to a conversation with Spej.
AI Roadmap is starting at $10K. Design & Build is starting at $20K. AI Office is starting at $10K a month. Scope determines the price.