Real customers,real engagements, real outcomes.
Each story is a working SPREAD deployment — what was built, who it serves, and what shifted in the daily work of the engineers using it. Filter to find the story closest to yours.
€20M+ a year, by shifting errors left on the SDV cost curve.
An error caught at architecture review costs almost nothing. Caught in the field, a thousand times more. SPREAD's job at the flagship electric platform is to shift errors leftward on this curve. €20M+ in annual savings is what that shift produces.
- Product Explorer
- Error Inspector
- Action Tower
Rework operators now answer questions that used to escalate to senior engineers.
At the lead plant for a new electric architecture, the rework operator scans the VIN and the system returns a VIN-specific Product Twin. Diagnostic resolution happens at the line instead of at the senior engineer's desk. Live since 2025; the workflow shift travels with the architecture, not the plant.
- Error Inspector
The same Twin runs the production line. Can it run program reviews too?
SPREAD's Production Inspector is already live on this OEM's lead-plant production line for the new electric architecture. The R&D pilot extends the same Twin to a second surface: the ontology that resolves faults at the line now compresses the weekly program review from status-collection to decision-making. The production side is the existence proof. The R&D surface is the second deployment.
- Action Tower
At an SDV launch, the customer named the deployment sequence before we did.
A premium SUV maker launching its software-defined vehicle program asked: "where does the bottleneck actually sit, and what do you build against it first?" Their program manager answered before we did. The triage team carries ~5,000 active defect tickets; time-to-develop-fix runs 3× every other lifecycle stage. Engagement is open under two named blockers, both procurement-engineering not technology.
- Error Inspector
- Ticket Analyzer
50 harness editors. 50,000 workshop technicians. One pipeline between them.
50 harness editors author the wiring data that 50,000 workshop technicians query VIN-specific on every electrical fault diagnosis, a 1,000× leverage point that has held across every procurement cycle since 2020.
- Ticket Analyzer
- Error Inspector
256,000 warranty claims, ranked by fraud likelihood instead of first-in-first-out.
Ticket Analyzer at the warranty-fraud surface of a premium automotive OEM. 256,000 claims processed in production. The reviewer queue shifts from FIFO to ranked. Roughly $2.5M annually per one-percentage-point fraud-detection lift at this scale.
- Ticket Analyzer
14 marques. One inherited SDV-toolchain bottleneck per brand. The same problem, fourteen times.
$190B group revenue. 270,000 employees. Fourteen marques across North America and Europe, two legacy OEMs merged into one. Every brand is running an SDV transition into the same inherited-toolchain bottleneck. The pattern in flight: a single engineering ontology making cross-brand component reuse traceable across that inherited complexity.
- Product Explorer
- Error Inspector
At a defense bid desk, the engineer's question changes shape: from searching to evaluating.
NATO procurement cadence is exogenous. The bottleneck is senior-engineer time, not procurement-process time. Requirements Manager shifts the bid engineer from search to evaluation: 20% faster time-to-market, +5% revenue uplift, weeks to days per RFQ.
- Requirements Manager
Defense engineering data is compartmentalized. The graph has to respect that.
On-premise knowledge graph across four national jurisdictions. The bid engineer queries from their clearance level; the graph returns candidates, confidence scores, and access state attached to each match. Search becomes evaluation.
- Requirements Manager
"Jetzt kommt die Killerfrage." The same architecture is already in production at another European land-systems prime.
On-premise, four national jurisdictions, audit-grade access controls layered into the data model itself, already in production at a peer European land-systems prime. The merged French-German prime evaluating Requirements Manager for its multi-variant armored-vehicle platform (six national customers) is the second instance of that working pattern, not a first-of-its-kind pilot.
- Requirements Manager
"Alleine dieses Konsolidieren setzt's mir momentan grade drei Monate an." Three months. Or one graph traversal.
The radar lead at a NATO supplier of rotating, non-rotating, and land radar systems on what currently costs three months of senior-engineer time: "Alleine dieses Konsolidieren setzt's mir momentan grade drei Monate an." The architecture that would collapse that cycle is already in production at a peer European land-systems prime, on-premise, across four national jurisdictions, audit-grade. Hensoldt-equivalent is another deployment of the same architecture, in radar. The structural argument the lead engineer raised in the same conversation, need-to-know access control (Berechtigungsverwaltung), is the structural question the architecture answers.
- Requirements Manager
- Product Explorer
- Action Tower
- Error Inspector
The day the customer corrected our business case: depth, not throughput.
A knowledge graph at a European rail OEM's bid desk: 5 plants, ~25 RFQs per year, ~13,000 engineering hours per RFQ. 55% of requirements cleanly covered, 37% partial, 8% net-new. The story is not the 55. It is the moment the customer reframed the engagement from a throughput tool to a depth tool.
- Requirements Manager
A tractor is a software-defined vehicle. Does the SDV ontology travel?
A dominant agricultural-machinery OEM, ~$2B annual R&D, asked: "if a tractor is now a software-defined vehicle, does the engineering data look like an automotive SDV program five years in?" Product Explorer is the cross-vertical thesis against five customer data sources: CAD, perception-stack lineage, calibration archives, fleet-operations telemetry, tribal knowledge.
- Product Explorer
Inside a defense-confidential pilot, the customer's own team named the next two use cases.
After a bounded Product Explorer pilot closed in a defense-confidential R&D program, the customer's own project team came back with two further use cases they had identified themselves, before any expansion conversation from our side. The pilot was deliberately narrow because the cost of a wrong tool decision in this regulatory regime (EMAR · AS9100 · FAA Part 21) is measured in program exposure, not procurement budget.
- Product Explorer
Can one ontology replace PLM + ERP + ALM + Excel + tribal knowledge, across six OEMs?
Global #1 in filtration and fluid management. €4.6B revenue. 22,500 employees. Six major European and Asian OEM relationships running in parallel. Each is a multi-million-euro annual revenue line. Each runs on data continuity reconciled by hand across PLM + ERP + ALM + Excel + tribal knowledge. The deployment runs one ontology at multi-OEM scale.
- Product Explorer
- Requirements Manager
- Action Tower
- Knowledge Agent
22M workshop tickets, each matched to the closest prior fix by technical similarity, not search.
Live tenant. 22M+ diagnostic-information-system tickets ingested on a daily LLM pipeline. The diagnostic application at the dealer technician's workstation surfaces closest prior resolutions, ranked by similarity. Mechanics fix issues 25% cheaper. Importer / OEM saves >€15M.
- Ticket Analyzer
A commercial vehicle isn't a car that's bigger. It's a different problem shape entirely.
A bus operator runs a unit for 15 to 20 years. A bus OEM carries hundreds of variants in active aftermarket because every regional fleet orders a different combination across six config axes: seating, climate, accessibility, drivetrain, doors, and telematics. Aftermarket revenue rivals new-vehicle revenue per platform. SPREAD's first commercial-vehicle test is a Product Explorer R&D engagement at the bus business unit of a European commercial-vehicle OEM, closed in March 2026. Passenger-car engineering ontology ingests commercial-vehicle variant-volume data on a bounded R&D use case.
- Product Explorer
- Error Inspector
- Action Tower
Production diagnostics moved to the line technician. 75% faster, every renewal cleared since 2020.
E/E Inspector replaces the generic schematic with a VIN-specific view at the workstation. Configuration filtering happens before the technician sees the schematic, not after. 75% faster troubleshooting at the line, ~€500k per line per year, holding across five years and multiple model generations.
- Error Inspector
Quote cycles compress from weeks to under one, on configurable industrial systems.
Requirements Manager configured for portfolio matching on a configurable product catalog: pumps, motors, hydraulic systems, control components. The bid engineer evaluates new RFQs against the product portfolio rather than past programs. 3x faster quotations, 30% less sales–engineering alignment effort, up to 5% revenue uplift from tighter conversion.
- Requirements Manager
No story matches this filter combination yet. Try widening one of the chips.
Ready to be next?Map your numbers in 20 minutes.
Book a working session.
We will trace one of your real engineering questions through your systems and show where the numbers come from.