I typed 'falcon' and got a stuffed animal
In 2024, I was managing purchasing for a 220-person company. I handle roughly $180,000 in annual spend across 12 vendors. One Tuesday, our maintenance lead sent a two-word request: 'Falcon part.' That was it. No part number. No photo. Just the brand name and a vague description.
I did what any admin would do. I typed falcon into our vendor portal and then into a search engine. The results were... not industrial. A peregrine falcon stuffed animal. An MSU falcon cam live stream. A LEGO Millennium Falcon set. A page for Simparica for dogs. And an article explaining what's the difference between a hawk and a falcon.
I thought the search engine was broken. It wasn't. My process was.
For a company in energy mining equipment, that kind of search noise is more than annoying. It is a procurement risk.
The surface problem: search results don't match intent
When you're buying for a business, you assume the internet knows what you mean. It doesn't. 'Falcon' is a word with dozens of meanings: a bird, a university mascot, a Star Wars ship, a pet medication search term, a sports team, and probably a dozen companies. Search engines rank by relevance to the average searcher, not to a maintenance tech in a warehouse.
That's the surface problem. You type a short word. You get consumer noise. You waste time clicking. You start over.
The deeper cause: your internal language is not a taxonomy
Here's what I missed for years. The problem wasn't the search engine. The problem was that our company didn't have a controlled way to describe what we buy.
It's tempting to think exact-match search fixes this. But 'Falcon' is not a SKU. It's a brand. And a brand without a model number, size, material, or photo is just a guess.
When I first started managing vendor relationships in 2020, I assumed the lowest quote was the best choice. Three budget overruns later, I learned about total cost of ownership. The same lesson applies to search. The shortest search term is rarely the cheapest one.
We didn't have a formal spec template. That cost us when a vendor quoted a 'Falcon replacement part' that was half the size we needed. It looked fine on the invoice. It was not fine on the machine. We ate the return shipping and a week of downtime.
The third time something like that happened, I finally created a one-page purchase spec. Should have done it after the first time.
Our real problems were three:
- Ambiguous names. 'Falcon' meant one thing to the requester, another to the vendor, and nothing to the search engine.
- No aliases. The vendor called it a 'coil assembly.' Our maintenance team called it a 'Falcon part.' Finance called it 'line item 4.'
- No fee transparency. The quote looked low. Freight, setup, and expedite fees showed up later.
Bottom line: we were not buying a part. We were buying a misunderstanding.
What the misunderstanding costs
Let's do the math. I spent about three hours—or rather, closer to four once I counted the calls—trying to figure out which 'Falcon' we needed. Our maintenance lead spent another hour. The vendor's rep spent time sending the wrong spec sheet twice.
At our loaded labor rate, that's roughly $400 in internal time. Then we paid a $180 rush fee because the correct part arrived late. Then finance rejected a $2,400 expense report from a different vendor because the invoice was handwritten and didn't match the PO.
None of those costs showed up in the original quote. That's the trap. A low price with hidden fees and vague specs is not a low price. It's a red flag with a number attached.
It also made me look bad. My VP asked why a simple replacement took nine days. I didn't have a good answer. 'The search results were confusing' is not a good answer.
“The vendor who lists all fees upfront—even if the total looks higher—usually costs less in the end.”
I've learned to ask 'what's NOT included' before 'what's the price.' That one question would have saved us the rush fee and the rejected invoice.
The fix: transparent specs and all-in quotes
The solution is not a better search engine. It's a better buying process. Here's what we do now.
1. Build a tiny internal catalog. For every repeat item, we store a part number, a photo, dimensions, material, and the name our vendor uses. If it doesn't have a part number, we create an internal one. This killed 90% of our ambiguous searches.
2. Use negative keywords when you're the buyer. In our portal, I added filters for 'toy,' 'stuffed animal,' 'livestream,' 'veterinary,' and 'collectible.' That sounds silly until you see peregrine falcon stuffed animal show up in a maintenance search.
3. Require an all-in quote. The quote must include shipping, setup, tax, and any rush fee. If a vendor can't provide that, it's a no-brainer to move on. The lowest ballpark number is meaningless if the final invoice is 30% higher.
4. Verify invoicing before ordering. I learned this the hard way. A great price from a new vendor meant nothing when finance rejected the handwritten receipt. Now I ask for a sample invoice and W-9 before the first PO.
5. Write the spec in plain language. If a stranger can't read the spec and repeat it back, it's not ready. 'Falcon part' becomes 'Falcon model X-12 coil, 4-inch diameter, 240V, vendor SKU 45-789.'
The part no one tells you
The same problem shows up in marketing, too. If your company is named Falcon, you're competing with birds, movies, college mascots, and pet meds. You can't fix that with one blog post. But you can make your content clear about what you actually do.
For procurement, the answer is boring: use specific terms. Use part numbers. Use photos. Ask for all-in pricing. Make transparency a requirement, not a nice-to-have.
The next time someone asks me to buy a 'Falcon,' I don't start with a search. I start with a question: 'Which Falcon—and what does it do?' That one question has saved us more money than any discount I've ever negotiated.
It's not glamorous. But it works.