Brutally assessing the idea
Start with the thing that should worry you most. In the time you have been thinking about this, Arccos has shipped a beta called AI Strategy, built with Ryder Cup vice-captain Edoardo Molinari, trained on a claimed 1.3 billion recorded shots. Their own description of it: personalised club selection and optimal targets for every shot, derived from your measured dispersion, overlaid on course layout and hazards, adjusted for wind, elevation, temperature and daily pin positions, with draggable targets so you can test alternatives and compare expected score against your baseline.
That is your product description, written by someone else, already in market. Separately, DECADE — Scott Fawcett's course-management system — sells an Elite membership at $325/year that includes up to four custom yardage books a month. So the "personalised strategy guide" is not an unoccupied space; it is a space occupied by two companies with distribution, data and credibility you do not have.
This does not kill the idea. It changes what the idea has to be. What follows assumes you are looking for a wedge, not a category.
Why customers would want it
- Golf's most valuable resource is a caddie, and almost nobody has one. A good caddie is worth around a stroke a round to a decent player, costs £60–100 plus a tip, and is unavailable at 95% of courses. There is a genuine, large, unserved job here.
- Amateurs demonstrably play the wrong strategy. They aim at flags, take too little club, short-side themselves, and hit driver when driver is wrong. The gap between "how they play" and "how they should play" is real and measurable.
- Unfamiliar courses are genuinely hard. Local knowledge is the one advantage money can normally buy. A guide that compresses ten rounds of learning into one page has obvious appeal.
- Golfers already pay for lower-value information. Yardage books, green-reading books, rangefinders, GPS watches, shot trackers. The willingness to buy "information that might help" is established.
Why they might not pay
- They cannot tell good advice from plausible advice. Golf outcomes are so noisy that one round tells you nothing. A beautifully-written wrong answer and a beautifully-written right answer are indistinguishable to the buyer. This is bad for retention even when your product is excellent.
- For most golfers, optimal strategy collapses to about five rules. Aim at the middle of the green. Take more club. Never short-side. Stop hitting driver when the fairway narrows inside your dispersion. Lay up to a full number. Eighteen holes of restating those rules reads as padding, and the customer notices by hole six.
- Strategy is not the constraint they believe they have. Amateurs think they have a swing problem. They spend on lessons, clubs and launch monitors. "Course management" sells poorly to people who have not yet accepted that they hit it sideways.
- The advice arrives at the wrong moment. Pre-round preparation competes with a bacon roll and the practice putting green. On-course delivery competes with Rule 4.3 anxiety, phone battery, and playing partners.
- One-off purchase, seasonal market. A guide for a course you play once has no natural recurrence. In the UK the buying season is roughly March to September.
What they use today
| Alternative | What it does | Where it leaves a gap |
|---|---|---|
| Arccos Caddie | Sensor-based shot tracking plus AI Strategy: personal dispersion, per-shot targets, conditions, pin positions. | Needs hardware plus a subscription, and needs your own rounds before it is any good. Weak on a course you have never played and will never play again. |
| Shot Scope | Tracking, mapped courses, performance stats. Cheaper, no subscription on some tiers. | Stronger as an analytics product than a prescriptive one. |
| DECADE | A taught strategy system plus custom yardage books. Strong following among college and elite amateur golf. | Sells a discipline you must learn and apply. Books are a fulfilment perk, not the core product. |
| StrackaLine | Laser-scanned green books and yardage books, sold per course, widely used in amateur championship golf. | Superb data, zero personalisation. It tells you about the green, not about you. |
| GPS apps (Hole19, 18Birdies, Golfshot, SwingU) | Distances, hole maps, some "smart caddie" club suggestions. | Descriptive. They tell you the bunker is at 240; they do not tell you what to do about it. |
| A human caddie | Everything, plus reading the wind, the lie, and your mood. | £60–100 plus tip, unavailable almost everywhere, and variable. |
| A practice round | The actual answer competitive golfers use. | Costs a green fee and half a day. |
What is defensible, and what is not
Not defensible
- The language model. Everyone has the same ones.
- The prose style of the guide. Copyable in an afternoon.
- Course geometry as such. iGolf alone licenses roughly 38,000 courses with perimeter geodata for fairways, greens, tees and hazards. OpenStreetMap improves monthly.
- The expected-value framework. It is in Mark Broadie's published work and has been for over a decade.
- The UI. A competitor with a designer clones it in two weeks.
Potentially defensible
- A calibration function that converts eight self-reported answers into a credible dispersion model. Arccos solves this with hardware. If you solve it with statistics, you serve every golfer who will never buy sensors — and each round of feedback makes it better.
- Expected-strokes tables by handicap band, lie and distance for amateurs. The public tables are PGA Tour. Amateur tables are the actual engine of the product and almost nobody publishes them.
- Strategic annotation of specific courses — the things a member knows after fifty rounds that no satellite shows.
- Recommendation-outcome pairs. Not shot data; advice data. Nobody has a dataset of "we told this player X, and Y happened."
Valuable versus gimmick
It is genuinely valuable if it changes what the golfer does on the four to six holes per round where the right answer is not obvious, and is right often enough that they notice over a season. That is a modest, honest claim: roughly half a stroke to a stroke a round. It is also a defensible one.
It is a gimmick if it produces eighteen confident paragraphs of plausible prose. Confident prose about geometry you have not verified is the failure mode, and it is the easy thing to build. An LLM will happily tell a golfer to carry a bunker that is not there.
The six ways this dies
- Course data accuracy at scale. Section 12 demonstrates this with numbers: a 12-yard error in one bunker position flips the recommendation from driver to 3-wood. You cannot hand-map 40,000 courses, and the licensable data is not everywhere precise enough for carry-the-bunker advice.
- Unfalsifiable value. Nobody can perceive whether the advice worked. Churn after guide one.
- The advice is obvious. Eighteen holes of "middle of the green" at £25.
- Arccos and Shot Scope bundle it free with hardware their customers have already bought.
- Garbage inputs. Golfers overstate driver distance by 15–25 yards. Personalisation built on inflated numbers is worse than no personalisation — it recommends carries they cannot make.
- No recurrence. One-off purchase, seasonal, in a market where the same customer already has four golf subscriptions.
Scores
Composite 4.0 / 10 as described. Roughly 6.5 / 10 for the narrowed version in section 2.
The honest summary
This is a good product idea and a questionable business idea in its current shape. The product will work; people will like it. The business fails on scalability and recurrence unless you deliberately shrink the target and design the revenue model around occasions rather than subscriptions. Do not build for 40,000 courses. Build for 40.
The first customer is the trip golfer
Pick: golfers playing a destination or bucket-list course they have never played, as part of a trip that already cost them four figures. In the UK and Ireland this means links golf — the Ayrshire coast, East Lothian, County Down and Sligo, Cornwall and Norfolk, the Open rota and the courses beside it.
Why this one
- The course list is bounded and therefore mappable. Roughly 100 courses cover most of the demand. You can hand-map 100 courses to survey quality. You cannot hand-map 40,000. This single fact converts an unscalable business into a tractable one.
- The purchase is emotionally attached to a large existing spend. £25 against a £2,500 trip is a rounding error. Against a £40 Saturday medal it is not.
- They have no shot history there, so Arccos's advantage evaporates. Arccos is strongest on courses you play repeatedly. On a once-in-a-lifetime round, everyone starts cold — and a cold start is exactly where an estimated profile is not a compromise but the only option.
- There is a clear substitute with a clear price. "A caddie's brain for £25" lands because they are actively deciding whether to pay £80 for a caddie, and often cannot get one.
- Links golf punishes bad strategy more than any other kind. Blind tee shots, pot bunkers that genuinely cost a shot, wind, and run-out that makes carry numbers decisive. The advice has more room to be non-obvious.
- Search intent already exists. "How to play the Old Course", "Royal County Down hole by hole" — high-intent, low-competition queries with a natural free/paid split (section 14).
- They are reachable without paid media. Tour operators, society organisers and a handful of forums and YouTube channels aggregate essentially all of them.
Why not the others
| Segment | Verdict |
|---|---|
| Scratch & low handicappers | Already have a strategy, often a good one, and will find your errors instantly. Valuable as testers, not as your first market. Recruit six of them free. |
| Mid handicappers (10–18) | Largest group, worst economics. Play the same course weekly, so the guide is consumed once. Lowest willingness to pay. This is the segment everyone builds for and it is why golf apps monetise badly. |
| High handicappers (20+) | The advice is nearly constant across courses — "hit the club that leaves you a full wedge, aim at the middle" — so the personalisation adds almost nothing and the product cannot justify its price. |
| Competitive amateurs | Your second segment, not your first. The best long-term subscribers: they play unfamiliar courses repeatedly in county events and away matches, they take strategy seriously, and they buy annually. But they will scrutinise your data harder than anyone, so sell to them once the geometry is provably good. |
| Tournament preparation | A high-value use case inside the competitive-amateur segment, but check Model Local Rule G-11 before selling into elite events (section 17). |
| Golf societies | Attractive as a bulk channel — one organiser buys twelve guides — but society golfers are the least strategy-motivated golfers alive. Good distribution, wrong motivation. |
| Coaches | A real B2B2C channel later. Coaches want a tool that makes them look rigorous with students. Wrong first customer: long sales cycle, they want white-labelling and analytics you will not have. |
| Tour operators | The single best distribution partner for your chosen segment. They are not the customer; they are the shelf. |
The positioning sentence
"You have waited fifteen years and paid £300 to play this course once. Play it like someone who knows it." Everything in the product follows from that sentence.
The smallest thing that proves someone will pay
The MVP is not software. It is you, a spreadsheet, a simulation script and a PDF, selling a guide before you build anything to generate it. The point of the first version is to discover whether a golfer will hand over money and then say the guide was useful — and the only way to learn that quickly is to make the guides by hand.
Must have
- One landing page with a real price and a real checkout (Stripe Payment Link is enough — no account system).
- Three courses, hand-mapped to survey quality. Pick the three with the most demand from your waitlist.
- A 10-field profile form (Typeform or a plain HTML form into a sheet).
- A deterministic strategy engine — roughly 300 lines of Python — producing club, aim line, expected approach, best miss and expected score for every candidate on every hole.
- A print-quality PDF, one page per hole, plus a one-page round plan.
- Explicit confidence labelling on every number, with visible "unknown" where you do not know.
- A post-round email with five questions.
Should have later
- Accounts and a saved profile.
- Mobile web guide with the printed version as a fallback.
- Self-serve course requests with a waitlist-and-vote mechanic.
- Wind adjustment against a forecast on the morning of play.
- Pin-position variants (front / middle / back).
- Automated geometry ingestion from licensed geodata.
- The feedback loop of section 16, doing real work on the profile.
Do not build yet
- An on-course live mode. Rule 4.3 exposure, battery, connectivity, and it competes with products that already do it well.
- Computer vision for hazard detection from imagery.
- An app in either store.
- Green contours and putting advice. StrackaLine own this and did it with laser scanning.
- Coach dashboards, club licensing, white-label.
- Shot tracking or hardware of any kind.
- A general course database. Three courses, done properly.
- Elevation modelling beyond flagging significantly uphill or downhill approaches.
- Any machine learning. Everything in section 6 is arithmetic.
The ruthless cut
Everything a golfer sees in the first version can be produced by a human in 90 minutes per guide. If it takes longer than that, the product is too complicated, not the process. Time the first ten and watch the number fall.
Eight questions, not fifty
Your seventeen-field list is a specification for a product nobody completes. Most of those fields are derivable from three or four others, and asking for them signals thoroughness at the cost of conversion. Ask for what changes a decision, derive the rest, and show the golfer your derivations so they can correct them.
| Field | Why it is needed | How it is supplied | Value | Auto later? |
|---|---|---|---|---|
| Handicap index | The single most informative number. Sets priors for dispersion width, mis-hit rate, recovery ability, putting and the whole expected-strokes table. Everything else adjusts around it. | One field. Validate against the national body's lookup where available. | Very high | Yes — WHS lookup |
| Driver carry | Decides every tee-shot candidate. Carry, not total: hazards are carried, not rolled over. | Ask for "your normal good drive, not your best". Offer a launch-monitor number if they have one. Cross-check against handicap and flag disagreement. | Very high | Yes — tracker import |
| 7-iron carry | Anchors the whole bag. With driver carry and 7-iron carry you can interpolate a full gapping ladder to within a few yards. Asking for fourteen club distances gets you fourteen guesses. | One field. | Very high | Yes |
| Shape and severity | Sets the lateral bias of the distribution — which side of the fairway to start the ball on. This is the difference between "aim at the left rough" and "aim at the right bunker". | Two taps: draw / straight / fade, then slight / strong. Optionally a yardage of curve. | Very high | Partially |
| One-way or two-way miss | Changes the shape of the model entirely. A player who only misses right can be aimed at trouble on the left. A two-way miss must be aimed at the middle and the engine should recommend less club. | "When you miss badly, is it always the same way?" Yes / no. | High | Yes |
| What is actually in the bag | There is no point recommending a 3-wood to a player who carries a 5-wood and two hybrids. Also reveals the gap yardages where the advice must be "this is an awkward number for you". | A checklist of fourteen slots, pre-filled from handicap. | High | Yes |
| Risk appetite | Shifts the selection criterion from lowest mean score toward lowest variance or toward birdie probability. Matters most in matchplay and on par 5s. | One three-position slider: protect my score / balanced / chase birdies. | Medium | Inferable from behaviour |
| Relative short game | Decides lay-up targets and whether to leave a shot short-side. A player who is poor from sand but good chipping should be steered past bunkers into rough; the reverse for someone who hates a bare lie. | Rank three items: bunkers, chipping, putting — best to worst. Fifteen seconds. | Medium | Yes |
Derived, not asked
- Driver total = carry + roll, where roll is estimated from launch characteristics implied by handicap and from the course's turf conditions. On a links in summer the roll assumption is the difference between a good guide and a dangerous one; make it visible and let the golfer override it.
- Every other club distance — interpolated between driver and 7-iron with a standard gapping curve, then shown as a table the golfer can edit. Editing a pre-filled table converts far better than filling an empty one.
- Lateral dispersion — from handicap, shape severity and the one/two-way answer. Section 7.
- Ability from rough and sand, long-iron strength, confidence, lay-up preference — all priors from handicap band, then corrected by feedback.
The input problem you must solve on day one
Golfers overstate driver distance. If a golfer tells you 265 and actually carries 240, your guide will recommend carrying a bunker they cannot carry, and the product is not merely unhelpful — it is harmful. Three defences, all cheap:
- Ask for carry and phrase it as "your normal good one", never "how far do you hit it".
- Run a plausibility check against handicap and challenge outliers in the interface: "A 14 handicap carrying 280 is unusual — is that a launch monitor number or a career best?" People correct themselves when asked politely.
- Shade recommendations conservative when confidence is low. If you are not sure of the number, do not recommend the shot that requires the number to be right.
The long-run answer is the calibration function in section 15: after a few thousand feedback rounds you know, statistically, that a 14-handicap who claims 265 carries 243. That correction is proprietary and compounding, and it is arguably the most valuable thing you can build.
The course model, and the much smaller model you actually need
Two observations before the schema.
First: provenance is a field, not a footnote. Every geometric value carries where it came from, how it was obtained, when, and its uncertainty. Confidence scores are then computed rather than asserted — which is the only way to honour the no-hallucination requirement. A number with no provenance is not stored.
Second: you do not need full polygons to give strategy. A full GIS model of a hole is beautiful and slow to produce. What the engine actually consumes is a decision profile: the corridor of safe ground at each distance band, and the carry and finish distance of each hazard from each tee. That is roughly 25 numbers per hole, obtainable by a person with an aerial image and a measuring tool in ten minutes. Polygons are a phase-3 refinement, not a phase-1 requirement.
Core objects
// COURSE { "course_id": "gb-sco-westlinks", "name": "West Links", "country": "GB-SCT", "turf": "links", // links | parkland | heathland | desert — drives roll model "prevailing_wind": { "bearing_deg": 245, "source": "club_confirmed" }, "elevation_source": "ea_lidar_dtm_1m_ogl", "data_confidence": { "geometry": 0.91, "yardage": 1.0, "elevation": 0.86 }, "last_verified": "2026-05-02", "verified_by": "on_site_survey" } // TEE — one row per tee set per hole { "hole_id": "gb-sco-westlinks-h07", "tee_set": "white", "yardage": { "value": 402, "unit": "yd", "provenance": "scorecard", "confidence": "verified" }, "par": 4, "stroke_index": 5, "tee_point": { "lat": 56.0000, "lon": -2.0000, "provenance": "gnss_survey", "sigma_m": 0.4 } }
The hole, expressed as a decision profile
{
"hole_id": "gb-sco-westlinks-h07",
"centreline": [[0,0],[6,180],[2,300],[0,402]], // [lateral, downrange] yards from tee
"play_corridor": [ // safe width by distance band
{ "from":175, "to":300, "left":-18, "right":18, "lie":"fairway",
"provenance":"traced_naip_2024", "sigma_yd":2.5 },
{ "from":300, "to":315, "left":-18, "right":18, "lie":"rough", "sigma_yd":3.0 }
],
"hazards": [
{ "id":"h7-fb1", "type":"bunker", "side":"left",
"carry_yd": { "value":245, "provenance":"laser_on_site", "sigma_yd":1.5 },
"finish_yd":{ "value":270, "provenance":"laser_on_site", "sigma_yd":1.5 },
"lateral": { "near":-8, "far":-25 },
"severity": "steep_face_lateral_only", // affects the ES penalty used
"in_play_for": ["carry_230_275"] },
{ "id":"h7-ob", "type":"out_of_bounds", "side":"right",
"lateral":46, "from":170, "to":430,
"provenance":"osm_boundary + on_site_check", "sigma_yd":4.0 }
],
"layup_zones": [
{ "label":"short of the bunker", "from":195, "to":238, "width":34, "leaves_yd":[164,207] }
],
"green": {
"front_yd":387, "centre_yd":402, "back_yd":417,
"width_yd":22, "long_axis_deg":4,
"surrounds": [
{ "type":"bunker", "position":"front_right", "from":378, "to":393, "lateral":[8,24] },
{ "type":"bunker", "position":"left", "from":394, "to":412, "lateral":[-24,-13] },
{ "type":"run_off", "position":"back", "from":421, "severity":"downslope_away" }
],
"safe_miss": "short_left",
"pin_sheets": ["front","centre","back_right"],
"provenance":"traced_orthophoto", "sigma_yd":2.0
},
"elevation": { "tee_to_landing_m":-2.1, "landing_to_green_m":+4.4,
"provenance":"ea_lidar_dtm_1m", "confidence":"calculated" },
"local_knowledge": [
{ "text":"Ground runs hard left-to-right from 260 onward in dry conditions.",
"provenance":"club_professional_interview", "confidence":"inferred" }
],
"unknown": ["green_contour", "rough_height_seasonal"]
}
The four provenance states, and what each permits
| State | Means | The engine may | The guide says |
|---|---|---|---|
| Verified | Measured on site, supplied by the club, or read off an official scorecard. | Recommend shots that depend on the number being right within ±2 yards. | States it plainly: "The bunker carries at 245." |
| Calculated | Derived arithmetically from verified inputs — elevation deltas from open LIDAR, remaining distances, plays-like adjustments. | Use freely, propagating the input uncertainty. | States it, with the derivation available. |
| Inferred | Traced from imagery, taken from OSM, or reasoned from a hole description. | Use, but widen sigma and re-test whether the recommendation survives the error (section 6, layer 7). | "Bunker estimated at 243–252 from imagery. Treat as 240." |
| Unknown | Not obtained. | Not use it at all. No defaults, no plausible substitutes. | Says so: "We do not have green contours for this course." An honest gap costs you nothing; an invented number costs you the customer. |
Confidence, defined properly
Do not invent a percentage. Define the two numbers this way:
Course data confidence = the share of the decision-relevant fields for that hole that are Verified or Calculated, weighted by how much each field moves the recommendation. A hole where the bunker carry is verified but the green surround is inferred scores higher than the reverse, because the bunker carry is doing more work.
Strategy confidence = stability of the recommendation under perturbation. Re-run the engine with every geometric input resampled from its own uncertainty, say 200 times. If the same club wins 95% of the time, confidence is High. If it wins 60% of the time, it is Medium and the guide should present both options as genuinely close. If it flips, say so. Section 12 shows a case where a 12-yard error changes the answer — that case must never be sold as High confidence.
Where the intelligence actually lives
The engine is arithmetic. There is no model in it, no learning, and no language model anywhere near a decision. The language model writes the sentence at the end, and is forbidden from introducing a number. Structuring it this way is not merely tidy — it is what makes the no-hallucination requirement enforceable, because you can assert it as a validation rule rather than a hope.
The contract that stops hallucination
Layer 8 is the only generative step, and it runs under three hard rules enforced in code, not in the prompt:
- Every numeral in the output must appear in the input payload. Extract all numbers from the generated text and assert set membership. On failure, regenerate; on second failure, fall back to a template.
- Every hazard named must exist in the payload's hazard list. Named-entity check against a whitelist.
- Nothing marked Unknown may be mentioned as if known. If green contour is unknown, the word "slope" is not available to the generator for that hole.
Templates get you 80% of the quality at zero risk. The language model's job is to make hole seven read differently from hole eleven while saying exactly the same verified things — and that is worth having, but it is worth having on a leash.
Where a language model genuinely helps
- Upstream, in ingestion. Reading a scorecard photo, parsing a club's hole-description page into structured candidates, normalising course names. Every extraction is proposed, then human-verified before it enters the database.
- Downstream, in conversation. "Why did you tell me 3-wood there?" answered from the stored candidate table. The answer is retrieval, not reasoning.
- Never in the middle. The moment an LLM chooses the club, you have a product that cannot be audited and cannot be trusted, and you will not be able to tell it apart from a good one until customers stop renewing.
A shot cone you can build from four inputs
Keep the first version deliberately crude. A model that is directionally right and honestly uncertain beats a sophisticated one fitted to data you do not have.
The model
Each shot is two independent draws plus a mis-hit mixture.
// Longitudinal (how far) carry ~ Normal(mu_carry, sigma_long) sigma_long = mu_carry × k_long(handicap) roll = f(club, turf, firmness, landing_angle) // Lateral (how far offline) — bias is the shape, sigma is the control offline ~ Normal(bias, sigma_lat) sigma_lat = mu_carry × k_lat(handicap, club) bias = shape_direction × shape_severity_yards // Mis-hit mixture — the tail that actually causes big numbers with probability p_mishit(handicap, club): carry ×= (1 - loss) loss ~ 8–14% sigma_lat ×= 1.9–2.2
The mis-hit mixture matters more than anything else in the model. A pure Gaussian understates how often an amateur produces the shot that ends the hole, and it is precisely those shots the strategy is meant to avoid. Two components is enough; do not reach for a skew-normal until feedback data justifies it.
Starting parameters
| Handicap band | k_long (driver) | k_lat (driver) | Implied cone at 250y carry | p_mishit | k_lat (irons) |
|---|---|---|---|---|---|
| Tour reference | 3.0% | 6.0% | ±30 yd | 6% | 4.0% |
| Scratch to 3 | 3.5% | 6.8% | ±34 yd | 8% | 4.5% |
| 4 to 8 | 3.8% | 7.4% | ±37 yd | 10% | 5.0% |
| 9 to 14 | 4.8% | 9.2% | ±46 yd | 15% | 6.2% |
| 15 to 20 | 6.0% | 11.5% | ±58 yd | 20% | 8.0% |
| 21 plus | 7.5% | 14.0% | ±70 yd | 27% | 10.0% |
From distribution to decision
You never need a closed-form overlay of a probability density against a polygon. Sample it. Forty thousand samples against a hole geometry runs in well under a second in NumPy, which means you can afford to evaluate every club at every aim line exhaustively and still generate a full eighteen-hole guide in seconds. Analytic elegance buys you nothing here; brute force buys you correctness and the ability to change the geometry model later without touching the maths.
One refinement worth making early
Aim and shape interact. A player who fades the ball and aims left does not get a symmetric cone about the aim line — the ball starts left and curves back, so the left side of the distribution is tighter than the right. Modelling start line and curvature separately (rather than a single lateral draw) costs five lines of code and materially changes the aim recommendation for a strong shaper. Do it in version two.
Eight ways to know where the bunker is
This section decides the business. Everything else is tractable.
| Approach | Cost | Accuracy | Scalability | Legal position | Difficulty |
|---|---|---|---|---|---|
| Licensed golf geodata iGolf and similar: roughly 38,000 courses, 20,000+ with detailed mapping; perimeter geodata for fairways, greens, tees, hazards and trees. | Per-transaction or unlimited licence; expect four to five figures a year plus negotiation. | Good, uneven | Excellent — the only option that gets you global coverage on day one. | Clean, if the licence permits derived analytical output and offline PDF generation. Ask that question first, in writing. | Low — a contract and an importer. |
| On-site survey Laser rangefinder plus RTK GNSS rover, walked. | £1–2k of kit once; 3–5 hours per course. | Best available | Terrible — and that is the point. Deliberately unscalable, deliberately excellent. | Immaculate. It is your data. No licence, no share-alike, no terms to breach. | Low technically, high logistically. Needs club permission. |
| Course-supplied data Architect's drawings, irrigation as-builts, the club's own course plan. | Free to cheap. A phone call and some goodwill. | Excellent when it exists | Poor, but one call per course and a meaningful share say yes. | Best of all — explicit permission from the rights holder, and it opens a club relationship. | Low technical, medium relationship work. |
| OpenStreetMap golf=fairway, golf=green, golf=bunker, golf=tee, golf=water_hazard are established tags. | Free. | Very variable | Good where coverage exists; coverage on well-known courses is often surprisingly complete. | ODbL share-alike is the trap. A database derived from OSM may itself have to be offered under ODbL. That directly attacks any plan to treat course geometry as a moat. | Low. |
| Open public imagery USDA NAIP for the United States, roughly 60cm, public domain. | Free. | Adequate, not precise | Excellent for US courses only. | Public domain — trace and redistribute freely. The cleanest imagery option that exists. | Medium — tiles, georeferencing, a tracing tool. |
| Open LIDAR elevation Environment Agency Composite DTM/DSM at 1m for England under the Open Government Licence; USGS 3DEP for the US. | Free. | Excellent for elevation | Excellent within coverage. | Open Government Licence — attribution and you are done. | Medium. Worth it: DTM gives you real elevation profiles and bunker depressions; DSM minus DTM gives you tree heights. |
| Commercial satellite / aerial Mapbox, Esri, Airbus, Bluesky, Getmapping. | Meaningful, and rises with resolution. | Very good | Good. | Display rights are not tracing rights. Building a derived vector database usually needs a specific written permission. Get it before you trace, not after. | Medium. |
| Google Maps / Earth | — | — | — | Do not. Google Maps Platform terms restrict creating content from Google Maps Content, restrict caching beyond narrow per-API allowances, and generally forbid using Google content alongside a non-Google map. Tracing their imagery into your own database sits against all three. | — |
| Computer vision Segmentation of bunkers, greens and fairways from orthophotos. | Weeks of your time, then ongoing correction. | Unproven at the precision you need | Excellent in principle. | Inherits whatever the imagery licence permits — CV does not launder a licence. | High, and the last thing you should build. |
What to use for the MVP
Hand-map three to twenty courses yourself, from course-supplied plans plus an on-site walk with a laser, with elevation from open LIDAR. Accept that it takes half a day per course. This gives you: the best data anyone has on those courses, zero licensing exposure, an asset you own outright, and a relationship with each club.
In parallel, and before you write any importer, get a written answer from a licensed geodata provider on one question: may we derive and distribute analytical output and printed guides from your geometry? That answer determines whether phase 4 exists at all, and it costs an email to find out.
Use OSM only as a cross-check on your own measurements during MVP — never as a source of record — until you have taken advice on whether share-alike reaches your derived database.
The decision-profile shortcut, again
You are not building a map. For each hole you need: the tee point; hazard carry and finish distances from each tee; the lateral extent of safe ground in 10-yard bands from 180 to 300; front, middle and back of green; green width; and what is immediately around the green. That is twenty-five numbers, and a person with a laser rangefinder can collect most of them from the tee and the fairway in fifteen minutes per hole. Build the capture tool, not the GIS.
Adding a course
| Step | What happens | Phase 1 | Phase 3 |
|---|---|---|---|
| 1 | Course requested. Demand recorded against the course before any work is done. | A form and a waitlist counter. | Automatic — a threshold of requests triggers the job. |
| 2 | Scorecard obtained: yardages per tee, par, stroke index. | Manual. Photograph or download; type it in. | Vision extraction proposing values, human confirms. |
| 3 | Tee and green points located. | Manual from imagery, confirmed on site. | Licensed geodata, or automated with review. |
| 4 | Hole geometry: centreline and corridor widths by band. | Traced by hand on a permitted orthophoto. | Semi-automatic from licensed polygons. |
| 5 | Hazards identified and measured. The step that decides whether the product is any good. | Always human. On site with a laser where possible. | Still human review. Automate detection, never automate acceptance. |
| 6 | Elevation profile. | Open LIDAR where available; otherwise mark Unknown. | Same, plus club-supplied where offered. |
| 7 | Validation. Do the summed geometry distances reconcile with the scorecard yardage per tee, within tolerance? | Automatic — this check catches most tracing errors and costs ten lines of code. | Automatic, blocking. |
| 8 | Strategic distances computed: carry and finish for every hazard from every tee, lay-up zones, corridor widths. | Automatic. | Automatic. |
| 9 | Local knowledge captured: prevailing wind, run-out, blind shots, the things only a member knows. | A fifteen-minute call with the club professional. Do this — it is the highest value per minute in the whole pipeline, and it is the part no competitor can scrape. | Same. Never automate. |
| 10 | Human QA: generate a guide for three synthetic players and read all eighteen holes. Does any recommendation look wrong to a good golfer? | You, every time. | A trained reviewer, with the engine flagging low-confidence holes for priority. |
| 11 | Publish with a confidence score, and a public non-personalised page for SEO. | Manual. | Automatic. |
Course selection is capital allocation
At half a day per course, each mapped course is a real investment. At £25 a guide you need roughly twenty sales per course before it has paid for the mapping at any sensible valuation of your time. So never map a course before demand exists. Run the waitlist first, map second. This one rule is the difference between a business and an expensive hobby.
Two players, one hole, two different games
The hole is the one specified in section 12: a 402-yard par 4, fairway from 175 to 300 yards and 36 yards wide, a left fairway bunker carrying at 245 and finishing at 270, trees 30 yards right and 34 yards left of the centreline, and a boundary fence 46 yards right. Every number below is the output of the Monte Carlo engine described in section 6, run at 60,000 samples per candidate — not an illustration written to make a point.
Player A — 5 handicap
Driver 275 total, 255 carry. Draw, roughly 9 yards of curve. Good long irons. Aggressive.
Player B — 18 handicap
Driver 215 total, 195 carry. Slice, roughly 14 yards of curve. Weak long irons, good wedges. Conservative.
| Player | Club | Best aim | E[score] | Approach left | Fairway | Bunker | Trees | OB |
|---|---|---|---|---|---|---|---|---|
| A — 5 hcp | Driver | 1.0° right | 4.282 | 122–138 yd | 55.9% | 8.6% | 11.1% | 1.3% |
| 3-wood | 2.0° right | 4.312 | 152–165 yd | 67.9% | 10.5% | 4.5% | 0.6% | |
| 4-iron | 1.0° right | 4.366 | 185–196 yd | 85.1% | 0.0% | 1.6% | 0.2% | |
| B — 18 hcp | Driver | 6.0° left | 5.153 | 183–205 yd | 47.8% | 0.2% | 20.3% | 3.6% |
| 3-wood | 4.0° left | 5.209 | 206–225 yd | 52.5% | 0.0% | 11.1% | 2.0% | |
| Hybrid | 4.0° left | 5.384 | 223–239 yd | 30.6% | 0.0% | 6.5% | 1.0% | |
| 7-iron (lay-up) | 4.0° left | 5.740 | 252–266 yd | 0.0% | 0.0% | 2.6% | 0.3% |
What the engine actually found, and why it is not what you would guess
Both players should hit driver. That is not the conventional answer for either. Player A's driver puts nine per cent of tee shots in the fairway bunker and eleven per cent in the trees, and it is still the best club — because 3-wood leaves him 160 yards instead of 132, and on this green the difference between a 9-iron and a 6-iron is worth more than the bunker costs him. Player B hits 20% into trees and 3.6% out of bounds with driver, and it is still his best club — because laying up leaves him 216 yards, from which an 18-handicapper's expected score is worse than from the trees at 195.
But the margins are completely different. For Player A, driver beats 3-wood by 0.030 strokes. That is noise. The honest output is "these are the same; pick the one you will commit to", and a product that presents a 0.03-stroke edge as a firm recommendation is lying about its own precision. For Player B, driver beats the 7-iron lay-up by 0.59 strokes — an enormous, unambiguous, act-on-it margin. The advice a conservative 18-handicapper most needs is to stop laying up.
The real decision is aim, not club. This is the finding that justifies the whole product, and it is the one no GPS app gives you:
| Aim | A: E[score] | A: fairway | A: OB | Aim | B: E[score] | B: fairway | B: OB |
|---|---|---|---|---|---|---|---|
| 6° left | 4.635 | 12.0% | 0.2% | 10° left | 5.263 | 33.1% | 1.9% |
| 4° left | 4.505 | 23.6% | 0.3% | 8° left | 5.187 | 41.8% | 2.5% |
| 2° left | 4.380 | 38.4% | 0.5% | 6° left | 5.155 | 47.4% | 3.6% |
| Centre | 4.297 | 51.9% | 0.9% | 4° left | 5.168 | 50.2% | 5.1% |
| 2° right | 4.288 | 57.6% | 1.8% | 2° left | 5.256 | 48.4% | 7.7% |
| 4° right | 4.385 | 53.1% | 4.1% | Centre | 5.398 | 43.4% | 11.2% |
| 6° right | 4.630 | 40.8% | 9.5% | 2° right | 5.635 | 35.7% | 17.2% |
| 8° right | 5.037 | 25.8% | 19.8% | 4° right | 5.927 | 27.5% | 24.7% |
Player B aimed down the middle — which is what he does, and what every app implicitly encourages by drawing a line at the fairway centre — hits it out of bounds 11.2% of the time and scores 5.40. Aimed six degrees left, at what looks like the left rough, he goes out of bounds 3.6% of the time and scores 5.16. A quarter of a stroke, on one hole, from a single instruction that costs nothing to follow. Repeat that on the six holes a round where it applies and you have the entire value proposition of the business, expressed in a number you can defend.
The pattern to sell
For the good player, the engine resolves genuinely close calls and stops the occasional disaster. For the weaker player, the engine mostly does two things: it aims him away from the thing that ruins his card, and it stops him laying up to distances he cannot play from. Those are different products wearing the same clothes, and the copy for each should say so.
What the golfer actually holds
The primary artefact is printed: an A5 booklet, one hole per page, that fits a back pocket. Not an app. Three reasons, in order of importance.
- It is unambiguously legal under Rule 4.3. Written notes prepared before the round are permitted. A phone doing live calculations invites questions in competition, and your competitive-amateur segment cares about that a great deal. Print removes the issue entirely.
- It survives contact with golf. No battery, no signal, no gloves-off fumbling, no playing partner tutting.
- It feels like something. A £25 PDF is a receipt. A £25 booklet with your name on the cover is a souvenir of a round you waited fifteen years to play — and souvenirs get photographed, which is free distribution.
Ship it as a print-ready PDF plus a simple mobile web version for pre-round reading on the plane. Build the web version second.
The hole page
Ruthless constraint: one page, readable in eight seconds standing on the tee, in wind. That budget buys about forty words and one diagram. Everything else goes in a notes band at the bottom for people who want it.
| Zone | Contents | Why it earns the space |
|---|---|---|
| Header | Hole number, par, yardage from the tee being played, stroke index. | Orientation. One line. |
| The instruction | One line, largest type on the page: "3-wood. Start it at the left edge of the right bunker." | This is what they read on the tee. If they read nothing else, this must be enough. |
| Diagram | Schematic of the hole with their dispersion cone drawn on it at their carry distance, hazards labelled with carry numbers, and the recommended start line marked against a visible aiming feature. | The cone is the whole argument, made visually in one second. It is also the single most shareable image the product produces. |
| Expect | "Leaves you 152–165 yards." A range, never a point. | Sets up the approach and lets them plan the next club before they walk. |
| Approach | Club, aim relative to the flag, and the number they should be playing to. Front / middle / back pin variants where the green demands it. | Where most strokes are actually lost. |
| Miss | Two items only: best miss and the miss that ruins the hole. "Long left is fine. Short right is a bogey minimum." | Amateurs do not need to be told to hit it well. They need to know which bad shot to prefer. |
| Ignore | The hazard that is not in play for them. "The cross bunkers at 290 are irrelevant today." | Unexpectedly the most-loved line in guides of this kind. Removing fear is as valuable as adding information, and it is uniquely personalised — it is only true because of who they are. |
| Why | One sentence, small type. "Driver brings the bunker at 245 into the middle of your pattern and only saves you a club." | Builds trust and teaches. Small enough to skip. |
| Confidence | A small mark, not a percentage on the page. Full provenance lives online. | Honesty without clutter. A number like "94%" on every page becomes wallpaper. |
Deliberately absent
No strokes-gained figures. No expected-score decimals. No probability tables. No general course description. No history of the course. No three options where there is one right answer. The engine computes all of it; the page shows almost none of it. A caddie does not read you the distribution; he hands you a club and tells you where to aim.
The other two pages
- Round plan, front page. The four holes where the decision is unusual, the two where they will be tempted into a mistake, the target score by stroke index, and one sentence on how the wind changes things. If the customer reads only this page, the product still worked.
- Scorecard back page. With a two-tap outcome grid per hole, which is how you collect the feedback in section 16 without asking anyone to do anything.
The seventh at West Links, played twice
A hypothetical hole, fully specified, run end to end through the engine of section 6. Every figure below is simulation output. Nothing here is estimated by eye.
Geometry Verified
| Feature | Position | Notes |
|---|---|---|
| Hole | 402 yd, par 4, SI 5 | White tees. Flat; no elevation adjustment. |
| Fairway | 175–300 yd, 36 yd wide | Centred on the tee line. Rough to 315, scrub beyond. |
| Fairway bunker (left) | carry 245, finish 270 | 8–25 yd left of centre. Steep face: lateral escape only. |
| Trees | 30 yd right, 34 yd left | Recovery only; no advancement to the green. |
| Boundary fence (right) | 46 yd right, from 170 yd | Out of bounds. Stroke and distance. |
| Green | front 387, centre 402, back 417 | 30 yd deep, 22 yd wide. Bunker front-right and left. Runs away behind. |
Tee shot: Player A, 5 handicap
Candidate set: three clubs × eleven aim lines, 60,000 samples each.
RECOMMENDED Driver, start line 1° right of the centre of the fairway Expected score 4.282 (3-wood 4.312 · 4-iron 4.366) Margin 0.030 strokes over 3-wood → TIE. Present both. Leaves 122–138 yd (interquartile), median 132 Outcomes fairway 55.9% · rough 23.2% · bunker 8.6% · trees 11.1% · OB 1.3% Driver of the decision is AIM, not club: the same driver aimed 8° right decision scores 5.037 — three quarters of a stroke worse.
What the guide says: "Driver or 3-wood — they are worth the same to you here, so take the one you will commit to. Start it a yard or two right of the centre and let the draw work. The left bunker carries at 245 and finishes at 270; your pattern only clips its right edge. What you must not do is start it at the right half of the fairway — that is where the fence lives."
What it does not say: that driver is definitively correct. It is not, by any margin the engine can defend, and claiming otherwise would be the beginning of a product that cannot be trusted.
Tee shot: Player B, 18 handicap
RECOMMENDED Driver, start line 6° left — at the left edge of the fairway Expected score 5.153 (3-wood 5.209 · hybrid 5.384 · 7-iron 5.740) Margin 0.59 strokes over the lay-up → ACT ON THIS. Leaves 183–205 yd, median 195 Outcomes fairway 47.8% · rough 28.2% · trees 20.3% · OB 3.6% Cost of aiming Centre: 5.398, OB 11.2%. Six degrees left: 5.155, OB 3.6%. down the middle 0.24 strokes, free.
What the guide says: "Driver, and aim at the left edge of the fairway — further left than feels right. Your slice will bring it back. Aimed down the middle you put it over the fence once every nine attempts on this hole; aimed at the left edge, once every twenty-eight. Do not lay up: from 216 yards you score worse than you do from the trees at 195."
Approach: Player A from 132 yards, back-right pin
Ball at the recommended position. Green centre is 132 away, the back-right pin 141, the front edge 117. His ladder: 8-iron 152, 9-iron 140, PW 128, GW 116.
RECOMMENDED 9-iron, start line 7 yd right of the green's centre
(the draw brings it back to 4 right — three yards left of the flag)
Expected score 3.077 from here
Outcomes green 62.6% · fairway/rough short-and-left 29.1% · long 6.4%
front-right bunker 0.7% · left bunker 0.8%
Median proximity 8 yd
Worst tested 8-iron aimed 3° left: 3.837. +0.76 strokes for one wrong
option club and a lazy aim.
Same green, centre pin (132 yd): PW, start 2 yd right. E = 2.855, green 86.3%
Same green, front-left (122 yd): GW 3.020 vs PW 3.022 — identical scores,
different risks. GW finds the green 48% and the
front apron 44%; PW finds the green 84% but sits
11 yd away. Offer the choice; do not fake a winner.
What the guide says for the back-right pin: "9-iron, starting at the right edge of the green. Your draw brings it to the middle-right and takes the front-right bunker out of play — you will find it less than once in a hundred. The flag is back-right; do not chase it. Long is the one place you cannot be, because the ground behind runs away from the green. Short and left is fine and leaves a straightforward chip. The mistake that costs you a shot here is taking 8-iron."
The finding that matters more than any of the above
The engine was re-run with the fairway bunker moved, to simulate the error you would make tracing it from a 60cm satellite image rather than measuring it on site.
| Assumed bunker position | Driver | 3-wood | Margin | Recommendation |
|---|---|---|---|---|
| carry 245, finish 270 — as mapped | 4.289 | 4.312 | −0.023 | Driver (barely) |
| carry 233, finish 258 — 12 yd nearer | 4.266 | 4.341 | −0.075 | Driver |
| carry 257, finish 282 — 12 yd further | 4.326 | 4.272 | +0.054 | 3-wood — the answer flips |
Read this twice
A twelve-yard error in a single bunker position — well inside what you would accept from imagery tracing, and roughly the error in a hazard digitised from a 60cm orthophoto by someone who has never stood on the hole — reverses the recommendation. Not degrades it. Reverses it.
Three consequences, and they should shape the whole company:
- Course data precision is the binding constraint on this business, not AI quality. Every hour spent on better prose is an hour not spent on the thing that decides whether the prose is true.
- The robustness test in layer 7 is not a nice-to-have. It is the only mechanism that stops you shipping a confident wrong answer. Run it on every hole and let it downgrade the confidence label automatically.
- When the margin is under 0.05 strokes, say so. A product that admits two options are equivalent is more credible, not less — and it is the single clearest signal to a good golfer that there is real machinery underneath rather than an LLM with a thesaurus.
Sell occasions, not subscriptions
The instinct is a subscription, because subscriptions are what good businesses have. Resist it for the first year. Your chosen customer buys a trip, not a season, and asking them for a recurring commitment before you have earned one converts badly and churns worse. Charge for the occasion; earn the subscription later.
| Model | Price | Verdict |
|---|---|---|
| Single course guide | £24 | The entry product. Anchored against a £70 caddie fee and a £15 yardage book. Low enough to buy on impulse against a trip that already cost thousands; high enough that it is not a toy. Marginal cost once the course is mapped is pennies. |
| Trip bundle | £55 / 3 · £85 / 5 | The main revenue line. Your customer is playing four courses in five days. Bundling raises order value 2.5× and is the natural unit of their actual purchase. Lead with this on the landing page and let the single guide be the fallback. |
| Tournament preparation | £45 | Guide plus a practice-round plan plus a revised version after they report back from the practice round. Genuinely worth more; a small market; excellent margin; a good test of whether the competitive amateur segment is real. |
| Season pass | £89 / year | Introduce at roughly 40 mapped courses, not before. Unlimited guides, profile that improves with feedback, and re-issued guides when conditions change. This is your eventual recurring line and it is aimed at the competitive amateur, not the trip golfer. |
| Coach seat | £349 / year | Up to 30 player profiles, guides for any mapped course, a comparison view. Real, but a slow sale and it demands features you will not have for eighteen months. Take inbound; do not chase it. |
| Tour operator wholesale | £9 / guide | The best distribution in the list. An operator selling a £2,800 Scotland package adds personalised guides as an included premium and pays you £9 a head. Zero acquisition cost, volume in blocks of 8–16, and it reaches your exact customer at the moment they are thinking about the trip. Margin is thinner; the volume and the zero CAC more than repay it. |
| Golf club licence | — | Skip for now. Long sales cycle, committee decisions, seasonal budgets, and they will want their logo on it. Revisit when you can show a club that members bought 200 guides for their course. |
| Pro shop resale | £24, split 50/50 | Worth a trial at two or three destination clubs. The shop already sells yardage books; a card on the counter with a QR code costs you nothing and tests whether the point of sale can be the first tee. |
The architecture, in one line
Trip bundle as the headline SKU, single guide as the entry point, tour-operator wholesale for volume, season pass introduced in year two for retention. That combination gives you an easy first purchase at a price nobody has to think about, gross margin above 90% on marginal units, a channel that does your acquisition for you, and a credible path to recurrence — without betting the first year on a subscription your customer has no reason to want yet.
The number that decides everything
Guides sold per mapped course. At £24 and half a day of mapping, twenty sales per course is roughly break-even on your own time and anything above fifty is a real business. Track it per course from the first week. If the median mapped course sells four guides, you do not have a pricing problem or a marketing problem — you have the wrong courses, and possibly the wrong business.
Three channels, and a dozen you should ignore
1. A public page for every mapped course — the compounding one
Each course you map gets a free, genuinely excellent public page: hole by hole, the strategy for a generic 12-handicapper, the real carry numbers, the hazards that matter. Then the offer: "This is the guide for an average golfer. Get the one for you."
Why this is the strongest asset you can build:
- The search intent is specific, high-value and low-competition. Nobody is seriously competing for "Royal Dornoch hole by hole strategy", and the people searching it are three weeks from a trip.
- It compounds. Every mapped course adds a permanent acquisition asset that costs nothing to maintain.
- It is the honest version of a paywall — the free page is useful on its own, which is what makes people trust the paid one.
- It gives you a reason to talk to the club, which gets you course-supplied data, which improves the product.
2. Tour operators and society organisers — the fast one
There are perhaps forty operators who control most of the UK and Ireland inbound golf trip market, and each one books hundreds of golfers a year onto exactly the courses you want to map. One signed operator is worth more than six months of social media. Lead with the offer that costs them nothing: personalised guides included free for one trip, in exchange for feedback and a testimonial. Society organisers are the same play at smaller scale and shorter sales cycle.
3. The free shot-cone tool — the viral one
Three inputs — handicap, driver carry, shape — and it draws your actual dispersion pattern over a generic hole, with the line: "Your driver is 74 yards wide. The fairway is 36." That image is confronting, personal, instantly shareable, and it teaches the concept the product is built on. Golfers will post it themselves. It also collects the three profile fields you need, so every share is a half-completed signup.
Make the hole generic and invented — do not use a real, recognisable course for this, and do not reproduce anyone's yardage-book artwork.
Worth doing, second tier
- YouTube creators who film at destination courses. Send a guide for the course before they film. The video writes itself: "I got an AI caddie for Ballybunion." Mid-size channels convert far better than large ones here, and will do it for free.
- Genuine forum contribution on GolfWRX and the golf subreddits — posting the actual simulation output for an interesting hole, not a link. The content in section 12 is the template: it is interesting on its own terms and the product is implied rather than pitched.
- County and regional amateur golf — a free guide for every competitor in one championship, in exchange for feedback. This is how you enter the competitive-amateur segment when you are ready for it.
Ignore for now
TikTok and Instagram paid acquisition: the audience skews away from your customer and the creative demands a full-time habit you should not have yet. Golf clubs as a direct channel: too slow. Anything requiring an app install before purchase.
What is actually proprietary when everyone has the same model
Assume a competent competitor with the same language models, the same public research and a better designer. What do you have that they cannot have next month?
| Candidate | Real? | Assessment |
|---|---|---|
| Course geometry database | No | Licensable from multiple vendors, improving monthly in OpenStreetMap, and already owned at scale by Arccos and Shot Scope. Worse: if you build yours from OSM, share-alike may oblige you to give it away. Treat geometry as a cost of doing business, never as the moat. |
| Recommendation engine | No | It is Monte Carlo over an expected-strokes table. A competent engineer rebuilds it in a fortnight — I built a working one in an hour for section 12. |
| The prose | No | Prompt-level. Copyable by looking at one guide. |
| Amateur expected-strokes tables | Yes | The public benchmarks are PGA Tour. Accurate strokes-to-hole-out by distance, lie and handicap band for amateurs is the actual engine, and it is only obtainable from outcome data at volume. This is the first thing your feedback loop should be built to produce. |
| Self-report calibration function | Yes, and it is the best one | The mapping from what a golfer tells you to what is true. Arccos does not need it because they have sensors — which means they will never build it, and it is precisely what lets you serve every golfer who will never buy sensors. Every feedback round improves it for every future customer. This is the one genuinely compounding asset in the business. |
| Recommendation–outcome dataset | Yes | Shot trackers know what happened. Only you know what was advised and what then happened. That pairing lets you measure which advice actually works, retire the advice that does not, and make a marketing claim nobody can match because nobody else can measure it. |
| Local knowledge annotations | Partly | The club professional's fifteen minutes about run-out, blind lines and the wind. Not on any satellite, not in any database, and each one is a small permanent advantage on that course. Copyable one course at a time, at the same cost you paid — which is a real if unglamorous barrier. |
| User history and switching cost | Weak | A profile that improves with use creates some stickiness, but a golfer can re-enter eight fields anywhere. |
The three-to-five year build
Two taps a hole
Every product like this dies on feedback design. Ask for too much and you get nothing; ask for too little and you learn nothing. The binding constraint is that the golfer is holding a pencil, on a course, playing golf.
What to capture, in order of value per unit of effort
| Capture | Effort | What it teaches |
|---|---|---|
| Tee shot outcome, as a 3×3 grid printed on the hole page: short/right length × left/centre/right. Two pencil marks. | ~3 seconds | Directional bias and dispersion width directly. After three rounds you know whether their stated "slight fade" is actually 25 yards of slice. Highest value in the whole loop. |
| Did you follow the recommendation? One tick. | ~1 second | Without this, nothing else is interpretable — and it is the field that creates the recommendation–outcome dataset of section 15. |
| Approach club and result — club plus on/short/long/left/right. | ~4 seconds | True iron distances, and whether they are systematically short (they are). |
| Score per hole | Already written | Validates the expected-strokes tables at the aggregate level. |
| Actual measured distances from a rangefinder | Optional | Gold-standard calibration from the minority who will do it. Ask, do not require. |
How it comes back
Two routes, both cheap. The scorecard back page carries the grids; the golfer photographs it after the round and you extract it with vision plus human review. Or a 90-second web flow emailed two hours after the tee time: eighteen holes, two taps each, thumb-sized targets. Build the second; support the first, because a meaningful share of your customers will fill in paper and never open the email.
What the system learns
GUIDE SAID 3-wood, start line 2° right → expect 152–165 yd GOLFER REPORTED 3-wood, 218 yd, left rough → 8-iron, green followed: yes UPDATES 3-wood carry prior 232 ±8 → posterior 226 ±6 (3rd observation) lateral bias prior −7 (draw) → posterior −11 (draws more than stated) 8-iron distance no prior → new observation: reached from 152 POPULATION claimed 3-wood vs observed, handicap band 4–8: n=1,847, mean bias −5.8 yd recommendation adherence on par 4 tee shots: 71% mean score on holes followed vs not: −0.19 strokes (n=22,410, not yet significant by course)
The Bayesian framing matters. The self-reported profile is a prior, not a fact. Each observation moves it. After three rounds the model of the big clubs is materially better than what the golfer told you; after ten it approaches what a shot tracker would give you — without hardware. Show the golfer the updates, because watching "we now think your 3-wood carries 226, not 232" is the single most convincing demonstration that something real is happening, and it is the thing that turns a one-off buyer into a season-pass renewal.
Design rule
Never ask the golfer whether the recommendation was good. They cannot know, one round is not evidence, and the answer is dominated by whether they struck it well. Ask only what happened. You do the inference.
Where you need a lawyer, and how to need one less
Not legal advice. This is a map of where the risk sits and which design choices reduce it, so that a solicitor's hours are spent on the two or three questions that matter rather than on the whole idea.
| Area | The concern | Lower-risk approach |
|---|---|---|
| Google Maps and Google satellite imagery | Google Maps Platform terms restrict creating content from Google Maps Content, permit caching only within narrow per-API allowances (place IDs indefinitely, latitude and longitude typically 30 days), and generally forbid using their content alongside a non-Google map. Tracing their imagery into a database you then sell from runs against all three at once. | Do not use it at all, for anything, at any stage. This is the cheapest decision in the document: it removes an entire category of risk for free, and there are adequate alternatives. |
| Commercial imagery (Mapbox, Esri, Airbus, Bluesky, Getmapping) | A licence to display imagery is not a licence to derive a vector database from it and redistribute the result. Terms vary by provider and, for aggregated basemaps, by individual contributor. | Ask for written permission for derived vector extraction before tracing a single hole, and name the use case exactly: "we will digitise hazard positions and sell printed guides derived from them." Providers answer this question routinely. Get it in an email. |
| OpenStreetMap | ODbL share-alike. Whether your course database counts as a derivative database (which you may have to offer under ODbL) or a produced work (which you may not) is a genuine legal question, not a matter of opinion, and it goes directly to whether you own your core asset. | Either take advice and design the boundary deliberately, or keep OSM out of the database of record entirely and use it only to cross-check your own measurements. For a business whose whole premise is proprietary geometry, the second is the safer default. |
| Open public data | Minimal. USDA NAIP imagery is public domain; the Environment Agency LIDAR composites are Open Government Licence. | Use freely with attribution. These are the cleanest sources available and should carry as much of the load as they can. |
| Scorecards | Individual yardages, pars and stroke indices are facts and facts are generally not protected — but a scorecard's layout and artwork are, and in the UK and EU a systematic extraction of a substantial part of a compiled database can engage database right independently of copyright. | Record the facts, never reproduce the artwork, and prefer obtaining the data from the club directly. Do not bulk-extract another product's course database. |
| Course websites and hole descriptions | Website terms of service commonly prohibit automated access. The descriptive text itself is copyright. | Read pages manually or with permission; never reproduce descriptive text; use it as a prompt for questions to ask the club, not as content. A fifteen-minute call gets you better information and explicit permission. |
| Course names, logos, likeness | Names and crests are trade marks. Some clubs are aggressive about commercial use of their name, particularly the famous ones your chosen segment cares about. | Use names descriptively and factually ("a guide for playing at …"), never a crest, never imply endorsement, and carry a clear disclaimer. Better still: get the club's blessing — several will give it, and one that does becomes a reference. |
| Existing yardage and green books | StrackaLine's and others' books are original works. Their layout, symbols and contour renderings are protected. | Never trace or transcribe from a commercial book. Your visual language must be independently designed — and yours should look different anyway, because it is showing something theirs does not. |
| Third-party APIs | Redistribution and derived-output rights, offline caching, and whether printed output counts as a permitted use. | Three questions before you sign anything: may we store it, may we derive analytical output from it, may that output be distributed offline as a PDF? |
| Rules of golf | Not a legal risk but a product one. Written notes prepared in advance are permitted under Rule 4.3 — but Model Local Rule G-11, adopted at the highest levels of competition, restricts players to Committee-approved yardage books and limits green diagrams to minimal detail such as major slopes and tiers. Handwritten notes are limited to what the player or caddie personally observed. | Keep green detail minimal by design — which you want anyway, since you are not laser-scanning greens. If you sell into elite amateur events, say plainly which of your materials are designed to be G-11 compatible and let the Committee decide. Getting this right is a trust signal to exactly the segment that cares. |
| Liability and claims | "Lower your handicap" is a performance claim. A golfer following your advice into a hazard because your bunker distance was wrong is a complaint you will eventually receive. | Terms that describe the product as informational; visible confidence labelling (which is also the honest thing); no guaranteed-improvement claims until you can substantiate them from your own outcome data. |
Three questions worth an hour of a solicitor's time, before you build
- Does building our course database from OSM oblige us to license that database under ODbL?
- Does digitising hazard positions from licensed aerial imagery, and selling guides derived from them, require a specific derived-works permission from that provider — and what wording should we ask for?
- Where is the line between recording factual yardages from published scorecards and infringing UK database right?
Everything else can wait. Those three determine whether your core asset is yours.
Boring on purpose
One architectural decision dominates all the others: a guide is a static artefact, generated once and stored. No live inference, no on-course compute, no real-time anything. That single choice removes scaling, latency, cost and reliability from your list of problems for at least two years.
| Layer | Choice | Why |
|---|---|---|
| Frontend | Next.js on Vercel | Static per-course SEO pages and a small authenticated area from one codebase. The SEO pages are the growth engine of section 14, so server rendering is not optional. |
| Engine | Python + NumPy, FastAPI, on Fly.io or Render | The simulation is vectorised array maths and belongs in Python. It is a job, not a service: a full eighteen-hole guide is seconds of compute. Keep it as one repository with a command-line entry point so you can run guides by hand from day one. |
| Database | Postgres via Supabase, with PostGIS | Auth, storage, database and row-level security in one product. Add PostGIS when you move from decision profiles to real polygons; you will not need it in month one, and enabling it later is one statement. |
| Job queue | A Postgres table | You will generate tens of guides a day, not thousands a second. A table with a status column and a worker loop is correct here. Do not introduce a broker. |
| Headless Chromium via Playwright, rendering the same HTML templates as the web guide | One template, two outputs. CSS paged media gets you A5, crop marks and page breaks. Typst is the alternative if typographic control becomes the bottleneck. | |
| Diagrams | Server-rendered SVG, generated by the engine | No mapping provider, no tiles, no licence. The hole schematic in section 12 is a few hundred bytes of generated SVG — it prints perfectly, scales to any size, and has no runtime dependency at all. |
| Language model | Any frontier API, layer 8 only, behind the numeric-validation wrapper of section 6 | Keep it swappable. It is writing 60 words a hole; the model choice is a cost decision, not a product one. |
| Mapping / ingestion tool | An internal admin page: MapLibre GL over permitted imagery, drawing the decision profile | Build this in week three, not week one. Your first three courses should be captured in a spreadsheet, by you, with a laser rangefinder. |
| Payments | Stripe. Payment Links first, Checkout later | A Payment Link needs no code and no account system, which is exactly right for a pre-order. |
| Auth | Supabase Auth, magic link | Golfers will not remember a password. Defer auth entirely until people are paying. |
| Resend or Postmark | Delivery of the guide, and the feedback flow. |
Running cost at MVP: comfortably under £60 a month. The expensive input is your time mapping courses, which is exactly as it should be, because that is the part that is hard to copy.
Two things not to build
No mobile app. It adds store review, two more codebases, push infrastructure and an install step between a stranger and a purchase, in exchange for nothing your customer asked for.
No live on-course mode until at least phase 4. It is the feature that sounds most impressive in a pitch and delivers least: it competes head-on with Arccos and Hole19 where they are strongest, raises Rule 4.3 questions with the segment that cares most about them, and depends on connectivity in exactly the coastal places your customers are playing.
Thirty days, and the numbers that decide
The objective is not to build. It is to find out whether a stranger will pay £24 and then tell you the guide was good. Everything below is achievable alongside a job.
Fifteen conversations, twenty minutes each, with people who have played a destination course in the last two years — find them in forums, at your club, through a society organiser. Do not describe the product until the last five minutes. Ask instead: what did you do to prepare? Did you take a caddie? What did you get wrong on the first nine? Then put up a one-page site with the section 12 example as the demonstration, a real price, and a Stripe Payment Link for a course you have not mapped yet, clearly labelled as delivering within seven days.
- Targets
- 15 interviews. Landing page live by day 5. 200 visitors from three forum posts and one society mailing.
- Signal
- At least 6 of 15 describe a specific strategic mistake they made on an unfamiliar course. If they cannot, the problem is not felt and nothing downstream will work.
Write the engine — realistically two days, as section 12 demonstrates. Map one course properly: go there, walk it with a laser, talk to the professional. Open pre-orders at £24 with a founding price of £19 for the first fifty. Push to the forums, the society organisers and two tour operators.
- Targets
- Engine producing a full eighteen. One course mapped and QA'd. 25 pre-orders.
- Kill signal
- Under 8 pre-orders from 400 visitors. That is a 2% conversion on warm, high-intent traffic at an impulse price, and it means the willingness to pay is not there at any price you can charge.
Produce and send every guide yourself. Time each one. Then the step that matters more than the sale: get on the phone after they have played. Not a survey — a fifteen-minute call. Did you use it on the course or read it once? Which hole was most useful? Where were we wrong? Would you buy one for the next course?
- Targets
- 100% delivered within 48 hours. 10 post-round conversations. Median production time under 90 minutes by guide ten.
- Signal
- At least 7 of 10 name a specific hole where the guide changed what they did. This is the single most important number in the thirty days. If they liked it but changed nothing, you have built a pleasant artefact, not a product.
Raise to £24 and introduce the £55 trip bundle. Map a second course, chosen purely by waitlist demand. Approach three tour operators with the completed guides and real testimonials in hand. Then sit down with the numbers and make the call.
- Targets
- 15 further sales at full price. Bundle attach rate above 30%. 2 operators in conversation. 40+ waitlist requests naming specific courses.
- Decision
- Continue, narrow, or stop.
What would convince me
| Measure | Kill | Rethink | Continue |
|---|---|---|---|
| Visitor → pre-order | < 2% | 2–5% | > 6% |
| Total paid pre-orders in 30 days | < 15 | 15–34 | ≥ 35 |
| Completed 8-field profile after payment | < 70% | 70–85% | > 90% |
| Named a hole where the guide changed their play | < 40% | 40–65% | > 70% |
| Would buy again for another course | < 40% | 40–60% | > 65% |
| Bundle attach rate | < 15% | 15–29% | > 30% |
| Guides sold per mapped course | < 6 | 6–19 | ≥ 20 |
| Post-round feedback returned | < 20% | 20–40% | > 45% |
The result that should genuinely stop you
Strong sales combined with a low "changed my play" rate. That combination means you have built something people enjoy buying and do not use — which reads as success for one month and produces no second purchase, no word of mouth, and no feedback data. It is the most dangerous outcome of the four, because it is the one that feels like validation.
Five phases
- Objective
- Find out whether strangers pay, and whether the guide changes behaviour.
- Functionality
- Landing page, payment link, profile form, one mapped course, hand-produced PDFs.
- Technology
- A static page, Stripe, a Google Form, a Python script, a spreadsheet.
- Cost
- Under £300 plus your time. A laser rangefinder if you do not own one.
- People
- 100% you. Every guide, every call.
- Metric
- 35 paid pre-orders and 70% naming a hole where the guide changed their play.
- Risk
- Selling to friends and reading it as market validation. Your first fifteen buyers must be strangers.
- Objective
- Prove the guide is good, repeatedly, and learn what actually goes on the page.
- Functionality
- 8–12 mapped courses chosen by waitlist demand. Web profile form. Engine generating the candidate table. PDF templated but assembled with human judgement. Post-round feedback flow.
- Technology
- Next.js, Supabase, Python engine, Playwright PDF. Still no accounts, no app, no polygons.
- Cost
- Under £100/month plus roughly half a day per course.
- People
- You map, you QA, you call every customer. Target 90 minutes per guide falling to 30.
- Metric
- 150 guides sold. 20+ per mapped course. 45% feedback return.
- Risk
- Automating too early. The manual step is where you learn which of the eighteen pages anybody reads.
- Objective
- Take yourself out of the guide, but not out of the mapping.
- Functionality
- End-to-end self-serve: buy, profile, guide in ten minutes. Internal mapping tool. Confidence and robustness testing automated per hole. Pin-position variants. Wind adjustment on the morning of play. Public course pages live for SEO.
- Technology
- Add the admin mapping tool, PostGIS, the job queue, a forecast API.
- Cost
- £300–600/month. First contractor for mapping if volume justifies it.
- People
- Mapping and QA only. Zero human involvement in generation.
- Metric
- 30 courses. 800 guides. Guide production cost under £1. Organic search delivering 25% of sales.
- Risk
- Quality falls when you stop reading every guide. Keep a sampled manual review permanently — a fixed share of guides, read by a human, forever.
- Objective
- Recurrence, and the second segment.
- Functionality
- Season pass. Profile that visibly improves from feedback. Tournament preparation product. Tour operator portal with bulk ordering. Competitive-amateur launch through county championships.
- Technology
- Calibration model in production. First measured amateur expected-strokes tables replacing the priors.
- Cost
- £1–3k/month including mapping contractors.
- People
- A part-time mapper and a part-time support person. You on partnerships and the model.
- Metric
- 80 courses. £15k monthly revenue. Season-pass renewal above 55%. Three operator contracts.
- Risk
- Arccos or Shot Scope ship a materially better free version. Your defence is the segment they cannot serve — golfers without sensors on courses they have never played — so do not drift toward competing on their ground.
- Objective
- Break the linear relationship between courses and human effort — the constraint identified in section 1.
- Functionality
- Licensed geodata for breadth plus your own survey data for depth, with the product honestly signalling which it is using. Coach and team accounts. Measured advice-efficacy claims. Possibly club-branded editions.
- Technology
- Assisted feature extraction with human acceptance. Full geometry pipeline. The calibration and expected-strokes models as the core asset.
- Cost
- Data licensing becomes the largest line item.
- People
- A small mapping and QA function. Engineering on the models, not the pipeline.
- Metric
- 400+ courses, tiered by confidence. £75k+ monthly revenue. A published, defensible claim about how much the advice is worth.
- Risk
- Breadth dilutes quality and the brand becomes "another golf app with vague maps". Never let a low-confidence course look like a high-confidence one. The confidence label is the product's conscience — if you ever soften it to make the catalogue look bigger, the business is over.
If I were building this tomorrow
In order. Nothing here requires a line of production code until action nine, and nothing requires a company until action fifteen.
- Write the engine first. One day.Roughly 300 lines of Python: a shot-dispersion sampler, an expected-strokes table, one hard-coded hole. The version behind section 12 took about an hour. Do this before anything else, because it tells you immediately whether the recommendations are interesting or obvious — and if they are obvious, you have saved yourself a year.
- Hand-build three guides for courses you know well.Use holes you can picture. Read all fifty-four pages as a golfer. Are you surprised anywhere? If the engine never surprises you, the product has no reason to exist.
- Show those three guides to five good golfers and shut up.Do not explain. Watch which page they linger on and listen for the first thing they say. That reaction is your headline.
- Pick one course and go and measure it.Walk eighteen holes with a laser rangefinder. Note every hazard's carry and finish from two tees. You will learn more about the data problem in four hours than in four weeks of reading about mapping APIs — and you will discover how wrong the satellite numbers are.
- Send three emails.One to a licensed golf geodata provider: may we derive analytical output and distribute printed guides? One to an aerial imagery provider: may we digitise features for a commercial derived database? One to a solicitor with the three questions in section 17. All three answers arrive while you do everything else.
- Interview fifteen destination golfers.Twenty minutes each. Do not pitch. Find out what they actually did to prepare, what it cost them, and what they got wrong.
- Write the landing page copy before you design anything.If you cannot make the offer compelling in 150 words, the product is not clear yet. The section 12 hole diagram with two dispersion cones on it is your strongest visual asset — lead with it.
- Build the free shot-cone tool.Three inputs, one image: "your driver is 74 yards wide, the fairway is 36." Half a day of work. It is your best acquisition asset and it collects the three profile fields you need.
- Put up a one-page site with a real price and a Stripe Payment Link.£19 founding price. Deliver within seven days, stated plainly. No accounts, no app, no database.
- Post the section 12 analysis to the golf forums — the analysis, not the product."I simulated 60,000 tee shots on one hole for a 5 and an 18 handicap and the 18 should aim at the left rough." That post is interesting on its own terms, which is why it will work. The link goes at the bottom.
- Email ten tour operators and five society organisers.Offer free guides for one trip in exchange for feedback and a testimonial. One yes is worth more than a month of anything else on this list.
- Take the first twenty-five orders and produce every guide by hand.Time each one. The number will fall from three hours to forty minutes, and where it stops tells you exactly what to automate first.
- Call every single customer after they play.Fifteen minutes. One question above all others: which hole did this change? Write down the exact words they use — that is your marketing copy, and it is the only honest source of it.
- Instrument the feedback loop before you have anyone to use it on.Store the full candidate table for every guide, and the recommendation alongside the outcome. This data is the only moat in the business and it cannot be reconstructed later. Building it in week one costs an afternoon; retrofitting it in year two costs the moat.
- At day thirty, hold yourself to the table in section 19.Be honest about the "changed my play" number specifically. Strong sales with weak behaviour change is the outcome that looks like success and is not.
The one thing to hold on to
Every impressive-sounding capability in the original brief — computer vision, automated ingestion, elevation modelling, on-course mode, green contours — is a way of avoiding the two questions that actually decide this: will a stranger pay £24, and is the bunker really at 245. Answer those two with a spreadsheet, a laser rangefinder and three hundred lines of Python, and the rest is engineering. Answer them in the wrong order and the engineering is worthless.