Buyer's guide
Microschool management platform or a general-purpose tool stack: which features to prioritize for attendance, billing, and communication
A spreadsheet, an invoicing tool, a form and a group text will run a school of eight. The question is what breaks first as it grows, and which features are worth paying for before that happens. Here is the order to rank them in, and where the stack is still the right answer.
Written by the Pearspark team · updated · about 8 minutes
In short
Choosing between a microschool management platform and a general-purpose tool stack comes down to one test: does each record know the same child? A stack keeps three or four lists of the same students. Prioritize, in order: attendance in under a minute on a phone with excused and late codes and same-morning parent notice; recurring per-family billing with sibling discounts, bank debit, autopay, reminders and split households; and messaging by roster audience with replies kept in the record and one parent login where attendance, invoices and messages sit together.
The test that decides it
A general-purpose stack is a spreadsheet for the roster, an invoicing tool for tuition, a form for attendance, and a group text or email list for families. Each one holds its own list of the same students. Every new child, every withdrawal, every sibling and every split household gets typed into all of them, and they drift apart within a term.
Under about fifteen students that is an hour a week and a few mistakes a year. Past that it is where the mistakes come from: the sibling discount applied to one child and not the other, the parent who left in May still on the class list, the absence recorded on a form nobody reads. A platform's only real claim is that one child has one record, and attendance, billing and messages all read from it.
So judge every feature by whether it removes a re-typing step or a list that can go stale. Not by whether it looks impressive in a demo.
Attendance: the order to rank features in
The first item matters more than the other four together. If attendance takes more than a minute, teachers stop doing it every day and the record becomes fiction.
- Under a minute on a phone. Mark all present, fix the exceptions, save. The class should be remembered from yesterday. A form that asks for each name in turn fails this test.
- Present, absent, late and excused, with a note, and the ability to correct yesterday. A tool that only records absent cannot produce an excused-absence count for a scholarship program or a state review.
- Parents told the same morning. An unexcused absence should reach the parent's phone without a staff member doing anything. In Pearspark that is a push notification to the family app, on purpose not an email or a text.
- Reports you run yourself: each student's history, the attendance rate over a date range, a chronic-absence list, and which classes have not taken attendance today. Every one exportable as CSV for state or scholarship paperwork.
- Nice, not necessary: attendance by period rather than by day, and parents excusing an absence from the portal. Pearspark has neither today. A parent messages the teacher instead.
Billing: the order to rank features in
Stripe, Square or QuickBooks on their own will send a recurring invoice. What they do not know is that two invoices belong to siblings, or that a family's aid award changes the amount. That is the line where a stack starts costing more than it saves.
- Recurring plans per family, not per invoice. Weekly, every two weeks, monthly, quarterly, twice a year or yearly. Sibling discounts that apply on their own. Scholarships and financial aid as a flat amount or a percent for a date window. A month-based plan can name the day it falls due, 1st to 28th, for the school whose handbook says tuition is due on the 5th.
- Bank debit first, cards second, autopay optional or required. ACH costs a school far less than a card. Make sure the money lands in the school's own payment account, not the vendor's. Pearspark never holds the money; it goes to the school's Stripe account.
- Reminders and an aging view without you. Automatic overdue reminders, and one screen showing who owes what. In Pearspark: up to three emailed reminders per overdue invoice a week apart, plus optional reminders before the due date and before an autopay draft. Late fees are a rule the school switches on — a flat amount or a percent of the unpaid balance, after a grace period you set — added once per invoice and never backdated onto invoices already overdue when you switched it on.
- Split households and partial payments. Two parents, two invoices, two autopays, split by percent. A family can pay part of an invoice from the portal unless the school turns that off, and the office can record a partial payment by hand either way, with the balance updating on its own. Each family has its own ledger page showing what is open, partial, overdue and paid. This is the case that breaks spreadsheets first.
- Export to your accountant. A billing journal as CSV and a year-end statement per family showing what the family paid and what a scholarship paid.
Communication: the order to rank features in
A WhatsApp group is faster than anything on this list, and every parent already has it. It also has no record, no audience control, and lives on a teacher's personal number. Rank accordingly.
- Audiences, not lists you maintain. All families, one class, one family, one parent — and, for an admin, a whole grade, or a whole campus at a school that runs more than one. The roster is the list, so it is never stale.
- Replies come back into the record. A family's reply should land in a thread the office can see, not in one teacher's phone.
- An emergency broadcast that ignores mutes and shows who acknowledged. Lockdown, fire, all clear, drill. This is the one message where a group text's lack of an acknowledgement list matters.
- One parent login where the absence, the invoice and the message sit together, with all the family's children under it. No stack can do this, and it is the thing families notice.
- Text messages, and what they cost. Group texting has them for nothing. Pearspark sends them too — one-way alerts from the emergency console and the message composer, to families who opted in, with emergencies going to every number on file — but they are prepaid credits from 2.7¢ a text rather than part of the plan, and they are not a newsletter channel and take no replies. A school whose families will not install an app should price a year of texting before it chooses.
Where each option wins
Honest scorecard. The stack column assumes a spreadsheet, Stripe or QuickBooks invoicing, a Google Form and a group text, run by one careful person.
| Need | General-purpose stack | Platform (Pearspark shown) |
|---|---|---|
| Attendance in under a minute on a phone | A form, if built well | Yes; class remembered from yesterday |
| Excused and late with a note, corrections later | Depends on the form | Yes |
| Parent told of an absence the same morning | No, unless someone texts | Push notification, automatic |
| Chronic-absence and not-taken reports | Built by hand in the sheet | Yes, CSV, can be emailed on a schedule |
| Recurring tuition invoices | Yes, Stripe or QuickBooks | Yes, eight cadences |
| Sibling discounts and aid applied on their own | No; typed per invoice | Yes |
| Split households | Two customers, kept in sync by hand | Yes, by percent |
| Bank debit and autopay | Yes, in Stripe | Yes; ACH offered first |
| Overdue reminders without you | Some invoicing tools | Yes, three, a week apart |
| Text messages | Yes, group text | Yes; one-way alerts, prepaid from 2.7¢ a text |
| Message audiences from the roster | No; lists kept by hand | Yes; class, student, teacher, and — for an admin — a grade, a campus or all students |
| Replies kept in the school's record | No | Yes |
| Emergency broadcast with acknowledgements | No | Yes |
| One login for all of a family's children | No | Yes |
| Export everything if you leave | It is already yours | Reports and rosters self-serve as CSV; the full dump is run on request |
Where the stack column says yes, it means yes for a school of ten with one careful person. The rows go wrong at thirty students because the person is now three people.
Pearspark's answers to those questions
One plan. $50 a month covers the first 20 students, then $2.50 a student a month; a school of 25 pays $62.50. No setup fee, no contract, no minimum, and parent accounts are free and unlimited. Online payments cost Stripe's standard rate plus 0.5% to Pearspark; cash and check cost nothing. Every report is self-serve CSV, and any report can be emailed on a schedule.
The export-everything dump, messages included, is run by Pearspark on request rather than by a button. Rosters, attendance, grades, the billing journal, aid, library and every report export on their own.
Nothing marked yes on this page is on a roadmap. The not-today list is the one above: an accounting-package sync, a billing reminder by text, and reversing a card or bank payment anywhere but Stripe. Elsewhere in the product: no student work submissions, no public API, no calendar feed, and no attendance by period. A parent can tell the school about an absence from the portal, but only a teacher can excuse one.
The three areas in Pearspark
Each page lists what the feature does today, with the same rule about naming what it does not.
Watch each one done
Attendance, a month's billing, and a message to every family. A minute each.
Common questions
What features matter most in attendance software for a microschool?
Speed first: under a minute on a phone, mark all present and fix the exceptions. Then the four statuses (present, absent, late, excused) with a note and the ability to correct a past day, automatic notice to parents the same morning, and reports you can run yourself: per-student history, rate by date range, a chronic-absence list, and which classes have not taken attendance today, all exportable as CSV.
Can I just use Stripe or QuickBooks for tuition billing?
Yes, at a small size. Both send recurring invoices and take bank debit and cards. What they cannot do is apply a sibling discount or an aid award on their own, split one child's tuition between two households, or keep the roster and the customer list in sync. Those are typed by hand each time, and that is what breaks first as a school grows.
Is a group text good enough for school communication?
For speed, yes. It reaches everyone and every parent already has it. What it lacks is a record the office can see, control over who is in which audience, an acknowledgement list for an emergency, and any separation between a teacher's personal phone and the school. Most schools that grow past twenty students end up wanting those four things.
Does Pearspark send text messages (SMS)?
Yes, one way. A school switches the text module on, buys prepaid credits from 2.7¢ a text, and can then text families from two places: the emergency console and the message composer. Ordinary texts go to families who opted in; an emergency goes to every number on file. Families cannot reply by text, there is no newsletter builder and no scheduled campaigns, and email, push and the in-app inbox are still unlimited and free.
What hidden costs should I ask a school platform vendor about?
Whether SMS, payment processing or parent accounts are billed separately; whether there is a per-student minimum, setup fee or contract; whether you can export all of your data yourself; whether any report is only available by asking support; and which advertised features are live today rather than on a roadmap. Pearspark's answers: one plan, no setup fee or contract, free parent accounts, Stripe's rate plus 0.5% on online payments, text messages as prepaid credits from 2.7¢ each (the only thing we charge by use), self-serve CSV for every report, and a not-today list published on this page.
At what size does a microschool need a management platform?
Somewhere between fifteen and thirty students, or earlier if a sibling discount, a split household or a financial aid award shows up. Under fifteen, one careful person with a spreadsheet and an invoicing tool is fine. Past thirty, the person keeping four lists in sync is usually three people, and the lists disagree.
Sources
Every figure on this page is read from the source linked below. Where no source could be found for a claim, the claim is not made.
The full comparison behind each row
Each one is sourced feature by feature, last reviewed August 2026, and says plainly where the other system is the better choice.
See it before you decide
Every task is on video — one minute each — and your first 30 days are free. No sales call.