Daily-fee and municipal golf courses buy software under economics that private clubs do not share. A public course earns most of its money from people who walk in once, collects it at the counter rather than on a monthly statement, and at a municipal facility has to justify the whole operation to somebody who does not play golf. Software built around member accounts and annual dues billing does not fail loudly under those conditions. It makes every ordinary task take one step longer, all season, worked by staff who started in April.
Why is the software math different at a public course?
Three things change at once, and they change together.
The first is who the customer is. A private club knows every golfer on the property by name and bills them monthly whether they play or not. A public course sells a round to somebody it may never see again, at a price that depends on the day and the hour, and has to collect the money before that golfer reaches the first tee. Member profiles and family billing hierarchies sit at the center of a private-club system. At a daily-fee counter, where the large majority of transactions come from people with no account at the course, they are close to dead weight.
The second is who the buyer answers to. A municipal GM reports to a parks department, a council committee or an authority board. Those bodies approve the operating appropriation, they approve capital spending, and they ask a question private-club boards rarely put in the same form: is this course covering its costs, or is the city covering them for it? Every software purchase at a municipal facility has to survive that question in a public meeting.
The third is staffing. Public courses hire for a season. The starter and the grill staff working a July Saturday often were not there in April, and some of them will not be there in September. A system that rewards a year of familiarity is a system that never gets a year.
What the revenue actually looks like
Before any argument about software, it helps to know the size of the thing. According to the National Golf Foundation's 18-hole facility profiles, total facility revenue is about $1,457,700 for a daily-fee course and about $1,269,100 for a municipal one. On the same NGF profiles, green fees plus cart fees, the line most operators mean when they say "the golf revenue", come to somewhere between $793,500 and $825,100.
The gap between those two lines is the first thing worth noticing. At an 18-hole municipal facility, green fees and carts are roughly two thirds of total revenue. The remaining third arrives through the pro shop, the grill, the range and the outing calendar, which is to say through exactly the parts of the operation most likely to be sitting on a separate register.
The second thing worth noticing is a labeling error that shows up constantly and that inverts conclusions. A total-revenue figure is not an operating budget. Revenue is what came in. A budget is what the authority appropriated to spend. Quote one as the other and you produce an expense ratio well above 100% or well below 50% depending on which way the mistake runs, and neither number means anything. This figure gets quoted badly, including by us. When you see a facility number cited, establish which line it is before you build a comparison on it.
For the rest of this article, one illustrative course. It is not a measurement of any real facility; it is a set of inputs estimated to sit inside the NGF profile published above, so the arithmetic can be checked rather than trusted.
The course plays 30,000 rounds a year. Green fees and carts bring in $810,000 of that, which is $27.00 a round. Total facility revenue is estimated at $1,270,000, or $42.33 a round across every line. The season runs about 210 operating days, so an average operating day is roughly 143 rounds. Every figure that follows comes back to those four numbers.
What a public tee sheet has to carry
A private club tee sheet manages booking windows and guest policies for a population it already knows by name. A public tee sheet is a point-of-sale device that happens to look like a calendar.
The load on it is not evenly distributed, and that is the part software gets wrong. On a Tuesday in April the sheet is close to idle. Between seven and eleven on a July Saturday it is carrying walk-ups at the counter, phone bookings, third-party channel inventory and the starter working two groups ahead, all writing to the same set of times. A system that is comfortable at ten transactions an hour and slow at eighty has not failed a benchmark. It has produced a line at the counter, which is the same thing measured in golfers.
There is a second demand that private clubs rarely put on a tee sheet. At a public course the sheet has to price as well as book. Rates move by season, by day of week, by time of day and by how far ahead the booking was made, and if the rate lives in a separate system from the inventory, somebody is retyping prices every time the weather forecast changes.
Does dynamic pricing annoy golfers?
Sometimes, and the honest answer matters more than the convenient one.
The idea of applying revenue management to golf was set out by Sheryl Kimes in 2000 in the Cornell Hotel and Restaurant Administration Quarterly, volume 41, issue 1, pages 120 to 127. That paper is a conceptual framework. It proposes how the tools hotels and airlines were using could map onto a golf operation, using rate fences and duration control against a fixed daily supply of tee times. It is a good piece of thinking and it is worth reading. What it is not is evidence that demand-based pricing captured revenue at any particular course, and it should not be cited as though it were.
The golf-specific evidence on how players react came later, from the same research program, and it points the other way. Kimes and Wirtz published "Perceived fairness of revenue management in the US golf industry" in the Journal of Revenue and Pricing Management, volume 1, issue 4, pages 332 to 344, in 2003. Golfers in that study rated varying price levels unfair. Pricing that varied by time of booking, which is precisely the mechanism most modern golf systems implement, was rated somewhere between neutral and slightly unfair.
Two caveats belong with that finding, and they are what keeps dynamic pricing defensible rather than dead. The study is from 2003, before a generation of consumers grew up buying travel and ride-hailing at fluctuating prices. And Wirtz and Kimes found in 2007 that familiarity with a pricing practice increases how fair people perceive it to be, which suggests the 2003 result is a starting position rather than a permanent one.
So the argument for dynamic pricing at a public course is reasonable. What is not reasonable is telling operators their customers will not mind, because the only golf-specific study on the question found that a meaningful share of them did. Price the way the research suggests people tolerate best: publish the rate card so the structure is visible rather than mysterious, frame off-peak as a discount rather than framing peak as a surcharge, and give the categories that will complain loudest, seniors and regulars, a defensible fence of their own. The resistance is real. It is manageable, and it is cheaper to manage it before the first complaint than after.
One register, or four
A daily-fee course commonly runs green fees and carts on the pro shop counter, merchandise on the same or a second register, the grill on a third, and the beverage cart on a tablet app that talks to nothing. Each one has its own card processor, its own settlement report, its own close-out routine and its own login for a nineteen-year-old who started last Thursday.
The subscription cost is the easy number and the smaller one. Three transaction systems at, say, $250 a month each is $9,000 a year. Write that down, because it is the figure that appears in the capital justification, and it is the figure a council will focus on.
The cost that never appears there is the reconciliation. Somebody matches the tee sheet against the pro shop register against the grill against the bank deposit, and does it again every week the course is open. Suppose that absorbs four hours a week across a 30-week operating season, at a fully loaded $22 an hour. That is 120 hours and $2,640 a year. Both of those inputs are placeholders. We do not have a measured figure for reconciliation hours at public courses and neither does anybody else who has published on the subject, so the only number worth trusting is the one your own operation produces. Ask whoever closes the week to log the time honestly for a month, corrections included.
The $2,640 is not the point of that calculation anyway. The point is what the person doing it is not doing, and the error rate. A green fee rung on the wrong rate code is a small discrepancy on Monday and a wrong round count in the annual report, and round counts by rate type are the thing a council actually reads.
Consolidating those registers matters more at a public course than at a private one for a structural reason. A private club has an accounts department that can absorb reconciliation work. A public course often does not have one. The GM may also be the head pro and the person matching deposits on a Monday morning.
What a council report has to contain
Municipal managers carry a reporting obligation that private club GMs do not, and it has a fixed shape. A parks committee or council wants rounds played by month against the same month last year, revenue split by line so green fees can be read separately from merchandise and food, the rate mix showing how many rounds sold at each price, revenue year to date against what was projected, and a defensible justification for any capital request.
The structural problem is worth being precise about, because it determines what software can and cannot fix. A golf system holds the revenue side and the rounds side. It does not hold the expense side. Payroll, utilities, equipment leases, insurance and the capital service on the irrigation project live in the city's general ledger, not in the tee sheet. So the report a council reads is always a join between two sources, and no golf platform will ever produce all of it.
What a platform can do is stop the golf half from being its own multi-source join. If rounds, rates, merchandise and food already sit in one database, the golf side of the report is an export with a date range on it. If they sit in four, the manager rebuilds the same spreadsheet every month, and every rebuild is a fresh opportunity for the round count in the council packet to disagree with the round count in the annual report.
That is also the answer to a question councils ask and golf systems answer badly: is the course subsidized? Getting to a defensible answer requires the revenue line at the granularity the council asked for and the expense line from the finance department, put side by side by somebody who understands both. Making the golf half of that a five-minute export is not the whole job. It is the half of the job that software can actually take off the manager's desk.
When a vendor says "integration"
Ask what the word is doing.
Two systems that "integrate" through a nightly data feed have not removed any of the work that made you look for software. The starter still switches screens. The close-out still requires matching one system's report against another's. The month-end still needs somebody to decide which number is right when the two disagree, and they will disagree, because a feed that ran at 2am does not know about the refund posted at 2:15.
The useful question is not whether a platform integrates. It is whether it replaces systems. During a demo, ring a green fee and a cart and a sleeve of balls on one screen, then ask to see that sale land in the revenue report and in the round count while you watch. A sale that is already counted by the time the salesperson switches screens was written once. A sale that needs a moment, or a refresh, or the phrase "it will be there in the morning", was written twice, and the second write is the close-out work you were trying to stop doing.
The same scrutiny applies to the word "all-in". Some vendors price the tee sheet, the POS, the booking widget and the reporting module separately. At a private club a couple of those might genuinely be optional. At a public course none of them are, so a headline price that excludes half the operation is not a price.
A Saturday and a July, with the arithmetic showing
Back to the illustrative course and its four estimated inputs: 30,000 rounds, $810,000 in green fees and carts, $1,270,000 total, 210 operating days.
Take a genuinely full Saturday in July at 220 rounds. That is within capacity and not comfortably so: a nine-minute interval sheet running seven to five holds 67 tee times, or 268 player slots, and 220 rounds fills 82% of them. Weekend rates run above the annual blend, because the $27.00 blended figure includes twilight, senior, junior and midweek play, so put green fees and carts at $34 a round. That is $7,480. Add $780 through the pro shop and $420 on the range. The grill and the beverage cart take $1,660 between them. The day totals $10,340, which is $47.00 a round.
Now the check that most worked examples skip. That Saturday is 1.54 times the 143-round average operating day. If every day looked like it, the course would play 46,200 rounds a year against the 30,000 it actually plays. So the peak day is a peak, which is the whole point of it, and any article that quietly treats a peak day as typical has stopped describing one course.
The month follows from the same estimated inputs. July at 15% of annual play is about 4,500 rounds and $198,000 of revenue, which is $44.00 a round. That sits where it should, between the $42.33 annual blend and the $47.00 peak Saturday. Inside the month, weekends run around 205 rounds a day and weekdays around 120, and 31 days of that comes to about 4,500.
The council packet for that month contains three lines the golf system produces on its own: 4,500 rounds against last July, $198,000 of revenue split by line, and $44.00 revenue per round with the rate mix behind it. The fourth line, expenses against appropriation, comes from the finance department. Two sources, not five.
Every number in this section is illustrative. What is not illustrative is the discipline. A daily figure and an annual figure describing the same facility have to reconcile, and so does the month sitting between them. Where they do not, the figure you can check least is usually the one that is wrong.
Red flags when you are evaluating
The demo is about member billing. If the salesperson spends the first twenty minutes on family plans and event chargebacks, the product was built for a private club and your operation is an accommodation inside it.
The rate structure lives outside the tee sheet. If changing a twilight price means opening a second screen, or worse a second product, the pricing will drift out of date every time the weather does something interesting.
Reporting ends in an export to a spreadsheet. Ask for a round count by day and by rate type against the same period last year, generated live in the demo. If the answer involves rebuilding it in Excel, you are buying a data store rather than a reporting system.
Onboarding assumes a permanent team. A certification path that takes two weeks is designed for staff who will be there next season. Ask how long it takes to get a new starter from nothing to checking in groups unsupervised, then halve your confidence in the answer.
Multi-course means multiple logins. If your authority runs two or three courses, ask to see one report spanning all of them, with per-course and combined figures, produced from a single sign-in. Some platforms sold as multi-course are single-course instances with a shared logo.
What we do not know
The revenue profile in this article comes from NGF facility averages, and an average of a wide distribution is a weak description of any individual course. A municipal course in a twelve-month climate and one with a 210-day season are not the same business, and neither is well described by a single national figure. Use the profile to sanity check your own numbers, not to replace them.
There is no published measurement of how many hours public course staff spend reconciling disconnected systems. The four-hour figure above is a placeholder and is labeled as one. Any vendor quoting you a specific industry average for it, including us, should be asked where it was measured and on how many courses.
The fairness research on golf pricing is more than twenty years old and describes US golfers. The 2007 familiarity finding suggests attitudes move, but nobody has repeated the 2003 study in the current market, so the honest position is that we know players objected then and we are inferring about now.
There are no before-and-after figures in this article, from us or from anybody else, because none exist for public course software that survive a source check. What can be described instead is what the software does, which is testable in a demo in about ten minutes, and that is the standard we would rather be held to.
Start with one measurement rather than a purchase. Take last July, pull the round count and the revenue by line from whatever systems you have, and work out revenue per round. Then do the same for one Saturday inside that month. If the two do not reconcile, the gap between them is where your revenue reporting is broken, and you will have learned more about your operation than any vendor demo will tell you.