The fleet you have
Mixed naming conventions across decades of acquisitions, CMMS migrations, and supplier portals. "ATLAS 90kW VSD #2" in one row, "Atlas Copco Compressor" in another, "kompressori 90 kW" in a third — all the same machine.
InRecipe.AI turns messy equipment, parts, and item-master records into structured, verifiable data — and into the business outcomes that clean data finally unlocks. An industrial-services customer's contract-pricing ML model gained 50% accuracy. A mining OEM enriches a parts master that powers four downstream systems. A marine manufacturer's procurement and customs flows run from one trusted source.
Industrial companies sit on equipment, parts, and item-master databases they can't fully trust. The same Atlas Copco compressor appears four ways. Parts catalogs have the same SKU under five names. Item masters arrive at production planning with blanks where there should be cost, lead time, and HS code. And every analytics or pricing or compliance initiative downstream assumes clean inputs that don't exist.
Mixed naming conventions across decades of acquisitions, CMMS migrations, and supplier portals. "ATLAS 90kW VSD #2" in one row, "Atlas Copco Compressor" in another, "kompressori 90 kW" in a third — all the same machine.
A data steward in Excel, working through 2,000 records by hand. Different stewards produce different answers. The work is invisible until something downstream breaks. Industrial companies hire more headcount to do the same job, slower.
Predictive maintenance, contract pricing, procurement automation, customs compliance, ESG reporting, M&A integration — all of them assume clean equipment or parts data. None of them get it.
InRecipe.AI is an enrichment layer that sits between your raw industrial data and the systems that depend on it. You upload a CSV, connect a CMMS export, or feed an item master. InRecipe runs your records through a recipe — a manifest of skills built specifically for industrial data.
Each skill knows something specific. One cleans device or part names. One resolves manufacturers against a curated catalog. One extracts technical specs from model numbers using manufacturer-specific patterns. A fourth classifies each record into industry-standard taxonomies. Skills compose; the recipe orchestrates them.
You don't build the recipe. You don't train the model. But the pack for your industry - Industrial Air, Mining Spare Parts, Marine Equipment - gets built with you: your data and edge cases drive the catalogs and patterns, and you inherit what earlier customers in your vertical already built. It gets smarter every release, across every customer in the vertical.
Every record takes the same auditable path. What runs is declared up front in a recipe you sign off on. Each skill reads real sources and emits a value with its evidence. A validator checks every claim before it reaches your database. Nothing enters on the model's word alone.
Compair L15-10A K1 screw compressorDeclares which skills run and which fields are in scope: the surface you sign off on before a single record is touched.
Each does one thing - resolve a manufacturer, extract a spec, classify a code - reading real sources and emitting a value with its evidence.
Checks every claim against its cited source: right source, allowed evidence, confidence within that source's ceiling. Any check fails, the value is rejected.
Clean master data isn't the goal - it's the unlock. The same enriched record moves margin, speeds procurement, and de-risks compliance: the initiatives you already want to run but can't, because the inputs aren't there. Here is what it frees up.
Quote maintenance and contracts on the equipment that's actually installed, not on guesswork. Loss-making options stop hiding in the ERP, and every quote is defensible.
Proven: +50% pricing-model accuracyComplete item and parts data means new models reach the sales configurator on time, and teams stop chasing the same missing facts. One clean-up unblocks design through after-sales at once.
Proven: 6,000 stuck items, 7 teamsHS codes and country of origin resolved and cited against the regulatory reference, so cross-border shipments are classified right. The importer carries the liability; the evidence is the defense.
Checked vs TARIC / FINTARICInRecipe.AI doesn't just clean data. It unlocks the value that bad data was blocking.
The proof isn't a benchmark - it's the work itself. InRecipe is live and in pilot across industrial air, mining, and marine today, on real registers: three pack shapes - devices, parts, and item-masters - one method. Customers are named anonymously here; every figure is real.
An industrial services company maintaining compressed-air devices for B2B customers. Maintenance contracts priced via an internal ML model. Before InRecipe.AI: a device register with mostly missing or inconsistent structured data.
"What used to take a dedicated person months took us three hours, with documented evidence on every field."
A mining heavy-equipment OEM with an enormous parts catalog. Their pain isn't device data — it's parts data, with fields that aren't on any manufacturer spec sheet: classification, change interval, stocking strategy, critical-spare flag.
Enrich the parts master once, and four business processes light up — sales recommendations, the webshop, service planning, and proprietary-parts onboarding.
A boat manufacturer. A 6,000-item master across 10 product groups — hull and deck hardware, marine electrical, piping, HVAC, propulsion, composites. Before InRecipe.AI: items reached production planning with blanks where there should be HS code, weight, dimensions, origin.
AI does the manufacturer-source research your buyer would otherwise do — and tells you when it can't.
The model never returns a bare value. It returns a value, a citation, and one of three honest outcomes - each checked by code before it reaches your database.
Taken from a manufacturer source with a citation that points back to it. The highest-trust result.
Searched, and nothing trustworthy turned up. A real blank, distinct from "didn't look."
A bounded estimate when no source exists - capped low, routed to a human, never disguised as fact.
// Model output with evidence{"canonical_id": "mfr.kaeser","confidence": 0.95,"evidence": [{"matched_alias": "KAESER","matched_in_field": "raw_name"}]}// Validator, in order:✓ entry_id exists in catalog✓ "KAESER" is a registered alias✓ "KAESER" appears in raw_name✓ canonical_name matches catalog// All pass → accepted
The system would rather refuse to answer than write something that might be wrong. That is what makes the data it does produce trustworthy.
Every customer engagement produces curator work that compounds back into the pack. Every pack release benefits every customer in the vertical. Speed of pack authorship is the durable advantage — and new verticals ship by copying the machinery and swapping the content. The Industrial Air pack is live. The Mining Spare Parts and Marine Equipment packs proved the same machinery extends from devices to parts to item-masters.
A customer's records surface a manufacturer or pattern the pack hasn't seen yet.
Verified against manufacturer sources, then added to the shared pack.
Catalogs, model patterns, and failure modes accumulate, release over release.
Every customer in the vertical gets it from day one - including you.
The loop compounds: a denser pack wins the next engagement, whose records make it denser still. Speed of pack authorship is the moat - a competitor has to relearn it engagement by engagement.
Most extension work happens at the catalog edit level — a new manufacturer, a new product line, a corrected pattern. Easy entry, version-controlled, no code, no retraining.
And the same architecture extends further. Spare parts mapping — connecting parts to the devices they belong to, with the same evidence contract — ships in 2026H2. Devices, parts, item-masters today. Spare-parts mapping next. Same machinery, different content.
The wedge is industrial data. The platform is industrial data, made trustworthy.
Four domain packs, a shelf of reusable skills, and a growing base of curated manufacturer knowledge. These are the assets every new engagement builds on, and they compound with each one.
Each a self-contained vertical: catalogs, vocabulary, validation rules.
Reusable units of capability. Ten distinct types, composed differently per pack.
Verified commercial entities: the closed-world catalogs the evidence contract checks against.
Skills are shared across packs; only the content differs. That's why a new vertical ships in days, and why the curated catalog compounds into a durable, defensible asset.
Every value InRecipe.AI touches has an owner. We sort them into three tiers by who that owner is - and that ownership, not a policy you have to trust us on, decides what's shared and what stays yours. The rule is simple: if a manufacturer or a regulator already publishes it, it can be shared; if it's about your operations, it never leaves your tenant.
The model number encodes its kW rating - a public fact, true for everyone.
Your 4,000 Kaeser units, their serials and service dates. And you call them "Kaeser screws" - that label stays in your layer.
Same brand. You can see exactly where shared stops and yours begins.
You don't just contribute to the pack. You inherit from it.
The real number isn't what InRecipe.AI charges. It's what untrusted data already costs you - quietly, on every quote, every shipment, every stalled initiative. A pilot makes that cost visible before you commit to anything.
Options sold at a loss no one can trace. Upgrade costs blur together in the ERP, so the loss-makers stay hidden.
Product data lands 3-4 weeks late, so new models miss the sales configurator at launch. Late data is late revenue.
Wrong or missing customs codes invite back-duties and penalties on cross-border shipments. The importer is liable, not the supplier.
A data steward clears 2,000-5,000 records a year by hand, and different stewards disagree. The backlog never actually closes.
What InRecipe.AI costs is a conversation, sized to your data volume - not a per-seat license. The pilot is where you find out what fixing it is worth.
Enrichment fixes the backlog you already have. That treats the symptom. The cause lives upstream, in how items get created, who owns them, and how they are governed. Data Design has delivered that governance side for years, across energy, industry, and platforms. InRecipe is the engine inside those engagements; the advisory credibility is already established.
A supply-chain compliance audit: governance roles, standards, and a risk-mitigation framework for obligation reporting.
Product and vendor data aligned across five countries, in step with the S/4HANA transformation.
Ownership, onboarding process, and required fields standardized, unblocking finance automation.
A practical ownership model built through interviews and workshops: clearer accountability, faster decisions.
Named data owners across seven data domains and a three-level decision model, built with the business and run inside the strategy cycle.
A network-wide data ownership and access-rights model, validated by piloting, with competition-law requirements addressed.
Tools without governance treat symptoms. Governance without tools leaves the backlog standing. The full offering is both.




