From engineering requirement to sourceable component.

The pipeline starts at the requirement, so the application, the performance envelope, the volume, and the date are enough. If you already have a BOM, we validate it — and a fair proportion of the time the most useful finding sits upstream of the part choice.

We are funded by the people who use the work. The output is intelligence and a validated supplier mapping; where you buy stays entirely your decision, and the record is yours to keep either way.

Four passes: identity, capability, technical claims, and commercial continuity. Each finding carries its sources and one of three states — verified, unverified, or contradicted. Nothing is upgraded to verified because it appeared on a datasheet.

It is recorded as unverified and stays visible in the shortlist, with the open question named. Knowing which of five options still has a thermal question outstanding is exactly the point.

Drone, robotics, and battery and energy systems, across roughly 100 component categories and 500 mapped companies. Requirements that cross domains — a robotic platform with its own pack, for instance — are handled as one structure rather than three separate exercises.

It depends on how much of the structure already exists. A single well-defined category within a covered domain is fast, because the intelligence layer is already built. A novel system requiring fresh supplier validation takes longer, and we tell you which one you have before starting.

Yes. Academic and research procurement is a distinct programme. The failure mode there is different — usually a specification derived from a paper rather than from the working conditions — but the pipeline is the same.

The requirement record, the validation findings, and the shortlist are yours. The underlying category intelligence — parameters, landscape structure, historical validation — is ours and improves across engagements.