Building FairWayOS: why golf courses are stuck in 2005
The golf industry runs on software from two decades ago. Here’s why we’re building FairWayOS and what we’ve learned about selling to an industry that’s allergic to change.

In this post 5 parts
I played a round at a municipal golf course last summer. When I booked the tee time, I had to call. When I arrived, the pro shop was using software that looked like it was built for Windows XP. The tee sheet was partially paper.
This is not unusual. This is normal in the golf industry.
The problem
Golf course management software is dominated by legacy players who built their products in the 2000s and have been coasting on switching costs ever since. The typical course runs: - A tee sheet system from one vendor - POS from another - Member database in a spreadsheet (seriously) - Communication via individual emails or a physical bulletin board - Analytics? What analytics?
Each system costs money. None of them talk to each other. And the staff spends hours doing manual work that should be automated.
Why now
Two things changed: 1. AI capabilities are now good enough to genuinely automate scheduling optimization, dynamic pricing, and member communication 2. Cloud infrastructure costs dropped enough that even municipal courses with tight budgets can afford modern software
The incumbents aren’t adapting. They’re adding features to 15-year-old architectures. That’s not modernization. That’s lipstick on a pig.
What we’re building
FairWayOS is designed to be the single platform a golf course needs. One login, one system:
- Smart tee sheet that optimizes revenue through dynamic pricing (like how airlines price seats)
- AI member communication that handles reminders, promotions, and updates automatically
- Integrated POS that connects to the tee sheet so you can see revenue per time slot
- Real-time analytics that help operators make decisions (not just reports they ignore)
The hard part
Selling to golf courses is hard. These operators are: - Busy (running a course is 7 days/week, dawn to dusk) - Skeptical (they’ve been burned by technology promises before) - Budget-conscious (municipal courses especially) - Change-averse (the current system “works” even if it’s painful)
Our approach: don’t sell features. Show the time savings. If we can give a course operator back 10 hours a week, the software sells itself.
Current status
We’re in active development with conversations happening at several Edmonton-area courses. The first beta will focus on tee sheet management and booking, the pain point that matters most.
Updates coming as we ship.
Keep reading
More in Notes →
How we use Claude to build faster
Our actual workflow using Claude for everything from architecture decisions to code reviews. Not hype: the real productivity gains and limitations.

AI automation for Edmonton small businesses: where to start
Most Edmonton businesses still do work by hand that could run on its own. Here’s a practical guide to AI automation: what’s worth automating, what isn’t, and where to start.

Web development in Edmonton: what to look for in 2026
Choosing a web developer in Edmonton? Here’s what separates a good investment from a waste of money, from someone who’s built sites for local businesses, campaigns, and startups across Alberta.
