The Future of SaaS Doesn't Have Screens

John Carter | 8 min read | Jan 20, 2025

It has agents that reason across data. Mine models PGA Tour player form, course fit, and live odds from over a dozen sportsbooks to surface value and send you the report before tee-off.

What if your “app” just delivered the outcome?

No screens. No settings. Just results.

Building a fully autonomous agent taught me the new pattern: products as recurring deliverables, not destinations.

I built Golf Agent Pro to prove it — an autonomous golf analytics agent that wakes up each week, pulls PGA data, runs the analysis, compiles an insanely detailed tournament breakdown, and emails finished reports.

No dashboards. No buttons. No forms. No clicks.

It’s not “another tool.” It’s insight on a schedule.

For years, building a tech product meant building software. Now, it means building systems that think. With large-context models and true agentic frameworks, “shipping software” is evolving. It’s not about apps or dashboards anymore — it’s about automated intelligence delivery.

From SaaS to DaaS: Data Delivery & Insight-as-a-Service

We all know Software-as-a-Service: sell access to tools.

With the advent of agents, we’re moving into something deeper: Data Delivery & Insight-as-a-Service.

Your product isn’t a UI; it’s a living system that delivers analysis and recommendations.

No dashboard to click. The system wakes up, pulls data, thinks, writes, and sends — like a digital analyst on payroll. That’s exactly what Golf Agent Pro does.

Industry signals point the same way:

  • Investors and operators are talking about software that performs and orchestrates work, not just software that enables it
  • Agentic products are moving beyond chat into real workflows
  • “Insight engines” have matured into end-to-end delivery systems

The direction is clear: outcomes over dashboards.

The Industry Consensus

Foundation Capital calls the model “Service-as-Software,” where software moves from tool to worker through systems of agents (they peg the opportunity at $4.6T).

McKinsey’s latest guidance is blunt: AI is turning software from something that enables work into a platform that performs and orchestrates work.

What Golf Agent Pro Delivers

Every PGA Tour week, subscribers receive three reports designed to give them an edge sportsbooks don’t have:

Wednesday: Pre-Tournament Preview

We analyze the top favorites using odds from 12+ sportsbooks, course fit and surface history, and the four-day weather outlook.

Each player includes:

  • A clear Statistical Profile (strokes-gained breakdown and key strengths by distance)
  • A Why This Matters explanation so you understand the rationale behind the pick

We finish with a top pick that includes odds, units, and a value score.

Saturday — Post-Cut Analysis (Adjust for the weekend)

Once the cut is made, we deliver:

  • A leaderboard read with live model probabilities
  • One decisive top prediction (units + quick justification)
  • A value play

We also show how our Wednesday predictions performed — who’s in contention, who missed, what changed — followed by “what we got right” and “what surprised us.”

Accountability isn’t a tagline; it’s the product.

Sunday: Final-Round Prediction

A focused deep dive on the top contenders with our strongest AI-backed winner projection, explicitly tied to current conditions, trends, and momentum.

We summarize “how Saturday went” (lead changes, hot putters, wind effects) and include one or two value predictions for chasers who can go low early. It’s clean guidance before final-round tee times.

Monday: Ranger Randy’s Roundup

Every Monday brings a quick recap, accuracy tracking, and market comparison. “Our picks went 7/3 this week — if you want this every tournament, grab the reports.”

There’s simply nothing else like it.

Not ESPN+. Not Yahoo Sports. Not DraftKings. Not even paid data services.

This is a fully autonomous system running week after week, event after event.

Teaching the Agent How to Think and Write

What makes Golf Agent Pro special isn’t just the data it pulls or the tools it calls — it’s the way it talks about that data.

I wrote detailed prompt instructions that coach the agent on how to analyze players, interpret conditions, and express personality. The Saturday prompt, for example, tells the agent to analyze the top 10 after the cut, compare round-to-round performance, and surface live betting opportunities.

Just as important, it enforces tone:

  • Write like you’re texting golf picks to your buddies
  • Celebrate when a call hits
  • Own it when a call misses
  • Avoid generic AI phrasing

The result is analysis that reads like a real fan with receipts.

The Technology Stack (Exactly What I Used)

AI & Development:

  • OpenAI (ChatGPT): early-stage reasoning & brainstorming to shape product direction and messaging
  • Claude Desktop: refining technical requirements, prompts, and the agent’s behavior
  • Claude Code CLI + Claude Agent SDK: implementing agentic functionality (planning, taking actions, producing deliverables, tooling, etc). The SDK builds on the same harness that powers Claude Code to ship production-ready agents. Check out the Claude Agent SDK Docs