InRecipe.AI is a Data Design product, built by a team that has spent the last decade in industrial AI, supply chain, and enterprise SaaS.
Where your data goes, which models touch it, and how the architecture maps to where EU AI regulation is heading. The short version: your data stays in your environment, the model never trains on it, and every value is traceable.
Processing runs in Data Design-controlled environments. Your records, outputs, and review history stay in your own engagement tenant.
Calls go to Anthropic's commercial API, where inputs and outputs are not used for training, on SOC 2 Type II infrastructure. The pipeline itself is model-agnostic.
Human oversight, transparency, and audit trails are core to the product, not bolted on afterward. Minimal personal data keeps GDPR exposure narrow.
Send us the security questionnaire - the audit trail was built for exactly that conversation.
A pilot is low-risk by design. You bring one business case and a sample of your data; we cover the AI cost and do the build. From there, two tracks run in parallel: InRecipe enriches the data and keeps it clean, while our advisory team fixes the upstream processes that let it go bad - so you are genuinely ready to autopilot, not just temporarily tidy.
One business case, couple of manufacturers or suppliers, a 50-100 record sample. We bear the costs, analyze your data, build the catalogs and recipes, and apply the relevant skills. You walk away with real evidence-graded output - not a demo on someone else's data.
Deeper analysis and curated manufacturer catalogs, with enrichment tailored to your data. Most of your device or parts records enriched with high confidence. Priced against your data volume.
Enrichment embedded in your workflow: new records enriched, categorized, and linked automatically. Maintenance-free data quality, on a monthly fee tiered on volume.
Enrichment treats the symptom. Alongside Copilot and Autopilot, our advisory team fixes what created the mess: item-creation processes, data ownership, and governance. The data doesn't just get clean - it stays clean, and your organization is ready to run on autopilot. It's the same governance practice behind our work with Anora, Helen, KSS Energia, MHYP, and more.
We bear the cost of the first week. You bring the data and judge the output. That's the whole risk.
Drop your email and we'll set up a free first week on your own records - real evidence-graded output on your data, not slideware.