Attendance that stays on paper
The app exists, the staff still use the register, and the data in the system is a week behind reality.
Attendance, operations and parent communication that actually get used
Education software fails for a boring reason: the person who has to use it every morning is holding a register and forty children, not a laptop. We design for that minute first, and the dashboard second.
- Udyam UDYAM-UP-50-0280551
- GSTIN 09CPBPD9064H1ZS
- Lucknow, Uttar Pradesh
- Source code and IP yours
- Reply in 1 working day
What we hear
The four problems behind most briefs.
If two of these describe your week, the rest of this page is written for you.
Parents who only hear bad news
Communication is a WhatsApp group and a phone call when something is wrong, which makes every message feel like a complaint.
Enquiries and fees in four places
A ledger, a spreadsheet, a notebook and someone's memory — and no reliable answer to how many enrolled this month.
Software priced for a university
The products that do all this are sold to institutions with an IT department and a budget to match.
What we build
The system, not a component of it.
- Attendance recorded at the moment it happens
- Parents informed routinely rather than exceptionally
- One number per branch that the owner trusts
- 01Attendance that takes one tap per student and works without a signal, syncing when the phone finds one
- 02Parent-facing updates that are worth opening — attendance, progress, fees, notices, in the language the parent reads
- 03Enquiry-to-enrolment tracking, fee schedules, receipts and the reports a centre head actually runs
- 04Role-based access for teachers, centre heads and owners, across multiple branches
- 05Dashboards that answer the three questions an owner asks on a Monday
Proof you can click
Open it and use it, rather than read about it.
Everything below runs in your browser. Each is labelled for what it is — a demonstration build we own, not a client engagement we are quietly implying.
Client engagements under NDA are not published here. Ask on a call and we will talk through the relevant ones.
Where most briefs land
Packages that fit this industry.
Fixed scope, a timeline and a starting price — so the first conversation is about fit rather than about what a quote might look like.
Before the first call
What technical buyers ask us.
The questions that decide whether a project is worth starting — answered here so you do not have to book a call to find out.
That is the design constraint, not an afterthought. The attendance flow is one screen and one tap per student, it works with no signal, and it never asks a teacher to resolve a sync conflict. If a feature cannot survive a corridor and a bell, it belongs on the admin side instead.
Tell us what the product has to do.
We'll tell you what it takes.
Startups, enterprises and product teams — from a napkin sketch to a fleet in the field. One team, concept to production.
- Udyam UDYAM-UP-50-0280551
- GSTIN 09CPBPD9064H1ZS
- Lucknow, Uttar Pradesh
- Source code and IP yours
- Reply in 1 working day
Start a project
Come with a problem. We'll scope it before we quote it.
Send us the constraint that worries you most. An engineer reads it — not a form queue — and replies within one working day.
Direct
- Emailadmin@thegradlew.com
- Phone+91 79859 20361 · Sourabh
- Websitethegradlew.com
- Book a callcalendly.com/abhishek-thegradlew
- OfficeKN135MINB, Neel Matha, Malak Road, Lucknow, Uttar Pradesh 226002, India
Lucknow, Uttar Pradesh · India
LinkedInGitHubXDribbble