TutorDesk
SchoolDeckK–12 school OS
CampusAllyColleges & universities
TutorDeskCoaching & tutors
BookNestLibrary management
Soon
PaperDeckAI question papers
PrepWiseCompetitive exam prep
FinDeckAccounting & analytics
Soon
StockWiseInventory & stores
Soon
TaskDeckTasks & workflows
Soon
PeopleDeckHRMS & payroll
LeadDeckSales & admissions CRM
Soon
TicketDeckSupport service desk
Soon
ConnectlyCommunity & messaging
LiveLoopVideo meetings
AskWiseAI assistant
Soon
Kids' STEM academies run small batches through level ladders with kits, projects and competitions — closer to a dojo than a tuition centre. TutorDesk runs the operations underneath: batches, level-wise fees, kit billing, parent updates and the seat arithmetic small batches force.
A robotics class caps at eight because that is how many circuits one mentor can rescue at once. Small batches mean every empty seat is expensive, every kit is inventory money, and a batch that dips to four quietly loses its margin to rent and mentor time. The academies that thrive know their per-batch fill and their level-completion rates as numbers, not impressions, and they steer enquiries into the batches that need them; the ones that struggle discover the arithmetic at year-end. Live seat truth per batch is not a nice-to-have in this model — it is the business.
Competition season is the STEM academy's annual exam: team selections, registration fees, travel consents, build deadlines and a calendar that collides with school exams. Run it as operations rather than heroics: competition entries as events with fees attached, team rosters drawn from level records, consent and payment chased through the same reminder machinery as tuition, and mentors' extra sessions counted in their load. Academies that run one clean competition season keep those families for years, because nothing sells the ladder like a child on a podium and a parent who watched the logistics work.
A level ladder, foundation Scratch to Python to microcontrollers to competition track, is what keeps a nine-year-old enrolled for three years instead of one summer. Run each level as a course with its own fee and duration, record completions, and let the ladder itself sell the next level to the parent at each milestone. Certificates issued from recorded completions rather than memory, and competition entries tracked with their fees, turn the ladder from a poster on the wall into an operating system.
Scratch, Python, Arduino, competition track — each a course with its own fee, duration and completion record.
Kits, deposits and competition fees as line items on the family ledger, refundable pieces flagged as refundable.
Free workshop attendees become tracked enquiries with owners and follow-up dates, not a sign-up sheet in a drawer.
Batches clustered on weekends with mentors across them; conflicts visible before parents find them.
Small batches are the model in STEM classes, and per-active-student pricing follows it: you pay for the students you have. The batch-occupancy calculator on our tools page is worth running, because kit costs make fill rate matter even more here.
Yes — kit deposits, competition registrations and level-up charges run as line items beside the monthly or level fee, on one family ledger, which keeps the robotics-kit deposit conversation clean at exit time.
Courses map to your levels — Scratch, Python basics, Arduino, competition track — and a student's history shows the ladder climbed. Batch moves between levels are recorded, so certificates and parent updates say something true.
Each centre runs its own branches, batches and fees under one account; a licensor's curriculum and level names slot in as course structure. Multi-branch reporting shows each centre and the whole, side by side.
Yes, the same dual calendar sports academies run: level batches through the school year and intensive camps in holidays, each with its own price, seats and dates. Camp attendees carry their records into the school-year ladder, which is exactly how a two-week summer camp becomes a three-year student.
Session-wise attendance, level completions and project milestones reach parents as plain updates. A parent who cannot debug Python can still see the ladder: joined Scratch in June, built first game in August, moved to Python in January.
A 20-minute demo set up for a coding or robotics academy — levels, kits and all.
