Golf club management software should be chosen by the person who is accountable for how the club runs, which at almost every club is the general manager. IT belongs in the process with a defined scope: security review, integration architecture, vendor stability, data migration. What an IT evaluation cannot settle is whether a system fits the way this particular club actually operates. Fit is the thing clubs report going wrong, and fit is an operational judgement.
That last claim is not a matter of taste. It is the clearest finding in recent research that asks club managers directly about the software they run.
Why do clubs actually change software?
Research commissioned in July 2024 by the Golf Club Managers Association, together with The Golf Club Secretary, the Scottish Golf Club Managers Association, the UK Golf Federation and the Club Management Association of Ireland, was published in February 2025. It was conducted by the survey firm Players 1st and it covers 134 club managers across the UK and Ireland. Two of its headline findings land directly on the question of who should own the decision. Around 66% of those managers were considering changing software provider, and close to half reported that their existing software no longer fully met their requirements.
Then the reason. In the same survey, the most common driver for switching was that the product did not meet the requirement, at 48%. Cost was the least common driver of all, at 10%.
Read that pairing slowly, because it inverts the way most club software gets bought. Procurement processes are built to control price and risk. The research says price is almost never why a club leaves a system. What ends a software relationship is the product failing to do the job, and the job is the club's operation.
Three caveats belong in the same breath. The survey firm is a paid commercial partner of the association, and the questionnaire was designed in consultation with a software vendor who hosts the report, so the independent leg is not fully arm's length. At 134 responses the true proportions sit several points either side of every figure above. And it describes clubs in the UK and Ireland, not North America, though nothing in the mechanism it describes is nationally specific.
Even with all three, the direction is hard to argue with. Cost is a finance question. Security, integration and vendor viability are IT questions. Whether the product meets the requirement is an operational question, and it is the one that decides whether the club is back in the market in three years.
What do members already expect from a club's software?
The National Golf Foundation published app-usage research in "Golf App Usage On The Rise" on 1 July 2021. It found that 78% of Core golfers, meaning those who play eight or more rounds a year, had at least one golf-specific app. The same NGF research puts that at 56% in 2018 and 37% in 2011, and has Core golfers averaging 3.5 apps each.
Two honest qualifications. Those are 2021 figures, so they describe where member habits had already arrived five years ago rather than where they are now. And Core golfers are not all golfers: they are the frequent players, which happens to make them the segment most likely to hold a membership.
The point for a software evaluation is what those habits do to the baseline. A member who books restaurant tables, flights and tee times elsewhere on a phone arrives at your member portal with expectations formed by companies that spend more on interface design than your club spends on everything. A technical scorecard records that a member portal exists and that it authenticates properly. It has no field for whether booking a Saturday four-ball on a phone at 6:40 in the morning is pleasant, and pleasant is the whole of the member's experience of your software.
What IT Optimizes For vs. What GMs Need
To be fair to IT departments: they have legitimate concerns. Security matters. Integration complexity matters. Vendor stability matters. A system that gets breached or goes down during peak season is a genuine disaster, and a club that treats those risks casually will eventually pay for it.
The problem is that IT departments evaluate software the way they evaluate server racks and network switches. Technical specs. Compliance checklists. Vendor financial health. Those are valid criteria for infrastructure. They are the wrong criteria, on their own, for member-facing operational software.
GMs evaluate differently. They ask:
- Can my front desk staff learn this in one shift?
- Can a member book a tee time in under 30 seconds on a phone?
- Does this handle the way we actually run tournaments on Saturdays, rather than the way tournaments run in the demo?
- Can my food and beverage team split a check eight ways at a member dinner and refund one line of it afterwards?
- Can I see, right now, how many rounds we have booked this month and what our revenue per round looks like, without raising a support ticket?
None of those appear on an IT procurement scorecard. All of them determine whether the investment delivers anything.
There is a sharper example of a criterion an infrastructure scorecard has no field for. Some vendors offer discounted or free software in exchange for tee time inventory sold through an online booking channel. The NGCOA published a 62-page guide on the practice in January 2020, Beware of Barter: The Ins and Outs of Trading Your Tee Times, written by an outside contributor. It works through price elasticity and rate integrity: what happens to a rate structure when a third party is discounting your inventory, and how hard it is to recover a rate once the market has learned that a cheaper one exists. The NGCOA's own conclusion is that success stories involving barter are exceptions rather than the rule.
Two things bound how far that guide reaches, and a GM should know both before quoting it. It was written for daily-fee and public courses trading inventory to online tee-time agents, so a private club with a waiting list is looking at a different calculation entirely. And it names no vendors, which means nobody, including us, can honestly cite it as evidence against any particular company's pricing model.
What it does establish is the shape of the judgement. A procurement scorecard reads a barter arrangement as a licence cost of zero, which is the best score available. An operator reads the same arrangement as a question about who controls the rate card in a soft season. Both are looking at the same contract. Only one of them is looking at the club.
The Fragmentation Problem IT Can't See
Most clubs do not run one system. The same February 2025 research found that about 64% of the 134 clubs surveyed use several software suppliers rather than a single provider, and the report frames that as a deliberate best-of-breed choice rather than as a failure. That framing is worth keeping, because it is inconvenient for anyone selling consolidation, including us.
Inconvenient, and still incomplete. A best-of-breed stack is chosen module by module, and the seams between the modules are chosen by nobody.
IT departments see those seams and think "integration challenge". They evaluate whether System A can push data to System B through an API, whether the vendors support standard protocols, how difficult it is to make everything talk. That work is real and someone has to do it.
The GM sees something different. They see the staff member who logs into four systems to answer one member question about a charge. They see the member who receives three versions of the same email because three lists do not sync. They see the month-end close where the tee sheet, the point of sale and the accounting package each report a different number and somebody has to decide which one to believe.
Here is the honest limit of what can be said about that. No research I can point to measures the cost of fragmentation at golf clubs. Nobody publishes an average, and any vendor who quotes you one should be asked for the sample size and the publication date before you write it down. What the GCMA research supports is narrower and enough: clubs are leaving systems because the product does not meet the requirement, and the requirement lives in exactly these seams.
So measure your own. For one week, have whoever closes the day write down how long the reconciliation took and what did not match. That number is not published anywhere and it does not need to be. It is yours, it is specific to your club, and it belongs in every vendor conversation you have this year.
Three Questions Every GM Should Ask Before IT Takes Over
If your IT department is leading a software evaluation right now, ask these before the process locks.
1. Who is going to use this system every day? If the answer is the front desk, the restaurant team, the pro shop and the GM, then those people need to evaluate it. Not watch a demo. Log in, book a tee time, take a payment, refund a payment, run a report. IT can assess security and compliance in parallel. Usability testing has to be done by the people who will live in the system.
2. What does the member experience actually feel like? The National Golf Foundation research above tells you what members bring with them. The member portal, the booking flow, the payment experience and the club's outbound communication all have to be judged through a member's eyes, on a member's phone, at the times members actually book. An IT evaluation confirms the portal exists. A GM has to confirm it is worth using.
3. How much staff time goes into making systems agree? Not an estimate. The measured figure from the week you just spent counting. If the evaluation contains no specific plan for reducing that number, the GM should push back, because that time is the clearest operational cost the club is currently paying and it appears on no invoice.
When IT Should Lead vs. When GMs Should Lead
None of this argues that IT should have no role. That would be irresponsible. IT should absolutely own:
- Data security, access control and regulatory compliance
- Integration architecture and API quality
- Vendor financial stability and support infrastructure
- Data migration planning and execution
What IT should not be is the decision-maker on which system the club buys. It should be a stakeholder with a defined scope and a veto on its own subjects. The GM should own the final decision, because the GM owns the operational outcome.
Put it this way. You would not ask the IT department to set the restaurant menu, or to design the member event calendar. The software is not infrastructure in the sense that a switch is infrastructure. It is the operating environment for every member interaction and every staff workflow in the club. The person who runs that environment should choose the tools.
What does a GM-led evaluation actually look like?
It looks like a script, written before the first demo, and applied identically to every vendor.
Take three real days out of your own calendar: a busy Saturday morning, a competition day, and the last day of a month. Write down what actually happens on each, in order. Then require every vendor to let your staff perform those days in their system, with your data if possible, while somebody times each step and notes every point where a member would notice something clumsy.
Score the script, not the presentation. Sales engineers are good at demos, which is what they are for. A scripted test measures the product instead, and it measures it in your operation rather than in an idealised one.
Give the same script to IT, with different columns. Where does member data sit, who can reach it, what happens when the integration fails at four o'clock on a Saturday, what does a full export cost and how long does it take. Those answers matter and they should be gathered with the same rigour. They just do not decide the purchase.
Then let adoption be the metric you care about. A technically superior system that staff quietly work around is worth less than a plainer one everybody actually operates, because the value of club software is entirely in the workflows it removes. Adoption is also the metric nobody puts on a scorecard, which is why the person who will watch it happen should be the person who signs.
What this evidence does not establish
Two things, and it is better to say them than to be caught leaving them out.
The GCMA research establishes why clubs leave software. It does not compare outcomes at clubs where a GM led the evaluation against clubs where IT did. Nobody has published that comparison, in golf or outside it, and this article does not pretend otherwise. The argument here runs from what fails, not from a measured trial of who chooses better.
And the NGF app figures describe golfer behaviour in 2021 among frequent players. They establish that digital expectation is long-standing, not that any particular portal will meet it. Treat them as a floor for what members already do elsewhere.
The Bottom Line on Who Should Buy
Give IT a defined role: security, integration, vendor vetting, migration. Then put the GM in the driver's seat, and make the final call on the evidence of a scripted operational test rather than on a scorecard total.
The reasoning is simple enough to take to a board. Clubs change software because the product does not fit the operation, far more often than because it costs too much. Only the people who run the operation can assess fit before the contract is signed. So the evaluation has to be run by them, on real workflows, with IT covering the risks that are genuinely IT's to cover.
Apply the same test to us. Ask for a working login rather than a demo, run your three real days through it, and time each step: check in a four-ball, split a member dinner eight ways, refund one line of it, then pull the round count and revenue per round for the month yourself. Links Meridian runs the tee sheet, the point of sale, member records and accounting as one system on one database, which means the reconciliation step you have been timing all week does not exist to be timed. That is an architecture claim and you should treat it as one: make us show it in your workflow, not on a slide.
Run the same script against every vendor on your list. A vendor who would rather present than hand you the keys has already told you which part of the product they trust.