Learning management system (LMS)
Course delivery, enrolment and content, and the launch point for every external tool. Almost always bought rather than built.
The systems an institution actually runs on: admissions and counsellor workflow, fees, attendance, timetabling, gradebooks that survive a curriculum change, and the LTI and rostering standards a procurement team will hold you to. Session-scoped data is what makes education software different, and it is what most platforms get wrong in year one.
Tell us what you are building
Education software development builds the systems an institution runs on: admissions, fees, attendance, timetabling and gradebooks, all scoped to the academic session. The standards a procurement team will hold you to are LTI 1.3 for tool launch and OneRoster 1.2 for rostering. Phase one for a K-12 operations platform typically runs 3 to 5 months.
Our work
We have built one platform in this sector, and it is a discovery and admissions platform rather than a student record system. Saying so is cheaper than you finding out on the second call. The two builds beside it are the closest shapes we have: per tenant isolation on one codebase, and permissions that follow the role.
Taxonomy
Nine categories cover almost everything an institution buys. Most run four or five at once, from different vendors, which is why the interoperability standards further down decide more than any feature list.
Course delivery, enrolment and content, and the launch point for every external tool. Almost always bought rather than built.
Where content is authored, versioned and reused across programmes. An LMS delivers content; an LCMS is where it is produced.
Live teaching with attendance, recording and breakout rooms. Judged on how it behaves at class scale, not on its feature list.
Item banks, delivery, timing and marking. Server authoritative timing is the part a demo never shows and exam day finds.
Where a teacher builds a lesson or an assessment item without an engineer, then packages it for whichever platform delivers it.
Attendance, progression and intervention reporting that a board or a regulator reads, which is a different job from a dashboard.
A separate market with a separate buyer. HR signs it off, content arrives packaged for SCORM or xAPI, and completion answers to a compliance obligation.
Personalisation needs item level mastery data, not a course grade. Points, badges and leaderboards need an event log a gradebook does not keep.
Scope
Seven pieces of work, with the interoperability layer handled in its own section below. Most engagements are three or four of these, and the first one decides what the rest cost.
One fee ledger where a concession is its own object against the fee, not an edit to the invoice.
Attendance as an auditable daily record rather than a report, and constraint based timetabling that survives electives.
Grades scoped to the term, with report card templates an institution can change without an engineer.
Audience
Six positions we are called from. Not a fit if you want a consumer learning app built from scratch: that is a product build. We are not an LMS vendor and not an accreditation body.
Change a subject structure and last year's results stop rendering. Missing: records versioned by year and term.
Five enquiry channels, counsellors tracking privately, nobody able to say which source produced admitted students. Missing: one pipeline.
Procurement named the Advantage services and the answer is currently no. Missing: core launch plus Deep Linking, NRPS and AGS.
Instalments, concessions, late fees and part payments sit in three systems that disagree at month end. Missing: one ledger.
Taking personal information from under-13s outside the school consent route needs verifiable parental consent under the amended COPPA Rule.
The core idea
A student's marks, fees, class and even their name belong to a specific year and term. Store them flat and the first curriculum change makes history unreadable, short of reinterpreting every record you have issued. Six consequences, each one we have seen.
Change a curriculum and history stops making sense. Version from the first migration, because retrofitting means reinterpreting every result.
It has to render as it stood then, not as the current curriculum would read it. A versioning problem, not a reporting one.
They arrive mid build with their own permissions, notifications and app. Put every role on the list during discovery.
Reconciliation then cannot explain why two students paid different amounts for the same programme. Model the concession as its own object.
A browser clock and a non resumable attempt survive a demo and fail on exam day. Server authoritative timing, always.
By institution
What breaks decides what gets built. Corporate and enterprise training is a fourth market with its own buyer, and it is in the taxonomy above. The detail behind each of these is in the two deep dives linked under the tables below.
Parents are a user nobody scoped, attendance is a daily legal record, and every policy needs a per school override.
Credit accumulation across multiple entry and exit points, electives that break timetabling, and an exam controller whose process exists nowhere.
Video egress is the recurring cost nobody modelled, and completion tracking answers to a regulator rather than a dashboard.
Integrations
Six that turn up on almost every project. This is where an estimate that said it integrates with a few APIs goes wrong, because most of these are named by the institution rather than chosen by the vendor.
A launch, not a file export. 1EdTech's LTI page calls 1.3 the current version and the structure its Advantage services sit on.
1EdTech calls 1.2 the most recent version available. Ask which version your incumbent SIS exports before you promise either one.
1EdTech's QTI page says QTI 3.0 brings the earlier QTI and APIP versions into one specification, so item banks can move between tools.
Institutions arrive with an identity provider already chosen. Real integration work either way, and not a login form.
Instalments, part payments and refunds, reconciled back to the fee ledger rather than to a bank statement at month end.
Evaluation
We do not publish a product ranking, and a vendor ranking the market it sells into is not worth much to you. What is worth something is the test a procurement team can run on any shortlist. Six questions, in the order they save you money.
1EdTech's certified products listing says a product missing from it either has not passed testing or its certification has expired. Check the listing, not the brochure.
Core launch alone is not Advantage. Ask for Deep Linking 2.0, Names and Role Provisioning 2.0 and Assignment and Grade Services 2.0 by name.
1EdTech still publishes both the 1.1 and the 1.2 final releases, so a shortlist can hold both. Ask which it reads and which it writes.
For a US public district or university the Department of Justice rule sets WCAG 2.1 Level AA. Ask what was tested, and by whom.
A full export of people, enrolments, results and documents, in a format you can read without the vendor. Test it before you sign.
Ask it to render a result from two curricula ago. The answer tells you whether this is a record system or a reporting tool.
Interoperability
This layer is imposed rather than chosen. An RFP names the standard and the vendor does not get a vote. Every row below was read on 1edtech.org or in the specification itself, and says what those pages say rather than what the market repeats. Each row carries the date it was last read.
| Standard | What the published spec says | The trap |
|---|---|---|
| LTI 1.3 and LTI Advantage | 1EdTech's LTI page calls 1.3 the current version and says it addresses education security requirements. Its three Advantage services: Assignment and Grade Services 2.0 creates a gradebook column and posts grades against a resource link, Names and Role Provisioning 2.0 supplies users and their roles, and Deep Linking 2.0 returns a link that launches selected content. | The 1EdTech LTI 1.3 specification says 1.3 moves away from OAuth 1.0a style signing to OpenID Connect, signed JWTs and OAuth 2.0. A different trust model, so a 1.1 tool is not upgraded by changing a version string. Read 17 November 2026. |
| OneRoster 1.2 | 1EdTech's OneRoster page calls 1.2 the most recent version available and defines three services, each in REST and CSV and each implementable alone: Rostering, Gradebook and Resource. The 1.2 final release is dated 19 September 2022. | The same page still lists the OneRoster 1.1 REST and CSV final releases, so your incumbent may speak either version. It is also explicit that Resource allocates a resource without giving access to the resource itself. Read 13 November 2026. |
| QTI 3.0 | 1EdTech's QTI page says QTI 3.0 brings the earlier QTI and APIP versions together into a single specification, with better integration and accommodation support and more web friendly markup. | The item bank outlives the platform it was built in. A bank written to one vendor's private format is a migration you pay for twice. Read 13 November 2026. |
| client_id and deployment_id | The LTI 1.3 specification says a platform must generate an immutable deployment_id for each tool it integrates with, and that every message must carry the deployment_id in addition to the client_id. | A tool keyed only on client_id will cross tenants, because one platform can hold several deployments under a single registration. Every multi tenant LTI bug we have inherited lives there. Read 13 November 2026. |
We build to these specifications and can prepare a certification submission, but certification itself runs through 1EdTech's own test suite and staff review, not through us. For what each module of the work takes in hours, see the eight module LMS and school software breakdown.
Compliance
Not a badge wall. Three instruments that change the data model, the retention policy or the delivery date, each named with the body that published it and read at that body's own page. Each row carries the date it was last read.
| Instrument | What it forces the software to do | When |
|---|---|---|
| ADA Title II web rule, US Department of Justice | The Department of Justice page for the rule adopts Web Content Accessibility Guidelines version 2.1, Level AA, as the technical standard for the web content and mobile apps of state and local government entities. That includes public school districts and public universities. | Published in the Federal Register on 24 April 2024. An interim final rule on 20 April 2026 extended the compliance dates, now 26 April 2027 for public entities of 50,000 or more persons and 26 April 2028 for entities of 0 to 49,999 persons and for special district governments. Read 17 November 2026. |
| FERPA, 20 U.S.C. section 1232g, with regulations at 34 CFR Part 99 | The US Department of Education's student privacy FAQ says parents may inspect education records, request correction and control disclosure of personally identifiable information, and that those rights transfer to the student at 18 or on enrolling in a postsecondary institution. So the software needs per record access control, an amendment workflow and a disclosure log. | In force. That page does not state a year of enactment, so we do not quote one. Read 13 November 2026. |
| COPPA Rule, 16 CFR Part 312, as amended | Verifiable parental consent, data minimisation, and retention and deletion duties, wherever a product collects personal information from children under 13 outside the school consent route. The build items are age assurance, consent capture and a consent ledger. | The Federal Register notice for the amended Rule gives an effective date of 23 June 2025 and a compliance date of 22 April 2026 for all but three provisions. Both dates have passed. Read 17 November 2026. |
We hold no certifications ourselves, and none of these instruments certifies a vendor. We build the records that let you satisfy them and hand you the evidence for your own audit. India, the EU and the Gulf each add their own rules, and we confirm which of them bind you with the issuing body's page open. On what the student record underneath has to store, and why history is the expensive part, see what drives student information system cost.
Transparency
Hours rather than a total, so you can argue with any line. The scope here is a K-12 operations platform. A fixed price follows discovery, once the role list and the term structure exist on paper.
Phase one hours
1,320
The worked example, added up module by module below. Every line sits inside its own published range.
Typical timeline
3 to 5 months
Paced by the academic calendar as much as by engineering. One safe cutover window a year.
Useful hours
910 to 1,820
Every module at its minimum, through to every module at its maximum. QA and PM quoted separately.
| Driver | Hours |
|---|---|
| How many distinct user rolesStudent, parent, teacher, head of department, registrar, exam controller, finance, counsellor, admin. Each carries its own screens, permissions and audit trail, times any tenant-level overrides. | 40 to 90 each |
| Session-scoped dataApplied across every affected module. Each record versioned by academic year and term, with history that stays accurate after a curriculum change. | Adds 15 to 25% |
| Each integrationA documented REST API at the low end; a nightly batch that has to be reverse engineered and reconciled at the high end. | 60 to 160 each |
| Report card and certificate templatesBeyond the base gradebook, because every institution wants its own layout and will not accept a generic one. | 60 to 140 |
| Data migration from the incumbentIt usually arrives as inconsistent spreadsheets with no stable identifier, so identity resolution comes before loading anything. | Rarely small |
| Assessment integrityServer-authoritative timing, resumable attempts and exposure control. Expensive to do properly and unmistakable when it was not. | Invisible in a demo |
| Accessibility level requiredWCAG 2.1 AA is the level the Department of Justice rule holds US public entities to. Building to it costs far less than retrofitting. | 60 to 140 |
| The academic calendarIt does not change the total, it changes when the total can be delivered. One safe cutover window a year is a real constraint. | Schedule, not hours |
| Module | Hours |
|---|---|
| Discovery | 60 to 120 |
| Multi-tenancy, SSO and permissions | 90 to 180 |
| Student and staff master data | 120 to 220 |
| Admissions and counsellor CRM | 140 to 260 |
| Fees, concessions and instalments | 160 to 300 |
| Attendance and timetabling | 120 to 260 |
| Gradebook and report cards | 160 to 320 |
| Data migration | 60 to 160 |
Delivery
Five phases, each named by the artifact it hands you rather than by a stage in a generic waterfall, so you can ask to see one. In order: Role and term map, Session-scoped model, Admissions and fees, Teaching records and Cutover pack.
Phase 01
Every role with its permissions and audit needs, plus the term structure and the academic calendar. This artifact decides the size of everything after it, and it is the one most projects skip.
Phase 02
The student record versioned by academic year and term, agreed on paper before anything is built against it. Retrofitting it is a rewrite, not a migration.
Phase 03
Counsellor workflow and the fee ledger with concessions modelled as objects, because these two carry the money and the disputes.
Phase 04
Attendance, timetabling and the gradebook, with report card templates an institution can change without an engineer.
Phase 05
Migration, reconciliation reports and a rollback plan, run inside the one safe window the calendar allows.
Nine categories cover most of it: a learning management system for delivery, a student information system for the institutional record, a learning content management system for authoring and reuse, virtual classrooms, assessment and testing, authoring tools, analytics, corporate training platforms, and adaptive or gamified layers on top. Most institutions run four or five at once from different vendors, which is why interoperability matters more than any feature list.
We do not publish a product ranking, and a vendor ranking the market it sells into is not worth much to you. The useful test is what a shortlist can prove. Ask whether each product appears in the 1EdTech certified products listing, which LTI version and Advantage services it implements, which OneRoster version it reads and which it writes, what accessibility conformance was tested and by whom, and whether you can export your own data without the vendor.
An LMS delivers teaching: courses, content, enrolments and the launch point for external tools. A student information system holds the institutional record: people, programmes, fees, attendance and results, versioned by academic year and term. An LMS never has to answer a question about a student from four years ago, and a record system does. The two talk over LTI 1.3 and OneRoster 1.2, both published by 1EdTech.
They are not two versions of one thing. The 1EdTech LTI 1.3 specification says 1.3 moves away from OAuth 1.0a style signing towards OpenID Connect, signed JWTs and OAuth 2.0 workflows, and 1EdTech's LTI page calls 1.3 the current version. A different trust model, so a 1.1 tool is not upgraded by changing a version string: the launch, the key handling and the per tenant registration are new work.
1EdTech's OneRoster page calls 1.2 the most recent version available and defines three services, each available in REST and CSV and each implementable on its own. Rostering carries students, teachers, organizations, courses and enrollments. Gradebook carries results, line items, categories and score scales. Resource allocates resources to classes, courses and users, and the same page is explicit that it does not give access to the resources themselves. The 1.2 final release is dated 19 September 2022.
The Department of Justice rule, on the department's own page for it, adopts WCAG 2.1 Level AA for the web content and mobile apps of state and local government entities, which includes public school districts and public universities. It was published in the Federal Register on 24 April 2024, and an interim final rule on 20 April 2026 moved the compliance dates to 26 April 2027 for public entities of 50,000 or more persons and 26 April 2028 for entities of 0 to 49,999 persons and for special district governments.
The worked example below is 1,320 hours across eight modules, about three to five months with a squad. The go live date is set by the academic calendar, not by engineering. A fees or gradebook cutover has one safe window a year, between sessions, because mid term you would be migrating balances and marks that are still moving. These are two separate questions, and the second is usually the binding one.
Four steps with a shape attached to each, so booking a call is a known quantity.
Bring your role list, your term structure, and the one report your registrar builds by hand. Those three size the project faster than an hour of description.
We check whether your current system still renders last year's results correctly after a curriculum change. The answer tells us whether this is an integration or a rebuild.
The modules, the hour ranges and the arithmetic, with QA, project management and contingency shown separately. If your LMS already covers most of it, the document says so.
You choose whether we build it, your team does, or your incumbent extends. The code is yours on delivery, student records stay in your infrastructure, and the document is yours either way.
Almost every question on this page resolves to whether your records are scoped to an academic session. We will check that, tell you which regulations actually bind you, and give you the hours either way.
Real feedback from the people we've proudly partnered with.
Zyneto Global Technologies provided excellent project management and technical expertise throughout the engagement. The team was responsive, collaborative, and adaptive, ensuring the project met our expectations and set a strong foundation for future growth.
We engaged Zyneto to design and develop a custom web platform for Moneteo, aimed at improving project management, data tracking, and collaboration across internal teams and external partners. Their work included full-stack web development, custom modules for workflow automation, API integration, and comprehensive testing.
Overall, their responsiveness and timely deliveries contributed positively to the project's success. The client achieved better data management and quality. The service provider delivered the project on time and ensured prompt responsiveness throughout the engagement. Their innovative approach was outstanding.
Explore further
Where the session-scoped student record lives
Registrar, counsellor and parent surfaces
Parent and student apps
Transcripts, certificates and records
Enquiry triage and counsellor assistance
Accessibility built in rather than retrofitted
Moderation and identity for student cohorts
Many institutions on one multi-tenant platform
Every sector we build for, in one place
Module by module breakdowns and migration work that applies directly to student systems.