Open Devdocs VS LessonBrief

LessonBrief's answer:

Independent private tutors first — the people writing parent messages every evening — and small tuition centres of two to ten tutors, which get shared pupils, per-tutor assignments and an audit trail. Built in the UK; useful anywhere parent updates are written in English.

LessonBrief's answer:

Tutoring management suites run the business side — scheduling, invoicing, CRM. LessonBrief does the one job they don't: the writing after each lesson. Rough notes become a polished parent update, homework sheet or next-lesson plan in about a minute. And compared with pasting lesson notes into a general AI chatbot, the difference is simple: notes about children never leave LessonBrief's own server. It's also free during early access.

LessonBrief's answer:

Next.js, React and TypeScript, with Postgres (row-level security enforced at the database) via Supabase. Drafting runs on LessonBrief's own server-side template engine — deliberately no external AI APIs anywhere in the product.

LessonBrief's answer:

Privacy is the architecture, not a setting. Drafting runs entirely on LessonBrief's own server-side template engine — nothing is ever sent to an external AI provider — pupils are recorded by initials only, and every tutor's data is isolated with database-level row security. Every output is a draft the tutor reviews before sending, and it never invents facts beyond the notes the tutor typed.

LessonBrief's answer:

It started with watching tutors handle the same problem two bad ways: spend 15–30 unpaid minutes writing parent updates after every lesson, or paste notes about children into a general-purpose AI chatbot. Both seemed wrong, so LessonBrief was built as the third option: the after-lesson admin done in a minute, on infrastructure where nothing about a pupil ever leaves the building.