Why NetHunt for education
Education businesses rarely suffer from “bad sales” — they suffer from fragmented data. A student exists simultaneously across several dimensions: which group they are in, who their teacher is, how much they have paid, what level they are at. When each dimension lives in a separate spreadsheet, no one has the full picture of the student, and a simple question like “how many active students do we have right now, and how many of them are at B1” takes half a day. That is why, for schools, courses, and EdTech, we recommend NetHunt — not as a “sales” CRM, but as a lightweight ERP: a system that holds all these entities together. For very large migrations (tens of thousands of records), we consider Uspacy as the alternative.
The key here is the data model. In NetHunt a student goes through the path Lead → Student → Payer Contact, where these folders are connected by two-way sync: from the student’s record you can see their group, teacher, balance, and all correspondence. On top of this we build “active students” pipelines by level A1–B2 and Looker Studio BI, so management sees the number of active students at each level instantly. The second advantage is Gmail: administrators don’t learn a new program, and every email to parents links itself to the student’s record. The third element is automation: we maintain a catalog of 45 automations, but the key decision is architectural. Bulk and recurring work (monthly billing for hundreds of students, payment reconciliation) we move onto the server via API — integration with Portmone (invoices, webhooks, sub-invoice mapping) and FOP reconciliation, while leaving only single event-driven automations native in NetHunt. This is exactly what keeps a school on the base plan instead of the advanced one even with hundreds of students.
What this looks like in practice is clear from our flagship education project (anonymized). A language school with an active pipeline of hundreds of students (at peak — from 600 to 1400 students) kept its data in disconnected Excel spreadsheets, and teachers had no single gradebook. We built linked Lead/Student/Payer/Groups folders, integrated monthly billing through Portmone with FOP reconciliation, connected Binotel telephony and notifications in Telegram with a Viber fallback, and for teachers we built a Teacher Portal on Laravel (JWT, RBAC, grade journal) with two-way sync — a separate block of end-to-end development of roughly 55 hours: architecture, backend, frontend, integration, deployment. Base NetHunt implementation is 4–6 weeks, while the full ecosystem with portal and billing is rolled out in phases over several months. If your process has its own specifics, those can be accounted for too, with custom work: the folder model is flexible, and the only question is the right architecture for your learning cycle and the NetHunt plan.