Skip to content
SchoolIntel
Sign inBook a demo

Agency hub

School Intelligence for EdTech Marketing Agencies

Reviewed byJohn Thomas, Founder, SchoolIntellast reviewed May 2026

Marketing agencies serving EdTech clients use SchoolIntel as the data layer underneath their deliverables. Instead of staffing analysts to reconcile KHDA, IBO, BSO, COBIS, Cambridge, school websites, hiring boards, and association calendars, the agency starts with cited account maps, role coverage, and weekly signal updates. The first month is a sourced account map plus campaign wedges; months two through twelve are a monthly retainer brief, event packs for GESS, COBIS, BSME and EARCOS, and CRM enrichment shipped into the client's HubSpot or Salesforce. SchoolIntel makes the agency the source of truth — a positioning that wins retainers and survives renewals.

Build a client account mapSee data sources ↓

International schools worldwide

~14,500

Source: ISC Research market sizing (2024)

Private schools in Dubai alone

~220

Source: KHDA factbook (2024–25)

IB World Schools globally

~5,800

Source: IBO Find an IB School directory

Average agency research engagement

4–8 weeks

Source: SchoolIntel agency-customer interviews (2026)

Sources an agency must reconcile

8–12 per market

Source: SchoolIntel source-coverage model

Time saved with cited account maps

~60 hours per client brief

Source: SchoolIntel agency-customer benchmarks (2026)

Featured schools

A representative slice of the market

Client onboarding brief

Week 1 — discovery + market scoping

Agency interviews the EdTech client, agrees on curriculum stripes, geographies, role personas, and definition of a qualified account. SchoolIntel becomes the shared source of truth from day one.

Agency workflow + SchoolIntel hub

Verified

Sourced account map (v1)

Week 2 — defensible target list

First account map: 80–250 schools filtered by curriculum, region, group, and accreditation, each with a citation trail back to KHDA, IBO, BSO, COBIS, or school websites. Replaces an undated CSV.

SchoolIntel exports + source pages

Verified

Role coverage layer

Week 2–3 — buyer mapping

Heads of school, IB coordinators, heads of digital learning, EAL/ELL leads, admissions, and group-level CIOs mapped per account so the agency can route messaging to the actual champion.

SchoolIntel role taxonomy + role pages

Verified

Signal overlay

Week 3 — recency layer

Hiring activity, leadership changes, accreditation milestones, group expansion, KHDA/DSIB rating moves, and event sponsorships layered onto the account map so the agency can defend why now.

Hiring boards + association calendars + SchoolIntel signal model

Verified

Campaign wedge selection

Week 3–4 — message-market match

Agency picks 2–4 campaign wedges (e.g. accreditation cycle, new head, IB authorization, group rollout) and segments accounts so each wedge runs against ~30–60 schools instead of one undifferentiated blast.

Agency creative + SchoolIntel filters

Verified

GESS Dubai event pack

Pre-event + post-event playbook

Pre-show: visiting heads, exhibitor lists, target meetings. Post-show: sponsor follow-ups segmented by curriculum and region. Built for the GESS calendar instead of a generic blast.

GESS official program + SchoolIntel event mapping

Verified

COBIS Annual Conference pack

British international school leadership reach

Member-school list cross-checked against attending heads and bursars. The agency can deliver pre-conference invites, on-site meeting plans, and post-event nurture journeys.

COBIS member directory + conference program

Verified

BSME conference pack

Middle East British school leadership

BSME's annual conference brings Gulf British school heads together; pack includes member roster, regional KHDA tier overlay, and recommended booth/sponsorship messaging.

BSME annual conference page + regional sources

Verified

EARCOS event pack

East Asia + Southeast Asia leadership

EARCOS Leadership Conference and Teachers' Conference packs — country-by-country member coverage with role layer for vendors expanding into APAC.

EARCOS member directory + event calendar

Verified

Retainer market brief (monthly)

Ongoing — month 2 onward

A monthly market brief that re-scores the account list, surfaces fresh hiring/leadership signals, and recommends the next 10–15 accounts to work. The agency ships this to the client as a polished deliverable.

SchoolIntel weekly re-scoring + agency layer

Verified

CRM enrichment delivery

Operations layer

