K-12 enrollment teams run on three email inboxes, a shared Google Sheet of inquiries, a student information system that was not built for pipeline, and a parent-communications tool nobody loves. Strkr unifies the enrollment pipeline, the family record, the sibling link, the tour and shadow day calendar, and the parent communications on one platform with FERPA-aware access controls.
K-12 enrollment is a motion that most generic CRMs miss by a wide margin. The buyer is the family, not the student alone. The decision is seasonal and emotional. The data model has to handle siblings, re-enrollment, and the inquiry-to-enrollment funnel across tour, shadow day, application, financial aid, and decision. The pain points below are what we hear on calls with directors of enrollment, admissions ops, and heads of school across districts, charter networks, and private K-12 schools.
Generic CRMs model one contact per record. K-12 enrollment runs on family units: two parents, three siblings, a prospective applicant, and sometimes a non-custodial parent in the loop. A real education CRM has a family object with the student records linked, not a flat contact list where the admissions team guesses who belongs to whom.
Open house in October, applications due January, decisions in March, deposits in April. The pipeline is spiky, the team is small, and the workload triples for five months. A CRM that cannot handle a 10x inbound week does not survive October. Strkr handles the spike with routing, flows, and dashboards that keep the small team honest.
A family with three kids at the school gets a sibling discount. The returning sixth-grader is on a re-enrollment path, not a new-applicant path. The legacy family's youngest child goes through a different workflow than a cold inquiry. Generic CRMs cannot model these branches without a developer; Strkr admin can.
Schools use PowerSchool, Blackbaud, Veracross, or FACTS as the student information system. Those are strong for enrolled students and bad for prospective ones. The enrollment pipeline has to live somewhere else. Strkr becomes the pipeline, pushes enrolled families to the SIS, and keeps the two in sync.
FERPA requires that staff access to student education records be scoped to educational interest. In a CRM, that means not every admissions assistant, teacher, or office staffer should see every application essay, every financial aid detail, and every disciplinary note. Strkr's permission model handles the FERPA-aware scoping without a certified admin.
Mass email about open house, personal note to a hesitant applicant, broadcast about weather closures, 1:1 thread with a parent about financial aid. The same tool should handle all four. Most schools run four separate tools and the touches cross wires. Strkr handles broadcast, lifecycle flows, and one-to-one email and SMS in one surface.
The admissions team opens the family record and sees the whole picture. Below is the data model that sits on a family, built for how K-12 enrollment actually works, not retrofitted from a generic B2B schema.
A family record carries two parent contacts, the student applicants, enrolled siblings, and any non-custodial parent flagged in the record. The admissions team sees the whole family in one view, which matches how parents experience the enrollment process.
The applicant record carries grade applying for, year, program, athletic or arts interests, the application essay, teacher recommendations, test scores if required, and the decision timeline. Siblings on different pipelines live under the same family. Multi-year applicants have their history visible.
The pipeline stage reflects where the family is in the funnel. Default stages are inquiry, tour scheduled, tour completed, application started, application submitted, decision pending, decision released, deposit paid, enrolled. The admin can add stages for financial aid, interview, or shadow day.
Tour requests, shadow day bookings, and parent coffee signups route through the Strkr calendar surface. The booking lands on the family record with the slot, the host, and any pre-tour forms submitted. The team sees the day's tours in one dashboard with the right prep for each family.
For schools with financial aid, the record carries the aid request status, the award if offered, and the parent conversations about aid. The field is permission-scoped so only the aid committee and the director of enrollment see it. The classroom teacher and the admissions associate do not.
A family that inquired for 6th grade in 2024 and declined, then came back for 7th grade in 2025, is one family record with the full history. The admissions director reads the past touches and decides the right follow-up. No duplicate contacts, no missed context.
K-12 enrollment has a known rhythm. The lifecycle flows below are the seven motions that run every season, pre-built as templates the admissions ops lead can edit for the school's voice and timeline.
A form submission on the school website creates a family record and triggers the first email with the next steps, the tour calendar, and the application timeline. The admissions associate receives a task to follow up personally inside 24 hours. Response time is the biggest predictor of enrollment conversion.
Twenty-four hours before a tour, the family gets a reminder with parking, what to bring, and the host's photo. Twenty-four hours after, the host sends a personalized follow-up with the application link and answers to any specific questions raised. The admissions director sees the whole thread.
A family that started an application but has not submitted after 14 days gets a soft nudge with a reminder of the deadline and an offer of help. A family stuck at the financial aid step gets a different nudge pointing to the aid office. The lifecycle flow treats stalled applications as a real motion, not a mystery.
Decision day runs through the flow surface. Admits receive the welcome email, the enrollment contract link, and the deposit timeline. Waitlist and deny families receive honest, humane language that does not slam the door for next year. The head of school sees the decision ratios on the dashboard.
After admit, a flow runs the deposit timeline: contract signed, deposit paid, SIS record created in PowerSchool or Blackbaud. Each milestone updates the family stage. The admissions director sees the yield funnel in real time instead of asking the registrar for an export.
Returning families run on a re-enrollment flow with the contract renewal, the tuition conversation, and the sibling-adding path. The returning sixth grader is not a new inquiry. Strkr models the re-enrollment motion as a separate pipeline so the data stays clean and the touches stay right.
Families that reach decision stage and decline get a thoughtful winback after a season, not immediately. The intent is honest: understand why they chose elsewhere, keep the door open for a younger sibling, and build the referral motion. The flow is seasonal and the touches are human.
Family Educational Rights and Privacy Act requires that staff access to student education records be limited to legitimate educational interest. The Strkr permission model handles this at the field, record, and view level, with an audit log that passes a FERPA audit without a certified admin or external review.
Strkr ships role templates for director of enrollment, admissions associate, financial aid officer, division head, and classroom teacher. Each role has a defined scope: what pipeline, what fields, what families. The admin can tune the roles without a developer or a certified consultant.
The financial aid award, the disciplinary notes, and the sensitive family circumstances fields can be permission-scoped to the aid office or the division head only. A classroom teacher pulling up a family sees the student information they need and not the aid detail they do not.
Certain family records, such as board-member legacies or significant donor families, can be scoped to the head of school and the development office only. The admissions associate processing routine inquiries does not see those records. Legitimate educational interest, defined and enforced.
The audit log records every view, every edit, and every export of a family or student record with the staff member, time, and action. A FERPA audit or an internal review can read the log without a vendor services call. The log is retained per the tenant's configured policy.
Strkr exports contacts, families, applicants, and pipeline data as CSV. The export respects the exporting user's permissions, so an admissions associate cannot export a view that includes fields they could not see in the UI. A FERPA export of a family record is one-click for a records request.
Strkr carries HIPAA with a Business Associate Agreement available on request for schools with health services under FERPA plus HIPAA overlap. SOC 2 Type II is in progress through 2026 Q4. The security documentation ships under NDA during evaluation, not after signature.
The K-12 segment is not one shape. Districts, charter networks, independent private schools, and tutoring companies all have different pipelines, data models, and compliance realities. Strkr handles each with the same platform and different configuration, not a different product.
A charter network with four campuses runs each campus as a pipeline on one Strkr tenant. The CEO sees network-wide enrollment, the campus director sees their pipeline, and the admissions associate sees their queue. Transfer requests between campuses live as a flow with the right approvals.
An independent K-12 or PK-8 private school with a strong legacy family motion, financial aid, and a referral culture. Strkr handles the family record, the legacy tracking, the aid committee workflow, and the referral touches. The admissions director runs the whole season from one surface.
A public school district running magnet, choice, or specialized program enrollment. Strkr handles the lottery, the choice pipeline, the parent communications, and the FERPA-aware access scoping. The district office sees aggregate; the school principal sees their school.
A tutoring or test prep company with ongoing enrollment, package renewal, and parent communications. Strkr handles the family, the student profile, the package, the renewal, and the parent conversation. The business runs as a services firm with K-12 compliance posture.
A boarding school with international recruiting, agent relationships, and residential life interactions on the family record. Strkr handles the agent as an account, the international family as a contact, the application plus visa timeline, and the residential life context. One record, one view.
Strkr is not PowerSchool, Blackbaud, Veracross, or FACTS. The enrolled student lives in the SIS. Grades, attendance, and schedule stay there. Strkr is the inquiry-to-enrollment pipeline, the family relationship record, and the parent communications surface. Enrolled families sync to the SIS on deposit paid.
Side by side on the questions directors of enrollment and admissions ops leads actually ask when comparing Strkr to a Blackbaud, Veracross, or FACTS enrollment module.
| Feature | Strkr | Blackbaud or Veracross enrollment module |
|---|---|---|
| Family data model | Family unit with parents, students, siblings | Contact-first, family relationships bolted on |
| Pipeline flexibility | Admin-editable stages per campus or pipeline | Fixed enrollment stages, custom via services |
| Flow builder | Visual canvas for enrollment lifecycle | Scripted automations, consultant-built |
| FERPA aware access | Role and field-level permissions in admin | Enterprise tier add-on, services engagement |
| SIS sync | Open API plus prebuilt PowerSchool and Blackbaud sync | Native to one SIS, closed to others |
| Pricing shape | Per seat with every capability | Per-record meter plus module tiers |
| Setup time | Weeks for a single school, months for a network | Months to a year with a certified partner |
| Mobile parity | Native iOS and Android for tour and inquiry logging | Varies, often web-only |
| Audit log | Every access, edit, and export logged | Available on enterprise tier only |
The three admissions team shapes most common on buyer calls, with what the Strkr implementation looks like for each.
A charter network with four campuses, a central admissions team of three, and 2,400 inquiries a year. Strkr runs the inquiry-to-enrollment pipeline per campus with network-wide reporting. The CEO sees enrollment velocity in real time instead of a quarterly deck.
An independent K-8 with 240 students, 160 families, and a strong legacy motion. Strkr runs the inquiry flow, the sibling discount logic, the aid committee workflow, and the parent communications. The director of enrollment runs the whole season on one surface.
A boarding and day school with 420 students, 30 percent international, and agent relationships in six countries. Strkr handles the agent accounts, the international family records, the visa timeline, and the residential life context. The admissions office stops juggling three tools for international and one for local.
A charter network, an independent school, a district choice office, or a tutoring company can be in production inside a season. Start a trial and import families from the current spreadsheet in one afternoon.
A student information system such as PowerSchool, Blackbaud, Veracross, or FACTS is the system of record for enrolled students, which covers grades, attendance, schedule, and transcript. An education CRM is the system of record for prospective families and the inquiry-to-enrollment pipeline, which covers tours, applications, decisions, deposits, parent communications, and re-enrollment. The two are complementary and sync on enrollment events.
FERPA is a federal law that governs access to student education records. Strkr's permission model supports FERPA-aware scoping at the role, record, and field level, with an audit log of every access, edit, and export. The compliance posture also includes HIPAA with a Business Associate Agreement available on request for schools with health services overlap, GDPR and CCPA for European and California families, and SOC 2 Type II in progress through 2026 Q4.
Strkr ships prebuilt sync with PowerSchool and Blackbaud for the common enrollment events: contact sync, family sync, and enrolled family creation on deposit paid. For Veracross, FACTS, and other SIS platforms, the open REST API handles the sync with a modest configuration. The admin owns the mapping, which stays portable.
Our education-crm page is the K-12 lens: districts, charter networks, independent private schools, and tutoring companies. Our educational-crm page is the higher-education lens: colleges, universities, continuing education, and professional programs. The pipelines and data models differ between those segments, which is why we treat them as two pages.
Strkr is priced per seat with every capability on every paid plan. A typical independent school enrollment team is three to five seats; a charter network office is five to ten; a district choice office is five to twenty. There is no per-family or per-inquiry meter, so an enrollment spike in October does not change the invoice. The current pricing page has the live numbers.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
