Peter Gassner and the business of answering to someone

When Peter Gassner was about seven, he thought he had discovered the advantage of his father’s job. His father owned a machine shop. Other children’s fathers had bosses. His apparently did not. The reply supplied a small, durable correction: the business depended on large customers, and losing one could cost the family its house. Even the owner answered to someone.

Gassner grew up in Portland, Oregon, in a Swiss immigrant family, the third of six children. He helped in the shop. Years later, he would run a software company with customers far larger than itself. The machines had changed; the dependence had a familiar shape. A customer’s satisfaction could never be filed away as somebody else’s department.

It is a useful place to begin with the founder and CEO of Veeva Systems, based in Pleasanton, California. His business sells cloud software to the life sciences industry. Its fiscal 2026 revenue reached $3.195 billion. But the more revealing question in his career concerns the obligations that arrive with building something other people rely on.

A degree with several exits

Gassner’s education did not proceed in one uninterrupted march toward a graduation photograph. He liked computer science and disliked the structure of university. He left, returned, left again. Hawaii supplied work as a waiter. Australia and Thailand supplied further detours. A planned short stop in Bangkok stretched into almost a year in Thailand. Nepal, the intended destination, would have to wait.

One interruption was an IBM internship. There, professional software developers gave him a picture of work he could admire: difficult problems, serious craftsmanship, people who knew their material. He eventually returned to finish his studies. Oregon State awarded him a bachelor’s degree in computer science in 1989.

The university later inducted him into its Academy of Distinguished Engineers in 2013. Its account of his career also records an agreeable detail: Veeva chose orange as its primary corporate color, a nod to his educational roots. Some alumni buy a sweatshirt. Gassner’s company made a considerably larger color commitment.

From the engine room to the application

His professional route followed changes in the way businesses bought and used software. At IBM, he worked on relational database technology. At PeopleSoft, where he became chief architect and general manager, he moved into enterprise applications. At Salesforce, he served as senior vice president of technology from 2003 to 2005. The sequence gave him a view beneath the product demonstration: the machinery that made the demonstration possible.

Each move meant changing the scale of the problem he worked on. Database internals demand precision. Business applications demand an understanding of what people are trying to accomplish. A cloud platform adds a further question: which pieces should every customer share, and which deserve to be different?

Veeva’s eventual answer was specialization. A software company could use common cloud infrastructure while building deeply for a particular industry. The market would be narrower than all enterprise software. The product could be more closely matched to the people paying for it. Narrowness, in that argument, was a design choice with commercial consequences.

The CEO job he meant to hand over

Gassner founded Veeva with Matt Wallach in 2007. Their partnership brought together different strengths. Gassner concentrated on the technology and products in California; Wallach worked on customer relationships and marketing from the East Coast. It was a practical arrangement for a company that needed both a functioning product and someone willing to buy it.

The CEO title was not Gassner’s original ambition. He considered himself a developer and product person. His provisional arrangement was to lead the company and its products, then recruit a CEO if the business survived. Survival would create a staffing problem. As problems go, it was worth having.

At SaaStr in 2017, he recalled discovering that he enjoyed the role and could improve enough to keep it. The same appearance contained a useful glimpse of his distance from the industry’s social calendar. Asked whether he had attended the Crunchies awards, he admitted he might not know what they were. There are worse admissions for a software executive.

Veeva went public in 2013. A role he had imagined handing off had become a continuing responsibility. The product person was still there, but now the product also included the organization: who it hired, how it charged, and how it decided which demands deserved a yes.

Seven million raised. Three million used.

The early financing is one reason other founders keep asking him questions. Veeva raised $7 million and used only $3 million before the business could support itself. Gassner has credited the Salesforce platform, early customers and hires, good fortune, and a management team that expected to build a profitable company.

