← Dev Blog / Origin Story Series

Episode 01  ·  Origin Story Series

Where It All Began

How a lifelong golfer's obsession with baseball strategy sparked an idea that became a league, a platform, and a movement.

Every idea worth building starts with a moment of frustration — or in my case, a Sunday afternoon round of golf somewhere in the Dallas–Fort Worth suburbs, walking off the 18th green with that familiar hollow feeling. I'd played well. Shot a decent number. But it didn't mean anything. I played alone, I scored alone, and I drove home alone. Golf can be like that. Beautiful and solitary in equal measure.

I'd loved baseball my whole life — not just watching it, but the strategic depth underneath it. The matchups, the lineup decisions, the chess match between manager and pitcher. I kept thinking: why can't golf feel more like that? Why can't it feel like something that matters beyond your own scorecard?

"I wanted to build something where every single hole had consequence. Where your teammates were counting on you. Where the outcome of a two-foot putt on the 14th could swing an entire season."

— Brian Hackney, Founder

The Ryder Cup Revelation

I've been watching the Ryder Cup since I was a kid. There's nothing like it in golf — the intensity, the crowd, the pressure that transforms the world's best players into nervous rookies. Watching Rory McIlroy miss a two-footer that he'd make 999 times out of 1,000 because an entire nation is on his shoulders — that's something the PGA Tour stroke-play format can never replicate.

The Ryder Cup format is match play. You don't count total strokes. You win holes, you lose holes, you halve holes. What matters is the head-to-head battle, hole by hole. And you play as a team. Your individual result feeds into something larger than yourself.

I started asking a simple question: could regular amateur golfers — weekend warriors, mid-handicappers, the guys who play every Saturday at their local muni — experience something like that? Not a tournament. Not a club championship. A league. A season. Something with standings, rivalries, and stakes that persist from week to week.

The Core Mechanic

The scoring concept came together quickly, and it borrows directly from that baseball brain of mine. In baseball, every out counts. Every at-bat moves the needle. I wanted golf to work the same way — I wanted every hole to feel like an at-bat.

The NTMGL Scoring System

Every hole is a point. Every point matters.

  • Win a hole outright on net score: 1 point for your team
  • Halve a hole (tie on net score): ½ point each
  • Lose a hole: 0 points — your opponent earns the full point
  • 18 holes = 18 points available per individual match
  • Multiple matches per team matchup — all points accumulate for the team

This was the breakthrough. In traditional match play, a hole is halved and forgotten — it produces nothing. In the NTMGL system, every halved hole still produces value. The game is played all the way to the last putt on the last green, every single time. No conceeded matches. No early clinches. Every hole matters.

Net scoring with handicaps means that the 18-handicapper isn't just there to make up the numbers — he's a legitimate weapon. The right matchup, the right tee selection, and he can carry a team. That's the baseball strategy element I'd been craving. As a captain, who do you put in the anchor position? Who plays in the tough morning slot? Who do you matchup against the opponent's best player?

Building the League

I spent a few months in late 2023 sketching out what the structure would look like. Teams of six to eight players. A round-robin schedule that gave every team equal competition. A captain for each team who manages the lineup, sets the tee assignments, and makes the strategic calls. Season-long standings. A championship match.

The name came naturally: the National Team Match Play Golf League. NTMGL. It was ambitious — I was starting in Dallas–Fort Worth, but the concept was always bigger than one city. The "National" part was aspirational from day one.

I knew right away that this couldn't run on a spreadsheet. The scoring system — with halved holes, running match scores, individual records feeding into team standings, handicap differentials updating after every round — was too complex. There were too many moving parts. If I was going to build something real, I needed to build the software to run it.

That's where my background as a software developer became the second ingredient in the recipe. Twenty-plus years in document content management, data processing, and business automation. I knew how to build things. I knew ASP.NET Core. I knew SQL Server. I knew Azure.

"Most founders hire a developer. I am the developer. That's both a blessing and a curse — as I would soon discover at 1 a.m., staring at an EF Core query that refused to translate to SQL."

— Brian Hackney, on being the sole developer

So I started building. The platform, the league, and the rulebook all at the same time — which is every bit as chaotic as it sounds, and also exactly as exhilarating.

Season 1: Proof of Concept

Spring 2025 was always the target. Get something functional, recruit teams in the DFW area, run the season free of charge, and learn everything there was to learn about what works and what doesn't. Season 1 was never about revenue. It was about proof.

We got teams registered. We got courses partnered. We built the schedule, set the handicaps, and teed off.

NTMGL Season 1 — Spring 2025 — Dallas–Fort Worth ★ Inaugural Season
1 Season
DFW Market
Free Entry
★ Dallas Pin Seekers
Inaugural Champions
29 – 22
Slice & Dice
Westridge Golf Club

The Dallas Pin Seekers won the inaugural championship, defeating Slice & Dice 29–22 at Westridge Golf Club. Every one of those 51 points was earned hole by hole, putt by putt, exactly the way I'd imagined it.

Season 1 also taught me that the platform needed a lot more than I'd built. The scoring was working. The fundamentals were solid. But the gaps were everywhere — in the GameDay live scoring experience, in the captain's tools, in the handicap system, in the admin controls. That list of gaps became the backlog that defined the next six months of development.

And it started a much bigger question: could this work beyond DFW? Could the NTMGL become something national?

That's what Season 2 is all about. But we're getting ahead of ourselves.


In the next episode, I'll walk through the early technical decisions — why I chose ASP.NET Core MVC over a more fashionable stack, how the database schema took shape, and the first real crisis: a scheduling algorithm that worked perfectly in my head and spectacularly failed in production.

Tags origin founding format