Fixtures live on social media, tickets are sold by bank transfer or at the door, and nobody has one view of how many seats are left.
A sports club or event organiser needs supporters to find the fixtures, buy a seat in the right part of the venue and get through the gate — and needs the people running it to see what has sold. When that runs on social posts, bank transfers and a list at the door, every event starts with reconciling payments by hand and guessing how many seats are left.
Zutt Solution built exactly this combination for the Johor Southern Tigers Basketball Club (JST): the club’s public website, the backend and admin behind it, online ticketing with zone selection, and an offline ticket POS for sales at the venue. All of it is live. We are a software house in Johor Bahru, and the team that built JST’s system is the team that supports it.
The same building blocks fit other clubs, academies and event organisers: a website supporters actually use, ticket sales that know which zones still have seats, and sales at the venue recorded in the same backend as online sales. You can start with the website and add ticketing as a later, separately scoped phase.
JST’s build is delivered and running. The case study states exactly what we built.
The club’s public website, its backend and admin, online ticketing with zone selection, and an offline ticket POS — all live at johorsoutherntigersbc.my. Supporters choose a zone on a colour-coded arena map before buying, and staff at the venue sell from the ticket POS.
Start with the one bottleneck costing you the most time — you do not have to build everything at once.
The same five steps on every project, whatever your sector.
We map your business process, pain points, goals, and must-have workflows.
We turn the problem into screens, data flow, and a clear build roadmap.
We build in weekly working releases, so you can test progress early.
We test workflows, edge cases, reports, permissions, and real user scenarios.
We deploy, monitor, support users, and keep improving the system after launch. Go-live is where the support relationship starts, not where the project ends.
If tickets are sold online and at the venue, both need to draw from the same records. That is why JST’s online ticketing and its offline ticket POS run against one backend.
Zone selection lets supporters choose where they sit and lets the organiser price sections differently. It is worth settling the seating plan and pricing rules before the build starts, because they shape the whole ticketing flow.
Fixtures, results, team news and announcements change often. A backend and admin let the club update them without calling a developer each time.
When a system sells tickets, problems are time-sensitive. Support comes from the team that built it, over WhatsApp, rather than from a helpdesk that has never seen your setup.
Yes. JST’s ticketing lets supporters choose a zone on an arena map before buying, and it is live. We scope the seating plan, pricing and payment flow for your venue during discovery.
Yes. JST has an offline ticket POS alongside its online ticketing, so venue sales and online sales are recorded in the same backend.
Yes. A website with a proper backend and admin is a sensible first step, and ticketing can be added as a separate, scoped phase when the club is ready.
We quote per project after a short discovery call. A website alone is a different job from a website with ticketing and a POS, and the quote spells out what is included and what is not.
We work across these sectors too.
Five minutes, no sales pressure. We will identify your biggest digitalisation gaps and suggest the right next step for your budget.