Platform architecture · read top to bottom
This is not one website. It is two businesses sharing one engine — and the engine is the reason it can grow.
Everything below hangs off those two. Follow a line down and it never stops at a page name — it carries on to who runs that page, what their screen shows them, and what it keeps them out of.
Golfers, captains, sponsors, outside organisers
Competition. Singh Open, the PGL Inter-League, PTR leagues, and outings run by other organisations on PTR's infrastructure. Each keeps its own identity; none of them needs its own website.
Earns from entry fees, team entries, league seasons, sponsorship, and a fee on every outing PTR hosts for someone else.
Local players, members, families, companies booking a night out
A venue. 5,000 sq ft in Canton — five simulator bays, three standard, one premium, one for coaching, and a social lounge. Canton is the first one, not the only one.
Earns from bay time, memberships, coaching, corporate and private parties, gift cards and merchandise.
Nobody buys this — everybody uses it
One checkout, one customer database, one media library, one set of staff logins. The shared machinery sitting under both businesses.
Earns nothing directly. It is why adding the eleventh event, or the second city, costs a fraction of the first.
These six things are built once. A golfer entering Singh Open and a member booking a bay in Canton travel through the same forms, pay through the same checkout, and land in the same database — tagged differently. That is the whole argument for one site instead of three.
Built once does not mean visible to everyone. Each of these is one engine with scoped access layered on top: the Super Admin reads all of it, and everybody else reads only the slice their job or their contract allows. A hosted outing runs on the same registration form as Singh Open and sees none of Singh Open's entries. Every module below states exactly where that line falls, page by page.
Everyone signs in at the same place. What loads after that is decided entirely by the role, and the strictest boundary on this list is a contract term, not a preference.
Nine roles is not nine builds. It is one permission system asked nine questions — the screens underneath are largely the same screens, filtered.
Which is also why day one does not need all nine. Super Admin, Location Manager and Front Desk open the Lounge. Event Manager and Partner Organizer switch on when the first hosted outing signs. The architecture has to anticipate all nine now, so that switching one on later is a setting rather than a rebuild.