Matt Heaton and the cost of a free year

A year of web hosting was available for the price of a table-tennis victory. Matt Heaton, Bluehost’s founder, offered the deal to anyone in Utah who could beat him. It was a cheerful way to invite trouble. Good players appeared. Better players appeared. The hosts discovered that their own assessment of their abilities had been generous.

The wager belongs in the story of a hosting company because the table already had a place in its history. Dan Handy’s decision to join Bluehost followed a conversation over a game with Heaton. On Handy’s first day, the pair bought a table for the office. Some companies send a welcome basket. This one acquired a surface on which the founder could be beaten.

Heaton’s commercial education began with something considerably heavier than a website. At seventeen, he sold computers through bulletin board systems and shipped the products from his basement. He later sold that business and pursued internet ventures, including advertising-supported free hosting.

Eventually, he judged that model unsustainable. Bluehost, launched in Provo in 2003 with Danny Ashworth, offered another arrangement: customers would pay a subscription, and service would give them a reason to keep paying. The fee put the person using the hosting service at the center of the transaction.

There is a particular discipline in selling something that must work again tomorrow. A computer can be packed and posted. A hosting account remains an obligation after the sale. The customer expects a page to appear, an inbox to open and a person to answer when either fails.

Heaton’s company found an audience among people building their own corner of the web. WordPress.org began recommending Bluehost in 2005. The association joined a publishing tool with a place to run it, reducing one practical decision for people who wanted to get on with writing, selling or showing their work.

By November 2006, the bargain had acquired the complications that come with growth. Heaton sent a long letter explaining a repair to Bluehost’s systems. Excessive file access was hurting performance. The company moved quickly, and the change temporarily prevented some users from accessing their email.

Heaton explained the intervention and acknowledged that customers had received no advance warning. He also promised a way for users to see server monitoring information, giving them a better chance to distinguish a problem at Bluehost from one elsewhere.

“I care about what happens to your sites”

Matt Heaton, customer letter, November 2006

The revealing part was his description of the job itself. Managing the company had reduced his technical involvement. Now he thought that needed to change. The president was being pulled back toward the system that delivered the promise on the sales page.

A letter cannot repair a server. It can make the person responsible for it visible. Heaton’s message put his own judgment in the discussion, including the decision to act before notifying customers. That made an operational problem personal in a practical sense: somebody with authority had explained what happened and what he intended to do next.

Customers supplied their own verdicts. In April 2007, one longtime computer user wrote to Heaton praising the value and service of a $6.95 monthly account. The customer also disclosed that a referral could earn him a commission. Satisfaction and a commercial incentive occupied the same page, an ordinary feature of the hosting business.

A different letter, published in May 2009 by an Australian customer, described an account with about fourteen websites being deleted without warning. He said the staff were friendly and helpful, but that he had been unable to recover the sites or obtain an explanation. It was a customer’s account of a failure, and a reminder of how much could depend on a modest subscription.

These experiences gave the service promise its stakes. Praise could help bring the next customer through the door. A failure could affect somebody else’s clients as well as the person paying the bill. The founder’s accessible public voice made him a destination for both kinds of message.

Heaton’s technical interests had a habit of escaping into public view. In February 2010, he described a way to improve performance for customers with slower internet connections: compress suitable files on the server before sending them to the browser.

HTML, JavaScript and CSS could shrink substantially. Images and already compressed files were a different proposition. The browser would unpack the compressed material automatically, leaving the visitor with the familiar page and less data to receive.

There was a catch. Compression consumes processing power. Apply it while a server’s CPUs are already overwhelmed and an attempt to speed things up can make them slower. Heaton’s explanation lingered on that constraint, where a feature meets the conditions under which it actually has to work.

The subject was an unglamorous one for a chief executive to take up in public. It was also close to the customer’s experience. A visitor does not need to know which module handled a file. The visitor notices the wait.

Bluehost made control over the machinery part of its approach. In 2012, the company described building its own servers, operating its data center in-house and using a proprietary Linux kernel. The ambition was to manage the underlying technology so customers could concentrate on their websites.

Owning more of that work creates more opportunities to adjust it. It also leaves fewer places to send the awkward question when something performs badly. Hardware, software and service become parts of the same argument about whether a subscription is worth renewing.

The table-tennis habit ran alongside that work. Heaton studied the sport through books and videos, sought practice with highly ranked players and entered national tournaments. A game in the office could be a diversion. His approach required homework.

Handy remembered the free-hosting challenge as an education in how much further they had to go. Stronger opponents gave them a more accurate picture of their game. Lessons followed. The office’s enthusiasm for table tennis also spread among employees.

By the 2012 cPanel conference, Heaton had adjusted the prize. At the BetterLinux booth, a challenger who beat him would win a laptop. Nobody took it home. The company’s alligator mascot also had a turn at the table, with no better luck.

A trade-show booth generally asks people to look at a screen. Heaton gave visitors another reason to stop. The hardware prize was tangible, the rules were easy to understand and the demonstration had the considerable advantage of being fun.

It is tempting to turn every hobby into a theory of management. This one needs no such promotion. It brought a future colleague into the company’s orbit, supplied an office ritual and generated a few good stories. That is already a respectable return on a table.

Bluehost joined Endurance International Group in 2010. In June 2011, Heaton announced that he was stepping down as CEO. Handy, previously chief operating officer, took over. Heaton described a focus on the design and technical structure of the hosting platform.

That change gave a formal shape to the tension visible in his earlier customer letter. The business needed someone to run it. He wanted to spend more time on the platform. The two jobs were related, but they competed for the same hours.

By 2012, Heaton was appearing publicly as BetterLinux’s CEO. His subsequent chapter stayed close to server software rather than repeating Bluehost’s consumer hosting proposition. BetterLinux announced in June 2015 that it would shut down on July 1.

The end of that venture belongs beside the launch of Bluehost. A career has room for a company that becomes familiar and a later business that closes. Removing the latter would give the story a tidier shape at the expense of the person’s actual work.

People around Bluehost remembered the founders’ involvement in service. Employees later described Heaton and Handy as engaged with technical support, with a small founding group that also included Ashworth and developers. The customer’s route into the company could therefore lead surprisingly close to its leadership.

One memory of that proximity resurfaced in a February 2026 conversation with website-security specialist Thomas Raef. He recalled helping Bluehost technician Alex Lundquist with a problem affecting Heaton’s website. The advice worked. Lundquist called back and offered to send customers Raef’s way.

Raef remembered the referrals as a boost to his business. His thank-you took a form rather easier to share than a server benchmark: fifty Chicago deep-dish pizzas sent for a Bluehost party. The episode joins a technical problem, a useful answer and a working relationship. The pizzas are a pleasing footnote.

Bluehost carried on beyond Heaton’s tenure. It added VPS and dedicated hosting in 2013, and its later corporate history includes new products, ownership changes and other executives. Those chapters belong to the company’s continuing life. Heaton’s founding chapter remains specific: subscriptions, customer service and an appetite for the systems underneath them.

The table-tennis wager is memorable because it gives those corporate dates a human scale. Heaton could make an offer, invite an opponent and discover whether he could keep the prize. Hosting imposed a longer test. Every renewal gave the customer another chance to decide whether the arrangement was still worth it.

A free year might depend on one afternoon’s score. A paid year had to earn its place day after day.