/ Project: Private kindergarten, Kyiv · 2026 /

Private kindergarten website with group prices and tour booking

Case study: a private kindergarten site in Kyiv. Group prices and open places, menu and routine, tour booking, enquiries in Telegram and Google Sheets.

Key decisions Tour bookings without calling the head
Type
Websites
Industry
Early childhood education
Year
2026
Build stages 3–4 weeks
  1. Brief & research ≈ 1 wk
  2. UX/UI design ≈ 1 wk
  3. Development ≈ 1 wk
  4. QA & launch ≈ 1 wk
  • Astro
  • Sanity
  • Telegram Bot API
  • Google Sheets API

Product screens 08

  1. 01 Home with tour booking
  2. 02 Groups and prices
  3. 03 Daily routine and menu
  4. 04 Teachers
Private kindergarten website with group prices and tour booking
  1. 05 Settling in
  2. 06 Contract and licence
  3. 07 Telegram bot for the head
  4. 08 Enquiry sheet
About the project

A private kindergarten website in Kyiv where parents see group prices, the menu and the teachers and book a tour without calling, while the head gets enquiries in Telegram and a sheet with a waiting list.

  • Answers before the call Monthly fee, meals, routine and settling in on every group page.
  • A tour in a minute Group, child’s age and a convenient time — parents book on their own.
  • Enquiry sheet The bot adds every enquiry to a Google Sheet with a status from tour to contract.
  • A queue for places A waiting list by group shows whom to contact when a place opens.
01 · The brief

A three-group private kindergarten in Obolon had an Instagram page and an old website with photos and a phone number. There were no prices, menu or daily routine on the site, so the head answered the same questions by phone every day. Tour bookings and waiting-list requests were kept in a notebook, and some parents booked and did not come. When a place opened in a group, it was unclear whom to call first.

02 · What we built

We built a Standard business-card site. Each group has a page with the age range, group size, monthly fee, what it covers and open places. The daily routine, weekly menu and teachers with their qualifications are on the site, and the head updates them in Sanity. Parents book a tour or a trial day by choosing a group, the child’s age and a time. The enquiry reaches the head through a Telegram bot and is added to a Google Sheet with a status, and parents get a confirmation and a reminder the day before. If there is no place, the enquiry joins the group’s waiting list, and the head sees whom to contact first.

  1. Before Price and menu explained by phone every day.

    After Groups, prices and menu on the site before the call.

  2. Before Tour bookings in a notebook.

    After Enquiry in Telegram and a sheet with a status.

  3. Before Parents booked and did not come.

    After A confirmation and a reminder the day before.

  4. Before A place opened up, nobody knows whom to call.

    After A queue by group in the sheet.

03 · The client’s path

How a person moves through the product, from the first step to the result the business needs.

  1. Compare

    Fee, meals, routine and teachers on the group page.

  2. Book

    A tour or a trial day at a convenient time.

  3. Come

    Instant confirmation and a reminder the day before.

  4. Wait for a place

    The enquiry sits in its group’s queue.

  5. Sign the contract

    The status in the sheet changes to “enrolled”.

04 · What is inside the project

  1. Groups with prices, open places and what the fee covers

  2. Daily routine, weekly menu and teachers on the site

  3. Tour or trial-day booking without a call

  4. Enquiries in Telegram and Google Sheets with statuses

  5. A reminder to parents the day before the tour

  6. A waiting list by group instead of a notebook

Forecast

In the first 2–3 months 40–60% of tour bookings come through the site, and repeat calls about price and menu fall by about half. This is a benchmark, not a promise.

05 · Architecture

How the product is put together: from what the user sees to the data and services behind it.

  1. User Opens the site on a phone or a computer
  2. Interface What a person sees and taps
    • Astro
  3. Logic Rules, roles and scenarios
    • Telegram Bot API
    • Google Sheets API
  4. Data & integrations Where the data lives and what the product talks to
    • Sanity

06 · How a project like this is built

Total: 3–4 weeks
  1. 01 ≈ 1 wk Brief & research Goals, audience, page structure and what the product must do
  2. 02 ≈ 1 wk UX/UI design Prototype, design of the key screens and the mobile version
  3. 03 ≈ 1 wk Development Front end, CMS, integrations and animation
  4. 04 ≈ 1 wk QA & launch Device testing, speed, SEO groundwork and launch

Typical phase split for a project of this size

07 · Services in this project

Next project Driving school, Odesa · 2026 Driving school website with a course calculator, CRM and student portal Driving schools and driver training

Solutions for a specific job

Ready-made scenarios for your case — with examples and indicative pricing.

More projects

All projects →