Eddie vs. Hawk: The NETZSCH Logo PNG Mistake That Made Me Respect Small Orders

"That logo is pixelated, and the blue is wrong."

I froze in the middle of the shop. The voice belonged to Hawk—our client's quality manager, a guy who genuinely uses a loupe on printed documents. He'd circled the NETZSCH logo on my proposal and sent it back with an email that said, in no uncertain terms, "Do it again, properly."

Let me back up. I'm Eddie. I handle technical proposals and small pump packages for a small integration shop. Not the giant projects you see in press releases—I'm talking pilot lines, replacement pumps, and the kind of orders that don't show up on a corporate radar. In six years, I've made eleven significant mistakes. I've personally documented $14,000 or so of wasted budget. My boss, however, has a policy: we write the mistakes down so we don't repeat them. I'm the one who keeps that list. This story has joined the top of it.

The small order that started it

The whole thing started with a $3,200 order. A new client needed a NETZSCH rotary vane pump package—pump, motor, a couple of sensors, and a small control panel. For many suppliers, that's too small to be interesting. For us, it pays the electric bill and keeps the lights on. I treated it like a real project, because that's what it was.

I prepared the proposal in a hurry. (Should mention: I was also trying to impress a new client, which made me rush.) The cover page needed the NETZSCH logo. Instead of asking the manufacturer or our distributor for the asset, I went to Google and typed "netzsch logo png". I found something that looked great on a laptop screen: crisp edges, nice rectangle, correct-looking blue. It went straight into the document, and I hit send. Hit send and immediately wondered if I'd just used a screenshot. The upside of sending it fast was looking responsive; the risk was looking sloppy. I convinced myself it was fine. Hawk would prove otherwise.

The client approved the proposal. We were the right price and the right pump. It should have been a small win. That's when the logo became a problem.

What a PNG can't tell you

Hawk does approval audits before final purchase orders. When he got the printed cover page, he noticed what my monitor didn't show. The logo was soft. The white gaps in the letters were jagged. The blue didn't match the official brand blue. He pulled out the Pantone books and showed me three different blues from our own printed quote. "Which one is the NETZSCH blue?" I couldn't answer.

The file I'd downloaded was a 72-DPI PNG. On a screen, that's fine. Print is a different world. The industry standard for commercial print is 300 DPI at final size; for a logo printed across an 8-inch-wide cover, that means the file has to contain enough pixels to stay clean when rendered at that size. My file didn't. It also had an RGB color profile, not CMYK. The printer translated it to a muddy approximation of the actual brand color.

Per Pantone Color Matching System guidelines, brand-critical color tolerance should be Delta E < 2. Delta E of 2–4 is noticeable to trained observers; above 4 is visible to most people. My cover-page logo was probably somewhere in the 6–8 range. It was obvious to everyone except me.

The fix wasn't hard. The NETZSCH distributor—same one we'd bought pumps from—sent a proper brand kit that afternoon: vector EPS, high-res PNG, RGB values for screens, CMYK values for print, and a note that the official blue is Pantone 286 C. Oh, and it was free. It took about ten minutes to swap into the document. What cost $890 was the reprint of the full proposal, plus a one-week delay while we waited for the corrected version to come back from the printer.

Project Peregrine and the checklist

You might wonder why I'm making such a big deal about a logo. I think it's because I've been through this exact pattern before. We name our internal projects after birds. A year before this, I mixed up the specs for Project Peregrine and Project Osprey. Peregrine was the fast one; Osprey was the long-lead, high-load one. I used the wrong pump curve for the wrong job. That mistake caused a 3-day production delay and nearly lost us a client.

After that, we built a pre-flight checklist. It has 23 items, and the first one says: "Brand assets: vector / high-res / correct color." I added that item myself, after the Project Peregrine disaster. But on the small order, I skipped it. I told myself it was only a cover page, only a small order, only a logo. That's how the old "it's just a logo" thinking comes from an era when proposals were printed in-house on a laser printer and nobody had a loupe. That era is gone.

In the 18 months after we started the checklist, we caught 47 potential issues. This logo was number 48, and it wasn't caught by the checklist—it was caught by Hawk. The checklist only works when you actually use it, even on the small stuff.

Why the distributor deserves credit

What saved us wasn't just a new logo file. It was the way our NETZSCH distributor treated a tiny order. I called expecting a brush-off—"We'll get back to you when we can." Instead, the rep asked for our pump selection and double-checked it.

"You quoted the right series for flow," she said, "but if the fluid temperature is above 80°C, you should verify the elastomer rating. Want me to re-run it?"

That one expression—re-run it—was worth more than the logo. It reminded me that small orders don't have to be sloppy orders. A distributor that takes a $3,200 quote seriously earns the right to quote the $50,000 order later. That's a no-brainer.

I've been on the other side too. When I was starting out, the vendors who treated my $200 orders with respect are the ones I still buy from now. Small doesn't mean unimportant; it means potential.

My pre-flight checklist (logo edition)

If you're reading this and thinking about saving time on the next proposal, don't. Here's the version I run now:

• Get the logo from the manufacturer or an official distributor, not a free-icon site.
• Use a vector file (EPS, AI, PDF) for print; use a high-res PNG with transparency for screen.
• Confirm the resolution: at least 300 DPI at final print size, 72 DPI only for web.
• Check color modes: CMYK or Pantone for print, RGB for screen, never a screenshot from a website.
• If you're in doubt, ask the brand owner. It's a two-minute email that can save an $890 reprint.

I still keep the Project Peregrine story in my head. It reminds me that speed without a checklist is just a fast way to make a mess. And I keep an even newer image in my head: Hawk, staring through his loupe at a blurry blue rectangle, then looking up and saying, "Do it again, properly." That's now my version of the "Eddie vs. Hawk" test—the moment when I decide whether I'm going to send something that looks like I care, or something that looks like I rushed.

One last caveat: my experience is based on small-to-mid-size B2B orders—maybe 200 real projects, a few hundred quotes. If you're in aerospace, automotive, or another highly regulated industry, your document standards will be even tighter. But the core lesson is the same. The logo is part of the product. The small order is part of the relationship. And the checklist is part of the process.

Bottom line: a NETZSCH logo PNG mistake cost me $890, one week, and a little pride. It taught me more than any pump training course did. Now, I check. Every time. Even on the small ones.