MyClassboard is an established Indian school ERP with a broad module set. SchoolDeck covers fewer modules deliberately. Module count is the most common way schools compare products and among the least predictive of satisfaction, because a listed module and a used module are very different things.
Every school ERP evaluation eventually produces a spreadsheet with vendors as columns and modules as rows, and the vendor with the most ticks wins. It is the wrong instrument, and everyone who has run an implementation knows it.
The right-hand column below is what to ask them, not what we claim about them. We publish SchoolDeck and do not track other vendors’ current feature sets; anything material should be verified with the vendor directly.
Count the modules you will actually switch on in year one, not the modules offered. If your requirement genuinely spans the long tail — alumni, inventory, canteen, library, transport, all in use — breadth is a real advantage. If four modules carry ninety per cent of the pain, buy the product that does those four best.
| What you are comparing | TurtleDock | MyClassboard |
|---|---|---|
| Module breadth | Narrower — 24 modules, not all switched on | Ask for the list actually in production at schools your size |
| Depth in fees | Concessions following families, part payments, RTE receivables native | Ask to configure a sibling concession and a part payment, live |
| Depth in attendance | Period-wise, offline-tolerant, conflicts surfaced | Ask what happens with no signal, and on a sync conflict |
| Modules in the long tail | Library, canteen, inventory present but not our strongest | Ask which of these are used daily by reference customers |
| What a module costs to switch on | A permission change, never a migration or a new fee | Ask whether enabling a module later costs money or a project |
Across implementations, the same four account for nearly all of the value and nearly all of the failure. Test these four to destruction and treat the rest as secondary.
A product excellent at these four and absent in the long tail will serve a school better than the reverse, every time.
Do not accept a demo of the happy path. Bring your own awkward cases and ask the vendor to configure them live, in the room. Ours included.
A vendor who needs to "get back to you" on any of these has answered the question.
Phrased the way they arrive, answered so each one stands on its own.
Almost certainly, and that is a real trade. What we hold to is that switching one on is a permission change rather than a migration or a new line on the invoice, so breadth you are not using costs you nothing and breadth you need is available immediately.
In our implementations, most single schools run around fourteen of twenty-four in year one, and the long tail gets switched on gradually or never. Plan for the ones you will use in the first term.
Checked by the Implementations desk on 7 September 2026. Corrections go in the page, dated, rather than quietly.
Pricing is on the page, in the open, with the counting rule written next to it. Nobody has to book a call to find out what it costs.
See pricingForty minutes with an implementation engineer — your classes, your fee heads, your grading scheme, entered as we go. No slides, no sample school.