# Marcus Hensley, VP of Compliance & Risk at Meridian Benefits Group — read of compliance-radar-ai, May 7 2026

> 14 years in compliance, currently running a 5-person team at a 340-person benefits administration firm in Columbus. We touch ERISA, state insurance regs, and ACA reporting. My oldest just started driving, which is somehow more stressful than any SEC examination I've been through.

## How I got here

Someone in a LinkedIn compliance group I'm in posted "has anyone tried this for multi-state regulatory tracking?" with the link. No context, no endorsement, just the link. Three people commented "following." I had 8 minutes between calls so I clicked.

## What I clicked first

The hero line "Never Miss a Regulatory Change Again" is the kind of thing that gets printed on a tradeshow banner. Every product in this space says some version of it. What slowed me down slightly was the sub-line: "flags impact to your operations, and prioritizes action items." That specific phrasing -- the "impact to your operations" part -- is closer to what I actually care about than most of these tools admit to caring about. Most tools tell you what changed. Fewer try to tell you what it means for *you*. So I kept reading.

## Where I paused

The FAQ answer about feed frequency: "Most changes surface within 24 hours of publication."

That word "most" is doing real work. In benefits compliance, a Department of Labor field assistance bulletin can drop on a Thursday afternoon and create a Friday deadline for plan administrators. If "most" means 95% in 24 hours and 5% in 72 hours, I need to know which 5%. If it means 80% in 24 hours, that's a significant gap. This sentence is technically honest and practically uninformative. I sat on it for a minute.

## What I distrusted

Two things.

First: "200+ official sources and industry bodies." They list SEC, EEOC, IRS, state boards. That is 4 named sources. I need to know if they cover DOL, CMS, HHS, my state insurance commissioner, and the dozen state-level equivalents for the jurisdictions we operate in. "200+" is a number that sounds impressive and tells me nothing about whether any of those 200 are the ones I actually watch. It might be 200 sources, most of which are irrelevant to my industry.

Second: "Plain-language summaries of complex regulatory language." My concern is not whether the summaries are plain. My concern is whether they are accurate. If an AI gives me a plain-language summary of a proposed ERISA exemption and gets the carve-out wrong, and I act on that summary, I have a problem that plain language made worse. There is zero mention of how this is reviewed, whether a human touches it, or what the error-correction loop looks like. That is a real gap for a compliance tool.

Also: "Built by Wishdeal Studio" in the footer. That is a product studio, not a compliance company. Not disqualifying, but it does mean the domain knowledge had to come from somewhere, and I have no idea where.

## What would convince me

A source list. Not "200+." The actual list, searchable, with update timestamps showing the last time each source was pulled. If I can look for DOL Advisory Opinions, Ohio Department of Insurance bulletins, and CMS MLN Matters and find them there, I'm significantly more interested.

One real customer story from a firm my size in a regulated industry. Not a logo. A paragraph with a specific regulatory event -- "we caught the DOL guidance on PTE 2020-02 amendments before our competitor did, here's what we did with it." That's the story that moves me.

And I want to know what happens when the AI summary is wrong. Is there a correction mechanism? Do they flag uncertainty? Do I have any recourse?

## What I'd ask in an email reply

1. We're primarily a benefits administrator operating in 14 states, touching ERISA and state insurance regs. Before I trial this, can you show me a sample alert from the last 60 days that would have been relevant to us specifically -- something from DOL or a state insurance department -- and what the plain-language summary said?

2. The Professional plan caps at 3 team members but my compliance team is 5 plus two people in HR who need read access. Does "team members" mean users who can act on tasks, or anyone with a login? And what's the ballpark for Enterprise if we're under 400 employees?

3. The FAQ says "most changes surface within 24 hours." What percentage is that in practice, and is there a way to configure faster alerts for specific agencies I flag as high-priority?

## Verdict: on-the-fence

The product is solving a real problem and the framing is cleaner than most compliance tools I've seen pitched. But the page is written for someone who will be impressed by "200+ sources" and "SOC 2 Type II" without asking follow-up questions. I need actual source coverage and one honest customer example before I spend time on a trial.

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