The honest version
A children's tutoring site is not a hard build. It is a short list of pages that have to say difficult things clearly: what a session is, who the tutor is and how they are checked, how a parent hears about progress, what it costs, and how to book a trial.
The build almost never stalls on design or code. It stalls on the fees table, on photographs, and on a safeguarding page nobody has written down before. Knowing that in advance is most of what makes it quick.
Stage 1: the first conversation
Half an hour, mostly questions. Who you teach, which subjects and stages, one to one or groups, in person or online or both. Whether you are a solo tutor or a centre with staff. What you charge and how you take it. Which platform you run, or whether you are choosing one.
Then the practical ones. Who owns the domain. What exists now and what is worth keeping. Whether there are photographs of the room and the team, and whether any include children.
Out of this comes a page list. For most tutoring businesses it is Home, Subjects with a page per subject or stage, How sessions work, Fees, Our tutors, Safeguarding, Online sessions if you offer them, Reviews, Book a trial and Contact.
Stage 2: the fees table
We do this early because it is the slowest decision, not because it is the hardest page.
We need the session rate by stage and format, the term equivalent, the price of the trial or assessment, and the rules on cancellation, missed sessions and holidays. Most tutors have never written the rules down, and writing them is genuinely useful work regardless of the website.
Nothing else can be finished until this exists, because the booking flow, the subject pages and the calls to action all point at it.
Stage 3: safeguarding and tutor profiles
The second slow one. We need the list of tutors, a real photograph of each, subjects and stages taught, qualifications, and a truthful statement of which checks each holds.
We also need your safeguarding position: the named lead, how a concern is raised, the rules on one to one sessions and on contact outside them, and the policy document if there is one. If there is not, this is the stage where you write it.
Where a photograph includes a child, we need evidence of consent from the person with parental responsibility, or we use a different photograph.
Stage 4: photography
Real pictures of your room, your desk, your whiteboard, your materials and your tutors. If you teach online, a screenshot of an actual session with a real question on the board.
Stock photographs of smiling children with pencils are the fastest way to look like every other tutoring site in the county. A phone camera, good daylight and twenty minutes beats them comfortably.
Stage 5: design direction
You see the home page and one inner page as a real design, not a slide. We agree typography, colour, how tutor profiles look and how the fees table reads on a phone.
Two rounds of changes at this point is normal, and it is much cheaper to move things here than after the whole site is built.
Stage 6: build
The pages are built, the copy is written to the parent rather than the child, and the content goes in. A page per subject or stage, because each one is a search result on its own.
At the same time the practical layer: fast on a phone, accessible, correct headings, a privacy notice that covers a child's details and session notes, and forms that ask for the minimum.
Stage 7: wiring the booking
Your platform, whether TutorBird, Teachworks, ClassForKids or Acuity, gets configured to match the fees page: the trial as its own service, recurring weekly slots, the parent as account holder and the child as student.
Then the site is deep linked into it from the header, the fees table and every subject page, and the confirmation and reminder messages are branded with your name, address, what to bring and the safeguarding link.
Stage 8: review and launch
You get a link and a list of what to check: names, qualifications, checks, prices, hours, the cancellation rule. We test the booking route end to end on a real phone and inside the Instagram in-app browser.
Then launch, with redirects from the old pages, the search console verified, and the sitemap submitted. Nothing about launch day should be dramatic.
Stage 9: the first month
We watch which pages parents land on and which button they press. Usually one or two things want changing: the trial explained higher up, a subject page split in two, or a question that keeps arriving by email turned into a paragraph.
What actually causes delay
Fees not decided. Photographs not taken. Tutor details half collected. A safeguarding policy that does not exist yet. None of them are technical, and all of them are yours. Gather them before the first call and the build runs quickly.
Where this sits
That process is how we build a children's tutoring website, and the same stages run through our other childcare and family websites. The packages are on pricing. Decide the fees, take the photographs, write the policy, and the rest is our problem.