← What fathm does

Makeups off your front desk.

A kid misses Tuesday. Somewhere between the sick text and Saturday, the makeup question lands on your front desk.

The way it works today.

The policy lives in someone's head. Two per term? Was it 24 hours' notice? It depends who answers the phone.

So the class runs a seat short while a waitlisted kid stays home. The parent calls three times. Somebody scrolls a spreadsheet and reads out whatever sounds right.

What I'm building.

Miss with enough notice and a Makeup Token issues itself, under the limits your school sets. Miss without the notice and nothing issues, because the rule lives in the software. Either way it never turns into an argument at the desk.

Parents book their own makeup from the seats the live class list shows as free. The count is worked out from that list, every time, so nobody reads it off a whiteboard. When a teacher is out, the class merges with another for the session and every booking moves with it. And the freed seat gets re-offered to the next family, in order.

This is the piece that already runs. The engine behind it is built and tested, tokens and all. Your school's policy is the part we shape together.

I'm Matthew Bilo. I build software used by 10,000+ firms at Sitemate and LRQA. fathm gets the same engineering.

Build it with me.

Send me your makeup policy, in your own words. "Two per term, don't ask" is a policy. What you say decides what gets built:matthew@fathm.io