From the people who built this site
How this site was built
Treasure Valley Tee Times reads thirteen public golf courses across six different booking systems and puts every open tee time in one list. It is free, it holds no accounts, and it was built in a week by Collister Computing in Boise.
The problem it solves
Finding a Saturday morning tee time around Boise used to mean opening six different booking sites, because thirteen courses do not agree on a vendor. Each one wants a date, a party size and a few clicks before it will admit it has nothing. This site does that walk on a schedule and shows you the answer in one list, sorted by time, with a link straight to the course's own booking page.
How it works
A computer in Boise does the reading
Every fifteen minutes or so, a small program walks each course’s own public booking page, one request at a time, and writes down the open times it finds. It runs on a home machine in Boise because several of these booking sites only answer a real browser on a real local connection.
One file goes up
The result is a single file: every course, every open time, for the next eight days. It is published to a small API that costs nothing to run at this size, and it replaces the previous one wholesale. There is no database to keep healthy and nothing to migrate.
The page is already built
The site itself is static files. Nothing is rendered on a server when you open it; the page arrives finished and then fetches that one file. That is why it feels immediate on a phone in a parking lot, and why the whole thing fits inside a free tier.
The pieces are ordinary on purpose: a Python poller, a static site, and a small worker with a key-value store, all of it inside Cloudflare's free tier. Nothing here needs a platform bill to stay up, which is the only reason a free tool like this can keep running.
What it deliberately does not do
It never books. It holds no login for any course, never asks you for one, never asks for a card, and cannot reserve, change or cancel anything on your behalf. Every time links out to the course that owns it. Reading a public page politely and booking on someone's behalf are different products, and this is the first one.
The constraint is also the interesting part of the build. One request per second per booking platform, a hard stop on any refusal, a real browser where a real browser is required, and a course comes off the site the same day if it asks.
Who built it
Collister Computing — web and app development in Boise, Idaho. Practical software for local businesses, built to be understood by the next person who opens it and kept running after it ships. This site is not a client project; it is the same work, pointed at a Saturday morning problem.
Websites
One clean page for a local business that needs somewhere good to send customers. The first version gets built before you commit to anything, and you decide after you have seen it.
See the website plan →Apps and tools
Internal dashboards, customer portals and small web apps for the work that spreadsheets and paper forms keep making harder. This site is one of them.
See the app work →Managed operations
For a company whose website and advertising already run and already cost real money. The engagement starts read-only, in accounts the business owns, before anything is changed.
See managed operations →Have something that should work like this?
Say what you are trying to build, or what is already running and nobody can explain. A reply comes from the person who would do the work.