CTE Recruiting and Demand Capture.

Keep all three. Your website has to be complete — every program, every requirement, every policy — and that is exactly why it can't also take one person interested in one program and get their name. Your CRM works the funnel once someone is in it. Your ads bring traffic. The gap is where that traffic lands and what happens to the people who weren't ready to apply: a program page with a phone number loses them, and the CRM never sees them. Point the same traffic at a destination built to capture instead of inform, and you get the two numbers neither system can give you: inquiries by program, and cost per inquiry by program.

Whoever your institution's process says. We make it short for both. Marketing: the instance carries your name, logo, tagline and colors, and we send the brand files for review before anything goes public; your existing campaigns keep running and simply point here. Technology: there is nothing to install, integrate, or host, and no SIS or CRM connection is required, so the review is a read, not a project. Inquiries route to your team, or can be forwarded into the CRM you already use.

Keep both. Forecasting projects headcount by term and by division from historical yield, retention curves and market data — that's how you plan budget and staffing, and we don't do that job. Your CRM works the funnel once someone is in it. The blind spot is the same from both directions: a forecast is built entirely on students who made it into the funnel, and the CRM starts working the moment someone begins an application. A certificate that has run at capacity for six terms looks stable to the model rather than suppressed, because the people who inquired too late, inquired at the wrong office, or never inquired at all were never recorded. Everyone who wasn't ready to start an application is invisible to both systems. That's exactly who we capture — a name and a program, before the application — so your projections have real people behind them instead of extrapolated ones.

You stay in control. A prospective student who has never enrolled doesn't have education records yet, so FERPA generally isn't the operative question at the inquiry stage — but we'll sign your institution's data agreement regardless, and we're built to pass the same review. The form captures adult contact information only, consent-gated: a name, the program they're interested in, and how to reach them. Nothing else. If your legal team would rather we collect nothing at all, we ship that build and the platform still works. Submitted info is stored in an access-controlled, encrypted database under our sole control, hosted on U.S. cloud infrastructure. No other institution can read your records. It is never sold, never used for advertising, and never shared beyond the hosting, database, and email services that operate the platform — the same infrastructure layer any enterprise system runs on, each contractually bound to the same protections. No advertising cookies, no tracking pixels, no retargeting. Inquiries route wherever you want them — your spreadsheet, an export format you choose, your admissions inbox — and you can have the records deleted at any time.

Then don't renew. The term is one year. At the end of it your team holds a named inquiry count per program and a cost per inquiry by program, which is more than the college has today whether or not it continues. If that data isn't changing how you staff and promote programs, the decision makes itself.