SolutionsCase StudiesAI ToolsResourcesAboutContact
Get Your Free AI Automation Audit Book a Free 30-Minute Strategy Call
Web Development

One Desktop App for Students, Fees, Attendance and Results

The School Management CRM is a Windows desktop application that brings a school's core records — students, teachers, fees, attendance, exam results, staff salary and admissions — into one program that works without an internet connection. It was built with Electron, Express and SQLite so a school can run it on its own office machines with no hosting and no subscription.

Client / project typePrivate school
IndustryEducation (private school administration)
Project typeSchool management CRM, Windows desktop
TechnologyElectron, Express, SQLite, Node.js

The challenge

What was manual, slow or missing

Schools generate a lot of interlinked records, and in many independent schools they still live in separate places: an admissions register, a fee ledger in a spreadsheet, attendance in paper registers, results compiled term by term, and salary worked out by hand. Every question — has this family paid, how many days was this student absent, what did this class score — means opening a different file and trusting that it is the current version.

The brief called for a single application the front office could use all day, on ordinary Windows PCs, without depending on a stable internet connection or a monthly software bill. It had to be quick to enter data into, produce the printouts a school actually needs — fee receipts, attendance summaries, result cards — and keep the data local under the school's own control. Cloud-first school platforms were considered and set aside because connectivity and recurring cost were both concerns.

The solution

What TaimurTools built

We built the CRM as an Electron desktop app so the interface could be developed with web technology while installing and running like native Windows software. Inside the app, an Express server handles the application logic and talks to a local SQLite database, which means the entire system — interface, API and data — lives on the machine it is installed on. There is nothing to host and nothing that stops working when the connection drops.

The data model is built around the student record. Admissions creates the student and links them to a class and guardian; fees track what is due, what has been paid and what is outstanding per student; attendance is recorded per class per day; results are entered per subject and exam and roll up into term reports; and the teacher module holds staff profiles alongside a salary section for monthly payroll. Because everything shares one database, a fee status, an attendance count and a result card all draw on the same student row.

SQLite was chosen deliberately: it needs no separate database server, the whole school's data is a single file that can be backed up by copying it, and it handles a school's record volume comfortably. Express gives the app a clean internal API, which also means the same logic could later be exposed to a web or mobile front end if the school ever wants remote access.

How it works

How the CRM works

One student record

Admissions creates the student and links class and guardian. Fees, attendance and results all draw on that same row.

Fees and receipts

Dues, payments and outstanding balances per student, with receipts printed on the spot.

Attendance and results

Attendance is marked per class per day. Marks entered per subject and exam roll up into term report cards.

Staff and salary

Teacher profiles with a monthly salary section, kept alongside the academic data.

Local data, backed up by copying

An Express API and a SQLite database run inside the Electron app. The whole school's data is one file on the school's own PC.

Key features

What's inside

Student and admissions records

Enroll a student once; class, guardian and admission details follow them through every other module.

Fee management

Track dues, payments and outstanding balances per student and print receipts on the spot.

Attendance

Mark attendance per class per day and pull absence summaries for any student or period.

Results and report cards

Enter marks by subject and exam; term reports are generated from the same records.

Teachers and salary

Staff profiles with a monthly salary section, kept alongside the academic data.

Fully offline, local data

Runs on the school's own Windows PCs with a single SQLite file that backs up by copying.

Business outcome

What changed

Outcome: Records that lived in an admissions register, a fee spreadsheet, paper attendance and hand-worked salary now sit in one offline application the front office uses all day.

  • Every question answered from one current record instead of several files
  • Receipts, attendance summaries and result cards generated from the same data
  • No hosting, no subscription, data under the school's control

Outcome figures for this engagement are not published. Verified client metrics are added only with a source and written approval.

Technology

Built with

ElectronExpressSQLiteNode.jsJavaScriptWindows

Services used: Custom AI Development, AI Business Automation, AI Website Development

Need something similar?

Tell us what you are building. We will show you how a similar system would work for your business, then send a fixed-fee proposal.