Scoping an AI procurement platform against real manufacturer demand

The challenge: a procurement problem that software keeps failing to hold

Sourcing process equipment across pharma, chemical and industrial manufacturing is a slow, document-heavy business: a specification becomes an enquiry, an enquiry becomes a set of quotations that are not comparable, and somebody reconciles them by hand.

It is an obvious candidate for software, which is why so many attempts exist and so few are used. The failure is usually the same. The product is scoped against how procurement is described rather than how it is done, and the first real specification breaks it.

The approach: scope against manufacturers who would have to use it

ASE supported early product and MVP scoping. The discipline applied is the one the firm uses on physical plant: establish the operating case before selecting the solution. What is the workflow, who touches it, and what does failure cost the person holding it.

The sector data points at where the opportunity actually sits, and it is not where it is usually assumed to be. Chemicals and pharmaceuticals run roughly twenty percentage points above the manufacturing average on ERP adoption, around 77 to 81 percent against 58. These are not companies without systems. But only about 30 to 39 percent exchange supply-chain data electronically with counterparties. The deficit is supplier-facing integration, which is precisely where an enquiry lives, and it is why a platform that improves internal workflow solves the wrong half of the problem.

The pilot set is what makes that real. Manufacturers including Seqens, Axyntis, Humens, Elementis and William Blythe give the scope something to be wrong against. Scoping validated only internally produces a specification everyone agrees with and no customer recognises.

The results: a scoped MVP with its assumptions exposed

The engagement delivered the early product and MVP scope. The venture is early: it operates as an Austrian sole trader from Graz behind a UK-facing domain, and states in its own trust centre that it is not currently ISO 27001 or SOC 2 certified, with both on a roadmap.

That is worth stating rather than omitting. An early venture that publishes what it has not yet certified is easier to scope honestly than one that implies otherwise.