What a Website for a Tutor or a School Costs

en 2026-09-20 6 min read

A single tutor teaching one or two subjects needs a step 02 mini-site, EUR 900 to 1.500, live in 2 to 3 weeks. A school, a language institute or a course provider with a page per course, a term calendar and an enrolment flow is step 03, EUR 1.500 to 3.500, in 3 to 6 weeks. Taking the enrolment itself, with accounts and payment, is step 04, EUR 3.500 to 7.500.

One question decides which you are buying: what changes, and who changes it. Content fixed for years can be built cheaply and left alone. Dates, courses, tutors and places that move every term need an editor your office can use without ringing a developer, and that lifts a teaching site from step 02 into step 03.

What a course page has to carry

The course page is the page that sells, so it has to survive being read next to two competitors' versions of it. Six things earn their place:

• What is taught, in the student's words. Not the syllabus code. The thing they will be able to do at the end.
• Who it is for. Level, year group, prior knowledge, exam board where that matters.
• When it runs. Start date, weekday, time, number of sessions, the term it belongs to.
• Where and how. A named room at a named address, online, or both, stated once and clearly.
• Who teaches it. A named tutor with a face and a short history, linked to a profile.
• What it costs to attend, and what happens next. A price or an honest range, then one button that does what it says.

Six blocks, one template. That is the argument for putting course pages in a CMS rather than in code: the template is built once, then your office adds the next course without a developer.

Term dates are the part that rots

Term dates, holiday closures, enrolment deadlines and exam weeks all expire on a known day. A site still showing last year's dates when term starts does more harm than one with no dates at all, because it tells a parent that nothing here is maintained. The question is not whether to publish dates. It is who edits them, and how fast.

Where a CMS earns its place

A CMS is not automatically the right answer. It is right for content that changes on a schedule you do not control, and wrong for structure that should not change. Six kinds of change, sorted:

Read the right-hand column and the price follows. If four or five of those six rows are live for you, the CMS is what keeps the site honest between terms, and that is a step 03 build at EUR 1.500 to 3.500. If only the last row applies, because you teach one subject on a fixed timetable, a step 02 mini-site at EUR 900 to 1.500 is the better buy.

Enrolment, three honest options

Enrolment is where quotes diverge, so choose the option first.

1. Enquire, then a human. A short form capturing the course, the level and a phone number. Your office calls back and enrols the student in the system you already run. Step 02 or step 03.
2. A structured enrolment form. Course choice, term, student and guardian details, conditions accepted, delivered to your office and exportable. No accounts, so still step 03, though a long conditional form sits at the upper end of EUR 1.500 to 3.500.
3. Enrolment with payment on the site. The student or parent creates an account, picks a course and a term, pays, and holds a confirmed place, while you get a roster and a capacity count. Accounts, payments and a dashboard are step 04, EUR 3.500 to 7.500, over 6 to 12 weeks: application work rather than a website, built the way our Next.js development page describes.

The steps, priced

Every step is defined in full on packages, and a fixed quote always follows scoping.

How the build runs

Scoping comes first: a call, then a written scope covering pages, the course template, who edits what and what happens when a student presses the button, with the quote fixed against it. Then copy, then a few screens designed properly with the rest built on the same system, which is how design and engineering works here. Then the build: course template, term calendar, enrolment or enquiry flow, analytics, and the content load before launch.

Step 02 runs 2 to 3 weeks, step 03 runs 3 to 6 weeks, step 04 runs 6 to 12 weeks. Course descriptions and tutor bios are the part that waits on you, so write them while the build runs rather than after it.

When to spend less

• One tutor, a full roster, all word of mouth. A step 01 landing page at EUR 600 to 900 in 1 to 2 weeks holds your subjects, your method and a form.
• The timetable already lives somewhere official. If an exam board or a school system publishes the dates, link to that source instead of copying it into your CMS. Two places holding the same dates will disagree, and yours will be wrong.
• Term starts before a step 03 could finish. Ship a step 02 in 2 to 3 weeks with the course list and the term dates, then add per-course pages on the same codebase.
• Hold the monthly SEO. SEO foundation is a one-off at EUR 450 to 750: Search Console, analytics, indexation, technical hygiene, titles, internal links, a 3 to 6 month plan. Take it at launch. SEO growth at EUR 500 to 800 per month is for subject and town pages later.

After launch

Care is EUR 100 to 300 per month for updates, monitoring, backups and small fixes. It does not cover a redesign or new features; those get scoped and quoted separately. You own the code, the repository and the database. We can host it, and that is agreed per project rather than assumed.

Common questions

Do students need a login?

Only if something sits behind it: a paid place, materials, a schedule that is theirs alone. A login is the line between step 03 and step 04. If a student only needs to read about the course and get in touch, it adds cost and a password to forget.

We already have a student information system. Does the site replace it?

No, and it should not try. The site markets the courses; your system keeps the records. Connecting the two so an enrolment lands in it is an API integration, step 04 work at EUR 3.500 to 7.500. Until then, an export your office imports is a much cheaper answer.

How many course pages should we build?

One page for every course a stranger could search for by name, and a subject page for the rest. Step 03 covers 4 to 7 pages, the template plus the pages around it. If you run more courses than that, the template is still built once and the extra pages become a content load, quoted separately after scoping.

Send the courses you run, the terms you publish and whether you want money taken on the site, and you get a scope and a fixed quote. Start the conversation here.