Education Software Development

Four products publish no price on any path

Blackbaud, Rediker and Vidyalaya were each read on two paths and none of the three printed a figure. Blackbaud’s tuition management pricing page serves a quote form and one offer, six months of Financial Edge NXT free for new customers with conditions applied but not stated; its general pricing page says pricing is customized to the organization. Rediker has no pricing, plans or quote page anywhere in its navigation, only Request Information, Get Started and See a Demo. The fourth is smartschoolmanager.com, which is the most peculiar of the group. Three approaches were examined, all of which guarantee a lifetime license with no monthly fees or other expenses, and none of them specify a price. A price assertion that has no price attached.

Four publish a figure and never say what period it covers

Edufy publishes a student-range table running from ৳2000 to ৳40000 and never states whether those are monthly, annual or one-time; a Monthly and Yearly toggle renders on both its homepage and its pricing page, and no yearly value appears on either. Zaman IT publishes ৳ 50,000, ৳ 100,000 and ৳ 150,000 with the identical eight module groups listed under all three, no student limits and no billing period. Acquaint’s only figure is one FAQ line saying the basic price starts from 50,000 BDT. The bdstall listing prints ৳30,000 and is simultaneously marked Sold Out and Currently unavailable, with no seller, on a listing seven years old, and it still ranked for the Bangladesh price query when this guide was researched.

The price that renders on only one path, and what the comparison is worth

Pathshalasoft’s homepage carries no amount at all. Its FAQ says there is a one-time installation fee and a monthly support fee based on student numbers, and stops. The figures live on its services page: installation of BDT 5000 on Basic and BDT 10,000 on Standard, both with a monthly per-student charge of 10 BDT, and a Customizable tier whose installation reads 20,000 with no currency symbol or code printed anywhere near it. A buyer who reads the homepage concludes the vendor publishes nothing. This is the single best argument for reading every vendor on more than one path, and it is why this guide does.

Not much, taken at face value, because the structures are not comparable. GegoK12 publishes a core product at zero dollars forever under an MIT license and charges for hosting, modules and support. eSkooly publishes a free forever cloud tier. QuickSchools charges $0.99, $1.49 and $2.99 per student per month with a floor of thirty students billed. Fedena charges $999, $1399 and $1699 a year with unlimited users. Those are four different businesses wearing the same category label, and a per-student rate and a flat annual license cross over at a student count a buyer has to work out for themselves.

What Is a School Management System

A school management system records who is enrolled, what they owe, whether they attended and what they achieved, in one place, so the finance office, the registrar and the teacher read the same row. It is also called an SIS or a school ERP. It is not a learning platform, and that difference matters once fee money is involved.

What the system has to hold

Four record sets, and they are not equally hard. A student record with an identifier that never changes even when the name, the class or the campus does. A fee ledger that can express what is owed, what was paid, by whom, against which head, and what remains. An attendance record with a timestamp and an author. An academic record that can be reissued years later. The first and the second are where custom work concentrates, because both carry exceptions that a product’s data model may simply refuse.

Where the definition gets slippery

Vendors describe the same software as a school management system, a student information system, a school ERP and a campus management platform, and the pages that rank for the plain definition query are vendor blogs explaining why their own product is the answer. One of the nine results for the term when this guide was researched was a university cyberlaw wiki page, and another was a machine-generated category index. The term is weakly defended, which is a reason to answer it clearly and not a reason to write another product pitch.

One question: How many locations record the fact that a student pays half of their term’s fees in cash at the office and the remaining amount online six weeks later, and which is authoritative? There is just one solution in a true system. Three modules make up the collection, and the reconciliation takes place in an unowned spreadsheet.

Why the open-source answer is worth a serious look

GegoK12 publishes its core as free forever under an MIT license with unlimited students, staff and parent accounts, twenty-six modules and no time limit, and charges $49 a month or $490 a year for managed hosting. Its annual price is exactly ten times its monthly one, which is $588 over twelve months against $490, a saving of $98 or 16.67 percent. Moodle and Canvas occupy the equivalent position in the teaching tier. For an institution whose problem is the fourth tier rather than the first three, starting from a free core and paying for integration is often the cheaper honest answer, and a development supplier should be willing to say so.

Why Schools and Training Providers Commission Custom Software in 2026

Three reasons recur, and none is a missing feature. Fee money arrives through rails whose costs nobody published. Records now carry statutory deadlines with retrieval attached. And the products bought in a hurry during remote teaching are now three systems that do not talk to each other.

The collection rail has become a cost center

A school that moves fee collection online acquires a per-transaction cost that is usually invisible during procurement, because the software vendor does not quote it and the gateway may not publish it. The arithmetic further down this page shows the result: at the lowest per-student software rate published in Bangladesh, the fee on a single modest payment can exceed a whole month of that student’s software license. Nobody is hiding this. It simply sits in two different documents, one of which does not exist.

Records now come with a clock

