In the US education market a CRM is almost never “just a funnel.” The cycle runs through inquiry or campus visit, application or admissions review, deposit or contract, tuition or student accounts, then retention and re-enrollment. Higher-ed offices, private K–12 schools, and course operators do not buy the same stack — and a generic sales CRM does not hold any of those stages by itself.
There is a third group that is easy to confuse in a demo: the sliced stack. Enrollment CRM, SIS, tuition management, and family portal are often separate products from the same brand. This yardstick marks a feature native only when it ships in the product under review. A sibling SKU, marketplace app, or school communications tool sold next door counts as missing — and the profile explains what lives elsewhere.
Family outreach in the US lives in email, SMS, phone, and parent portals. The family outreach axis asks for native messaging on the candidate or family record — SMS/inbox or WhatsApp API. Email-only and portal-only tools do not earn the flag; invoice alerts and third-party school apps stay false.
A daily rotation re-reads official pages in this cut — one category per day — price, trial, new module, URL that disappears. The box at the top says what changed and what stayed the same, so you do not have to open every vendor site. The order only moves when the public source changes the product.