Multi-site rollout
A repeatable deployment pattern across sites and regions, with site-level autonomy settings and group-level reporting.
Standardiseautonomy acrossevery plant.
One line proves it. One factory operationalises it. An enterprise agreement makes Duromex the way your group builds appliances — with custom models, a managed edge fleet, contractual SLAs and outcome-based terms.
Built for multi-site appliance groups
Refrigeration OEM · EU
Laundry OEM · North America
Cooking OEM · Turkey
Dishwashing OEM · Italy
Air-conditioning OEM · Asia
Tier-1 cabinet supplier
Design-partner programme, 2026. Duromex is pre-launch — partner identities are withheld under NDA and shown by segment, not by logo.
Beyond the Factory plan
Everything here exists because a group standardising on Duromex has problems a single plant does not.
Custom models
Dedicated product, line and quality models trained on your platforms rather than a shared baseline.
Managed edge fleet
A managed factory-edge GPU fleet with versioning, canary rollout, rollback and OTA updates across every plant.
Isolation and on-prem
Per-tenant scoping end to end, strict recipe IP protection, and a fully on-premises option for sensitive producers.
SLAs and support
Contractual uptime, response and escalation commitments with a named engineering contact.
Outcome-based terms
A share of measurable first-pass-yield, warranty, scrap and throughput improvement, for the workflows where value is unambiguous.
How a group goes from one line to a standard
Site zero
One plant, one line, one metric, in shadow then advisory. The reference that every subsequent site is sold against internally.
- Paid pilot with a written success metric
- Baseline published before any control
- Design-partner terms for the first cohort
Site expansion
Adjacent modules in the same plant, then the full loop, then the second plant on the same pattern.
- Shared edge runtime and identity
- Marginal cost of module two far below module one
- Group-level yield and warranty reporting
Fleet operations
A managed edge fleet across sites, with model rollout, canary and rollback handled centrally.
- Per-site autonomy authority
- Central model registry and versioning
- Regional data-residency controls
Standardisation
Duromex becomes the system of action: the audit trail of record, the recipe home and the encoded craft of the group.
- Recipe and quality dependencies consolidate
- Re-qualifying an alternative becomes the real cost
- Network benchmarks unlock as a premium tier
How enterprise agreements are structured
Price follows value, and the term follows the proof.
| Component | How it works | Why |
|---|---|---|
| Platform subscription | Tiered by line and factory across the group | Predictable base that scales with footprint |
| Usage | Per-unit, per-line or per-action metering above plan limits | Aligns cost with actual production volume |
| Outcome component | A share of measured first-pass-yield, warranty, scrap or throughput improvement | Puts our margin behind our claim |
| Add-ons | Dedicated models, on-prem, premium support, custom integrations | Depth where the group needs it |
| Annual prepay | 15–20% discount | Improves cash and retention on both sides |
| Multi-year | Usage ramps with committed expansion | Discounts traded for term length and case studies |
Who is allowed to change what
In a multi-site group, autonomy is a governance problem before it is a technical one. Duromex models authority explicitly: which agent, on which line, at which site, may write what — and who approves a change to that.
Every grant is revocable, every action is logged immutably, and the twin gates any change to a validated process.
Governance controls
- SSO/SAML/OIDC with role-based access control
- Per-site, per-line, per-workflow autonomy authority
- Approval workflows for authority changes
- Immutable, assurance-grade quality and safety audit log
- Twin validation as a mandatory gate
- Regional data-residency and on-prem options
The model behind an enterprise deal
$2.9M
modelled lifetime value at 135% NRR
$80k
blended enterprise CAC
<12 mo
target payback period
78%
target gross margin at scale
Modelled unit economics from the Duromex financial model. Pre-launch figures, not audited results.
The objections, answered
Every enterprise buying committee raises the same four. None of them are unreasonable.
Trust and accuracy
Shadow mode with a published accuracy gap against your own baseline, before any write access is discussed.
Quality and safety risk
Human checkpoints on high-impact decisions, fail-safe stop paths, twin validation and an immutable audit trail.
Change management
Graduated autonomy means the line changes at the speed the team accepts, not the speed the software allows.
Integration effort
Pre-built connectors for forming, paint, foaming, test, assembly and MES, with a deliberately narrow first workflow.
The same loop, in every plant
The reason multi-site works is that the loop is identical. What changes is the product, the equipment vendor and the local constraints — all of which are configuration, not a rebuild.
Form & stampWeld & seamEnamel & paintFoam & insulateWire & assembleLeak & function testRate & pack
What we sign up to
Enterprise agreements make these contractual.
99.9%
uptime target
1
named engineering contact per group
4
quarterly ROI reviews per year
100%
actions retained in the audit trail
What each approver needed to hear
“Our end-of-line functional testers told us what failed. They never told us which press stroke or foam shot caused it. That link is the whole product.”
“Foam voids are invisible until the energy rating comes back wrong. Predicting density distribution before the cabinet cures is the part I could not buy anywhere else.”
“If it writes to the press, it needs an audit trail a quality auditor accepts. Duromex started there instead of bolting it on.”
Procurement and rollout
Can we run entirely on our own infrastructure?
Yes. An on-prem option exists for sensitive producers. Cross-site learning is federated, so shared models improve without your recipes or quality data crossing a boundary.
What happens to our data if we leave?
Your data and, in enterprise agreements, model artefacts trained on it remain yours and are exportable. We would rather retention came from the loop working than from hostage-taking.
How do outcome-based terms actually get measured?
Against the baseline established in shadow mode, on a metric agreed in writing before the pilot, with the measurement method documented and auditable in the platform.
Do you support regional data residency?
Yes — through regional deployment and the on-prem option, with per-tenant scoping enforced throughout.
Make Duromex the way your group builds.
Start at one plant, on one line, with one number. Standardise from the proof.
Duromex is pre-launch. Figures shown are design-partner targets and modelled economics, not audited results. Ask us for the methodology.