The demo class: a low-stakes way to check tutor fit before committing

The first thing that distinguishes a useful demo from a polished demo is the choice of topic. We ask families to pick a chapter the child is currently studying or recently failed to handle well in a school test. That gives the tutor a chance to demonstrate diagnosis on a real gap, instead of running a smooth presentation on a chapter the child already knows. The demo is more valuable when the chapter is genuinely difficult; that is where the tutor's actual approach becomes visible.

Parental observation is the second thing that matters. We encourage the parent to sit in for at least part of the session — ideally the opening ten minutes and the closing five. The opening reveals how the tutor begins: do they ask the child what they have understood, look at the notebook, check recent homework? Or do they jump straight into delivering a lecture? The closing reveals how the tutor wraps up: is there a specific written takeaway, a small homework with a clear purpose, or a vague "do some practice"?

During the demo itself, four things signal a good fit. First, the tutor diagnoses before teaching. They ask questions, look at the student's existing work, and try to find the actual gap before explaining anything. Second, the child appears comfortable enough to admit confusion or ask a question. Third, the explanation lands — when the tutor asks the child to redo a question, the child can attempt it with less hand-holding. Fourth, the tutor leaves the child with one specific written takeaway, not a vague instruction to "practise more."

What signals a bad fit is just as important. A tutor who launches into explanation without diagnosis. A child who looks anxious or shut down. An explanation that the child cannot repeat back. An ending that just trails off. Inconsistent energy — too friendly, too stiff, too distracted by their own phone. We have seen all of these in demos and we treat them as serious signals, not minor concerns.

After the demo, we call the parent within twenty-four hours and ask one question: what did you observe? We listen for the parent's honest read — not their politeness. If the fit felt strong, we move to scheduling regular sessions and writing up the first-month plan. If the fit felt weak, we discuss what felt off and decide whether to try the next name on the shortlist or rebuild the shortlist with a different profile in mind. There is no judgement; this is exactly the purpose of running a demo before any commitment.

Demos are intentionally low-pressure for the child too. We do not let tutors test the child or assign a heavy task during the session. The aim is for the child to leave the demo with one small win — a concept they understood better, a question they got right, a clearer sense of what to work on next. A demo that leaves a child more anxious is a failed demo, regardless of how impressive the tutor was as a presenter.

By the end of a well-run demo, the parent should be able to say one clear thing: "yes, I want this tutor for my child," or "no, this is not the right fit." If the answer is somewhere in between, we usually need a second demo or a brief revisit of the brief. That clarity is the only outcome a demo really needs to deliver.