Precision inspection instrument OEM
A German instrument OEM publishes full specifications, application notes and metrology data for quality-lab buyers.
Situation
The company builds optical inspection systems used in industrial quality control and metrology, and it is based in Bavaria. Its buyers are application engineers and metrology specialists at manufacturing firms, and they buy on documentation as much as on the instrument. A quality lab choosing an inspection system works from published specifications, application notes that show the instrument on a realistic measuring task, and evidence about measurement traceability. The people who make the final call are rarely the people who read the marketing page.
The engineering content existed, but it was distributed through email attachments one request at a time. An application engineer evaluating the company would ask for a spec sheet, then an application note, then a question about uncertainty — and each answer restarted the exchange. The website carried tidy descriptions but not the technical depth a metrology buyer needs to justify an investment to their own quality management. The buyers were qualified and serious; the friction was that they had to chase every piece of evidence.
Specification revisions compounded the problem: the version on a salesperson’s machine occasionally differed from the one a buyer had been sent months earlier, and in metrology, working from an outdated specification is a real cost, not a clerical one. The company needed its documentation to be current, public, and organised the way an evaluation actually runs.
The build
The deployment made the technical library the centre of the site. Each instrument family carries its full specification, its application notes, and the metrology data behind its accuracy claims — organised so an application engineer can complete a first-pass evaluation without writing in. The measurement conditions behind each accuracy figure sit with the number itself, because a metrology buyer will not accept a result without the setup that produced it. Because the documents are tied to the product revision they describe, a buyer can be confident the spec they are designing against is the current one.
The inquiry path routes by intent: an application question, a specification clarification, a demonstration request. Each reaches the applications engineer or sales person who should answer it. The site shares a domain with the company’s corporate mail, so a follow-up from a quality lab arrives from the same owned address as the documents they were reading.
Every request is kept in a record the company can export on demand, so the technical conversations that precede a metrology sale are not lost when the person who handled them changes.
Outcome
- Application engineers can evaluate an instrument family from public specifications, application notes and metrology data
- Technical inquiries are routed by intent to the applications engineer who should answer them
- The company owns a current, exportable record of the technical conversations behind each sale