# Lena Vasquez, Field Operations Manager at Meridian Utility Contractors — read of HeatGuard, June 14, 2026

> 11 years managing outdoor crews in the Southwest, currently overseeing 70 field techs across three crews in Phoenix and Tucson. My youngest starts kindergarten in August and I spend most lunch breaks reading OSHA memos in my truck.

## How I got here

Our safety director forwarded an OSHA bulletin about the new heat illness prevention rule last week. I went looking for tools. Typed "heat stress scheduling software" into Google, got a LinkedIn post from someone I don't know, and followed a link here. Didn't recognize Wishdeal. Kept going anyway because the URL had the words I searched for.

## What I clicked first

"Keep Your Team Productive When It's Too Hot to Work" did not push me away, which is unusual. That's the actual problem. Last August I had two techs go down during a panel install in Chandler. We halted the job for four hours. So "Automatically shift high-intensity outdoor work to cooler hours, eliminating manual heat-stress planning" felt like it was written by someone who'd been on one of those job sites. I kept reading.

## Where I paused

The scoring block. "63/100 Adoptability. $-22,637 Year-1 take-home (Fermi). 1 in 8 Meaningful-success odds."

I read that three times. Then this: "Honest disclosure: we don't have live customers on this idea yet. We shipped the strategy package; you ship the customer conversations."

I came here to buy software to use on Monday morning. This is an idea for software. Someone is selling me the right to build what I was looking for. That's a completely different product and I did not realize it until that sentence.

## What I distrusted

The feature bullets are written like an existing product. "Real-Time Risk Monitoring: Track wet-bulb temperature, worker fatigue, and heat-stress indicators to intervene before safety incidents." "Regulatory Readiness: Stay compliant with OSHA heat standards and emerging climate-resilience labor regulations across 40+ jurisdictions."

Those are product claims. But there is no product. So what am I supposed to do with "40+ jurisdictions"?

Also, "buyer clarity: 10/10" shows up as a top strength. I don't know who the buyer is on this page. Me, a crew manager looking for software? Or a developer who wants to build and sell this software? We need entirely different things from a homepage. I had to read down to the pricing section to figure out which one I was.

The stock visual of a generic outdoor scene doesn't help. It's the kind of photo I've seen on seventeen other "workforce productivity" pages.

## What would convince me

If the product existed: one sentence from a real crew manager who moved their concrete pours to 5:30 AM because of this tool and watched their incident rate drop. Not a logo wall. Not a stat from a white paper. Just a person, a company name, a state, and a before/after that's specific enough to be falsifiable.

If this is an idea kit aimed at builders: that's fine, but say so in the first three seconds. Don't show me OSHA compliance features before telling me the software doesn't exist yet.

## What I'd ask in an email reply

1. Is HeatGuard a product I can buy and use for my crews right now, or is this a package for someone who wants to build that product?
2. The "wet-bulb temperature" tracking -- if a version of this existed, would it pull from a weather API automatically, or would someone on my crew have to enter readings manually? That detail determines whether it's a real-time tool or a spreadsheet with a better UI.
3. You list "emerging climate-resilience labor regulations across 40+ jurisdictions" -- which two or three jurisdictions matter most right now, and are any of them Arizona?

## Verdict: dismissive

The problem is real and the feature list is aimed squarely at it. But the page is trying to do two things at once -- market software to operators and sell a build kit to founders -- and it ends up doing neither clearly. I spent four minutes on it before I understood what I could actually buy, and I won't be back.

---
*Memo by skeptic persona, generated 2026-06-14. Studio breaks own self-grading loop.*