Ship It Live — $1,999 flat
Design + build + deploy · kickoff in 24h · limited slots
Ship It Live · education admin sprint
Attendance, grades and parent comms, in one place in 30 days.
One system instead of six spreadsheets, a WhatsApp group and a filing cabinet — with parents finally able to see what they keep phoning about.
Quick answer
A school management app can be designed, built and in use in 30 days for a fixed $2,500, covering student records, attendance, grades and reports, timetables, fee tracking and parent communication, with separate views for staff, parents and students. Full accounting and statutory reporting integrations are scoped separately.
The plan
Day one to day 30, written down.
You get this schedule before you commit, not after. If a phase slips, that is mine to absorb — the price and the date were agreed before anything started.
- 1
Days 1–3
Scope lock
Your academic structure — terms, classes, sections, grading scheme — and who is allowed to see what. Permissions in a school are unusually important and unusually specific.
- 2
Days 4–12
Design
Attendance and grade entry first, because staff use them daily and abandon anything slow. Then the parent portal and admin views.
- 3
Days 13–24
Build
Records, attendance, grading, timetables, fees and the permission model. Your real class lists go in during the build.
- 4
Days 25–28
Run a real week
Staff marking real attendance and entering real grades alongside the current process. Every gap surfaces while it is still cheap to close.
- 5
Days 29–30
Launch
Data migrated, staff trained, parent accounts issued, and the spreadsheets retired.
What $2,500 gets you
Everything needed to launch — nothing padding the invoice.
Who books this
Built for
Schools and academies running admin across disconnected spreadsheets
Training institutes with more students than their process can hold
Administrators whose day is spent answering parents' basic questions
Real situations
Five ways this shows up, and what actually fixes it.
Not hypothetical — the shape of the problem before someone books this sprint, and the specific part of the build that resolves it.
Situation 1
Admin runs across six disconnected spreadsheets
A school tracks enrolment, attendance, grades and fees in separate spreadsheets that don't talk to each other, forcing manual reconciliation whenever any two need to agree.
Student records, attendance, grades and fees live in one system, with parent, staff and admin views drawing from the same source of truth.
Situation 2
Staff spend the day answering parents' basic questions
A meaningful share of administrative staff time goes to answering the same routine parent questions — attendance, grades, fees — that parents could see themselves if given access.
A parent portal shows attendance, grades, notices and fees for their own child only, removing most of that routine question traffic.
Situation 3
More students than the current process can actually hold
A training institute or growing school has outgrown the informal system that worked at a smaller size, and administrative errors are starting to show.
Structured student records, attendance and grading replace the informal process before it breaks further under continued growth.
Situation 4
Worried a parent might see another student's information
A school is cautious about digitizing records specifically because a poorly built system might expose one family's information to another.
Permissions are enforced server-side, per guardian, per student — the requirement that matters most in a school system, and the one weak systems get wrong.
Situation 5
Per-student licensing fees that grow every single term
A commercial school management system charges per enrolled student, meaning the software bill grows every term regardless of whether usage actually increases.
The system is built once with no per-student licensing — a one-time cost rather than a fee that compounds with enrolment.
The honest part
When 30 days is the wrong answer.
A fixed deadline only works when the scope genuinely fits inside it. These are the cases where I will tell you so rather than take the booking.
Full double-entry accounting and payroll. Fee tracking fits; replacing your accounting system does not.
Government or board reporting integrations, which vary by jurisdiction and are quoted once the format is confirmed.
Learning content delivery and online classes — that is the education app sprint, and the two can be joined later.
Inside the 30 days
- Student records: enrolment, classes, guardians, documents
- Attendance marked in seconds, per class or per period
- Grades, assessments and printable or downloadable reports
- Timetables for classes, teachers and rooms
- Fee tracking with invoices, payment status and reminders
- Parent portal — attendance, grades, notices, fees, for their child only
- Announcements and messaging to a class, a year, or the whole school
- Source code, design files and 30 days of support at handover
Quoted as one number before day one. A week running long is mine to absorb.
Outside the line
- Full double-entry accounting and payroll. Fee tracking fits; replacing your accounting system does not.
- Government or board reporting integrations, which vary by jurisdiction and are quoted once the format is confirmed.
- Learning content delivery and online classes — that is the education app sprint, and the two can be joined later.
Real work, sized and priced separately. You hear it before you book, not at handover.
Questions
Before you book
Yes, for the core: students, attendance, grades, timetables, fees and parent access. What extends it is accounting, payroll and statutory reporting, which are separate systems for good reasons.
Other sprints
30 days from now, this could be live.
A 30-minute call decides whether the scope fits. If it doesn't, I'll tell you what would.