Limited project slots available for Q3 2026 — secure your formwork engineering support now. Request Consultation →

Peri, Very Peri, and Peri Peri: How a Name Mix-Up Cost $3,200

If someone asks you to quote “Peri,” don't assume you know what they mean. In January 2022, my team produced 180 safety signs in PERI yellow because the spec said “Very Peri.” The client wanted Pantone 17-3938—a blue-purple. The signs went straight to the trash: $3,200 wasted, plus a week-long delay. Full disclosure: I've personally made (and documented) 14 significant mistakes, totaling roughly $28,000 in wasted budget. This checklist came out of those failures, not a textbook. Since then, every request gets the same three-line checklist: exact product, exact specification, exact color reference. If you're in construction procurement, this rule will save you money.

Why “Peri” Is a Search Confusion, Not a Spelling Problem

Here's what I mean. Our company, PERI, sells concrete formwork, shoring, and system scaffolding. But “peri” also shows up in other places: “House of Peri Peri” is a restaurant name, and “peri peri” is a sauce—not a construction material. The Pantone color of the year 2022, Very Peri, made it even worse. If you've ever typed “peri” into a search box and gotten results for grilled chicken, you know the frustration.

Search engines can tell the difference based on the words around the query. But a contractor forwarding a request doesn't have that luxury. A procurement manager might write “need peri quote” and actually mean three different things. This isn't just a search annoyance. It's a procurement risk. In the same way that people search “leaf filter vs leaf guard” and end up comparing two similar-sounding gutter systems, we get requests that mix up “peri” the formwork brand and “peri” the color. Names are shortcuts, not specs.

Case #1: “Very Peri” vs. PERI Yellow

The mistake happened because someone trusted a name, not a number. The architect's drawings mentioned “Very Peri” accents for site safety signage. A new project coordinator forwarded the request with a note: “Client wants PERI color.” In our world, PERI color is yellow. So that's what we made.

(Should mention: the coordinator didn't open the PDF attachment. The attachment had the actual Pantone reference.)

The client rejected the batch in the design review. 180 signs, $3,200 including material and installation. Actually, $3,200 was the quoted figure; the redo with blue-purple powder coating came to $4,100. We ate the difference to keep the project moving.

That's when I learned the rule: color names are useless in procurement. The Pantone color of the year 2022, Very Peri, is officially Pantone 17-3938. Very Peri showed up on a swim cap, a coupe glass, even the plastic cover of a project binder. But in a construction spec, it needs a code. Pantone's color matching guidelines set the standard tolerance at Delta E < 2 for brand-critical colors; Delta E of 2-4 is noticeable to trained observers; above 4 is visible to most people. And Pantone colors may not have exact CMYK equivalents, so the printed result can vary by substrate and press calibration (Reference: Pantone Color Matching System guidelines). The name alone isn't enough. Ask for the number.

Looking back, the mistake was avoidable at three different points. The coordinator could have opened the PDF. The client could have written “Pantone 17-3938” in the request. And I could have asked one clarifying question before approving production. I didn't. We all assumed the other person meant the same thing.

Case #2: The “House of Peri Peri” RFP

Believe it or not, we got an RFP from a restaurant project named House of Peri Peri. Our spam filter nearly sent it to the trash because “peri peri” looked like a lunch order. The general contractor was actually looking for a system scaffold package to build a feature wall. The client's brand name had nothing to do with the product they needed.

We almost replied with “we don't do food services.” Honestly, I'm glad I read the full scope before responding. Dodged a bullet. An informed client asks better questions, and it only took 10 minutes on the phone to explain that PERI is a formwork and scaffolding company. That 10 minutes turned a near-miss into a $78,000 quote.

That experience changed how we respond to vague requests. We don't ask “is that the color or the brand?” sarcastically. We ask: “Can you tell us more about the scope?” Most of the time, the other person just needs a shorthand for something concrete.

What “leaf filter vs leaf guard” Taught Me About Brand-Name Bias

Here's where the “leaf filter vs leaf guard” comparison gets useful. Those two names are so similar that it's easy to treat them as interchangeable. But the systems use different mounting designs, different materials, and different maintenance requirements. The same problem shows up in formwork: different suppliers use similar names for different components, and “compatible” isn't always true.

I have mixed feelings about brand-name comparison content. On one hand, it's natural to ask “which one should I pick.” On the other, the answer changes with your site conditions, your concrete schedule, and your crew's experience. A “best” answer without context is basically a guess. So now I tell clients: give me a roof pitch and a rainfall number, and I'll tell you whether a filter—or a guard—makes sense. For formwork, it's the same: give me a pour plan and a load table.

The deeper issue is that brand names become categories over time. “I need a Kleenex” means tissue. “I need a peri quote” could mean formwork components, or a color sample, or anything else. When that happens, you have to slow down and verify the spec.

The Pre-Quote Checklist I Use Now

After the Very Peri incident, I created a checklist. We've caught 47 potential errors with it in the past 18 months. It's not fancy, but it kills ambiguity:

  • Full legal entity and project name. If the project is called “House of Peri Peri,” that doesn't mean the scope is peri-peri chicken.
  • Product type: formwork, scaffolding, shoring, or access? People say “scaffold” when they mean “formwork” more often than you'd think. Or rather, more often than I expected.
  • Exact color or finish code. Pantone, RAL, or a physical sample. If the spec says “Very Peri,” ask for the number.
  • Quantities and unit sizes. A missing zero on a quantity created a $450 reorder in 2023.
  • Delivery location and required date. We once saved $80 by guessing the delivery site, then paid $390 for an emergency transfer.
  • Sign-off role. Who approves the final sample before production?

Each item exists because of a mistake. The project-name line came from the House of Peri Peri RFP. The color line came from the signage rejection. The delivery line came from the $390 transfer. No bullet is theoretical.

What This Doesn't Cover (Read Before You Copy It)

This worked for us because our context is B2B formwork and scaffolding with predictable ordering patterns. Your mileage may vary if you're in e-commerce, residential roofing, or anything where projects are more seasonal. If you're dealing with international logistics or a client who refuses to use codes, you'll need a different process.

Also note: Pantone's “Very Peri” was the 2022 Color of the Year, not a permanent standard. As of January 2025, verify current color references before production. And I can only speak to PERI's systems; other formwork suppliers may have different tolerances and documentation. The principle—names are not specs—still applies.

One more thing: this checklist won't fix a client who doesn't know what they want. But it will surface the gaps early, while there's still time to ask.

So if someone asks you to quote “peri” tomorrow, ask the question before you print the label. “Which peri?” is not a joke. It's a $3,200 question.

Leave a Reply