/ Project: Online school of digital professions, Lviv · 2026 /

An online school website with a course catalogue and cohort enrolment

Case study: an online school website with a course catalogue, weekly syllabus, graduate work and cohort enrolment with instalments and instant course access.

Key decisions Enrolling in a cohort with instalments, no sales manager needed
Type
Websites
Industry
Education and online courses
Year
2026
Build stages 4–6 weeks
  1. Brief & research ≈ 1 wk
  2. UX/UI design ≈ 1 wk
  3. Development ≈ 2 wk
  4. QA & launch ≈ 1 wk
  • Astro
  • Sanity
  • WayForPay
  • Telegram Bot API

Product screens 08

  1. 01 Course catalogue
  2. 02 Course page
  3. 03 Weekly syllabus
  4. 04 Instructors and graduate work
An online school website with a course catalogue and cohort enrolment
  1. 05 Formats and payment
  2. 06 Cohort enrolment
  3. 07 Blog
  4. 08 Course admin
About the project

An online school website where people see the whole course — weekly syllabus, instructors, graduate work, format and price — enrol in a cohort with instalments and get course access straight away, without a manager.

  • Course catalogue Price, length and format on each card, so courses are easy to compare.
  • Syllabus and instructors Modules, topics, weekly practice and graduate work show what people will learn and what ends up in their portfolio.
  • Instalments Self-paced, with a mentor or pay in full with a discount, side by side, with online instalments.
  • Access without a manager After payment the student lands on the learning platform with a schedule, and the sign-up goes to the CRM.
01 · The brief

The school teaches UX/UI design, digital marketing and analytics. Courses were sold through one-off landing pages for every launch and Instagram DMs. The syllabus lived in a Google Doc, the price in a manager’s reply and the cohort start date in stories. After payment a manager added the student to the learning platform by hand, sometimes a day or two later. Someone comparing schools could not see what they would study each week or what it cost, and went where that was clear. Google brought almost no students: old landing pages disappeared with each cohort.

02 · What we built

We built one school website on the Company Lite plan instead of separate landing pages. Every course has a card with price, length and format, and a page with the syllabus by module and week, instructors and graduate work. The “self-paced”, “with a mentor” and “pay in full with a discount” formats sit side by side. Enrolment in the next cohort takes card or instalment payment through WayForPay; after payment the site passes the student to the learning platform, sends an email with access and schedule, and sends the sign-up to Telegram and the CRM. The school updates courses, cohort dates, prices and instructors itself in Sanity. Each course has a permanent page with Course markup, and the old landing pages redirect to it.

  1. Before Syllabus in a Google Doc, price in a manager’s reply.

    After A course card with price, length and format, and a week-by-week syllabus.

  2. Before The cohort start date only in stories.

    After Enrolment in the next cohort right on the course page.

  3. Before Access opened by hand a day or two after payment.

    After Platform access and the schedule arrive straight after payment.

  4. Before A landing page per launch, no students from Google.

    After One school site with permanent course pages people find in search.

03 · The client’s path

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

  1. Finds a course

    Searches “online UX design course” and lands on a permanent course page.

  2. Studies the syllabus

    Modules, topics, weekly practice and graduate work.

  3. Chooses a format

    Self-paced, with a mentor, or pay in full with a discount.

  4. Enrols in a cohort

    Card or instalment payment online and confirmation in Telegram.

  5. Starts learning

    Platform access and the schedule arrive by email right after payment.

04 · What is inside the project

  1. Course catalogue with price, length and format on each card

  2. Course pages: week-by-week syllabus, instructors, graduate work, FAQ

  3. Cohort enrolment with card or instalment payment

  4. Platform access and a schedule email sent automatically after payment

  5. Sign-ups to Telegram and CRM, analytics events for enrolment and payment

  6. Permanent course pages with Course markup instead of one-off landing pages

Forecast

Within 2–3 months, 20–30% of enrolments come from course pages in search, “how much” and “when does it start” DMs halve, and instalments remove part of the drop-off at checkout. A guideline, 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
    • WayForPay
    • Telegram Bot API
  4. Data & integrations Where the data lives and what the product talks to
    • Sanity

06 · How a project like this is built

Total: 4–6 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 ≈ 2 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 Construction company, Lviv · 2026 A construction company website with projects and an estimate request Construction and renovation

Solutions for a specific job

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

More projects

All projects →