What changes when a microfactory runs on its own system?
The whole chain, from demand to the shop floor, is instrumented in one system instead of a generic ERP template: per-piece costing, deterministic quoting, and a record of runs and incidents. IteraShop², our microfactory, works this way with 13 fabrication machines and 5 part families made to order.
Make it when it is ordered
IteraShop² is a digital microfactory built around make-to-order: a piece is produced when it is ordered rather than held in inventory. The floor combines CNC, 3D printing, and laser; the 13 fabrication machines are 11 FDM printers, 1 SLA printer, and 1 laser.
The output is real physical product, in 5 part families: lighting, branded tooling, automotive, marine, and industrial fixtures. Short-run, made-to-order work is exactly where a digital microfactory beats a warehouse.
- Fabrication machines: 11 FDM, 1 SLA, and 1 laser
- 13
- Part families, made to order
- 5
- Engines: market, product, and execution
- 3
- Processes, from market intelligence to delivery
- 11
An explicit value chain
The venture is organized into 3 engines (market, product, and execution) spanning 11 processes, from market intelligence to fulfillment and learning. The operating system instruments that chain as it is, instead of forcing it into a generic ERP template.
The practical difference: every process has its place in the system, and what happens in one is visible to the next. A piece's costing and its quote live in the same system as the run that makes it and the incidents it had.
Per-piece costing and deterministic quoting
Costing is parametric per piece: energy, labor, maintenance, and rework. That costing feeds a deterministic quote engine, meaning the same inputs always produce the same result. The price comes from a formula you can review, not from a generated answer.
- Per-part costingEnergy, labor, maintenance, and rework
- The systemDeterministic quoteSame inputs, same result
- Production runLogged in the same system, on the shop floor
- Incidents and learningOperator checklists
The floor and the agents in one system
Production runs, incidents, and operator checklists are tracked in the same system, deployed in the shop itself. The catalog and marketing pipeline is operated with AI agents, and a small team coordinates through version-controlled workflows.
Why it matters outside the shop
IteraShop² is deliberately the laboratory of IteraSystems: every pattern in our stack runs here before it ever reaches a client. Its status is in production, in-house. When we tell a client their operation can run on an agentic system, this is the existence proof.
For a client, that means what we propose has already run in a real operation before it reaches theirs.