# Marcus Delgado, Director of Enrollment Management at Mesa Verde Community College — read of Enrollment AI, May 9 2026

> 11 years in higher ed admissions, currently managing a 5-person team handling about 2,200 inquiries a year, running Slate CRM and a pile of duct-taped spreadsheets.

## How I got here

I Googled "admissions lead follow-up automation" on my lunch break after we lost a nursing applicant to Pima because we took 4 days to call her back. She had already deposited somewhere else by the time my coordinator found the intake email. It showed up maybe third or fourth result. I clicked mostly because the meta description didn't say "revolutionize" which already puts it ahead of the other three.

## What I clicked first

"Admissions teams spend 40% of their time on administrative tasks instead of relationship building." That one I felt in my chest because I just did our workload audit two weeks ago and it's basically accurate. So that landed. The hero subhead was reasonable too: "Capture leads through branded intake forms, score them by fit and intent, and automatically send personalized outreach." Fine. I understand what this does from those two lines, which is more than I can say for most of these.

I did not click the 30-second video. I never do on the first visit. I'm reading to decide if it's worth another tab.

## Where I paused

The lead scoring section. "Machine learning models that score leads by academic fit, demographic match, and enrollment intent." I stopped on "demographic match." In a community college context, where we have open enrollment and are actively trying to reach underserved populations, scoring down a lead because of demographic fit is something our equity office would flag in about four seconds. I don't know if that phrase means what I think it means, or if it's just lazy copy, but I'd have to ask before I'd show this to my VP.

## What I distrusted

Three things.

First, the stats: "45% Faster Time to First Contact," "23% Higher Conversion Rate," "12 Hours Saved per Week per Officer." No source. No sample size. No "based on a survey of N customers." These could be real. They could be made up. I have no way to tell and that's a problem because I'd have to present this to a budget committee.

Second, no mention of FERPA anywhere on the page. It says "GDPR-compliant" which is fine if I'm running a bootcamp in Germany. I'm in the United States. Student data falls under FERPA. That omission either means they haven't thought about it, or they're targeting bootcamps more than universities and just wrote a generic page. Either way it's a gap I'd need an answer to before I could even send this up the chain.

Third, at the very bottom: "Built by Wishdeal Studio." That reads like a web agency dropped this as a product. I don't know if that's what it is, but it makes me wonder whether enrollment management is the core focus or one of twelve products this studio ships. That's not disqualifying but it makes me want to know who I'd actually be working with.

## What would convince me

One real named customer in higher ed, specifically a community college or regional four-year, who would let me call them for 15 minutes. Not a testimonial blurb. A reference I can actually call. That would move me faster than any stat on the page.

Also: a data processing agreement template that addresses FERPA and explains where student inquiry data lives (their servers, mine, third party?). If that exists and is on the pricing page or somewhere I missed, that's actually a good sign. If it doesn't exist, that's the answer.

## What I'd ask in an email reply

1. Can you walk me through how "demographic match" works in the lead scoring model? Specifically, are you scoring leads down based on any protected class characteristics, or does that phrase mean something else?

2. Who are two or three community colleges currently using this, and can I talk to their admissions directors directly?

3. What's the data residency setup? Where does student inquiry data get stored, and do you have documentation on how you handle FERPA compliance for US institutions?

## Verdict: on-the-fence

The core problem is real and the feature set looks like it was built by someone who actually talked to an admissions coordinator. But the missing proof, the FERPA silence, and the "Built by Wishdeal Studio" footer give me enough pause that I'm not filling out a demo form on this visit. If they emailed me back with a reference call and a data agreement, I'd take the meeting.

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