Admissions teams at independent and international schools rarely think of a missed enquiry in financial terms. It feels like a small, forgettable thing — a prospectus request that sat in an inbox over the weekend, a scholarship question that didn’t get answered until Monday. Nobody logs it as a loss, because nothing visibly went wrong. The family just never replied again.

But run the numbers, and that quiet non-event turns out to be one of the most expensive things happening on your website.

A single enquiry is worth more than it looks

Independent school fees typically run well into five figures a year, and a family doesn’t enrol for one year — they enrol for a school career. Multiply an annual fee by the years a pupil is likely to stay, and a single enquiry that converts can be worth anywhere from the high five figures to well over £100,000 across the relationship.

Set against that, the cost of the systems needed to capture and respond to every serious enquiry is trivial. Which makes the inverse also true: losing even one enquiry that would otherwise have converted is an expensive mistake, and it’s one most schools are making silently, every week, without any record of it happening.

Why the losses stay invisible

Families choosing an independent or international school are rarely choosing between one option and a form to fill in. They’re comparing several schools simultaneously, often from overseas, often outside your admissions team’s working hours. They have specific, decision-relevant questions — entry points, boarding arrangements, scholarship eligibility, curriculum, pastoral care — and increasingly, visa and university-pathway guidance for the years beyond.

When those questions don’t get answered quickly, families don’t complain. There’s no support ticket, no angry email, no signal in any dashboard your team looks at. They simply enquire at the next school on their shortlist instead, and your admissions team never learns that the family existed.

This is what makes the problem hard to fix through effort alone. Your team can be responsive, well-trained, and genuinely stretched thin, and the losses will keep happening anyway, because the families most worth capturing are often the ones researching at 11pm in a different time zone, when no amount of effort puts a person at a desk to answer them.

The questions repeat, even when the families don’t

Look at what admissions teams actually spend their time answering, and a pattern shows up quickly: fees, entry requirements, boarding options, scholarship availability, registration deadlines, and — for overseas families — visa and pathway questions. Nearly all of it is already published somewhere on the school’s own website. The families asking aren’t missing information because it doesn’t exist; they’re missing it because finding it, or getting it confirmed directly, takes more effort or time than they’re willing to spend before moving to the next option.

Every one of those repeated questions is time your admissions team isn’t spending on the parts of the job that actually convert a family into an enrolment: the campus visit, the interview, the personal reassurance a hesitant parent needs before committing.

Turning the website into part of the admissions team

The fix isn’t asking your team to be faster or more available. It’s giving your website the ability to answer the recurring questions itself, instantly, in the family’s own language, at whatever hour they’re asking — and to quietly qualify who’s serious in the process, so your team’s time goes toward the conversations that need a human.

That’s the specific problem Julia is built to solve for independent and international schools: trained on your own website content, live in around two weeks, with no disruption to your existing site or team, and configured to ask the qualifying questions — year group, entry year, day or boarding, nationality, budget — that turn a browsing visitor into a lead your admissions team can act on with confidence.

Given what a single enrolment is worth over a school career, the maths tends to make the decision straightforward. The harder part is usually just seeing the problem clearly enough to act on it — which is exactly what a real demo, built from your own site, tends to make obvious.