OUR STORY
Why we built PeriAdmin
Built by a developer married to a peripatetic teacher, because start-of-term admin was breaking us both.

My husband has been a peripatetic guitar teacher for the better part of thirty years, driving between schools, teaching kids who come and go mid-term, and doing it all without ever really knowing, week to week, who’d actually paid him and who hadn’t.
Half of it wasn’t even the money. It was not having the information when he needed it — which student had switched days, whose form the school sent home three weeks ago and never came back, who’d actually signed up. Scribbled notes, forwarded emails, a folder of paper that was never in the car when he needed it. That frustration fed straight into everything else.
Every general invoicing tool we tried assumed a tidy world — one business, one set of customers, bills out and money back on schedule. That’s not what peripatetic teaching looks like. A student starts in October and leaves in February. A school covers part of the fee through Pupil Premium and the parent covers the rest. Most teachers charge for a missed lesson — the time was blocked out either way — but sometimes you make an exception, because you’re a person, not a billing machine, and you help when you can. None of that’s an exception; it was just Tuesday.
So I built the tool I wished he had: online sign-up forms so parents’ details are there when he needs them, not scribbled on a form at the bottom of a school bag; something that knows who owes what across every school he visits; something that copes with the small, constant changes real teaching throws at it.
“No peripatetic teacher has a PA. Even the luckiest of us only have an overworked partner roped in every September.”
Trying to reconstruct the year from a folder of paper that’s gone missing — We decided to fix that instead.
See what we built
Free forever on one school. No card required.
