The email that caught me off guard
On the first Thursday of November 2024, I got an email that summed up a tension I'd been circling for years.
A production manager at a pharmaceutical packaging plant was outfitting a new quality lab. She was on a timeline—the lab had to pass a customer audit by Q2 2025, and the equipment list was already approved. She'd sent the same request to four vendors that morning, and ours happened to be first.
The list included a couple of temperature data loggers, a thermal imager, and then three things that have nothing to do with what we make: an HPLC system, a Fluke 117 multimeter, and a Rice Lake bench scale with a calibration sheet she wanted help interpreting.
She'd contacted us because we sell testo measuring instruments, and in her mind, that apparently meant all measuring instruments. I get the assumption. Our catalog covers temperature, pressure, humidity, flow, gas analysis, data logging, and thermal imaging. But HPLC? That's a completely different discipline. Multimeters? Fluke's domain. Weighing systems? A field I respect but don't operate in daily.
What I actually do
I'm a quality and brand compliance manager at testo. I review what goes out the door before it reaches customers—datasheets, calibration certificates, instruction manuals, packaging claims. Roughly 600 documents per year. In 2024, I've rejected about 14% of first submissions for spec mismatches, wording that could mislead a user, or calibration data that didn't align with our stated tolerances.
My background is in mechanical engineering. I spent six years in manufacturing QA before moving into this role, so I've sat on both sides of the review process—as the person creating documents and as the person rejecting them. After more than four years in this position, I can usually tell when a document's author didn't truly understand the subject matter. The tell is usually a paragraph that stays just vague enough to avoid being wrong.
And in November, I caught myself about to write exactly that kind of paragraph.
Walking through the list
The afternoon looked fine on paper. The temperature logger question was straightforward, and I knew I could be useful on the calibration sheet. The rest was going to require some honesty.
What I could answer directly
The testo 174t data logger temperature range was the first item. The standard 174T measures from -40°C to +70°C (-40°F to +158°F) on its internal sensor. That covers cold-chain, warehouse ambient, and HVAC verification work—the kind of logging a pharma facility does daily. Resolution is 0.1°C, and accuracy is ±0.5°C in the range that matters for environmental monitoring.
I gave her those numbers, then added the caveat: verify against the current datasheet on testo.com. Specs can shift with product revisions, and I didn't want her relaying memorized figures from a 2022 datasheet into a regulatory audit. This was back in November 2024, and I'd rather be boring and correct than confident and outdated.
That's my standard approach for questions about testo measuring instruments: answer from experience, then give the customer a way to verify it themselves.
Where I had to say "not ours"
The HPLC price question was trickier. I don't sell HPLC systems. I'm not a chromatographer, and I'd be the first to admit it. But I had just reviewed a capital equipment request for our own lab, so I had some market context: a basic analytical HPLC system runs roughly $30,000 to $60,000, and a fully configured UHPLC with autosampler, column heater, and software licenses can go past $150,000 (figures from vendor quotes I reviewed in January 2025; verify current pricing, because this changes fast).
I could share that range. What I couldn't do was recommend a specific brand or configuration. That would be theater, and theater has a cost.
The multimeter 117 was next. It's Fluke's, not ours. I've used one in past jobs—it's a solid device for electrical work, with AC/DC voltage, resistance, continuity, true-RMS readings, and a low-impedance mode that filters out ghost voltages. But I'm not going to compare it against instruments we don't make. I have no skin in that game, and pretending otherwise would have been dishonest.
Then there was the Rice Lake scale. The specific request was how to read a Rice Lake weighing systems calibration sheet. This one, I could actually help with, because we use certified weight sets to validate our own instruments. I've probably read hundreds of calibration reports over the years. The format is fairly standard across the weighing industry, and the fields that matter are consistent:
- As-found readings—what the scale showed before any adjustment. This tells you how far it drifted from calibration.
- As-left readings—what it showed after adjustment. This tells you whether the calibration actually worked.
- Applied loads—the known weights used, plus whether the calibration certificates for those weights are current and traceable.
- Measurement uncertainty—the range of possible error in the calibration measurement itself. A report without this number is incomplete.
- Tolerance class—the acceptance criterion. A "pass" written right at the edge of tolerance is not the same as a comfortable pass.
That part I could speak to with confidence. But I told her honestly: I've never unboxed a Rice Lake scale, and for model-specific details, Rice Lake's own documentation and technical support are the right place to go.
The draft I deleted
Now, the part I keep thinking about. My first reply was a four-hundred-word monster that tried to cover everything. I wrote a paragraph on HPLC column selection. I offered an opinion on Fluke's firmware. I made a note about Rice Lake's calibration procedure like I'd used their equipment daily for a decade.
I stopped mid-sentence and read it back to myself. That's when I realized I'd become the kind of vendor I reject documentation for: confident, vague, and unverifiable.
Part of it was the instinct to be helpful. Part of it was the discomfort of telling a customer we don't have answers in an area they assumed we'd cover. I have a vivid memory from Q1 2024 of rejecting an entire batch of calibration certificates from a supplier who'd said "trust us" when asked about their test specifications. Their vagueness cost us two weeks and a $22,000 rework. And here I was, about to hand someone else the same bill.
I said "I'll take a look at that list" when I first replied. What she heard was "we'll help sort out the whole list." That mismatch was mine to fix. The only way to fix it was to not bluff.
The honest reply, and what happened next
The second draft was shorter and blunter:
The 174T question I can answer directly: -40°C to +70°C on the internal sensor. For accuracy details, verify against the current datasheet on testo.com—match the model number exactly.
The HPLC and the scale fall outside what we make. I can give you price context from recent vendor quotes, but I'd rather not recommend a brand I don't work with. Get itemized quotes from two lab equipment suppliers—column, software, installation, and training as separate line items. That's where the hidden costs live.
The Fluke 117 is a good meter. I can't compare it to meters we don't make, and you don't need me to—the spec sheet is public. Check it against the electrical testing your team actually does.
For the Rice Lake calibration sheet, here are the five fields I check: as-found, as-left, applied loads, uncertainty, tolerance. If any of them are missing, ask the supplier why.
She wrote back within the hour: "This is the most useful reply I've gotten from a vendor this month."
Not because I gave her a lot. Because I gave her what I had, and I was clear about what I didn't.
What I'd tell any buyer
The conventional wisdom in B2B is that a vendor should sound like they can handle anything. My experience reviewing 600+ deliverables a year suggests the opposite: the most expensive thing a vendor can say is "sure, we can do that" when they can't.
Vendor honesty is a quality signal. It tells you the vendor who verifies things is marking their own work before it reaches you. It means when they do make a promise, it's more likely to be one they can keep.
So here's my practical advice for anyone buying measurement instruments:
- Ask what they don't make. A clear answer tells you more than any pitch.
- Verify temperature logger specs against the datasheet. The testo 174t covers -40°C to +70°C on the internal sensor, but confirm the current revision before you put it in a protocol.
- For HPLC, get itemized quotes. Expect $30k–$60k for a basic system, and over $150k for a fully loaded UHPLC (as of January 2025; verify current pricing). Break out the columns and software.
- For a multimeter 117, read the public spec sheet and decide based on your workload, not a vendor's opinion.
- For weighing systems, learn the calibration sheet format: as-found, as-left, applied loads, uncertainty, tolerance. If a field is missing, ask why.
When I first started in quality management, I assumed being helpful meant answering everything. A few expensive lessons later, I've learned that the most useful thing I can say is "that's not ours—and here's who to ask instead."
That reply cost us nothing. The trust it bought was worth more than any upsell I could have forced.
