Students, bookings, planning, lessons, rentals, equipment, staff and payments, all connected in a single system built around how a watersports school actually runs.
Private beta · Being tested every day inside a working school
Watersports schools are operationally complex and most of them are run with generic, disconnected tools. The work gets done, but the coordination around it grows every season.
Customers in a spreadsheet, bookings in an inbox, the day on a whiteboard, payments in a notebook. None of it talks to the rest.
A booking becomes a lesson, becomes a rental, becomes a payment. Every step starts again from a blank field.
Who teaches what, with which gear, for which student. It works, until the person holding it takes a day off.
What came in, what is still owed, how many hours each instructor worked. Always later than you would like.
A student arrives, books a course, gets a lesson on the calendar and pays for it. In Kapay that is one chain of information, not four separate records to keep in sync by hand.
Student → Booking → Planning → Lesson · Rental → Payment
Who is arriving, who is leaving, one lane per instructor and every lesson in its slot. Drag a student onto a lesson and the booking, the spots and the instructor's day all follow.
One lane per instructor, swipe between them, drag an arriving student straight onto a lesson and add a new one without leaving the beach. Nothing to install: it is the same Kapay in the phone's browser.
Not a booking form with extras bolted on. Every module below opens a short video of that part of Kapay, running.
Kapay is made by people from the watersports industry, and it is being built against a real season: changing conditions, walk-ins, equipment, instructors and a schedule that never survives contact with the wind.
Kapay is in product validation. There are no external schools yet: the priority is to simplify and prove the product before opening it up.
Kapay is being tested in a real operational environment, which is where the workflows and the priorities come from.
The initial focus is building a strong concentration of schools across Europe, and growing from there.
Kapay runs in the browser. Setting it up means describing your school once: your activities, your prices, your instructors.
Activities, services, prices, instructors and how you take payment.
Your students, your bookings and your equipment, so the board reflects the real season.
Planning, lessons, rentals and payments stop being four separate jobs.
No tiered features, no per-module upsell and no setup fee. Every school gets the whole system.
€99/ month
No. Kapay is built for watersports schools and centres in general: kitesurf, wingfoil, windsurf, surf, SUP, kayak, foil. Schools that run several activities at once are exactly the case it is designed for.
No. Schools work differently, and Kapay is meant to fit that. A school with no storage lockers simply never opens that part. What matters is that the areas you do use stay connected to each other.
That is the intention: to replace the spreadsheets, the whiteboard, the message threads and the separate booking tool with one operational system. The honest answer for your specific school is best given after seeing how you work, and that is what the demo is for.
Private beta. Kapay is functional and in daily use inside a real school, and it is being validated and simplified before opening to external schools. If you want to be among the first, the demo is the place to start.
€99 a month per school, everything included, no setup fee and cancellable at any time. The pricing page has the detail. If your school has something unusual about how it operates, it is worth raising it on the call rather than guessing from a page.
A short call, your real operation on screen, and an honest answer about whether Kapay fits it.
Around 20 minutes · No commitment