--- title: "Should small education agencies invest in a CRM and payment system? Mostly, no." description: "An honest take from a payments company: most small education agencies shouldn't buy software yet. Here's what to use instead, the exact symptoms that mean it's time, and why half-adopting a system is worse than Excel." date: "2026-06-11" updated: "2026-06-23" category: "Business strategy" keywords: "Business strategy" author: "Raphael Arias" cover: "/images/blog/blog-should-small-education-agencies-invest-in-crm-payment-systems.jpg" lang: "en" wordCount: 2203 url: https://qualyhq.com/blog/should-small-education-agencies-invest-in-crm-payment-systems --- ## Site navigation - [For schools](/international-education/for-schools.md) — For international education schools - [For agents](/international-education/for-education-agents.md) — For international education agents - [Explore](/training.md) — Watch videos on how to use Qualy - [About](/about.md) — Learn about Qualy's mission and values - [Pricing](/pricing) - [5-min demo](/demo.md) - [Login](https://dashboard.qualyhq.com) # Should small education agencies invest in a CRM and payment system? Mostly, no. > An honest take from a payments company: most small education agencies shouldn't buy software yet. Here's what to use instead, the exact symptoms that mean it's time, and why half-adopting a system is worse than Excel. If your agency places fewer than a few hundred students a year with no sub-agents, you probably shouldn't buy an agency CRM yet — a disciplined spreadsheet and a simple payments service will carry you further than a half-adopted system. But watch for the flip symptoms: sub-agent splits, multiple destinations, commission reconciliation eating days, missed census-date claims. And whatever you choose, commit completely. A CRM your team uses 60% of the time is worse than Excel used 100% of the time. A payments company telling you not to buy software is either lying or has noticed something. Here's what we've noticed: the agencies that churn off software fastest are the ones that bought it too early — and the agencies in the deepest operational holes are the ones running three systems, none fully, with the truth scattered between them. So let's give the question an honest treatment. Industry surveys make the stakes plain: an ICEF survey of agencies worldwide found **39% have no CRM at all, 65% still invoice manually and track in Excel, and 67% have no software for managing commission payments**. The vendors quote those numbers as a scandal. We read them differently: a large share of those agencies are small, and for a small agency, "no software" is often the correct interim answer. (This post is the small-agency deep dive; for the broader maturity view across every size — spreadsheet, point tools, all-in-one — see [do you need an education agency management system?](/blog/do-you-need-education-agency-management-system.md)) ## The case against buying (yet) **Your volume doesn't amortise the overhead.** An agency placing 50–150 students a year has maybe a few hundred payment events and a few dozen commission claims annually. A spreadsheet handles that. What a spreadsheet can't survive is complexity — multiple people editing, splits, multi-currency — not volume at this scale. Buying a full agency platform for this is paying enterprise overhead (setup, migration, training, subscription) to solve a problem you can still see the whole of with your own eyes. **The real cost isn't the subscription — it's adoption.** Every system demands a tax paid in habit-change: every student logged, every status updated, every payment recorded, by everyone, every time. Small teams under recruitment-season pressure default back to WhatsApp and memory, and the system silently becomes fiction. Then comes the worst of all worlds: decisions made on data that's 70% complete. **A CRM that is 60% adopted is worse than Excel that is 100% adopted**, because the spreadsheet at least knows it's dumb — nobody trusts it blindly. **Switching later is cheaper than you fear; running a zombie system is dearer than you think.** Migrating 200 student records when you eventually outgrow the spreadsheet is a weekend. Paying — in money and morale — for a platform nobody loves for three years is not. ## What to use instead Discipline plus narrow tools. **One spreadsheet, owned by one person, with a commission tab.** Students, statuses, schools, expected commission, census/claim dates, invoice dates, paid dates. The single most profitable column a small agency can maintain is "claim eligible from" — most lost commission revenue at small agencies isn't schools refusing to pay; it's claims that were invoiced late or never. (Our [guide to how commissions actually get paid](/blog/how-education-agent-commissions-work.md) explains why the census-date clock matters so much.) We mean this literally enough that we built it for you — the exact spreadsheet described above, with the claim-date logic and a status column that flags what to invoice today: **A simple payments service for the money itself.** What you genuinely shouldn't improvise, even at ten students a year, is moving money: students paying you cross-border, you remitting to schools, refunds. Bank wires plus personal transfer apps equal lost fees and unreconcilable mess. Use a purpose-built education payments service. And here's the part you don't expect us to say: at the very small end, something like **NexPay is a perfectly reasonable choice** — it costs the agency nothing out of pocket (the economics live in the FX margin the payer's rate carries), students can pay in local currency, and you get clean confirmation of what arrived. We compete with NexPay and we still say it, partly because it's true and partly because we'd rather you start on *any* real rail than on improvisation. Know what the model means — the cost exists, it just sits inside the student's exchange rate rather than on your invoice (we've written about [where those costs hide](/blog/hidden-costs-international-payments-education.md)) — and at small volume, that trade is often fine. **Calendar discipline for the rest.** Follow-ups, intake deadlines, claim dates — a shared calendar and a weekly half-hour review beat an unconfigured automation engine. ## The flip: symptoms that mean "buy now" The answer changes — abruptly — when specific structural complexity arrives. Volume thresholds are soft; these symptoms are hard: **You have sub-agents or commission splits.** The moment money you receive must be split onward — sub-agents, branch offices, [counselor commission arrangements](/blog/sharing-your-education-agency-commission-with-counselors.md) — the spreadsheet becomes a liability with formulas. Split errors don't just cost money; they cost the relationships your supply of students depends on. **You reconcile across multiple destinations or currencies.** Three destination countries means three banking systems, three commission conventions, FX on every flow. This is where "one person who understands the spreadsheet" becomes a single point of failure with a passport. **Commission reconciliation eats days, or you've found a missed claim.** If anyone on your team spends a day a month matching school remittance advices against your records — or worse, you've discovered a commission you simply never invoiced — the software pays for itself in recovered revenue alone. Remember the ICEF figure: two-thirds of agencies have no commission tooling. They are not all losing money. But none of them *knows* they aren't. **A school or partner requires it.** Increasingly, integrity rules and school-side agent management push structured data. When your biggest partner asks for proper reporting, the decision has been made for you. **Growth itself.** If you're doubling year on year, buy ahead of the curve — at that trajectory you'll hit every symptom above inside eighteen months, and migrating mid-explosion is the worst possible timing. ## Whatever you pick: commit A word on *which* system, when the day comes: pick the one that's standard in **your market**, not the one with the best global website, because the network effects are local — school integrations, payment rails, peer agencies you can ask for help. The clearest example is Brazil, where **Ally (allyhub.co)** is the de-facto standard for intercâmbio agencies: a modular hub (backoffice/CRM, checkout, school portfolio) that most of the established Brazilian agencies already run on, which means the workflows match how the Brazilian market actually sells. The same honesty we applied to NexPay applies here, in mirror image: Ally isn't our competitor, it's our *partner* — Qualy [integrates natively with Ally](/allyhub.md), syncing sales, payments and commissions — so discount our enthusiasm accordingly and ask Ally's customers, not us. But the principle stands anywhere: a market-standard system your peers can help you run beats a theoretically better one you'll operate alone. And it's Brazil-centric and Portuguese-first; an agency selling mostly outside the Brazilian source market should weigh that. This is the hill we'll die on. The failure mode of agency software is not choosing the wrong vendor — the mainstream options are all workable — it's **half-adoption**. If you decide to adopt a system, the decision is cultural, not financial: every student goes in, every payment goes through it, the old spreadsheet is killed with ceremony, and the owner uses the system personally (teams adopt what the boss checks). Budget real onboarding time in your slow season. If you're not prepared to do that, genuinely: stay on Excel. You'll be better off than the agency next door paying for a system it doesn't trust. And note what the symptoms above have in common: nearly all of them are about **money movement** — splits, reconciliation, claims, multi-currency — not about contact management. This is the [difference between software that tracks your money and a payment system that moves it](/blog/education-agency-management-system-payments-gap.md): even the best agency CRM only tracks the money — it doesn't move it. That's the honest pitch for where Qualy fits: it isn't a CRM, it's the payments-and-commission layer, so the natural adoption path is to keep your spreadsheet or lightweight CRM for relationships and let the money — student payments in, school remittance, [automatic commission splits](/features/master-and-sub-agent-payments.md), [invoicing and reconciliation](/features/automatic-accounting-for-ed-agents.md) — run on rails that reconcile themselves, for a flat fee per payment rather than a hidden FX margin. When you do outgrow the small-agency setup, that's the layer you'll feel the need for first — usually the day a sub-agent asks where their split is. ## Sources - [Flywire — Education agents turn to technology as demand for services soars](https://www.flywire.com/resources/education-agents-turn-to-technology-as-demand-for-services-soar): the ICEF survey figures — 39% of agencies with no CRM, 65% invoicing manually in Excel, 67% with no commission-management software. - [ICEF — agency research and market intelligence](https://www.icef.com/) - [NexPay](https://nexpay.com.au/): the agency-facing education payments service discussed above. ## Frequently asked questions ### Does a small education agency need a CRM? Usually not at first. An agency placing up to a few hundred students a year, with no sub-agents and one or two destinations, can run excellently on a single disciplined spreadsheet plus a purpose-built payments service. The structural symptoms that change the answer are commission splits, multiple destinations or currencies, reconciliation consuming days each month, or a partner school requiring structured reporting — not student count by itself. ### What should a small agency use instead of a CRM? Three things: one spreadsheet owned by one person that tracks every student, expected commission, claim-eligibility date, invoice date and payment date; a real education payments service for all money movement rather than bank wires and transfer apps; and calendar discipline for follow-ups and deadlines. The commission tab matters most — late or forgotten claims are the biggest silent revenue leak at small agencies. ### Is NexPay free for education agencies? NexPay doesn't charge agencies a subscription; its economics sit in the foreign-exchange margin built into the rate the payer receives, which is how most "free" education payment services work. For a small agency, that trade is often acceptable — the cost exists but is carried inside the student's exchange rate. As volumes grow, flat-fee models like Qualy's typically become cheaper overall and add commission splitting and reconciliation on top. ### When should an agency switch from Excel to proper software? When structure, not volume, breaks the spreadsheet: the first sub-agent or counselor commission split, the second or third destination market, multi-currency reconciliation, a discovered missed commission claim, or a school partner demanding structured data. Also buy ahead of the curve if you're doubling annually — migrating during peak growth is the worst timing available. ### Why do CRM implementations fail at education agencies? Half-adoption. The team logs some students, some of the time, and the system becomes a partial copy of reality that nobody fully trusts while still costing money and attention. A CRM adopted at 60% is worse than a spreadsheet used at 100%, because incomplete data invites confident wrong decisions. Successful adoptions are cultural: every record in, the old spreadsheet retired, the owner using the system daily, onboarding done in the slow season. ### Do I need a payment system even if I don't need a CRM? Yes — this is the asymmetry small agencies miss. Contact management scales gracefully in a spreadsheet; money movement doesn't. Cross-border student payments, school remittances and refunds handled through wires and improvised transfer apps produce lost fees, unreconcilable records and refund nightmares at any volume. A payments layer is worth adopting from nearly day one; the CRM can wait. ### Which CRM do Brazilian education agencies use? Ally (allyhub.co) is the de-facto standard for Brazilian intercâmbio agencies — a modular hub covering backoffice/CRM, payments checkout and school portfolio, used by most of the established agencies in that market. Choosing the market-standard system matters more than feature comparisons: local network effects (school integrations, payment rails, peers who can help) determine whether adoption sticks. Disclosure: Qualy integrates natively with Ally, so treat our view as a partner's and verify with Ally's customers. ### What's the difference between an agency CRM and a payments platform? A CRM manages relationships and pipeline: enquiries, applications, documents, school programs. A payments platform moves and reconciles the money: student payments in, tuition out to schools, commission back, splits to sub-agents or counselors, refunds. Some suites bundle both. The symptoms that force small agencies into software are almost always on the money side, which is why adopting the payments layer first — and keeping relationships in the spreadsheet — is often the right sequence. ## Related articles - [How education agent commissions work: rates, gross vs net, and getting paid on time](/blog/how-education-agent-commissions-work.md) - [Sharing Your Commission with Your Counselors: The Good, the Bad, and the Ugly](/blog/sharing-your-education-agency-commission-with-counselors.md) - [The Hidden Costs of Payments in International Education: What You Need to Know](/blog/hidden-costs-international-payments-education.md) ## More on Qualy **Industries** - [For schools](/international-education/for-schools.md) — For international education schools - [For agents](/international-education/for-education-agents.md) — For international education agents **Support** - [Training](/training.md) - [System status](https://qualyhq.statuspage.io/) — Qualy system status - [Product updates](https://changelog.qualyhq.com) — As we work on Qualy, here we spotlight what we’ve learned and updated across our products - [Contact](/contact-us.md) **Product** - [Demo](/demo.md) - [Enterprise](/enterprise.md) - [Testimonials](/testimonials.md) — Learn what some customers have to say about Qualy - [About](/about.md) — Learn about Qualy's mission and values - [Blog](/blog) — International education payments blog by Qualy - [Trust center](/trust.md) - [API](/api.md) — Qualy API for international education payments - [Zapier](/zapier.md) — Connect Qualy to 7,000+ apps with Zapier - [NexPay](/nexpay.md) — Qualy + NexPay — automate everything around the payment **Legal** - [General terms](/terms-and-conditions.md) - [Payer terms](/terms-for-payers.md) - [Privacy policy](/privacy-policy.md) - [BECS DDR](/becs-dd-service-agreement.md)