The argument that made Matt Pfeil a founder

Matt Pfeil asked a colleague an apparently sensible question: who would run the business? Jonathan Ellis was preparing to leave Rackspace and start a company around the open source database Cassandra. Pfeil had been trying to talk him out of it. Ellis suggested that Pfeil take the job himself. Recruiting, it turned out, could be a dangerous occupation.

There is a pleasing economy to the exchange. An objection became an invitation. The person making the case for staying became a co-founder. In April 2010, the pair started the company that became DataStax, with Pfeil as its first CEO. The conversation had exposed a vacancy, and then supplied the candidate.

A year later, Pfeil would help recruit someone to take his own chief executive job. Those two decisions belong together. One brought him into a company; the other helped that company grow beyond the experience of its founders. Between them lies a more interesting account of entrepreneurship than the familiar business card with a steadily enlarging title.

Before the database, the inbox

Pfeil grew up in Europe and the Middle East while his father served in the Navy. He studied computer science at Virginia Tech, graduating in 2005, and joined Webmail.us, an email hosting startup in the same town. His early work involved the backend of a service for small businesses. Email looks modest when it arrives one message at a time. Storing enormous numbers of small files is another matter.

That job gave him a practical education in the difference between software that works and infrastructure that keeps working as demand grows. He described having to bend relational databases to accommodate the workload. The experience placed him close to the problem that would shape his next company: what happens when a perfectly reasonable system meets an unreasonable amount of data?

After Rackspace acquired the email business, Pfeil moved to Texas. His work there included shared infrastructure, allowing other teams to concentrate on features for customers rather than repeatedly solving storage problems. Ellis worked on Cassandra; Pfeil led the group preparing to deploy it internally. Their eventual partnership began with the unglamorous advantage of having worked on related problems at the same employer.

A company with customers already waiting

The founders called their business Riptano before adopting the DataStax name. Cassandra already had users, which changed the order of operations. They could begin by helping organizations run something those organizations had chosen to use. The first commercial question concerned support and services around an existing project, with a product business still taking shape.

Pfeil recalled Cloudkick signing up for a support package on the first day. Rackspace supplied a seed investment of just under $100,000 through a convertible note. About 85 days after formation, the startup had raised $2.7 million with Lightspeed leading the round. These were different kinds of money serving different purposes: a bridge from a former employer, then capital for a team.

The early support work also supplied product instructions. Customers needed help operating Cassandra. Engineers answering emergencies could do only so much, and Pfeil remembered the lack of enthusiasm for a pager going off at three in the morning. OpsCenter, the management software, offered a way to automate work that otherwise required a person. The company could learn from a support call and build something that made the next one less necessary.

It is an appealingly concrete origin for a software product. A management tool has fewer theatrical possibilities than a grand prediction about the future. It does, however, offer the prospect of a quieter night.

The job he chose to give away

Growth gave the founders a second operational problem: running the business itself. The initial hiring plan had allowed for six people in six months. Within a year, they had about 20. More engineering and support work meant more hiring, which meant the financing would have to stretch across a larger payroll than anticipated.

Enterprise sales supplied its own lessons. Ellis remembered a possible $80,000 deal that seemed large enough to suggest they might avoid outside funding. The deal eventually arrived roughly a year later. A promising conversation and a signed contract occupy different places on a calendar, particularly when a large organization must decide what to buy.

Pfeil recognized that DataStax needed a more experienced leader. Ellis later credited him with initiating the change and persuading a reluctant co-founder. Billy Bosworth joined as CEO in May 2011. The public announcement gave Pfeil a new title: vice president of solutions.

Bosworth was already known to them through his work running Quest Software's database business. He had become an early partner and had asked Pfeil for introductions to venture investors because he wanted to lead a startup. Pfeil connected the possibility to his own company's needs. The handover involved explaining the business, its difficulties and the work ahead. Familiarity gave the transition something more useful than a ceremonial handshake.

The choice deserves attention because it changed Pfeil's authority without ending his contribution. He remained involved in building the company. A founder's usefulness could move from one job to another. In this case, making room for someone else was an operating decision with consequences for the sales organization, the management team and the founders' working relationship.

Learning to speak customer

By March 2011, Pfeil was already explaining DataStax's technology at the Structure Big Data conference. The company had introduced Brisk, combining Cassandra with Hadoop and Hive capabilities. His explanation separated two needs: analyzing large amounts of data and letting an application interact with that data quickly enough for someone using it.

The distinction makes sense outside a conference hall. A business can spend time studying yesterday's activity. Someone waiting for a page to load has a shorter attention span. Pfeil's work involved connecting the architecture to those everyday expectations, translating a database discussion into a conversation about what a customer needed to accomplish.

As chief customer officer, he continued making that connection. In 2016, he discussed graph technology through fraud detection and recommendation engines. The attraction lay in relationships among pieces of information. He described customers spending time building graph-like capabilities themselves, work that was often outside their particular expertise.

Those repeated efforts could become a clue for DataStax. When several customers were constructing similar things, the company could consider providing a common capability. The approach extended the early OpsCenter logic: observe the work people were doing around the database, then see which parts software could take off their hands.

“No one buys a database because they want to.”

Matt Pfeil, discussing customers' business problems in 2014

His ambitions in 2014 reached toward broader data solutions. Customers were building applications because the particular solution they needed did not yet exist. A database put DataStax close enough to watch that building happen. For Pfeil, the patterns were a way to work out what the company should offer next.

The founder's work travels

The company eventually took directions that belong to a much longer history than its founding year. IBM announced its agreement to acquire DataStax in February 2025, describing how its database and application development technology would fit IBM's enterprise AI offerings. DataStax's investor Scale Venture Partners records it as acquired by IBM in 2025.

The change in vocabulary is striking: an enterprise AI acquisition at one end, Cassandra support packages at the other. The connecting work concerns getting useful software into organizations that need to depend on it. Pfeil helped establish the business at the beginning of that history; the later acquisition is a company milestone, with its own subsequent teams and decisions.

He also co-founded TravelBoss, a corporate travel software business, and moved into work with Top Tier Capital Partners as an entrepreneur-in-residence. The sequence took him from building and selling infrastructure to another operational problem, then to advising people facing the uncertainties of early companies.

Back to the classroom, with better examples

In April 2023, Pfeil returned to Virginia Tech's entrepreneurial seminar program to discuss the things he appreciated in his career and the things he wished he could change. In September 2025, the department listed him for another conversation about building software startups, identifying him as an entrepreneur-in-residence at Top Tier Capital.

The setting suits a career with both operating experience and revisions to the original plan. A student considering a company could ask about customers who take longer to sign than expected, hiring that outruns a budget, or choosing a successor. Each question has an episode attached to it. Experience becomes more useful to other people when the awkward parts remain in the telling.

His 2025 biography places him in Austin with his wife and two children, and lists macroeconomic debates, options trading and cornhole among his interests. There is room, apparently, for both an argument about the economy and a game with a considerably more visible target.

The recruiting question remains a fitting place to leave him. At Rackspace, asking who would handle the business helped create his next job. At DataStax, deciding who should handle the next stage helped him change it. Pfeil's story turns on the willingness to reconsider a position he had good reasons to hold. A company emerged from one such reconsideration. Another helped it continue.