You only pay for scale — not for features. Prices below are placeholders; set your real tiers before launch.
All plans billed annually and include every module. WhatsApp Business API conversation charges are billed by Meta directly.
School budgets are annual, deliberate, and accountable. A principal or trust plans the year's finances in advance and must justify every line to a board or a governing body. Software pricing that is unpredictable — that adds charges when you turn on a feature, that meters usage, that surprises you with an invoice mid-year — is fundamentally at odds with how a school plans. Shiksha CRM is priced to fit the way schools budget: one annual figure, determined by the number of students you have, covering the entire platform. You know at the start of the year exactly what you will pay, and nothing during the year changes it.
Every plan includes every module. The tiers below differ only in the scale they are built for — the number of students, the level of support, and options like custom domains and included data migration. They do not differ in features, because feature-gating a school's software means a school cannot fully rely on it, and reliability is the entire point. Whether you are a small school on the Starter plan or a large campus on Growth, you get live GPS tracking, WhatsApp automation, the parent mobile app, biometric attendance, the full examination suite and everything else, from your first day.
The one cost that sits outside your Shiksha CRM plan is WhatsApp itself. Because the automation runs on the official WhatsApp Business API, Meta charges a small per-conversation fee, billed by Meta directly. Shiksha CRM adds no markup to this — you pay Meta's rate, transparently, and you always know what your communication costs. Everything else — every module, every update, onboarding support — is covered by your annual plan.
It is easy to compare software on price alone, but the more useful question for a school is what the software saves and earns. Consider fees: a school that closes its collection in a day instead of a fortnight, and that recovers outstanding dues faster because reminders actually reach parents on WhatsApp, is not spending money on Shiksha CRM so much as recovering money it was previously losing to delay and leakage. For most schools, the improvement in fee collection alone more than covers the cost of the platform.
Consider staff time. The hours a front office spends sending messages, compiling attendance, reconciling registers and generating marksheets are hours paid for whether or not they produce anything. Automating those tasks does not just make the work pleasant — it frees paid staff to do work that actually matters, or lets a growing school avoid hiring additional administrative staff it would otherwise need. The return here compounds as the school grows.
And consider growth. The admissions CRM exists to fill seats, and a single additional admission that would otherwise have slipped away — an enquiry that was followed up instead of forgotten — can be worth more than a year of the platform's cost. In a competitive admissions market, the difference between a school that lets enquiries go cold and one that nurtures every lead to a decision is measured directly in enrolment, and enrolment is the lifeblood of a school's finances. Priced against these returns, Shiksha CRM is not a cost centre but one of the highest-leverage investments a school can make.
Beyond the headline price, what schools want from a software relationship is the absence of unpleasant surprises, and Shiksha CRM is structured to provide exactly that. There are no setup fees hidden behind the annual figure, no charges that appear when you switch on a module you already have, and no usage meters that turn a predictable cost into a variable one. The number of students you have determines your plan, and that plan covers the platform. When your school grows past a plan's student count, you move to the next plan — a change you can see coming and budget for, not a surprise.
Data migration, the step that schools most fear, is included on the Growth and Trust plans, so moving from your current system or from paper is part of getting started rather than a separate project with a separate invoice. Onboarding support is included on every plan, because software a school cannot get running is worth nothing regardless of its price. And because every school runs on its own isolated database, your data is genuinely yours — separate, secure, and portable — not entangled in a shared system you cannot cleanly leave.
The WhatsApp Business API is the one cost that sits outside your plan, and even there the principle of no surprises holds: Meta charges a small, published per-conversation fee, billed by Meta directly, and Shiksha CRM adds nothing to it. You can see exactly what your communication costs, separate from what your platform costs, with no markup buried in between. This transparency is deliberate. A school choosing Shiksha CRM should be able to know, at the start of the year, very nearly to the rupee what the year will cost — and it can.
Choosing between the plans is straightforward, because they differ in scale rather than capability. The right starting point is your current student count, since that is the single variable pricing turns on. A school of up to three hundred students fits the Starter plan; a school up to fifteen hundred fits Growth; larger campuses and multi-branch trusts are served by the Trust plan. Because every plan includes the entire platform, you are not choosing which features you can afford — you are simply identifying the tier that matches your size, and you can move up as you grow.
Beyond raw size, a few practical considerations point toward one plan or another. Schools that want a custom domain rather than a subdomain, or that want their existing data migrated in as part of setup, will find those on Growth and Trust. Schools that want priority support, or a dedicated onboarding manager and on-site training, are looking at Growth and Trust respectively. But these are conveniences layered on top of a platform that is complete on every plan — a Starter school and a Trust school run the same software, with the same modules, and differ only in the scale and the level of hands-on support around it.
If you are unsure, the simplest path is to tell us your student count and what matters most to your school, and let us recommend the plan that fits. There is no advantage to us in placing a school on a plan larger than it needs — a school that feels well-matched to its plan is a school that stays, and that is the outcome we are building toward. The plans exist to make pricing simple and predictable, not to create a puzzle; a short conversation is usually all it takes to know exactly where a school belongs.
Schools evaluating management software carry a set of well-earned worries about cost, formed by experience with systems that promised one price and delivered another. The most common is the fear of the feature-gated invoice — the sense that the advertised price is only the beginning, and that every useful capability will turn out to cost extra. Shiksha CRM is deliberately built to dissolve this worry: every module is included on every plan, so there is no capability waiting behind a paywall, and no invoice that grows as a school starts to actually use the system it bought. The price you see is for the whole platform.
A second worry is the usage meter — the anxiety that costs will balloon as a school grows or as it sends more messages or stores more data. Shiksha CRM's plan pricing turns on a single, visible variable: the number of students. There is no metering of features, no per-transaction platform charge, no storage tier that surprises a school mid-year. The one genuinely usage-based cost, WhatsApp conversations, is billed by Meta directly at Meta's published rate with no markup, so even that is transparent and separate, never buried inside the platform price.
A third worry is the exit — the fear of being locked into a system that becomes difficult or expensive to leave. Because every school's data lives in its own isolated database and is exportable, a school's records remain genuinely its own. Shiksha CRM aims to keep schools by continuing to be worth their while, not by making departure painful. Taken together, these principles — everything included, one visible variable, transparent WhatsApp costs, and portable data — are designed so that a school can adopt the platform with confidence rather than suspicion, knowing exactly what it is committing to and exactly what it would cost.
When a school weighs the cost of Shiksha CRM, the most important comparison is not against other software but against the hidden cost of carrying on without a connected system at all — a cost most schools pay without ever seeing it on an invoice. Consider the staff hours consumed by manual work: compiling attendance, reconciling fees across payment methods, sending messages to parents one at a time, generating marksheets by hand, chasing defaulters by phone. These hours are paid for month after month, and they produce nothing a connected system could not produce automatically. For many schools, the salaried time reclaimed by automation exceeds the cost of the platform several times over.
Then consider the money that leaks away silently. Fees collected late because reminders never reached parents. Dues that were forgotten because no one tracked them. Transport fees on a separate sheet that was never fully reconciled. Admissions enquiries that went cold because no one followed up, each one a family — and a year of fees — lost to a competitor. None of these appear as a line in a budget, yet together they represent a continuous drain on a school's finances that a connected system is specifically designed to stop. A single recovered admission, or a term's dues collected on time rather than late, can outweigh the annual cost of the platform on its own.
Finally, consider the cost to reputation, which is the hardest to quantify and often the most consequential. In a market where schools compete for admissions and parents share their experiences with one another, a school that feels disorganised — that loses information, communicates poorly, cannot say where a bus is — pays a price in the families it fails to attract and retain. A school that runs visibly well, that keeps parents informed and reassured, earns the opposite: trust, word of mouth, and the admissions that follow. Seen this way, the question is not whether a school can afford Shiksha CRM, but whether it can afford the accumulating cost of running without it.
The philosophy behind Shiksha CRM's pricing is that a school should pay in proportion to the value it receives, and that value scales naturally with the number of students a school serves. A larger school has more fees to collect, more attendance to track, more parents to communicate with, more buses to run, and correspondingly more to gain from a connected system that handles all of it — so it is fair that a larger school pays more than a small one. Tying price to student count rather than to features means that the cost a school pays always tracks the value it gets, and never punishes a school for wanting to use the platform fully.
This is a deliberate contrast with the feature-priced model that dominates the market, where a school pays more the more it wants to do, and is therefore quietly discouraged from doing more. Under such a model, the software's incentives run against the school's interests: the vendor benefits when the school needs more features, and the school hesitates to adopt the very capabilities that would help it most. Shiksha CRM's model aligns the two. Because everything is included, the school is free to use the whole platform, and the more fully it does so, the more value it extracts from a price that does not change. The software's success and the school's success point in the same direction.
For a school planning its year, this alignment produces a rare thing: a technology cost that is both predictable and fair. Predictable, because it is a single annual figure determined by a number the school already knows. Fair, because it reflects the scale of the school and the value the platform delivers at that scale, with no penalty for ambition and no reward for under-using the system. When a school looks back at the end of a year on Shiksha CRM, the question is rarely whether the platform was worth its price; it is why the school waited so long to adopt a system that so plainly pays for itself.
Once a school has chosen its plan, beginning with Shiksha CRM is designed to be quick and low-friction, because software that is hard to start is software a school never fully adopts. The process begins with understanding your school's structure and migrating your existing records, so that you go live with your real students, staff and fee structures already in place rather than an empty system to fill. From there, your team is guided through the parts of the platform they will use daily, and because the system is built to be used by people who are not technical specialists, that guidance is short and practical. Within days, not months, a school is running on Shiksha CRM.
There is no long implementation project, no expensive consultant, and no lengthy disruption to the school's operations. The whole platform is ready from the moment you begin, so a school can start with the modules that matter most and grow into the rest at its own pace. And because the annual price covers everything, there is never a later negotiation or a surprise cost as the school expands its use of the system. You choose your plan, you get started, and you have the entire platform available to you from your first day, with support alongside you as you settle in.
Tell us your student count and we'll recommend the right plan on a quick call.