Infrastructure & Delivery:

  • Python: async scheduler + polling scripts (detect tournaments, orchestrate data collection, generate reports)
  • Resend: HTML email delivery, unsubscribe management, and deliverability
  • GitHub: version control and CI trigger
  • Railway: one-click deploys and scheduled jobs (daily checks + report runs)
  • Webflow / Relume: UI and landing page

Data Sources:

  • PGA Tour: schedules, fields, player stats, and course info
  • ESPN: live leaderboard state and mid-tournament updates
  • DataGolf: advanced modeling, skill ratings, win probabilities, and multi-book odds (shout-out to the GolfData team — their models and API are excellent ground truth)
  • Yahoo Sports, Twitter/X, and other feeds: news, injuries, and momentum signals

These sources feed Claude’s analysis loop to produce readable, data-driven commentary that feels like it came from a veteran golf journalist — but it’s fully automated.

How It Works: Event-Driven in the Cloud

Everything is event-driven in the cloud.

No PGA tournament this week? The agent sleeps. Tournament week? It wakes up, researches, writes, and sends — on schedule.

Polling with Python (The Heartbeat)

A Python scheduler polls the PGA Tour calendar daily. If a tournament is active, the pipeline runs:

  1. Collect data from PGA/ESPN/DataGolf and news sources
  2. Run analysis through Claude (prompts tuned for stats and betting edges)
  3. Generate HTML reports
  4. Send via Resend

The system is asynchronous, idempotent, and resilient — more ops than app.

Why This Matters (And What It Costs)

Here’s the fun part: it’s cheap to run. Traditional golf analytics subscriptions can be ~$2,400/year.

Golf Agent Pro does more for about $114/year in operating costs for the reports themselves (not including infra costs).

That’s three reports per week plus Monday’s Ranger Roundup. Automation isn’t just efficient, it’s economically transformative.

Beyond the Sportsbook

This isn’t only about beating Vegas. It’s about beating your friends, too. When the weekend side bets start flying, you’ll already have sharper stats, deeper course analysis, and smarter angles.

It’s like having a professional data scientist quietly feeding you notes during the broadcast.

Lessons from Building with Claude

  • I don’t write full specs anymore — I converse them into existence
  • I don’t juggle IDEs and docs — I work with one model across code, strategy, and writing
  • I don’t “build apps” — I build loops that reason, act, and deliver

The Claude Agent SDK makes the loop agentic. Resend makes delivery effortless. Python makes it stable. Together, they turned what used to be a SaaS app into a living system.

Where This Is Going

Shout-out to DataGolf — we use their feeds for skill ratings, distance-bucket splits, win probabilities, and multi-book odds.

But Golf Agent Pro doesn’t just relay DataGolf, it builds on top of it.

We start with their fair numbers and market lines, then layer live context the raw model can’t fully see:

  • Leaderboard state
  • Tee-time waves and weather
  • Course archetype and surface
  • Recent form and momentum
  • Round-to-round stat deltas

Claude explains why those factors move today’s number; we publish our own implied probability with a clear units recommendation.

When we agree with DataGolf, we say why. When we diverge, from both the market and DataGolf, we call it out and justify the edge in plain language.

After the cut, we reconcile our Wednesday calls and update Sunday. DataGolf is the chassis; Golf Agent Pro adds context, timing, and transparent reasoning to deliver actionable decisions, not just numbers.

The Emerging Pattern

The future of software isn’t software, it’s autonomous insight delivery.

Agents like Golf Agent Pro don’t just serve data; they interpret it, act on it, and communicate results on a schedule.

The shift isn’t just technical, it’s philosophical. We’re moving from building tools to building teammates.


Built with OpenAI (ChatGPT), Claude Desktop, Claude Code CLI, the Claude Agent SDK, Python, Resend, Railway, and GitHub. Powered by PGA Tour, ESPN, DataGolf, and a belief that automation should think for you…not just work for you.

Get Started

If you’d like to join our growing list of Golf Agent Pro subscribers, you can sign up on the website. If you want a taste first, join Ranger Randy’s Roundup — a Monday tournament recap with accuracy tracking and a look ahead to the next event.

Let’s connect! You can find me on LinkedIn and GitHub. Looking forward to seeing how you’re building agentic workflows for yourself, so don’t be a stranger and hit me up!

Oh…and don’t forget to leave a 👏 if you liked this article and it was valuable for you.