Education CRM: the right shape for international school sales and marketing teams

School-side data is unusually mobile. Heads of school turn over every two to four years on average; IB coordinators rotate within international postings; group operators (GEMS, Nord Anglia, Cognita, Inspired, ISP) buy and rebrand schools constantly; KHDA and ADEK publish new ratings every cycle. A list of school contacts loaded into a CRM in January is meaningfully wrong by July, and badly wrong by the following January. Useful education CRM data has to refresh on a calendar the team can rely on. SchoolIntel re-reads its source layer weekly and re-verifies contacts on a 90-day rolling cadence so the CRM sitting on top doesn't go stale.

School buying committees do not look like SaaS buying committees. A single school can include a head of school as the strategic sponsor, a head of digital learning as the platform owner, an IB coordinator or curriculum lead as the programme owner, an EAL / ELL lead as the language-support owner, an admissions director as the marketing/intake owner, and — for group-owned schools — a group CIO who can pre-empt site-level decisions. Generic CRMs treat these as free-text 'job title' fields. A useful education CRM treats them as a structured taxonomy with role-by-role first-touch routing. See the head of digital learning role page for an example of the role detail SchoolIntel ships.

Curriculum is the single most useful segmentation axis in school sales — it determines who the buying committee is, what the procurement vocabulary is, and which proof points land. A CRM that doesn't know the difference between an IB DP school, a Cambridge IGCSE / A-Level school, and a US AP school will route generic messaging to the wrong champion every time. The same is true for regulators: a school heading into a KHDA / DSIB inspection cycle or a BSO inspection is in a different buying mode than one that just finished one. Useful education CRMs make curriculum and regulator state first-class facts on the account record, not free-text custom fields. SchoolIntel binds them to source citations — IBO, Cambridge International, BSO, COBIS, KHDA, ADEK — so the segmentation can be defended to a CRO.

In school sales, the most reliable buying signal isn't a marketing-qualified click. It's a hiring post or a leadership change. A school posting a head of digital learning role on TES international is signalling future platform spend three to nine months out. A new head of school appointed via TIE Online opens the most vendor-friendly window of the year — the first hundred days. Generic CRMs cannot read these feeds. A useful education CRM treats them as native account-level signals and reorders the queue when they fire.

Most CRM lead-scoring models assume engagement is the strongest signal — opened email, replied, booked a meeting. That works in fast-moving SaaS, but school procurement runs on academic calendars and inspection cycles, not on weekly engagement bursts. A useful education CRM scores accounts on a mix of curriculum / region fit, regulator timing, hiring signals, group activity, and event proximity — then refreshes the order weekly so reps work the right 5–10 schools each Monday.

Best fit: small or solo EdTech sales teams (1–5 reps), early-stage vendors, agencies running point on outreach for an EdTech client, anyone whose previous CRM was a spreadsheet. SchoolIntel ships the data layer, the role coverage, the signal feed, and a built-in outreach surface that drafts cited, role-aware first-touch messages. You don't pay extra for a separate CRM, and the team isn't constantly retyping data into a generic database. The trade-off: SchoolIntel is not a full pipeline tool — it doesn't model multi-stage opportunity pipelines, forecasting, quotes, or post-sale customer-success workflows. If you don't need those yet, this is the cheaper, faster setup.

Best fit: established EdTech sales teams (5+ reps) already running on HubSpot, Salesforce, or Pipedrive with deal stages and forecasting they trust. SchoolIntel sits upstream as the data layer: it hands cited, role-mapped accounts (and signal stamps) into the CRM, then keeps re-scoring the working list. The CRM stays the system of record for pipeline, forecasting, and reporting. The agency / sales team owns the cadence inside the CRM; SchoolIntel keeps the source list alive.

Most EdTech teams start in Mode 1 (SchoolIntel as CRM) and move to Mode 2 (SchoolIntel + Salesforce/HubSpot) once they have multiple reps, multi-stage pipelines, and a need for board-grade forecasting. The data layer doesn't change between modes — only the system of record does. That's by design: it should never feel like a re-platforming when you graduate.

The moment you're working more than ~50 schools, expanding into more than one country, or selling a product where the buying committee includes both a head of school and a curriculum-specific role, the generic-CRM model breaks. That's when source reconciliation, role coverage, and signal freshness start eating margin — and that's the gap the international school market intelligence stack and the ISC Research alternative comparison walk through.

Realistic effort to assemble a defensible school-side data layer on top of an existing CRM, before any sequencing happens:

What you get without building any of the above:

Monday morning: opens HubSpot. Sees the same list she opened last week. Sorts by 'last contacted'. Picks 30 schools to sequence. Half of them haven't been re-verified in six months — three bounce. Two have had a new head of school appointed in the last quarter; the AE doesn't know. One is in the middle of a KHDA inspection and would be highly receptive; the AE doesn't know. By Wednesday, reply rates look the same as last week, and she escalates to her manager that the territory is 'tapped out'.

Monday morning: opens the SchoolIntel queue. The list has reordered itself based on the last seven days of signals — three schools just hired heads of digital learning, two posted IB coordinator roles, one entered a KHDA re-inspection window, one ISP acquisition closed last week (re-opens platform decisions). The AE picks the top ten, exports them with cited reasons into HubSpot, and runs the cadence in HubSpot Sequences. By Wednesday, the AE has three replies — each sequence opened with a paragraph that named the school's actual situation, not a generic intro.