Start with a metric, not a demo
The most useful first conversation is about one number on one line: cure cycle time, splice-related scrap, escape rate, or hours lost to recall scoping. Tell us the number and we will tell you whether we can move it.
Teams we usually talk to
Reach the right team directly
Sales and pilots
Plant assessments, paid pilots, pricing and multi-site rollouts.
hello@treadum.com
Security and compliance
Security packs, architecture review, penetration test summaries and DPAs.
security@treadum.com
Customer support
Existing deployments, incidents and escalations, routed by severity per your SLA.
support@treadum.com
Partnerships
Equipment makers, inspection vendors, integrators and platform partners.
partners@treadum.com
Careers
Applications, speculative introductions and referrals for open roles.
careers@treadum.com
Press and analysts
Briefings, category questions and fact-checking on published claims.
press@treadum.com
What happens after you send this
- Reply: A real engineer or founder reads it and replies within two business days. Not a sequence.
- Scoping call: Forty-five minutes on the line, the constraint, the current baseline and the systems in place.
- Plant walk: One to two days on site, mapping data availability, sensing gaps and the highest-value wedge.
- Written proposal: A scoped pilot with a single primary metric, a baseline method and explicit success criteria.
- Decision: You decide. If we do not believe we can hit the metric, we say so instead of selling a pilot.
How to make the first call count
Five inputs that make scoping fast
You do not need a data project to talk to us. But the more of this you can bring, the faster we can tell you whether a pilot is worth running.
- One primary metric and its current 90-day baseline
- Which processes are in scope: mixing, building, curing, inspection
- What inspection equipment exists and whether its output is stored
- What MES, historian and PLC systems are in place
- Who signs off on a change to a press setpoint
Where we are
Amsterdam, Netherlands
Engineering, autonomy and platform teams. EU data residency available for all deployments by default.
[PLACEHOLDER] Registered address published once incorporation completes.
Wherever your plant is
Forward-deployed engineers travel to sites for assessments, deployments and gate reviews across Europe, North America and Asia.
Two business days
For every inbound request, including ones we decline. Silence is not a tactic we use.
EN · NL · DE · FR
Operator-facing surfaces localize further per deployment; the console ships with per-site language packs.
24/7 for production
Existing deployments have a severity-based escalation path with contractual response times.
What to expect by request type
| Request | First response | Typical next step |
|---|---|---|
| Plant assessment | 2 business days | Scoping call within 10 days |
| Paid pilot | 2 business days | Written proposal within 3 weeks of plant walk |
| Enterprise / multi-site | 1 business day | Architecture and security review scheduled |
| Security pack request | 2 business days | NDA, then pack delivered |
| Production incident (existing customer) | Per SLA severity | Escalation path and status channel |
| Press or analyst | 3 business days | Briefing scheduled |
What partners say about the first 90 days
“We had three people watching X-ray images and still shipped uniformity rejects. Treadum flagged the cord shift at the building drum, not four hours later at final inspection.”
“The cure agent found 40 seconds of margin on a construction we had run the same way for eleven years. It proved it in shadow mode before it touched a press.”
“Genealogy is the part I did not expect to care about. Every tire now has a linked record from batch to grade, and audit prep went from weeks to an afternoon.”
[PLACEHOLDER] Design-partner quotes are illustrative until pilot references are published.
How engagements typically run
Before you reach out
An engineer or a founder. The first technical conversation is with someone who can answer questions about sensing, envelopes and integration without scheduling a follow-up.
Almost nobody is, and that is fine. Part of the plant walk is establishing what exists, what is recoverable and what needs new sensing. Data readiness is an output of the assessment, not a prerequisite for it.
Yes. The Cell tier is scoped exactly for that, and it is how most deployments start.
Yes, routinely, and we sign yours rather than insisting on ours.
On this demo site, no — it is a static page with no backend. Email hello@treadum.com and you will reach a person.
Put one cell on autonomy in 90 days
Pick one wedge — splice inspection, X-ray defect detection, cure-state optimization or uniformity prediction. We baseline it, run shadow mode, then graduate to bounded autonomy under a signed control envelope.
Pilots start in shadow mode. No line changes until accuracy and safety gates pass.