Mike W. shot 71, his best round of the year, after about three months of using GOATY. He reported 36 on the front nine and 35 on the back, finishing with an 82-yard wedge to 14 feet and a birdie putt on the final hole.
The round is the headline. The more useful story is how he combined practice, saved swing analyses, and conversations about what was actually happening on the course. We reviewed his records and his own updates to see what changed—and what the evidence can reasonably tell us.
The result, at a glance
71 — reported best round of the year
5 greens in regulation and 5 of 7 fairways — on the front nine
881 scoreable drill reps across 47 sessions — in the June–August practice record
60.5 → 72.5 — a consistent-version comparison of earlier and later recorded GOAT scores
The problem: good back nines, costly front nines
Mike described a frustrating pattern over roughly four weeks: the back nine could be good or even exceptional, but damage on the front nine had already hurt the round. In an earlier community discussion, he said his head was full of swing thoughts early on. Later, there were fewer thoughts and more good shots.
He did not describe a finished swing. He said he still had issues that would take time to improve. That makes this a useful example of AI golf coaching results during a swing change: progress on the course can happen while the golfer is still working through inconsistency.
What he changed: a driver setup experiment
Mike began discussing his rounds with GOATY chat. He described good and bad shots, connected them to his current practice, and took a swing thought into the next round.
His clearest example was the driver. After a poor driving day, setup emerged from the conversation as something to test. His plan was to return to his previous driver setup and stop pursuing distance.
In his earlier update about using GOATY chat, Mike reported that the following day brought driving strokes gained from −4.0 to +0.9, a difference of 4.9 strokes. He also reported 89% fairways and a round seven strokes better. These are his reported Arccos and course results; they are not an independent download of his Arccos account.
That driver experiment was a separate example from the 71. It shows his process: describe a specific problem, choose something concrete to test, and check the next result. It does not establish that the same setup change caused the later 71.
Golf swing improvement over time: what the saved data shows
We also reviewed Mike’s saved face-on swing analyses. The goal was to look at his progress across multiple practice dates.
We kept the camera view and scoring version the same. For each date, we took the median of that day’s recorded analyses. We then compared the median of the first three available dates in June with the median of the last three in August. Each date gets equal weight, so a day with several uploads does not dominate the comparison.
Earlier and later recorded swing scores
| Measure | Earlier dates: June | Later dates: August | Change |
|---|---|---|---|
| GOAT score | 60.5 | 72.5 | +12.0 points |
| Engine | 61.8 | 74.5 | +12.7 points |
| Anchor | 57.9 | 65.2 | +7.3 points |
| Whip | 60.5 | 68.9 | +8.4 points |
See the story in your own swing data
Start with a swing analysis, then use what you learn to ask a more specific coaching question.
Get Your Free Swing Analysisor analyze a swing video free
Comparison dates: June 8, 14, and 18 versus August 6, 12, and 15, 2026. All comparisons use face-on analyses and the original version 1 score columns. Deleted analyses and demo records are excluded.
These are changes in recorded analysis scores, not stroke reductions or percentages of improvement. GOAT score and its component scores describe aspects of an analyzed swing; they are not a handicap. See how GOATScore works for context.
The distinction matters here. Mike also reported capture-quality problems during his practice, and his September analyses used a different scoring version. We have not mixed the September results into the June–August comparison. Better capture can affect a measurement, and these observational records cannot tell us exactly how much of the score change came from technique rather than capture conditions.
The practice behind the round
The saved practice record contains 881 scoreable drill reps across 47 sessions from June through August: 464 reps in June, 160 in July, and 257 in August. Another 15 recorded reps were not marked scoreable and are excluded from that total.
The record shows repeated practice over several months, alongside continued play on the course.
The useful connection is that Mike had both a practice history and a way to revisit his swing data. His course conversations added another source of feedback: whether what he was working on helped him play the next round.
The 71: a front nine that finally came through
In his best-round post, Mike credited chat coaching with helping the front nine come through. He reported five greens in regulation, five of seven fairways, and a 36. He then finished the back nine in 35, including the birdie on 18.
He also said the front-nine/back-nine inconsistency had not disappeared. That is part of the story, not a reason to discard it. A best round is worth celebrating without claiming that every swing problem is solved.
This case combines a reported on-course win with a documented practice record and an improvement in comparable recorded swing scores. His account connects the numbers to a real round of golf.
How to use the same process in your own practice
- Bring a specific round pattern into chat: Describe the shots that cost you, when they happened, and what you were trying to do. A recurring driver miss is more useful to investigate than a general feeling that the swing is bad.
- Choose one change to test: Mike’s example was his own driver setup and distance intention. Your useful test may be different; copying his exact setup is not the lesson.
- Check both the next round and the swing record: Look for patterns over several sessions. Keep the camera view and scoring method consistent, and separate a better measurement from a better course result.
Start with evidence from your own swing
Mike W.’s 71 gives us a reason to celebrate. His driver experiment and practice record give us something to learn from.
If you are exploring whether AI golf coaching is worth it, this is the kind of detail to look for: a specific problem, an actual test, and results that can be traced to their source. You can also see how GOATY’s tools fit together before starting with your own swing.
Sources and measurement notes
Member-reported course results: Mike W.’s September 12 best-round post and September 11 chat-coaching update. Community pages may require a member login.
Swing and practice data: GOATY’s saved analysis and scoreable-rep records reviewed on September 13, 2026, limited to data recorded before the best-round post. The table summarizes original same-version face-on scores; it does not recompute the swing or mix scoring systems. Mike’s first name and last initial are used here.
Make your next practice a useful test
Get your swing analyzed and start building a record you can learn from.
Get Your Free Swing Analysis →or upload a swing for instant analysis