Agency pushes cited, role-mapped, deduped accounts into the client's HubSpot, Salesforce, or Pipedrive — with source URLs, last-verified dates, and signal stamps preserved as fields.

SchoolIntel exports + agency CRM ops

Verified

Quarterly executive review

Stakeholder reporting

Quarterly readout to the EdTech client's leadership team: market coverage, accounts touched, signal-driven wins, and a fresh recommendation for the next quarter's wedges.

Agency reporting + SchoolIntel analytics

Verified

Account-list defence pack

Stakeholder evidence layer

When the EdTech client's CRO or CMO asks why a specific school is on the list, the agency delivers a one-page evidence card: source URLs, signal dates, role coverage, and recommended next action.

SchoolIntel source citations

Verified

Pilot-school shortlist

Sales-cycle support

10–25 schools where the EdTech client should run a pilot first — selected by curriculum fit, KHDA/BSO alignment, and recent buying signals. Used to seed reference customers fast.

SchoolIntel filters + agency strategy

Verified

Reference-school case-study queue

Marketing asset support

After pilots land, the agency uses SchoolIntel to identify the 3–5 reference schools most likely to consent to a logo/case study — based on group affiliation, regional visibility, and conference participation.

SchoolIntel + agency marketing ops

Verified

How a marketing agency uses SchoolIntel for an EdTech client

EdTech marketing agencies sit between two pressures. Their clients want pipeline tomorrow, and the international school market — across the UAE, Dubai, Abu Dhabi, Qatar, and beyond — does not behave like a SaaS list. Schools are accredited, regulated, and grouped; their buying committees split across curriculum coordinators, heads of digital learning, and group-level CIOs. The agency has to deliver a target list the client's CRO can defend in a board meeting, then keep that list alive for six to twelve months.

SchoolIntel is the layer agencies plug in so they don't rebuild the same scaffolding every project. Instead of starting from International Schools Database, WhichSchoolAdvisor, and a half-built CSV, the agency starts with cited accounts, role coverage, and recent signals. Discovery week becomes deliverable week.

Average research phase

4–8 weeks

Source: SchoolIntel agency-customer interviews

Sources reconciled per market

8–12

Source: SchoolIntel source-coverage model

Hours saved with cited maps

~60 per client brief

Source: SchoolIntel agency benchmarks

Agency engagement phases — typical EdTech client retainer

What a 1–2 month research engagement looks like before it transitions into a monthly retainer. Discovery and account mapping happen up front; the retainer keeps the list alive.

  • Discovery + scoping10.0% weeks
  • Sourced account map10.0% weeks
  • Role + signal layer10.0% weeks
  • Campaign wedge build10.0% weeks
  • Activation + first wave20.0% weeks
  • Monthly retainer brief40.0% weeksongoing

The four-week sprint that becomes a retainer

A typical EdTech-client research engagement lasts four to eight weeks, then transitions into a monthly retainer brief. SchoolIntel compresses the upfront sprint and powers the retainer:

  • Week 1 — scoping: agree curriculum stripes, regions, role personas, and what counts as a qualified account. Anchor the brief in published sources like the KHDA factbook portal and the IB Find an IB School directory.
  • Week 2 — sourced map: ship the first account map with citations. Cross-reference BSO inspection reports and COBIS member listings so every British-curriculum row has a verifiable origin.
  • Week 3 — role + signal layer: attach buyer roles and recency. Use the head of digital learning page and IB coordinator page as the persona scaffolding.
  • Week 4 — wedge build: pick two to four campaign wedges and split the account list across them — accreditation cycle, new head of school, IB authorization window, group-wide platform rollout.
  • Month 2+ — retainer brief: a monthly readout that re-scores the list, surfaces fresh signals, and recommends the next 10–15 accounts. The agency ships this as a polished client artefact.

Why this looks different from a SaaS playbook

EdTech buyers are not a CFO and a procurement manager. A single school can have an IB DP coordinator who chooses assessment tools, a head of digital learning who chooses platforms, an EAL lead who chooses language support, and a group-level CIO who pre-empts site decisions. See the EAL coordinator page and ELL coordinator page for the persona detail. Agencies that try to run a single hero-message campaign across all of them lose to specialists who segment.

What the client actually receives — deliverables agencies ship