Under the Family Educational Rights and Privacy Act, a United States educational agency or institution must comply with a parent’s or eligible student’s request to inspect and review records within a reasonable period, and 34 CFR § 99.10(b) fixes the outer bound as “but not more than 45 days after it has received the request”. Separately, § 99.32(a)(1) requires the institution to “maintain a record of each request for access to and each disclosure” of personally identifiable information from a student’s education records. A disclosure log is not a reporting feature. It is a design decision taken at the start or retrofitted expensively later.

Three systems that were bought in a hurry

The common shape in 2026 is an LMS chosen for teaching, an administration product chosen for records and a spreadsheet doing the fee work, with a person in the middle. Custom work is rarely a fourth system. It is the identifier, the sync and the single authoritative fee ledger that lets the existing three stay.

An institution running campuses in two countries is subject to two sets of record rules and two sets of payment rails, and the product’s single fee model and single consent model will not stretch. This is the case where the fourth tier stops being optional, because the thing that differs between the campuses is exactly the thing no vendor can configure.

What Omega Solution Builds for Schools and Training Providers

Four areas of work, all of them fourth-tier or integration, and all of them costed as hours against named roles rather than as a package. Omega Solution does not sell a school product, so nothing below is a license and nothing below has a seat price.

Enrollment and admissions flows

The delivered education project is an enrollment platform, which is where this capability is evidenced rather than asserted. Admissions is a funnel with eligibility rules, document capture, verification steps and a handover into the student record, and it is the part of an institution most likely to be running on forms and email.

Fee ledgers, exceptions and reconciliation

One authoritative record of what is owed and what was paid, able to express sibling discounts, scholarships, partial-term joiners, installment plans and fees collected on a third party’s behalf. Plus the reconciliation back to the gateway’s settlement file, which is the step that turns a payment report into an accounting entry.

There are mechanical reasons why attendance fails, such as the building’s lack of a network, a device shared by six teachers, or a correction made the next day without an author being identified. Offline capture, dispute settlement, and an audit trail that details who made what changes and when are the tasks.

Integration and migration into what already exists

Reading and writing the LMS, the accounting package and the payment rail, and moving historical records in without losing the identifier. Migration is where education projects overrun, because the old data is always worse than the sample suggested. Institutions that already have an internal team and need capacity rather than a project can read software team augmentation instead.

How Omega Solution Runs an Education Build

Five stages run in this order, with a decision gate at the third. The point of the sequence is that the expensive commitments come after the cheap discoveries, and the gate exists so that an institution can be told to buy a product instead of commissioning one.

Stage 1: read the fee rules and the records obligation

Before any architecture, two documents get written: every fee head with every exception that actually applies, and the list of record obligations with their deadlines and who can demand them. Both come from the institution’s own policies and the rules themselves, not from a feature list.

Stage 2: map what already exists, including the spreadsheets

An inventory of every system holding student, fee or attendance data, including the ones nobody owns. The identifier question gets answered here: what does a student carry today, and does it survive a transfer.

Stage 3: decide what not to build

This is the gate, and it is the part of an IT consultation that saves the most money. Each of the four tiers is examined against what products already do, and anything the first three tiers cover is bought. What survives this stage is the build scope, and it is deliberately smaller than what arrived in the brief. An institution that leaves this stage with a smaller project than it expected has had a good day.

Stage 4: build the ledger and the identifier first

The fee ledger and the student identifier come before interfaces, because every later decision depends on them and both are expensive to change once records exist. Two-week iterations, with the reconciliation path exercised against real settlement data rather than a fixture.

Stage 5: migrate, prove retrieval, then hand over

Historical data in, with a reconciliation report. Then the retrieval test: pick a student at random, produce their record and their disclosure log, and time it. Handover includes the runbook for that test, because the obligation outlives the project.

Case Study: X (NDA), an Enrollment Platform Delivered in 22 Weeks

This is the first project in this pillar series that sits genuinely inside its stated sector. X (NDA) is an AI-driven enrollment platform for South African TVET students, and its own project page publishes a duration, a team composition and a project size band. One of those three cannot be reconciled with the other two.

The published facts, and the hours derived from them

Four facts, taken from the page rather than from a sales deck. Industry recorded as Education. Launch date 2025. Country South Africa. Time taken, twenty-two weeks. The team is listed as four people: front-end and back-end development, DevOps, and project management. The reach claim is more than fifty South African TVET colleges. The testimonial is attributed to X (NDA) as an organization, with no individual named and no title.

The page publishes a duration and a team size but not an hour count, so here is the derivation. Twenty-two weeks times four people times forty hours a week gives 3,520 hours. That is the figure a buyer should compare against anything else they are quoted, and it is worth holding against the competitive set: of twenty-five agency pages read for this guide, six publish an education-scoped hours figure, and the largest of them is 1,500 hours. 3,520 divided by 1,500 is 2.35, so the delivered project ran roughly two and a third times the largest effort figure any ranking page is willing to print.