Education Agent CRM vs Notion or Airtable: When to Switch

A boutique education agency does not start with a CRM. It starts with what is already on the laptop. For most owners that is Notion, Airtable, or a shared spreadsheet. That works for a quarter, sometimes a year. Then intake season hits, a sub-agent splits a commission, a CAS deadline lands on a Saturday, and the setup that was fine for ten students drags on the thirtieth.

This article is the boring version of "when to switch." There is no "best of" claim here. Just the points where the database stops doing the work for you, and the points where it still beats a domain CRM.

When does Notion start to drag for an education agency?

Notion holds a small education agency for the first ten or fifteen students. It starts to drag when commissions across multiple currencies need to roll up to a single dashboard, when CAS or offer deadlines need to surface without someone opening the page, and when a sub-agent's share needs to settle on its own.

Notion's real strength for an agency is the writing: the SOP doc, the institution brief, the visa checklist. Those live as pages and get reused. The database side is a paginated table with rollups and relations. For a single counsellor with a clean caseload it is plenty.

The drag points usually fall into three:

• Multi-currency commission. A single rollup in Notion sums numbers. A student paying £4,800 GBP and another paying €2,400 EUR cannot honestly be summed into one currency without a formula and a hard-coded exchange rate. Owners end up with three separate dashboards, one per currency, or a column of converted GBP that drifts whenever rates change.

• Surfacing what is due. A CAS deadline is just a date field. Nothing tells the agency on Monday morning that three students have a deposit deadline this week, two have a CAS issuance window starting, and one has had no contact for nine days. The page does not act on its own.

• Sub-agent splits. When a sub-agent introduced a student and gets 30% of the commission, every invoice means two manual records. Notion does not enforce that pair. One of them gets forgotten until the year-end reconciliation.

None of this means Notion is wrong for an agency. It means Notion is a workspace, not a domain.

When does Airtable start to drag?

Airtable goes further than Notion for relational work. Public intake forms, automations, and per-record audit trails are real on paid plans. It starts to drag when the boutique outgrows a single base maintainer, when a counsellor leaves and the half-built automations are inherited by someone who did not write them.

Airtable's strength is structure. A base with linked tables for students, applications, universities, and commissions is a reasonable relational model. Automations on the Pro plan can flag overdue items and send Slack pings.

The drag points show up in season three:

• Maintainer fatigue. Every formula field, automation, and view was a decision someone made, usually the owner. After a year there are forty views, half labelled "v2," and nobody remembers why one is filtered to "Confirmed without CAS."

• Multi-currency commissions. Same problem as Notion. Rollups need a currency-aware formula. A sub-agent split needs two records linked manually each invoice cycle.

• Public intake form limits. Airtable forms accept submissions, but mapping them to fill only the empty fields of an existing student record, without overwriting confirmed data, is custom scripting work. Most boutiques skip the script and live with duplicate records.

Airtable is not wrong either. It is a database, and a database needs a maintainer.

What does an education agent CRM do that a generic database cannot do natively?

A domain CRM puts the work the agency already does, student lifecycle, commission across currencies, sub-agent splits, intake collection, deadline triage, into the table schema itself. The owner does not configure those concepts. They use them.

For a 1-15 counsellor boutique, that maps to roughly five things a generic database asks the owner to build:

• A lifecycle that names the real stages. Preparing, Applied, Offered, Confirmed, Enrolled. Each stage has the deadline fields that stage actually has (offer deadline, acceptance deadline, deposit deadline, visa deadline). The owner does not invent these.

• A commission record that knows its own state. Claimable, Invoiced, Partial, Collected, with an automatic "overdue" mark when an invoice has been sitting for thirty days. Across currencies, totals stay in their native currency. £4,800 and €2,400 stay £4,800 and €2,400, not a misleading sum.

• A sub-agent split that records itself. A referral percentage on the student record splits the commission into two records the moment the invoice is generated. Year-end reconciliation does not start from spreadsheet archaeology.

• A morning inbox that triages itself. Students with no contact for several days, applications with no deadline set, documents that have not moved in two weeks, these surface automatically. The owner does not write the rule.

• A public intake form that fills only what is empty. A token link sent to the student or parent collects test scores, parent contact, budget, and writes only the fields that were blank. Confirmed records stay intact.

Each of these is buildable in Airtable, with formulas and scripts. The question is whether the boutique owner wants to be the database engineer.

Where do Notion and Airtable still beat a domain CRM?

Notion wins for the writing side of the agency, SOPs, institution briefs, country guides, and as the everything-bucket for a one-person operation. Airtable wins when the boutique already runs other workflows on it and a separate CRM would mean a context switch. The honest segment lines:

• Under ten active students. A domain CRM is overhead. Notion is fine.

• Heavy non-CRM writing. If SOPs and institution profiles live in Notion and the team reads them weekly, ripping the writing out is loss without gain. Keep Notion for the writing and run a CRM in parallel.

• Workflows beyond agency work. An Airtable base running marketing, non-education invoicing, and event logistics is not replaceable by a CRM. Add a CRM beside it, do not switch.

• One-person operation. The maintainer problem disappears when there is one maintainer and one user. Notion or Airtable is fine until the second counsellor joins.

A CRM stops paying off when the data is not concentrated in the agency lifecycle. Below that threshold, a database is the right tool.

How should a 1-15 counsellor boutique decide?

Three threshold questions. If two of three are yes, a domain CRM starts to pay off:

1. Are you tracking commission in more than one currency? GBP, EUR, USD, INR. If more than one currency appears in your records and you cannot sum them honestly, the database is dragging.

2. Does anything other than your eyes flag overdue deadlines? If "I check the spreadsheet on Monday" is the answer, you are the automation. That works until a Monday is missed.

3. Have you ever lost or argued about a sub-agent split? Once is enough. The manual-record approach has already cost you. The next dispute is cheaper than the first.

If you answered yes to two or three, the monthly cost of a domain CRM is below the cost of one missed CAS deadline. If you answered no to all three, you are not the boutique this article is about, yet.

There is no "best CRM" claim here. The boutique that doesn't need a CRM is the one whose students fit on a single screen. Above that, the question is not whether to leave Notion or Airtable. It is whether to keep building the database, or to use one that already knows what an education agency does.

enrollo.io exists for the second answer. The first one is a perfectly good answer until it isn't.