Most EdTech CMOs hire an agency expecting a campaign. What they need first is an account list they can defend. SchoolIntel gives agencies the raw material to ship a tighter, sourced deliverable suite — and to charge for it. The education marketing agency data hub walks through the asset templates; this section is the workflow.

Agencies that win retainers tend to bundle four artefacts into the first month: a sourced account map, a role coverage matrix, a signal calendar, and a campaign wedge plan. Each one ties back to a specific source — KHDA inspection reports, BSO inspection reports, COBIS member search, Cambridge International, and live job boards like TES international — so the CRO never has to ask 'where did this come from?'.

Where agency hours go on a typical EdTech client engagement

A six-to-eight week engagement, broken down by where the work actually happens. Most agencies discover that source reconciliation and freshness — not creative — eats their margin.

The four core deliverables

Each maps to a specific moment in the EdTech client's quarter:

  • Sourced account map: 80–250 schools, every row with a citation. Replaces a stale CSV. Used by the CRO to defend the territory.
  • Role coverage matrix: for each account, which buyer roles are filled and which gaps need enrichment. Used by SDRs to know who to email first.
  • Signal calendar: month-by-month list of accreditation cycles, hiring windows, group rollouts, and event activations the agency will run against.
  • Campaign wedge plan: two to four message-market pairings, each tied to a sub-segment of the account list. The creative team gets a brief, not a guess.

Why agencies charge more for cited maps

A flat list of 500 schools is commoditised. A list of 180 schools where every row carries the source URL, last-verified date, role coverage, and a signal-driven reason to act is a strategy document. Agencies who bundle SchoolIntel's source layer routinely move from project pricing into recurring retainers because the artefact is repeatable but never finished — the world updates weekly. Compare with static school rosters and the international school email list alternative for the deliverable contrast.

Event packs — GESS, COBIS, BSME, EARCOS

International school events are some of the highest-leverage moments in the calendar. A single event can put hundreds of buying-power roles in one room. Agencies that arrive with a sourced pre-event list and a defined post-event playbook outperform agencies that show up and hand out QR codes. SchoolIntel ships event packs for the four conferences that matter most to EdTech: GESS Dubai, the COBIS Annual Conference, the BSME Annual School Leaders' Conference, and EARCOS.

Each pack pairs the official programme with a list of likely attendee schools, the role coverage on those accounts, and three message angles. See the dedicated guides for GESS Dubai and BSME conference for the full pre/post breakdown.

What goes into a SchoolIntel event pack

Each pack is built once per event cycle, then refreshed weekly until the event:

  • Likely attendees: school list filtered by region, member-association, and exhibitor history. GESS maps to UAE + KHDA cohorts; COBIS maps to COBIS member-school search.
  • Pre-event outreach plan: invite-to-stand and pre-meeting cadence by role — heads to heads of school, IB coordinators to IB coordinators.
  • On-site meeting list: named target meetings with role context and the SchoolIntel signal that justifies the conversation (e.g. KHDA rating drop, new head of digital learning, IB DP authorization in flight).
  • Post-event nurture: 90-day follow-up sequence broken into curriculum stripes (BSO/COBIS, IBO, NEASC) so the same booth conversation routes into different message angles.

Why event packs justify the agency retainer

Most EdTech vendors sponsor one or two events a year and lose half the value to weak follow-up. The agency that runs the event pack — pre, on-site, and post — captures the most defensible work in the calendar. SchoolIntel turns the four major events into reusable artefacts so the agency can run them across multiple clients without rebuilding. The ISC Research alternative page contrasts this with paid-list vendors who sell static attendee CSVs.

Agency-grade intelligence vs self-service tools

EdTech CMOs occasionally ask: why hire an agency when we can pull a HubSpot list and send a sequence? The honest answer is that the underlying data layer for international schools is structurally harder than the typical B2B SaaS prospecting motion. A HubSpot list, an Apollo filter, or a ZoomInfo export will surface domains, but it will not tell the difference between an IB World School with PYP/MYP/DP authorization, a British-curriculum school inspected by BSO, and an unaccredited tutoring centre listed on a parent-facing directory.

Agencies that ship sourced, cited maps with curriculum and accreditation context are operating in a different category from self-service prospecting. SchoolIntel exists to make that category cheap and repeatable for the agency, not to replace the self-service tools their clients already own.

What self-service tools miss

