Part IThe Story
Everything, Including the Passport
Somewhere in southern Malaysia, in the middle of the 1980s, a twenty-one-year-old American who kept starting and stopping college flagged down a man on a motorcycle and accepted a ride. It did not end well. By the time it was over he had been robbed of everything he had: the cash, and the passport, the small booklet of stamped pages that tells a border guard who you are, where you come from, and where you are allowed to go back to. He was left on an isolated rural road with the clothes on his back.
Investor's Business Daily, which told the story in 2019, breaks off at the exact moment a reader most wants it to continue. Rather than… Then the paywall comes down. I have not been able to establish what came after the ellipsis: how he got from the shoulder of that road to an embassy, a police station, a bus, a bed. He does not seem to have told the story often. That is characteristic. Peter Gassner has spent four decades declining to narrate himself, and he is now the founder and chief executive of a company that reported $3.195 billion in revenue and $908 million in net income for the fiscal year ending January 31, 2026. It sits in the S&P 500 between Universal Health Services and Vertex Pharmaceuticals. When Jason Lemkin introduced him at SaaStr Annual in February 2017 and asked whether he had made it to the Crunchies that year, the tech industry's self-congratulatory awards night, Gassner laughed and said, "Well, I might not even know what that is."
Hold the road in your mind: a young man with nothing, a long way from Portland, Oregon, with no papers to say who he is. Now move forward about twenty years and put him in a conference room.
It is 2007, or close to it. Veeva Systems is a few months old and is trying to sell customer relationship management software to a pharmaceutical company. Gassner has brought what he has. Across the table sits a delegation from the customer, large enough that one of its members stands up and says what everyone on that side is thinking: We have more people in this meeting than you have in your company. Why are we even talking?
"I just answered it truthfully," Gassner told TechCrunch a decade later, "that we have great people making great technology and this is a chance."
That is all he said. He offered no bluster and no pivot to a vision deck. He gave an honest inventory of what he was carrying, which was not much, and an argument that it would be enough. In both scenes, on the road and in the conference room, a man is stripped down to essentials and asked to account for himself. Most of what follows is about how he answered the second time, and about what he built so that he would never have to answer it in quite that way again: a company that consumed, by its first investor's account, about $3 million of capital on the way to a market capitalization above $20 billion; that rewrote its own charter so that the documents describing what it is would finally match what it does; and that kept its headquarters, for nineteen years, a short drive from the house its founder bought in the mid-1990s.
By the Numbers
Veeva Systems, Fiscal 2026
$3.195BRevenue, fiscal year ended January 31, 2026
$908MNet income, fiscal 2026
~$3MCapital used to build the company, per early investor Gordon Ritter (2019)
1,552Life sciences customers
7,928Employees
99%Share of votes cast in favor of converting to a public benefit corporation
$275,000Gassner's annual salary under his June 2013 pre-IPO letter agreement
Measure Twice
His parents came from Switzerland. His father owned a machine shop in Portland. Peter was the third of six children, born February 26, 1965, into a household where work was the normal condition of life, and he began working at eight as a paperboy. After that came lawns, then a restaurant, then, while still in high school, a roofing business of his own. He was captain of the wrestling team.
You don't need to lean on the national cliché to see the line running from a Swiss immigrant's machine shop to the habit of mind his son would later describe to Investor's Business Daily. Working construction as a teenager, Gassner said, taught him one rule above all: measure twice, cut once. In a machine shop a cut cannot be undone. On a roof, a mistake comes back as a leak in somebody's kitchen in November. The lesson is not caution for its own sake. It is that the expensive part of any job is the irreversible part, so you spend your attention before you get there.
He also grew up without a picture of a corporation. "As a kid," Gordon Ritter of Emergence Capital wrote in 2019, summarizing a conversation with him, "Peter did not know what a CEO was." His father was a small business owner, and Peter assumed he might someday run a business too, but the layered management of a large company was as unfamiliar to him as a ministry of foreign affairs. What he did know, he said later, was that he "always had an affinity for math and solving puzzles." A math teacher noticed and suggested a computer science class. That suggestion, an aside from an adult who was paying attention, set the direction of everything that came after.
He did not move in that direction quickly. Oregon State University gave him a B.S. in computer science in 1989, and his own records date his enrollment to 1983, so a four-year degree took six. In between he kept leaving: extended breaks in Hawaii, in Australia, and in Thailand, where he worked as a trekking guide and learned the language well enough that, by most accounts, he still speaks it. The Malaysian road belongs to these years. Wikipedia files all of this under "Early life," with the drifting tone of a gap-year anecdote. The pattern is more interesting than that. A young man from a working family that put a high value on staying put chose, again and again, to go somewhere he was a foreigner, as his parents had been in Oregon. He supported himself with whatever the place would pay for, and then he came back and finished.
Oregon State's College of Engineering inducted him into its Academy of Distinguished Engineers in 2013. Its citation contains one of the best small facts in the record. Veeva's corporate color is orange, because Oregon State's is. The college's write-up adds, with some pride, that he is "one of the few in the class who actually pursued a career in computer science," a line that also appeared, almost word for word, in his hometown newspaper in Pleasanton. Both institutions wanted to claim him, and the claims fit together without strain. He is a man from a particular place who carries that place's colors around and who has, as far as anyone can tell, never seriously tried to become someone from somewhere else.
"I put in my 20-plus years apprenticeship before Veeva," he told IBD. In a machine shop, apprenticeship is not a figure of speech.
Three Platforms Before His Own
The apprenticeship had three masters, and each one was a platform.
The first was IBM. Gassner joined in 1989 as a staff developer at what was then called the Santa Teresa Laboratory, later the Silicon Valley Lab, in San Jose, and he also spent time at IBM Research's Almaden Research Center. He worked on DB2, IBM's relational database, on the mainframe. "I started my career at IBM where I did a lot on the mainframe," he recalled, "and learned quite a bit from some really great people, including the inventors of System R and the relational database. That's where I really got my foundation and a true understanding of what great software is like."
The phrase what great software is like is worth lingering on. System R was the IBM research project of the 1970s that showed relational databases could actually work. It is the reason SQL exists and the reason nearly every enterprise application of the following half-century stores its data in tables. A twenty-four-year-old who had spent his college years leaving college was learning his trade from the people who built the foundation under the entire industry. He did not learn applications first. He learned the substrate: how data is stored, queried, and kept consistent, and what happens to everything above when something below fails.
In late 1994 he left, "because I could see that client server was really taking off," and went to PeopleSoft, the human-resources and enterprise software company then growing at a ferocious pace in Pleasanton, a quiet East Bay suburb about forty minutes from San Francisco when the traffic cooperates. He was approaching thirty. He stayed about nine years and became Chief Architect and then Vice President and General Manager of PeopleTools, the development framework on which PeopleSoft's applications were built. By the end he led a team of about 450 people. Once again he was not building the thing customers bought. He was building the thing the things customers bought were built on.
Around 1996 he bought a house in Pleasanton's Gates neighborhood. He has lived there since.
The third platform came with the third transition. In 2002, he told IBD, he realized "the real potential of cloud computing to be transformative." In the account given to his hometown paper, he left PeopleSoft before Oracle's takeover, a reminder that his era of enterprise software ended in a hostile acquisition. He joined Salesforce.com in San Francisco as Senior Vice President of Technology. Salesforce was then a hard-charging, loudly evangelized company whose founder treated "No Software" as a marketing slogan, and Gassner was among the people building what became Force.com, the development platform that let other people build applications on Salesforce's infrastructure. "I compare it to being at Salesforce in 2002 around the emergence of the cloud," he said years later, describing a different moment that also felt early.
He stayed about two years and left in 2005, by his own account and that of his LinkedIn profile, then spent roughly two years as an independent consultant. These are the least documented years of his career, and in hindsight probably the most important. He had now worked inside three successive generations of enterprise computing: mainframe, client-server, cloud. In each he had worked at the platform layer, where you learn what can be built on top only by having built the bottom. He knew Force.com's internals better than nearly anyone outside Salesforce, and possibly better than most people inside it.
That knowledge became the venture thesis. Investors would not see it until someone pointed it out.
The Pie Chart
One of Gassner's friends drew him a picture.
The friend's name does not appear in the record, which suits the parable, because the friend was doing what any reasonable person would have done. "In 2007," Gassner said in an interview with Neeraj Agrawal and Logan Bartlett, "I was talking a lot about the fact that industry-specific software would represent the next wave of cloud applications, but I didn't get a lot of buy-in from my peers at that time." So the friend drew a pie chart showing the whole enterprise software market, and inside it the pharmaceutical segment, and inside that pharmaceutical CRM. "Pharma CRM was minuscule compared to the overall enterprise software market," Gassner recalled. "He thought, why would I do that?"
It was a fair question, and the pie chart was accurate. It measured what existed. Gassner was making a claim about what did not exist yet. "My premise," he said, "was that if you could create a software application that would work very well and in one central place; mix it with some data; and then put some services around it, you could really capture a high percentage of market share at a good price point." The friend's chart showed the market as it was currently counted. Gassner was betting on how it would be counted once someone built the right thing. Years later he put it more directly: "The market of this stuff comes out of the woodwork. Most of the market is not even categorized because it's on custom stuff somewhere that nobody is counting."
The paperwork came first. Veeva's records show that on or about January 29, 2007, the company entered into an offer letter with Peter P. Gassner, so the founder was, formally, hired by his own startup. The corporate clock started a few days later. The founders, depending on which source you trust and how generous it is, were Gassner and Matt Wallach, or Gassner, Wallach, Doug Ostler, and Mitch Wallace. Wallace's entry in the founding story is short and almost entirely geographic. He was Gassner's next-door neighbor in Pleasanton, the man on the other side of the fence, who heard the pitch over the property line and decided to come along. Wallach's role was to know pharma from the selling side in a way that a database architect from IBM could not. The company found a small office on Ray Street in downtown Pleasanton, and how it found that office is a story for later.
Then it went looking for money and found that almost nobody wanted to give it any.
The objections were the ones the pie chart predicted, plus another. The market was too small, and the cloud was a strange place to put a pharmaceutical company's data in 2007, when the industry was among the most heavily regulated on earth and most enterprises still thought of "cloud software" as a contradiction. On top of that came the platform risk. Veeva planned to build its first product on Force.com, which made it a tenant in a building owned by someone else, a building that was itself new and unproven.
Gordon Ritter was the exception. He was the founder and general partner of Emergence Capital, a firm that since 2004 had invested only in software sold as a service. His partner Jason Green would later tell a conference hall of founders, "we still live, breathe, and bleed SaaS." Ritter had spent his career betting on the delivery model everyone else thought was a fad, so he was used to being early and to being told so. In June 2008 Emergence invested $4 million in Veeva. Ritter later explained why in terms that have very little to do with pharmaceuticals and a great deal to do with the apprenticeship:
"Everyone else was looking at Veeva with a knee jerk reaction: 'This can't be done.' They were forgetting that Peter built the platform and that he knew the details and knew the internals and how to strike the right balance to take advantage of the platform."
The pie chart measured the market. Ritter measured the man. "Peter and the team," he said, "had a unique way of mitigating those risks."
Gassner did not describe the skepticism as a burden. "I wasn't [ever] discouraged," he told TechCrunch. "I was encouraged. If you are doing something that most people think is impossible, but you think it could be possible,…then you are ahead of the game." It sounds like a motivational poster until you notice what it actually says. It is a claim about information asymmetry, not about grit. If most people think a thing is impossible and you have specific, technical reasons to think it is not, then their disbelief is not an obstacle. It is a moat, temporary and free of charge, that you did not have to dig.
Years later he described a different pie chart, one from Gartner, showing vertical-specific software as a $114 billion market with nothing else near it. "That pie chart didn't exist back in 2007," he said. He did not mention his friend's name. He did not need to.
More People in This Meeting
— A pharmaceutical customer's representative, as recalled by Peter Gassner to TechCrunch, 2017We have more people in this meeting than you have in your company. Why are we even talking?
The first product was customer relationship management for pharmaceutical sales representatives, built on Force.com and licensed from Salesforce in exchange for royalties. A critic would later call it, with some justice, a rebranded Salesforce CRM, and Gassner's choice was not entirely romantic. He knew CRM, and he knew the platform underneath it better than nearly anyone. Salesforce was happy to supply the infrastructure.
There was a deeper logic, which the vertical-software writer Eli Dukes later reconstructed. Software that cuts costs is hard to sell, because the savings are spread out, hard to measure, and easy for the incumbent vendor to dispute. Software that raises revenue is easier, because if it works, the people using it make more money and will say so. Commercial software for drug reps sat right on the revenue line, so its value was easy to prove. Satisfied customers talked about it, and their talk did the work an expensive sales force would otherwise have had to do. Dukes concluded that existing customers were often referring Veeva into other companies. Referrals cost nothing, and that is one of the quieter reasons the venture money never had to be spent.
Ray Wang of Constellation Research described the state of life sciences software in 2007 as "ancient companies making software that was hard to use." Veeva's pitch in that setting was almost embarrassingly simple: software that a drug rep would actually open. "Veeva succeeded at a time where existing tools, perceptions of regulatory hurdles and a nascent cloud seemed to be an unlikely bet," Wang said. "Yet building a product that met the unique needs of pharma sales people, betting on the Force.com platform, and strong vertical expertise eventually helped them break out."
Inside the company, the time horizon was deliberately short. Gassner told the SaaStr audience in 2017 that for roughly the first year and a half, Veeva thought about the next ninety days. There was no five-year plan, no total-addressable-market slide, and no talk of an "industry cloud." It thought about this quarter's customer, this quarter's release, and this quarter's hires. The long vision came later, when the company had earned the right to it. People who later made Gassner a symbol of patient, decade-long thinking tend to miss this point. The patience was something he built up to, and he started with impatience about the present.
They sold one company at a time. "He believed if they could get one company at a time to buy in," TechCrunch wrote, "they could build on that, and of course that happened." The physical history of the company shows the growth in square feet. In early 2009, with more than a dozen employees crowded into the Ray Street office, Veeva moved a few miles north to a 3,600-square-foot suite in the Hacienda Business Park, expecting it to last several years. It did not. A year later the company took another 8,700 square feet in the same building, and by September 2011 it was doubling its space again. Gassner had just added 50 people to a staff of 185 and opened offices in Europe, Japan, and China. In 2010, PharmaVOICE named him to its list of the 100 most influential people in life sciences. The man who had been asked why anyone was talking to him had become, in three years, one of the people the industry wanted to talk to.
He described the work to the Pleasanton Weekly in terms that are close to embarrassing coming from a billionaire database architect. He was proud, the paper wrote, to be part of an industry "that brings people out of their wheelchairs, that helps people regain their sanity." It is the least guarded thing in his public record. Without question it is also sincere.
The Head of Product Who Became CEO
He did not want the job.
"I worked at other software companies and saw what their CEOs did," he said in 2019. "I thought, 'That's not me. I can't do that. I don't want to do that.'" He had spent three decades near chief executives and had seen the travel, the dinners, the keynote circuit, and the performance of confidence for analysts. None of it appealed to him. So when Veeva needed a CEO he took the title the way you take a lease on a temporary office, assuming he would move out soon. "Most startups fail," he said. "I actually thought failure was the most likely outcome for Veeva, only because those are the odds. And then I thought, in the beginning, CEOs just function like the head of product, and I can do that. So if Veeva succeeds, we'll get someone else to take over as CEO, and I'll be the head of product."
This is one of the stranger founding stories in American software. The company's survival depended in part on the founder's belief that it probably would not survive, which let him take a job he did not want because he thought he would not have to keep it. The odds were wrong, Veeva lived, and the reluctant temporary CEO had to decide what to do about having been mistaken.
His solution was to rewrite the job. "What I really didn't realize before," he said, "was that as CEO, you can make the job — and you should make the job." He started by subtracting. "I spend about 20% or less of my time traveling, which is far below the standard for CEOs." He stopped saying yes to every event, dinner, and meeting. He did not do the speaking tour, as Lemkin teased him onstage, and he had not heard of the Crunchies. He did not move the company to San Francisco, though he had commuted there for Salesforce. Veeva's headquarters stayed in Pleasanton, among the office parks, in the same suburb where PeopleSoft had been and where his house was.
What remained after the subtractions was the head of product he had meant to be. "Peter Gassner is responsible for Veeva overall," his biography on Veeva's leadership page reads, "including strategic direction, product direction, and operations." Product direction sits in the middle of that list, not in the slot usually filled by vaguer CEO duties. At SaaStr he said he spends about 90 percent of his time on execution. Anyone can copy an idea, the logic runs, but execution is hard to copy. Oregon State's citation lists his priorities in order, with customer success first and employee satisfaction "followed closely." Shareholders are not on that list. They would turn up later, in a governance document.
The executive roster he built around himself is notable mainly for how long people have stayed. As of 2026, Vivian Welsh, the chief people officer, had been at Veeva seventeen years; Damian Kelly, who runs Asia and Latin America, fifteen; Howie Hsueh in global services, fourteen; Nitsa Zuppas, president and chief of staff, "responsible for helping set, communicate, and execute company direction," thirteen; Josh Faddis, the general counsel, thirteen; and Erik Smith in R&D and quality, also thirteen. In an industry where an executive's tenure is often measured in vesting cliffs, this looks less like a C-suite than a machine shop where the same hands have run the same lathes for a decade and a half.
His June 20, 2013 letter agreement with the company, filed with the SEC ahead of the IPO, set his salary at $275,000 a year. For a CEO about to take a company public, that was modest to the point of being pointed, though of course it was not where his wealth would come from. As of September 2026 he held about 32.9 million shares of Veeva, roughly 91 percent of a fortune estimated at $4.8 billion.
In June 2015 he joined two outside boards, which is the sort of thing CEOs who dislike CEO things do sparingly. On June 17, Guidewire Software, which sells core systems to property and casualty insurers and is another vertical software company, appointed him a Class I director and put him on its Nominating and Corporate Governance Committee. He served until 2019. The same year he joined the board of a small videoconferencing company founded by Eric Yuan. Yuan was an engineer from China who had spent years at Cisco building a product he believed customers disliked, and he left to build the one he thought they deserved. Emergence had been Zoom's first institutional investor too, and Zoom, like Veeva, never used Emergence's money. In 2022 the two men sat together onstage at an Emergence summit, interviewed by the hosts of the Acquired podcast about capital-efficient growth. They had something in common that went beyond the investor: both were engineers who had spent long careers inside larger companies and left with a precise, nearly technical complaint about what those companies had gotten wrong.
Money You Don't Touch
Look at the money closely, because it is where the story turns strange.
"Emergence was lucky to be the first institutional investor in both companies," Jake Saper of Emergence wrote in 2022 of Veeva and Zoom, "and neither used any of the money they raised from us." Read that again. The $4 million wired in June 2008, the bet that most investors had passed on, was not spent. It sat. Veeva was profitable early enough and grew on its customers' payments fast enough that the venture capital served as insurance. Ritter's 2019 accounting gives the total capital consumed in building the company as about $3 million. SaaStr's introduction to Gassner's 2017 podcast appearance says "just $4m in capital raised." The two numbers differ slightly, but they point to the same astonishing fact.
Set that $3 million against the fiscal 2026 results. Revenue was $3.195 billion, operating income $916 million, and net income $908 million. Total equity was $7.214 billion. Roughly speaking, Veeva now earns about a thousand dollars of annual revenue for every dollar of capital it ever burned. Few software companies of the cloud era come close.
The IPO came in October 2013 on the New York Stock Exchange, and the shares nearly doubled on the first day of trading. The Wall Street Journal called it a win for biotech cloud software. That framing would have amused the friend with the pie chart, since there had been no category called "biotech cloud software" until Veeva created it. In March 2019, Gassner told Jim Cramer that Veeva had reached $1 billion in revenue "a year ahead of our target." By the end of that year it had more than 3,000 employees and a market capitalization above $20 billion, and the stock had more than quintupled in three years.
The capital efficiency was not a philosophy he dressed up for conference panels. It was closer to a reflex, the reflex of a man who had once been left on a road with the clothes on his back, or of a machinist's son for whom every cut is irreversible. Raised capital that you do not spend is still yours to spend later. Capital you have spent is gone. The asymmetry is the same one he learned on the roof.
Then comes the ironic note, which keeps the story honest. In October 2025, Paragon Intel, a firm that sells management assessments to hedge funds, published a short summary of its research on Gassner under the headline "CEO Gassner's Tech Vision to Drive CRM Migration Despite Financial Questions." The analysis gave him high marks for technical vision and hands-on product leadership. It also raised "questions about financial discipline," and asked how he would "balance his visionary, product-first approach against the financial discipline needed to protect margins." The man whose company never touched its venture money, and who built a $3 billion business on $3 million, is now asked by the public markets whether he spends too freely. Both things can be true. A company that earns $900 million a year can afford product bets that a company with $4 million in the bank cannot, and the instinct that once refused to spend can turn into an instinct to build, which costs money. Still, there is something nearly comic about the founder of the most capital-efficient company of its generation being audited for thrift.
What Not to Do
— Peter Gassner, to Investor's Business DailyIn a horse race, you should pay attention first to your own horse. You can't control the other horses.
He calls himself a "focuser." That is his word, and he means it seriously, almost clinically. "The hardest thing," he told IBD, "is to pick what not to do," especially "if you're surrounded by optimists with promising ideas to grow the business." When something goes wrong at Veeva, the question he puts to colleagues looks inward, not out at the competition: "What can we change about our processes, people or product?" That, he said, is "better than focusing on what others are doing."
"I'd rather be really good at some things than be average at a lot of things," he said. "When you're excellent at a small set of things, your customers depend on you, and your employees feel good about what they do."
That sentence holds the whole theory of the firm. Excellence in a narrow area produces dependence: customers who cannot easily leave, because the thing you do for them is something they cannot get elsewhere at that quality. It also produces pride, in the form of employees who stay seventeen years. Both are kinds of retention, and both come from turning down breadth.
The obvious problem with a company built on saying no is figuring out when to say yes. By 2010 the CRM product was a hit. Gassner and his team decided to build a second product line, a bet as large as the first, because it meant leaving the Force.com platform that had made the first one possible. Veeva Vault, launched on February 15, 2011, was a regulated content management system for life sciences. It was built on Veeva's own technology and aimed at a part of the pharmaceutical business far from the sales reps: the vast, document-heavy, inspection-sensitive world of clinical trials, regulatory submissions, and quality control, where one misfiled document can bring an FDA warning letter.
This was measure-twice thinking in practice. Veeva did not jump to a second product at the first sign of success. It waited until the first one had earned the company the credibility, cash, and customer relationships to try. It then picked an adjacency close enough to share customers and far enough away that the company would learn to build infrastructure of its own. In hindsight, Vault was the start of the long move off someone else's platform.
From there the expansion went outward, carefully, one ring at a time. In August 2017 Gassner told Cramer about a push into quality. In October 2018 he described a move from pharma toward cosmetics and consumer goods, industries with their own regulatory paperwork and their own document problems. Acquisitions were few and specific: Zinc Ahead, a content management rival, in October 2015; Crossix, a privacy-safe patient data and analytics company, in October 2019; Physicians World, a business process outsourcing provider, a month later; Learnaboutgmp, compliance training, in August 2021; Veracity Logic, clinical trial randomization and supply software, that December. Each one filled a specific gap in a specific workflow. There were no splashy platform deals and no moves into horizontal markets. He was paying attention to his own horse.
The scale of the result is visible in a single hotel ballroom. In September 2023, Veeva's R&D and Quality Summit in Boston drew more than 2,500 people, with more than a hundred customer speakers. That is roughly what happens when a company that once had fewer people than a customer's meeting delegation becomes the place where an industry meets.
By 2017, ten years in and at about 1,700 employees, he could describe the destination in a single phrase that would later spread across a whole category: "We're building the industry cloud for life sciences." Then, more specifically: "We want to be essential and appreciated to every CEO in the life sciences industry."
The two words carry different weight. Essential is the dependence that comes from excellence at a narrow thing. Appreciated is more unusual in a vendor's mission statement, and stranger. It suggests he wanted customers to need Veeva without resenting it. The next section is about the gap between those two words and how he tried to close it in writing.
Papers
The documents never fit.
When Veeva incorporated in 2007, it did so as an ordinary for-profit corporation, because in 2007 there was essentially nothing else available. Its charter contained the usual implicit command of American corporate law, the one generations of business school students have learned to treat as natural: maximize value for shareholders. Everything else, including customers, employees, and the wheelchairs and sanity of patients, mattered only as means to that end.
— Paul Shawah, Veeva SVP of commercial strategy, to Clinical Leader, February 2021PBCs did not exist when he founded the company, so Veeva became a traditional for-profit corporation focused on shareholders. Peter was never comfortable with that, so he tried to align our values and our decisions with our employees and customers.
For thirteen years Veeva ran on an informal workaround. Whenever a decision came up, large or small, people asked whether it was good for employees and customers as well as investors. The company wrote down four core values — do the right thing, customer success, employee success, speed — and in its own corporate citizenship statement it glossed the first one this way: "Doing the right thing means that we are concerned about more than just financial success and return to shareholders." But a values statement on a website is not a charter. When Eric Ries interviewed him in 2026, the host's summary named the problem precisely: "his discomfort with founding documents that prioritized shareholder returns."
This is where the passport comes back. A young man loses the document that says who he is. He spends the rest of his life building things that are what they appear to be: a database that keeps its promises, a CRM that sales reps actually use, a company where executives stay. Then he finds that the most important document about his company, the one that defines what the company legally is, describes something he did not build.
The fix took about two and a half years. In 2020 Veeva began laying out publicly its case for becoming a public benefit corporation, a for-profit company that has also adopted a public benefit purpose and is legally required to balance that purpose and the interests of affected stakeholders against shareholder returns. Gassner discussed the idea with Ed Hammond at Bloomberg News. The company posted an explanation on its website that is notable for how unsentimental it is. "We see a conversion to a PBC as beneficial to our long-term financial results," it said. "It can give customers even greater confidence that our interests are not only well aligned today but will remain that way. We also believe a PBC structure will help us attract more talented people to Veeva."
That is the Gassner move. The case for stakeholder obligation was not made in the language of virtue. It was made in the language of retention. Customers stay longer when they trust that you will not turn on them under a new owner or a new quarterly target, and talented people come when the company's commitments to them are legally binding instead of a matter of the founder's mood. "Appreciated" turns out to be a business strategy. It is one he happens to believe in for other reasons too.
The shareholders agreed. Ninety-nine percent of votes cast supported the conversion. On February 1, 2021, almost exactly fourteen years after the offer letter, Veeva became the first publicly traded company to convert to a public benefit corporation. Its stated purpose is "to help make the industries we serve more productive and create high-quality employment opportunities."
"From an operational standpoint," Shawah told Clinical Leader, "there will be no noticeable change in how the company conducts business." That was the point. The charter had finally caught up with the company. "We feel we are correcting a disconnect that we always felt existed."
Some of the most consequential effects were also the least visible. In his conversation with Ries, Gassner described how the new structure made it possible to provide free software to clinical research sites, the hospitals and clinics where trials actually happen. Under a pure shareholder-primacy reading, that kind of giveaway is hard to justify. Under a charter that names the productivity of the industry as a purpose, it is close to obligatory.
The same thinking shows up in Veeva's treatment of employees, where the company's documents read less like HR policy than like a small political philosophy. "Employees are people," the corporate citizenship statement begins, with the bluntness of someone tired of the alternative. "They have free will and work at Veeva by choice. They are responsible for the direction of their own lives and careers. At Veeva, we advocate the idea of 'captaining your own ship.'" Any employee can apply for any internal job at any time without a manager's approval. Veeva requires no non-compete agreements. It has also gone to court against other companies' use of them, most visibly against Medidata Solutions, a rival in clinical trial software, which had sued Veeva over employees who moved from one company to the other.
When a federal court dismissed that suit, Gassner posted about it on LinkedIn in language that is, by his standards, nearly heated: "Federal court dismisses Medidata Solutions baseless lawsuit against Veeva Systems. A victory for innovation and #employeerights. Employees should have the freedom to change jobs and customers deserve access to new innovation. It's time to ban #noncompete that stifle the economy."
The man who once stood on a Malaysian road without papers to prove where he was allowed to go has built a company whose employee policy amounts to: you may go anywhere. Whether those two facts are connected, I cannot say. He has never said so. They sit next to each other anyway.
Leaving the House You Built On
In March 2017, beneath the SaaStr page for his podcast episode with Harry Stebbings, a commenter named ras marek left a complaint that was more barbed than most: "harry, way too many softball questions. for example, why not ask peter if he's such a 'technology' person, why is veeva essentially a rebranded salesforce crm?"
It was a fair question, and in 2017 the honest answer was: partly, yes. The original CRM ran on Force.com. Salesforce had provided the infrastructure in exchange for royalties. Veeva's flagship product, the one that won it the industry, lived in a building owned by a much larger and more aggressive landlord, and the landlord had noticed how much the tenant was earning.
The separation was slow and then sudden. Vault had been the first move off the platform in 2011. Over the following decade Veeva built more and more of its product line on its own technology, until the CRM was the most important thing still sitting on someone else's infrastructure. Then the landlord moved in next door. In December 2024, Bloomberg reported that Salesforce was "stok[ing] Veeva fight by snagging drug customers," building a competing life sciences CRM and courting Veeva's customers directly. In 2025 the partnership ended. Wikipedia describes Salesforce, without apparent irony, as "a competitor."
What followed is the riskiest operation Gassner has attempted since he answered the man in the conference room. Veeva is migrating its CRM customers from the Salesforce-based product to Vault CRM, which runs on its own platform. Paragon Intel counted a target of 200 customers for the migration and treated its execution, "against intense competition from Salesforce," as the central question about Veeva's management. The apprenticeship has come full circle. Gassner spent his twenties and thirties learning platforms from the inside so that he could build on someone else's with unusual skill. He has spent his fifties and early sixties making sure he would not have to.
He also made peace somewhere he had long been at war. For years Veeva had been in disputes with IQVIA, the giant of pharmaceutical data and contract research, over data access, competition, and the lawsuits that follow from both. One industry observer, commenting on the eventual settlement, said he had been "watching this unfold since 2013." In 2025 Gassner announced on LinkedIn "resolution of all disputes and long-term clinical and commercial partnerships." Typically, he framed it from the customer's side: "This partnership is great news for customers who can now use software, data, technology, and services from Veeva and IQVIA together in a simple and efficient way." Another commenter, an industry consultant, pointed out that the long dispute had likely left customers with "sub-optimal architectures" for years, and wished both companies had put customers first sooner. That is fair too. Essential and appreciated is easier to write in a charter than to practice against a rival who controls data your customers need.
Paragon's interviews with Gassner's former colleagues turned up one more finding, which may say more about him than anything in this account. The biggest risk to Veeva, these people believed, was not the break with Salesforce. It was his eventual retirement. He is sixty-one. The temporary CEO who expected to hand the job off and return to product has held it for nineteen years. In March 2026 Veeva paid $100 million for Ostro, a company that uses AI agents to handle conversations between pharmaceutical brands, patients, and physicians. The founder of the industry cloud is now placing a bet on the next platform transition, the fourth of his career, as AI arrives in the industry he has spent two decades making legible.
In August 2017, between the SaaStr talk and the Cramer interview about quality, Gassner gave a TEDx talk at Amador Valley High School in Pleasanton. His older son, Filaa, had been a sophomore there six years earlier. The title was "You Will Be Fine: A Handbook for High School Freshmen." The program summary says he told the students that life is not a race, and that they should stop worrying so much about getting into college and concentrate on their own goals and interests, their families, and their community. It was a strange message for a room full of Bay Area teenagers, and an even stranger one from a billionaire. It was also the life he had lived: six years to finish a four-year degree, a trekking guide's job in Thailand, a stolen passport, a company started at forty-two, a CEO title he did not want.
Under one of his LinkedIn posts about the 2023 Summit, an old acquaintance named Joseph Sliger left a comment: "You're a long ways from carp valley, my friend." I do not know where or what Carp Valley is. Gassner did not reply in public. He rarely does.
What we do know is how the company found its first office. In 2007 he and his neighbor Mitch Wallace were looking for space. Both of Gassner's sons were in the Spanish dual-immersion program at Valley View Elementary. One morning, driving them there, he noticed a rental sign at 309 Ray Street.
The building sat between the school and the house.
Part IIThe Playbook
What follows distills Gassner's methods into principles. They are drawn from the record above, not from his own self-description, which tends to be modest to the point of being unhelpful. Some of these principles are counterintuitive, and a few go against the dominant culture of venture-backed software. All of them are things he has actually done, and most were done long before anyone thought to call them strategy.
The principles
- 1.Apprentice at the platform layer.
- 2.Bet against the pie chart.
- 3.Start where value can be proven.
- 4.Earn the long horizon with a short one.
- 5.Treat raised capital as insurance, not fuel.
- 6.Make the job instead of taking it.
- 7.Pick what not to do.
- 8.Expand in rings, one adjacency at a time.
- 9.Make your documents tell the truth.
- 10.Let your people leave.
- 11.Rent the platform, plan the exit.
- 12.Make the customer the reason for peace.
Principle 1
Apprentice at the platform layer
The usual founder story treats prior employment as something to escape. Gassner treated it as training, and he picked his employers by the platform shift each one was riding: IBM and the relational mainframe, PeopleSoft and client-server, Salesforce and the cloud. Each time he worked on the substrate, not the applications. He worked on DB2, then PeopleTools, then Force.com. When he started Veeva, his deepest advantage was not knowledge of pharma, which his co-founders supplied. It was knowledge of how the platform he planned to build on actually worked inside.
Gordon Ritter's explanation of why Emergence invested when others would not is, at bottom, a description of this advantage: "They were forgetting that Peter built the platform and that he knew the details and knew the internals." What looked like platform risk from outside looked like home-field advantage from inside. The investors who passed were judging the plan. Ritter was judging the apprenticeship.
P
Three Platforms Before His Own
Gassner's career followed the major transitions in enterprise computing, always at the infrastructure layer.
1989
Graduates from Oregon State; joins IBM's Santa Teresa lab to work on DB2 alongside the inventors of System R.
1994
Moves to PeopleSoft in late 1994 as client-server takes off; becomes Chief Architect and GM of PeopleTools, leading roughly 450 people.
2003
Joins Salesforce.com as SVP of Technology, helping build what becomes Force.com.
2007
Signs offer letter with Veeva on or about January 29; the first product is built on Force.com.
2011
Vault launches on February 15, Veeva's first product on its own technology.
2025
Salesforce partnership ends; migration of CRM customers to Vault CRM begins.
Tactic: Before you start a company, spend years at the infrastructure layer of the platform you plan to build on, so that what outsiders call risk is, for you, simply known.
Principle 2
Bet against the pie chart
The friend's pie chart was not wrong. It accurately measured a market that, as currently counted, was too small to matter. Gassner's insight was that the counting itself was the problem: "Most of the market is not even categorized because it's on custom stuff somewhere that nobody is counting." Vertical markets look small in analyst reports because their spending is scattered across custom builds, consultants, spreadsheets, and legacy vendors, none of which show up under a single heading.
The deeper point is about consensus. "If you are doing something that most people think is impossible, but you think it could be possible,…then you are ahead of the game." Widespread skepticism, when you have specific technical reasons to disagree with it, is a free and temporary moat. The danger, which he avoided, is confusing contrarianism with insight. Gassner's bet against the chart rested on knowing Force.com and knowing CRM. It was not a mood.
Tactic: When a market looks too small, find out where its spending is currently hidden, in custom software, services, and workarounds, before you accept the size anyone has assigned it.
Principle 3
Start where value can be proven
Veeva could have started anywhere in the pharmaceutical value chain. It started with sales reps, and that choice was less obvious and more deliberate than it looks. Eli Dukes's analysis gets at the logic. Cost-reduction software has diffuse, contestable benefits that are hard for a startup to prove. Revenue software has direct, visible benefits that users are happy to talk about. A CRM that drug reps actually use turns quickly into reps who sell more, and those reps tell their peers.
That provability fed Veeva's capital efficiency directly. Satisfied customers referred Veeva to other companies, so the expensive enterprise sales motion that usually consumes venture capital was partly replaced by word of mouth. Only after the commercial wedge had earned credibility did Veeva move into the harder-to-prove areas of clinical, regulatory, and quality, where switching costs are far higher and the relationships last for decades.
Tactic: Pick a first product whose value shows up on a line the customer already measures, so that your customers will make your case for you.
Principle 4
Earn the long horizon with a short one
Gassner is now held up as a model of long-term thinking: an industry cloud, a public benefit charter, patient multi-decade relationships with customers. He did not start that way. For roughly the first eighteen months, Veeva thought in ninety-day increments, without a five-year plan.
The order matters. A long vision held by a company that has not yet proven it can execute is just a hypothesis with a slide deck. A short horizon forces contact with reality every quarter: a real customer, a real release, a real hire. Only after enough of those quarters have piled up does the long view become something other than wishful thinking. Even now he says he spends about 90 percent of his time on execution. The vision gets the remaining ten.
Tactic: For your first year and a half, plan in ninety-day blocks and refuse to let the long vision take time from the next quarter's customer.
Principle 5
Treat raised capital as insurance, not fuel
Emergence invested $4 million in June 2008, and Veeva never used it. Ritter's tally of the total capital consumed to build the company is about $3 million. Against fiscal 2026 revenue of $3.195 billion and net income of $908 million, that ratio is nearly without precedent in modern software.
The underlying view is that capital you have raised but not spent keeps all its value as an option, while capital you have spent is gone. A company that grows on customer payments is forced to build things customers will pay for, which is a discipline no board can supply. It also keeps control, since an unspent venture check comes with far less pressure than a burning one. This is the machine shop logic again: the irreversible cut is the expensive one.
The Paragon Intel critique deserves to be taken seriously here as a counterweight. A founder who has internalized frugality can, once the company is rich, swing the other way and fund product ambitions with less scrutiny than a cash-poor startup would apply. Capital efficiency is a habit, and habits can be lost.
$
The Capital Ledger
Veeva's capital consumption compared with its scale, using figures from Emergence Capital and the fiscal 2026 annual report.
| Measure | Figure | Source context |
|---|---|---|
| Emergence investment | $4 million (June 2008) | Never used, per Emergence's Jake Saper |
| Total capital used | ~$3 million | Gordon Ritter, December 2019 |
| Revenue milestone | $1 billion | Reached "a year ahead of our target," March 2019 |
| FY2026 revenue | $3.195 billion | Form 10-K, March 2026 |
| FY2026 operating income | $916 million | Form 10-K, March 2026 |
| FY2026 total equity | $7.214 billion | Form 10-K, March 2026 |
Tactic: Raise the money that buys you safety, then run the company as though you had not raised it, and let customer payments decide what you build.
Principle 6
Make the job instead of taking it
Gassner took the CEO title expecting failure, or, if Veeva succeeded, expecting to hand the role to someone else and return to product. Neither happened, and his response is the most useful thing he has said about leadership: "As CEO, you can make the job — and you should make the job."
In practice, making the job meant subtracting. He travels 20 percent of the time or less. He skips most events and dinners. He has no speaking tour and had not heard of the Crunchies. The company stayed in Pleasanton instead of moving to San Francisco. What was left was the work he was best at, which is product direction and execution. His reluctance turned out to be useful, because a founder who never wanted the CEO's ceremonial duties had no attachment to them and dropped them without regret.
C
The Conventional CEO vs. the Gassner Model
What Gassner subtracted from the role, and what he kept.
| Conventional expectation | Gassner's practice | Effect |
|---|---|---|
| Heavy travel and industry presence | 20% or less of time traveling | Focus |
| Accept every dinner, event, and panel | Selective; "not on the traditional speaking tour" | Focus |
| CEO as delegator of product | CEO as de facto head of product | Leverage |
| Headquarters in the startup capital | Pleasanton office park | Retention |
| Founder replaced at scale | Nineteen years and counting | Key-person risk |
Tactic: List the CEO duties you dread, cut or delegate every one that does not directly serve customers or product, and treat the role as something you design.
Principle 7
Pick what not to do
"The hardest thing is to pick what not to do," Gassner says, and the difficulty is specific: the threat to a successful company is not bad ideas but promising ones, pushed by optimists. His defense is a deliberate narrowing of attention. He pays attention to his own horse, and when something goes wrong he asks what Veeva can change about its "processes, people or product," not what competitors are doing.
The payoff he describes has two parts. "When you're excellent at a small set of things, your customers depend on you, and your employees feel good about what they do." Customers depend on you, and employees take pride in the work: two kinds of retention, both produced by declining to spread out. The long executive tenures at Veeva, several between thirteen and seventeen years, are the visible result of the second.
Tactic: Keep a written list of attractive opportunities you have decided not to pursue this year, and review it each quarter to keep yourself honest about focus.
Principle 8
Expand in rings, one adjacency at a time
Veeva did not jump to a second product at the first sign of success. It waited until the CRM was clearly working, in 2010, and then built Vault. Vault was close enough to share customers and credibility, and different enough, being regulated content on Veeva's own technology, to teach the company a new set of capabilities. Everything after that followed the same measured pattern: quality, then consumer goods and cosmetics, then a few targeted acquisitions, each filling a specific gap.
The rings matter because each one is earned by the previous one. Trust built in commercial software opened the door to clinical work. Content management opened quality. Data from the Crossix acquisition strengthened the commercial cloud. The Ostro acquisition puts AI on top of all of it. Measure twice, cut once, applied to a product roadmap.
R
The Expansion Rings
How Veeva moved outward from a single wedge product.
| Year | Move | Phase |
|---|---|---|
| 2007 | Pharma CRM on Force.com | Wedge |
| 2011 | Vault regulated content management, on Veeva's own technology | Expand |
| 2015 | Acquires Zinc Ahead, a content management rival | Expand |
| 2017–2018 | Push into quality; extension toward cosmetics and consumer goods | Expand |
| 2019 | Acquires Crossix (privacy-safe patient data) and Physicians World | Data |
| 2021 | Acquires Learnaboutgmp and Veracity Logic | Expand |
| 2025 | Salesforce partnership ends; Vault CRM migration | Risk |
| 2026 | Acquires Ostro, AI agents for brand engagement, for $100 million | Data |
Tactic: Launch your second product only after the first clearly works, and choose one that shares your customers but forces you to build a capability you lack.
Principle 9
Make your documents tell the truth
For thirteen years Veeva's charter said one thing and its decisions said another. Gassner "was never comfortable with that," and once public benefit corporations became available he spent about two and a half years making the legal structure match the company. The conversion took effect February 1, 2021, with 99 percent of votes cast in favor.
What stands out is how the case was made. Veeva did not argue from virtue. It argued that the structure would help long-term financial results, by giving customers confidence that alignment would last and by helping recruit talent. The public benefit purpose, making industries more productive and creating high-quality jobs, was presented as a competitive advantage, and in practice it opened options, such as free software for clinical research sites, that pure shareholder primacy would have made hard to justify.
Tactic: Read your company's founding documents next to its last ten real decisions, and if they disagree, change the documents.
Principle 10
Let your people leave
Veeva requires no non-compete agreements. Any employee can apply for any internal role without a manager's approval. The company has fought other firms' non-competes in court, and when the Medidata suit was dismissed, Gassner called non-competes something that "stifle[s] the economy." The philosophy rests on a blunt premise: "Employees are people. They have free will and work at Veeva by choice."
This looks generous, and it is also strategic. A company that cannot hold people by contract has to hold them by being a place worth staying, which is a much more durable kind of retention. The executive roster, with leaders at thirteen, fourteen, fifteen, and seventeen years, suggests the approach works. Open doors in both directions also mean Veeva can hire talent that competitors try to fence in.
Tactic: Remove every contractual barrier to leaving and measure how many people stay anyway, because that number shows whether you have earned them.
Principle 11
Rent the platform, plan the exit
Building on Force.com in 2007 was the right call. Gassner knew it better than anyone, it saved years of infrastructure work, and Salesforce supplied it for royalties. It also left Veeva's most important product sitting on a larger company's ground, and that company eventually built a competing life sciences CRM and went after Veeva's customers. The partnership ended in 2025.
What Gassner did well was start the exit fourteen years before he needed it. Vault, launched in 2011, was the first product on Veeva's own technology, and the platform it introduced is the one the CRM is now moving to. The migration is still Veeva's largest current execution risk, but it is a migration onto infrastructure that had a decade to mature, not an emergency rebuild. A borrowed platform is a fine place to start and a dangerous place to stay.
Tactic: If you build on someone else's platform, begin building your own the moment your first product succeeds, long before the landlord turns into a competitor.
Principle 12
Make the customer the reason for peace
Veeva and IQVIA spent years fighting, in court and in the market, over data and competition. When they settled in 2025, Gassner presented it entirely from the customer's side: customers "can now use software, data, technology, and services from Veeva and IQVIA together in a simple and efficient way." Some observers pointed out that customers had paid for the war in the form of awkward architectures. That criticism is part of the lesson.
A public benefit corporation that says it serves the productivity of an industry cannot comfortably keep fighting a battle whose main casualties are that industry's systems. The settlement is where the charter's language was tested against a real decision. The principle is not "avoid conflict," since Gassner has fought plenty. It is to judge each conflict by what it costs the people you say you serve, and to end it once that cost outweighs whatever the fight is protecting.
Tactic: For every long-running dispute with a competitor, estimate its cost to your shared customers each year, and settle once that figure exceeds the value you are defending.
Free playbook
Get The Business Model Playbook
58 business models, one visual page each: how the money flows, the metrics that matter, and who runs it. Free when you join the Faster Than Normal email.
Free. No spam. Unsubscribe anytime.
Part IIIQuotes and Maxims
In their words
— Peter Gassner, to TechCrunch, 2017Starting Veeva, I had the idea or vision you could make very industry-specific software in the cloud and it would be bigger than anyone would have thought. In 2007, [most] people thought that was incorrect.
— Peter Gassner, to TechCrunch, 2017I wasn't [ever] discouraged. I was encouraged. If you are doing something that most people think is impossible, but you think it could be possible,…then you are ahead of the game.
— Peter Gassner, at the Emergence Capital CEO Summit, 2019What I really didn't realize before was that as CEO, you can make the job — and you should make the job.
— Peter Gassner, to Investor's Business DailyI'd rather be really good at some things than be average at a lot of things. When you're excellent at a small set of things, your customers depend on you, and your employees feel good about what they do.
— Peter Gassner, on LinkedIn, after the dismissal of Medidata's lawsuit against VeevaEmployees should have the freedom to change jobs and customers deserve access to new innovation. It's time to ban #noncompete that stifle the economy.
Maxims
- Learn the substrate first. The founder who has built the platform can see opportunities in it that outsiders can only call risks.
- Distrust the pie chart. A market that looks too small is often one whose spending nobody has bothered to count.
- Prove revenue before you promise savings. Start where customers can see your value on a line they already measure.
- Ninety days before ten years. A short horizon earns a long vision the right to be taken seriously.
- Unspent capital is still an option. Raise for safety and grow on what customers pay you.
- Design the role. A CEO can delete the parts of the job that do not serve the work.
- Watch your own horse. When something breaks, fix your processes, people, or product before looking at competitors.
- Measure twice, cut once. Spend your attention before the irreversible decision, not after it.
- Let the charter match the conduct. If your founding documents describe a company you are not running, rewrite them.
- Open the doors. People who are free to leave and stay anyway are the only retention worth having.