The distinction between money raised and money consumed matters. An unused financing round cannot write the software or negotiate a renewal. It can provide a cushion. A business that stops needing the cushion has earned a different sort of freedom: fewer decisions depend on persuading another investor to pay for the next interval.

That does not make $3 million a recipe anyone can follow. Enterprise software has its own economics, and Gassner’s experience mattered. Reusing an existing platform also reduced what Veeva had to build. The interesting part is the expectation inside the management team: profitability belonged in the original plan.

In 2022, Gassner joined Zoom founder Eric Yuan for an Acquired conversation about capital-efficient growth, hosted at an Emergence Capital CEO gathering. Emergence had been the first institutional investor in both businesses. It reported that neither had used the money it invested. An investor celebrating unused money is a pleasing reversal of the usual fundraising photograph.

A promise gets written down

Long before the conversion vote, Gassner was describing Veeva as a business with obligations to employees, customers, society, and shareholders. In 2020, he explained the proposed public-benefit structure as a way to make the company’s formal charter reflect its existing approach. He also wanted that approach to endure beyond the current leadership.

On February 1, 2021, Veeva became the first publicly traded company to convert from a traditional Delaware corporation to a public benefit corporation. Shareholders had approved the proposal in January. The company continued to operate for profit. Its charter gave a formal place to responsibilities beyond shareholder returns, including high-quality employment.

For Gassner, this was also a question of consistency. A company could tell its employees that their work and its customers mattered, then give its directors documents organized around a narrower objective. He wanted the documents and the operating philosophy to agree. It is an engineer’s complaint, applied to the rules of an institution.

“The customers are my boss.”

Gassner’s father, as recalled by Peter Gassner

The parallel with the machine shop is hard to miss. Ownership had never removed his father’s obligations. A public listing did not remove Veeva’s. Making those obligations explicit offered a way to carry a personal conviction into a company that would eventually have different executives and directors.

The structure also places demands on management. When several groups have interests in a decision, leaders must explain how they weighed them. A charter can establish the responsibility; daily choices still determine whether employees and customers experience it. Gassner’s achievement here was getting a public company to make that commitment in its governing documents.

The platform changes again

Technical independence has brought another long project. Veeva’s original CRM product ran on Salesforce. In 2014, the companies extended their partnership into 2025. That arrangement let Veeva concentrate on industry-specific applications while using Salesforce infrastructure. It was a consequential choice about where to spend engineering effort.

Later, Veeva chose its own Vault platform for the next generation of CRM. The company’s filings acknowledged the difficulty: moving customers could be expensive, disrupt their businesses, and create openings for competitors. This is where a founder’s preference becomes an operating test. Customers have working systems, integrations, and people who must learn the replacement.

By August 2026, Veeva reported more than 180 customers live on Vault CRM. Its next technical bet was also underway: AI agents integrated with its applications and data, alongside the Veeva Falcon platform. In March’s prepared remarks, Gassner argued that established systems of record would incorporate AI. That is his position on the transition; the execution will decide how well it holds.

There is time to get there

There is another audience worth remembering. In a 2017 TEDx talk for high-school students, Gassner urged them to look beyond the contest to get into college. He directed attention toward their own goals and interests, families, and community. For someone whose university years included several departures, the advice had an autobiographical foundation.

His career gives that advice some texture. He left school and came back. He learned inside established companies before starting his own. He took a job he thought he would eventually give away, then stayed. The progress looks orderly when compressed into dates. Living it involved choosing, reconsidering, and discovering what he wanted to keep doing.

In September 2026, he returned to the subject of corporate purpose in a conversation with Eric Ries. He recalled deciding to pursue the conversion during a mountain-bike ride, then discussing it with chairman Gordon Ritter on a long hike. An idea had to leave the privacy of his own head and survive somebody else’s questions.

That is a fitting image to leave with: a founder stopping, then setting out to persuade another person. The father’s lesson still applies. Building a business gives you choices. Keeping it requires people on the other side of the transaction who have reasons to trust you.