These gaps are the reason EdTech CMOs hire agencies in the first place:

  • Curriculum context: Apollo and ZoomInfo do not know the difference between IB DP and IBCP, or whether a school runs IGCSE or A-Level. Use the Cambridge International school finder and IBO directory instead.
  • Accreditation source provenance: the agency needs to cite BSO, COBIS, IB World Schools, and Cambridge to defend the list.
  • Group structure: HubSpot does not group GEMS or Taaleem schools under a parent operator. Multi-campus decisions cluster at the group level.
  • Regulatory signals: KHDA's DSIB rating cycle is the single best buying-priority calendar in Dubai. No SaaS prospecting tool reads it.
  • Hiring as a buying signal: a head of digital learning posted on TES Dubai is one of the strongest pre-procurement signals in EdTech. Apollo will not tell you.

Where self-service still belongs

This is not an argument against HubSpot or Apollo. They are the right place to operate the cadence, log the sequence, and run reporting. The agency's job — and SchoolIntel's job — is to upstream the cited account list and the buyer-role coverage, then push that into the client's existing CRM. See the static school rosters alternative and international school email list alternative for the data-layer comparison.

The agency–client relationship — research, retainer, source of truth

The agencies winning EdTech retainers do not pitch as 'demand gen agency'. They pitch as 'we are the source of truth for your international school market'. That positioning only works if the underlying data layer is repeatable and defensible. The first month is research and account-map delivery. Months two through twelve are the monthly market brief, the event packs, and the campaign wedge cycles. SchoolIntel is the substrate so the agency can deliver all of it without staffing two analysts.

EdTech clients re-sign agencies that own three things: the account list, the role coverage, and the signal calendar. If those three are owned by the agency, the agency cannot be replaced without the client losing organisational memory. If they live in a stale shared spreadsheet, the agency is one fee renegotiation away from being swapped. See the marketing to international schools guide for the relationship structure agencies use.

The three engagement shapes

Most agency–EdTech relationships fit one of these shapes:

  • One-month research engagement: the EdTech client pays for a sourced account map, role coverage, and a campaign wedge plan. Often a 'land-and-expand' first project; SchoolIntel compresses this to two weeks of agency labour.
  • Two-to-three-month market brief: a deeper engagement that covers a full region (e.g. the entire Gulf, or all of Southeast Asia). Includes event-pack alignment with at least one major conference such as GESS or BSME.
  • Monthly retainer: the durable shape. The agency ships a monthly market brief, owns the campaign cycle, and runs all events the client sponsors. SchoolIntel powers the data layer; the agency owns the client relationship.

How the agency becomes the source of truth

The agency's job is to make sure the client never has to maintain the account list themselves. That means the agency owns:

  • CRM enrichment: HubSpot/Salesforce/Pipedrive fields populated with cited source URLs, last-verified dates, and signal stamps.
  • Quarterly cleanup: dedupe, archive closed schools, surface new openings (especially in fast-growing markets like the UAE and Qatar).
  • Onboarding new client hires: when the EdTech client hires a new SDR or AE, the agency provides the territory map. Without this, every new hire reinvents the list.

Build it yourself or use SchoolIntel

Everything on this page is technically buildable from public sources. KHDA, IBO, BSO, COBIS, Cambridge, school websites, hiring boards, and association directories are all reachable. The honest question is whether your agency should spend the time. Most don't — not because they can't, but because the integration, normalisation, and freshness work is more expensive than the data itself, and the engagement deadline never moves to accommodate it.

Two paths:

Build it yourself

Realistic effort to assemble a defensible international-school market for one EdTech client engagement, before any creative work begins:

  • Source inventory: 3–5 days to map ~10 sources across KHDA, IBO, BSO, COBIS, Cambridge, ISDB, and the major event programmes — and decide which to scrape vs API.
  • Normalisation: 2–3 weeks to dedupe schools across spelling variants, multiple campuses, and group naming. This is the biggest hidden cost in any agency engagement.
  • Role coverage: 1–2 weeks to scrape staff lists, infer titles to a buyer-role taxonomy across EAL, ELL, IB, and digital learning, and verify emails.
  • Signal layer: ongoing — weekly checks against KHDA, TES, school sites, and group press pages. An analyst owns this in perpetuity.
  • Honest timeline: one analyst for ~6–8 weeks per market to build, then ~0.25 FTE forever to maintain. The work breaks the day that analyst leaves the agency.

