Software for the companies that build physical things. Manufacturers, equipment OEMs, mechanical and interdisciplinary engineering firms — businesses where a product is not a SKU but a configuration tree, where a quote depends on twelve PDFs, and where the customer expects the same catalog in four languages with revision-controlled specs. We design platforms that preserve that complexity — instead of flattening it into spreadsheets and PDFs. Architecture-first, multilingual by default, integration-aware — and compatible with the ERP, PLM and document systems already in place.
Most of our industrial engagements start at the same friction point: a website that no longer represents the product, a catalog scattered across Excel, PIM and PDF, a quoting process that lives in three inboxes. We rebuild the digital surface around the actual engineering reality, not around marketing assumptions.
Public-facing platforms for industrial manufacturers — multilingual product catalogs, structured technical documentation, lead and inquiry flows integrated into ERP and sales processes. Built to handle deep product hierarchies (series → variant → configuration → spec sheet) without breaking under SEO or translation load.
Multilingual catalogs and spec packages for machinery and equipment OEMs. Versioned datasheets, controlled document delivery, distributor-aware pricing logic, and a content model that survives ten years of product evolution — with controlled evolution of product structures and backward compatibility.
Product configurators for engineered-to-order businesses — rules, dependencies, validation, CAD/spec output, hand-off to sales and ERP. The configurator is not a form; it's a constrained model of your product with deterministic outputs and integration into ERP and production workflows. We design it as one.
Internal and client-facing platforms for interdisciplinary engineering firms and consultancies — project portfolios, governance and compliance workflows, structured deliverables, controlled access for clients and partners.
Industrial software fails in patterns that look familiar across machinery, equipment OEMs and engineering firms. These are the five we see on first contact.
Each system holds its own version of a series. The catalog says one thing, the PDF datasheet says another, the ERP order configuration says a third. Outputs to customers are inconsistent — and they notice.
Without rules, dependencies or validation, a configurator produces invalid or unbuildable products. Sales accepts the order; engineering rejects it; the customer waits.
Outdated datasheets and specs ship to clients because the controlled document never reached the website. Internal drafts overwrite released versions; revisions are reconstructed from email threads.
Quotes pass through three inboxes, two spreadsheets and one CAD viewer. Deals get lost or delayed; the same configuration takes a different price depending on who quotes it.
Translations bolted on after the fact, no translation memory, no revision linking. Maintaining four languages means rewriting four sites — and inconsistencies become permanent.
German and EU Mittelstand manufacturers, equipment OEMs (mechanical, process, packaging, measurement), engineering and planning consultancies. Companies where product complexity drives the sales process — not marketing pages. Often modernising existing systems rather than starting from zero — see also our Mittelstand Modernisation track.
The platform we build sits in front of your ERP and PIM, not on top of them. ERP holds the source of truth for orders and stock, PIM holds product data, and our layer is the customer-facing and integration surface — multilingual catalog, configurator, quote engine, document delivery. The goal is to extend what you already have, not replace it.
Yes — that is the case we design for. The configurator is implemented as a constrained model with rules, dependencies and validation, not as a long form. It produces a structured output (CAD attributes, BOM, datasheet, quote) that is consumable by ERP and sales systems.
Multilingual is treated as an architectural decision from day one. Translation memory, fallback rules, locale-specific units and regulations, and translation workflows that preserve revisions on datasheets and specs. We do not retrofit translation onto a single-language system.
Every controlled document — datasheet, certificate, manual — has a version, an approval state and an audit trail. Distributors and customers always receive the released version; internal teams can work on drafts in parallel without breaking the public surface.
After the 5-day Architecture Sprint, a first production release is usually 3–5 months. Phased rollout — public catalog first, configurator and quoting second, deeper ERP integration third — is the default for Mittelstand clients, so operations stay live throughout.
Five days. €3,500. We map your existing systems, name scaling and integration risks, and hand over a roadmap you can deliver with us or with your own team.
