# Marcus Dunleavy, Owner at Local Prominence Consulting — read of Geo-Verified Review Monitor, June 19 2026

> 9 years running online reputation for local service clients. Currently managing 14 accounts: 6 dental practices, 3 HVAC companies, a salon group with 4 locations. I drive a 2019 Tacoma and coach under-10 soccer on Saturdays.

## How I got here

Googled "real-time review monitoring" after Grade.us had a 6-hour lag window during a client crisis last month. A review hit at 8 PM, I didn't see it until 2 AM when I happened to check, client was furious by morning. That was embarrassing enough to make me actually look for alternatives. This page was on page 2 of results. Clicked because "real-time" and "geo-verified" are exactly the two things Grade.us is missing.

## What I clicked first

"A 3-star review posted at 2:47 PM in Denver? You're notified at 2:49 PM."

That specificity pulled me in. That is a real scenario and a real gap. Two minutes. I wanted to believe it. I kept reading to see what held that claim up.

## Where I paused

The Belarus example: "A salon in Austin gets 8 one-star reviews from IP addresses in Belarus? We flag it instantly as coordinated attack."

I stopped here because this is the one use case that would make me genuinely excited about the tool. I have a dental client who got hammered with 11 one-stars in a 3-day window last year. Google support was useless. We couldn't prove coordination. If I could have shown them a dashboard with IP clustering data, that's a different conversation with both Google and the client. This is a real problem. The page actually describes it accurately.

## What I distrusted

Two things, and one of them is a full stop.

First: "Trusted by 2,000+ local service businesses" is in the footer. Then, lower on the same page, in a box that appears to be from the people who built this: "Honest disclosure: we don't have live customers on this idea yet."

Those two sentences cannot coexist on the same page. That is not a minor inconsistency. That is the page actively lying to me in the hero footer and then confessing in the fine print. I don't know what "Wishdeal Factory" is, I don't know what "adoptability axes" are, and I don't know what "Unlock the dossier $5" means, but I know that the "2,000+ local service businesses" claim is not real.

Second: "47 minutes average delay reduction vs. traditional monitoring tools." Where does this number come from? Which tools? Measured how? This is the kind of stat that sounds precise and means nothing without a methodology attached.

## What would convince me

If this were a real, live product: one month of timestamped review detection logs for a single client, showing the gap between when the review posted and when their system fired the alert. Not a quote, not a testimonial. A log file, even anonymized. That would prove the two-minute claim more than any copy on the page.

On the geo-verification / fake review detection side: a before/after case from a single business that got hit with a coordinated attack, showing what the flagging dashboard actually looked like and whether Google ended up removing the reviews. That specific outcome matters because my clients always ask "but can you get them taken down?" and the answer shapes the whole conversation.

## What I'd ask in an email reply

1. The footer says 2,000 local service businesses. The disclosure section says no live customers. Which is true, and if the latter, what does the $79/month plan actually buy right now?

2. Scraping Google Business and Yelp in real-time through residential proxy IPs is almost certainly against both platforms' Terms of Service. Have you had any accounts terminated or access blocked? What happens to my monitoring if Google detects and blocks the IPs?

3. The "reviewer location verification" capability -- when a review comes in, what data point are you actually verifying? Is it the IP of the Google account that posted the review, the account's home location setting, or something else? Because those are three different things with very different accuracy profiles.

## Verdict: on-the-fence

The problem description is accurate and the use case is real. If this were a live product with even 20 paying customers and real monitoring logs, I'd book a demo. But the customer-count contradiction is disqualifying until someone explains it, and the scraping ToS question is not a detail I can overlook when client reputation is what I'm actually selling.

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