Use SchoolIntel

What an agency gets without building any of the above:

  • Same-week sourced map: filter by curriculum, region, group, accreditation, and signal — get a cited account list ready for the client deck in one session.
  • Live source consensus: every account carries a confidence score across the 8+ sources we read. The agency can defend each row without doing the work.
  • Role coverage built in: staff lists pre-mapped to a buying-role taxonomy with the recency timestamps the agency needs to look credible.
  • Weekly re-scoring: the queue reorders itself. The agency ships a fresh monthly brief without a research sprint each cycle.
  • Cited reasons per account: every recommended target carries a paragraph explaining why now — backed by source URL, date, and signal type. The CRO never asks where the row came from.
  • Event packs out of the box: GESS, COBIS, BSME, EARCOS — pre-built packs the agency rebrands and ships.

Frequently asked questions

Questions this page answers

What does SchoolIntel actually do for an EdTech marketing agency?

SchoolIntel is the data layer underneath the agency's deliverables. It combines public sources — KHDA, IBO, BSO, COBIS, Cambridge, school websites, hiring boards, and association calendars — into cited, role-mapped account lists with weekly signal updates. The agency uses this to ship a sourced account map, role coverage matrix, signal calendar, and campaign wedge plan to each EdTech client without rebuilding the underlying data scaffolding.

How is this different from buying a static international-school email list?

Static lists from vendors like EducationDataLists answer who exists right now and stop there. SchoolIntel answers what changed and why now: weekly re-scoring across 8+ sources, role coverage, accreditation cycles, and signal stamps the agency can cite to its client. See the international school email list alternative and static school rosters alternative pages for the side-by-side workflow comparison.

What does an agency client engagement look like?

Most engagements are four to eight weeks of upfront research that ship a sourced account map, role coverage, signal calendar, and campaign wedges; then transition into a monthly retainer brief plus event-pack support. The agency owns the client relationship and ships polished deliverables; SchoolIntel powers the underlying data layer so the agency does not staff two analysts to do source reconciliation. See the marketing to international schools guide for the relationship structure.

Which events should an agency build packs for first?

Four packs cover most EdTech-client geography: GESS Dubai for the Gulf and wider MENA, the COBIS Annual Conference for British international school leadership globally, the BSME Annual School Leaders' Conference for Middle East British school leadership, and EARCOS for East and Southeast Asia. See the dedicated GESS pack and BSME pack pages.

Why does curriculum source provenance matter?

EdTech buying committees split by curriculum. An IB DP coordinator does not buy the same product as a Cambridge IGCSE lead or a US AP coordinator. Without source-backed curriculum context — IB World Schools, Cambridge International schools, BSO accredited schools, COBIS members — agencies route messaging to the wrong champion and burn first-touch credibility. SchoolIntel hard-binds curriculum identity to its source so the agency can defend the segmentation.

How does SchoolIntel handle Dubai's school groups?

Roughly 70 of Dubai's ~220 schools sit inside about ten major operators. The biggest is GEMS Education, followed by Taaleem, Nord Anglia, Innoventures, Cognita, Aldar Education, Kings' Education, Repton, and NLCS. SchoolIntel groups schools by operator so agencies can run group-level outreach for platform/MIS/AI products and site-level outreach for department-specific tools. See the Dubai international schools market map for the structural breakdown.

What goes into a monthly retainer brief?

A typical brief includes: re-scored top 20 accounts for the month, fresh signals (hiring, leadership, KHDA rating moves, group expansion, accreditation cycles), recommended next 10–15 accounts to add to the working list, two to four campaign wedge variants, and an event-pack outlook for the next 60 days. The education marketing agency data hub walks through the asset templates.

Does SchoolIntel publish personal contact details on this page?

No. Public pages explain methodology, sources, agency workflows, and account strategy. Names, emails, and phone numbers live inside the authenticated SchoolIntel product, governed by SchoolIntel's privacy controls and access/removal request process. Agencies use the authenticated product to enrich their client's CRM under the agency's own data-processing agreement.

next step

Want this as a live ranked list?

SchoolIntel can turn this page into a sourced target market with account reasons, role coverage, and outreach angles your team can use this week.

Build a client account map