Why we're building ClassFactors

Most schools run on a patchwork of spreadsheets, paper registers, and messaging apps — attendance in one place, fees in another, leave requests passed around by hand. It works, technically, but it means staff spend time re-entering the same information in three different tools, and parents are often the last to know what's going on.

ClassFactors started with a single, specific problem: staff leave requests and approvals were slow and hard to track. It's grown from there into a fuller platform, but the underlying idea hasn't changed — approvals, records, and communication should live in one system that's built for how a school actually operates, not bolted together from tools meant for other kinds of businesses.

We're a small team, and the product is still under active development. We'd rather ship something schools genuinely find useful than rush out a feature list, so we're building it module by module and listening closely as early schools try it out.