Finalist AWS Start-Up Challenge 2008

Breakfastball, LLC presents an Agent Fleet production

Winner Technical Emmy Award 2020

An AI consultancy for serious legacy code

and introducing nine secrets hidden in frame — then find the phone booth, the 19th hole

A storybook golf course tableau: the pink-and-mint Hickory Heights clubhouse on a hill, a caddie under a towering stack of golf bags, a golfer mid-swing, twin groundskeepers mowing in parallel, a striped breakfast cart, a leaderboard, a fox running off with a ball, a pink station wagon, a woman with a telescope, and a mint telephone booth.

Every codebase deserves a breakfast ball.

“I have told builders what to build in plain language for twenty-five years. The builders are agents now. The language still works.” Gregg · the operator

The Methodology

How a round is played

Every engagement fields a fleet established for your codebase — legacy excavator, architect, orchestrator, builders, compliance and QA agents — each with a defined role and engineered context: the right slice of the repo, the right constraints, a clear definition of done. Context engineering keeps every agent's tokens under par, so costs stay as predictable as the schedule. One operator who knows what an enterprise SaaS stack should look like directs the round; the fleet plays it in parallel.

Hole 1

The Walk-Through

The legacy excavator goes in first: every module, migration, and haunted corner of the codebase, mapped.

Hole 2

The Excavation

The business logic your company actually runs on is dug out and separated from the framework it is stuck in.

Hole 3

The Re-Architecture

A modern enterprise stack is designed around that logic — boring where it should be boring, fast where it counts.

Hole 4

The Rebuild

The fleet builds in parallel, with tests as the scorecard. Weeks, not quarters.

Hole 5

The Handover

Your team takes the bag: documentation, CI, security posture, and a development cadence that keeps climbing after we leave.

Breakfastball LLC presents “Breakfastball” starring Your Legacy Codebase with A Custom Agent Fleet and A Fox · kernel work Gregg (1997) · e-commerce pioneered Cart, Gateway & Hosting, Bundled (early 2000s) · bespoke software Two Decades of It · cloud transcoding encoding.com (2008) · statuette A Technical Emmy (2020) · media inspection probe.dev · token budgets Under Par · casting by 25 Years of Shipping · director of modernization Gregg · engagements measured in Weeks, Not Quarters

Now accepting engagements · Book a tee time Hickory Heights · Established 1997

Course notes — prefer to read the round?

  1. The Hook

    The fox is already running

    Your legacy codebase did not steal itself. Every quarter it sits, the rewrite gets bigger, the team gets slower, and the fox gets another ball. The phone booth works whenever you are ready.

  2. The Problem

    The bag only gets heavier

    Fifteen years of features. Five frameworks. One exhausted team carrying all of it up the hill. We carry exactly this.

  3. The Method

    A fleet mows faster than a mower

    Not one assistant — a fleet established for your codebase: a legacy excavator, an architect, parallel builders, compliance and QA agents, an orchestrator keeping tokens under par. Each carries engineered context: the right slice of the repo, a defined role, a definition of done. That is how 3x happens.

  4. The Operator

    Same swing, better clubs

    Gregg has directed builders in plain language for 25 years — kernel hackers, contractors, in-house teams. Agents are the same job with a faster swing. Kernel work in 1997. Cloud pioneer in 2008. Fleet operator now.

  5. 1997

    Where the round started

    First job: the first web hosting company in Silicon Valley, where Gregg extended the FreeBSD kernel to invent virtual hosting. He was solving infrastructure problems before most of today's legacy code existed.

  6. 2008, and the name

    Everyone gets a breakfast ball

    A breakfast ball is the free do-over on the first tee. Gregg took his in the cloud: encoding.com, the first cloud video transcoding service, built on S3 and EC2 before that was normal, scaled to the biggest names in streaming — work that earned a Technical Emmy in 2020. Your codebase deserves a do-over too.

  7. The Proof

    Check the leaderboard

    Every name on that board shipped. Rounds run in weeks, not roadmap quarters: platforms with fifteen years of history re-architected and back on the tee — coverage up, deploys multiplied, teams unblocked. Note who is in last place.

  8. The First Look

    Every engagement starts here

    Every round starts through the glass: the legacy excavator walks your codebase and excavates the business logic buried in it. You get an audit, a re-architecture roadmap, and a straight answer about what a fleet can and cannot do. No committal swing required.

  9. The Call

    One conversation

    Bring your gnarliest repo. If a fleet will not move the needle, you will hear that too.

    Book a tee time

  10. The Club

    Members only means you

    Breakfastball, LLC. One operator, one habit: virtualizing infrastructure before the tooling has a name.

    • 1997Virtual hosts in the FreeBSD kernel — before vhost
    • 2000Virtual Private Servers — before Docker
    • 2007Orchestrating EC2 and object storage — before Kubernetes
    • 2015Multi-cloud infrastructure at scale — before Terraform
    • 2022Successful exit of Encoding.com
    • NowManaging Agent Fleets — before …
Hickory Heights Scorecard

birdie  ·  bogey, caddie helped

Play the 19th hole

The 19th Hole

Book a tee time

The starter asks every member the same questions. Answer what you can — the caddie fills in the rest on the first walk-through.