/
.webp)
Generated by Master Biographer | Source for LinkedIn Content
The number was $35 million.
That's what Fred Luddy's stake in Peregrine Systems was worth at its peak. Not theoretical paper money — real accumulated wealth, built across thirteen years of writing code, shipping products, and serving as the company's Chief Technology Officer. Thirteen years of being the person who actually built the thing.
Then, in 2002, it became zero.
Not because the market turned. Not because a competitor beat them. Because Peregrine's executives — the CEO, the CFO, the head of sales — had been systematically lying. Inflating revenues. Fabricating deals. Booking transactions that hadn't happened. The SEC would later call it one of the largest accounting frauds in San Diego history. The company restated eleven consecutive quarters of financials, slashing more than $500 million off its previously reported revenue of $1.3 billion. Four billion dollars in shareholder equity evaporated. The CEO, Stephen Gardner, would eventually receive a prison sentence of eight years and one month.
Fred Luddy had nothing to do with it.
He just built the product. For thirteen years, he built the product.
He was 49 years old. He was, effectively, broke. He had spent his entire adult life — the bulk of his career, the best years of his technical prime — inside the world of IT service management. And now that world was radioactive. His company's name was synonymous with fraud. His $35 million was gone.
He told himself he would never, ever, ever go back into the IT service management industry.
His definition of "never" turned out to be about nine months.
To understand what Fred Luddy built, you have to understand where Fred Luddy came from. Because nothing about it was supposed to happen.
He was born November 24, 1954, in Hammond, Indiana. Oldest of four children. His father was an accountant — precise, disciplined, and by multiple accounts, verbally and physically abusive. He told Fred, repeatedly, that he was stupid. That he would never amount to anything. His mother was a Catholic schoolteacher — loving, but emotionally distant in the way people become when they're also surviving.
In adulthood, Fred Luddy would be diagnosed with Asperger's syndrome. Looking back, it explains a lot about his childhood — the social difficulty, the obsessive focus, the feeling of operating on a different frequency from everyone around him. Growing up in suburban Indiana in the 1960s, none of that was diagnosed. It was just called being strange.
At 16, he left.
He got in his parents' station wagon and drove straight to California. No plan. No connections. He camped along the way. When he arrived, he became a strawberry picker — because you got paid in cash at the end of the day. He washed cars. He found work that was simple and immediate, where the reward was proportional and the outcome was certain.
Eventually, he came back. He got his GED. In 1972, at age 18, he took a job at a machine shop at a folding door factory in New Castle, Indiana. The factory had recently purchased a computer. Fred Luddy asked if he could work with it. They gave him a book on programming and told him to see what he could do.
He taught himself Fortran overnight.
By morning, he had working code. By 1973, he was at Indiana University, writing Fortran programs for the dean of economics at $3.50 an hour — and working 50 to 60 hours a week because the dean told him he could work as many hours as he wanted. He dropped out after his freshman year. Not because he failed. Because he couldn't stop programming long enough to attend class.
He never went back to college.
Over the next decade, he assembled a career through sheer technical obsession. Amdahl Corporation in California, developing performance monitoring software. Boole & Babbage, consulting on mainframe automation. In the late 1980s, he co-founded Enterprise Software Associates, building mainframe-based IT management tools. He was good at one specific thing: making the machinery of enterprise IT work better. Faster. Less painful.
In 1990, Peregrine Systems hired him as CTO.
He stayed for thirteen years. He built AssetCenter, one of the first serious IT asset management platforms. He oversaw the acquisition of Remedy Corporation — the help desk software company — for a billion dollars in stock. He watched the company grow from $4.5 million in annual revenue to over $500 million. He accumulated $35 million in personal wealth.
And then he watched someone else burn it all down.
The thing about having Asperger's and a childhood shaped by an abusive father telling you you're stupid is that you develop a very specific relationship with competence. You learn that you can trust what you build with your hands. You learn that the code either works or it doesn't, and no one can take that from you.
So when Peregrine collapsed, Fred Luddy did the only thing that made sense to him.
He opened a new file.
Two weeks before his 50th birthday — he would later admit there was something psychological about the deadline, a refusal to become a first-time founder at 50 — he incorporated a company in California. He called it Glidesoft, Inc. The year was 2004.
He worked alone.
The vision was architectural. He had spent thirteen years watching enterprise IT software be deployed in the worst possible way: months of implementation, armies of consultants, painful on-premise installations that required dedicated infrastructure teams just to maintain. Every upgrade was a major project. Every integration was a negotiation. The software was expensive, brittle, and hostile to the people who used it.
His drive, he would later say, had always been about one thing: "putting a smile on someone's face because their lives got a little less painful."
The existing software — including the software he had built — did not put smiles on people's faces.
The insight he arrived at was, in technical terms, almost embarrassingly simple. What he was building was, as he described it, "just a forms-based workflow on top of a database." The real innovation wasn't in what the software did — it was in how it was delivered. Cloud-based. No servers to manage. No upgrades to schedule. No consultants required for deployment. The software just ran.
This was 2004. Salesforce had demonstrated the concept of cloud-delivered software for sales teams, but the enterprise IT market was deeply conservative. The idea of running mission-critical operations on someone else's infrastructure seemed reckless to most IT managers. Luddy bet otherwise.
He also did something counterintuitive: he initially gave the software away for free. To gather feedback. To get real customers using it and telling him what was broken. He understood, from thirteen years at Peregrine, that the gap between what enterprise software promised and what it actually did for users was enormous. He wanted to close that gap before he started charging.
From mid-2004 to mid-2005, Luddy was the only employee.
In mid-2005, JMI Equity invested $2.5 million. Five more people joined the company. By 2006, Glidesoft was renamed Service-Now.com.
The product was spreading — not through sales teams, but through word of mouth between IT departments. A manager would try it. Their team would stop complaining about the help desk system. Other managers would ask what they were using.
ServiceNow's customers, Luddy would later say, "actually asked us if they could talk to our prospects."
The early customers are often the most revealing test of a company's real potential. They show you not just whether the product works, but what it can become.
CERN — the European Organization for Nuclear Research, the people running the Large Hadron Collider — built an entire site management suite on top of ServiceNow. From their platform, a visiting researcher could use ServiceNow's service catalog to request anything: a desk lamp. Access to restricted research data. Entry to the particle accelerator.
They were also winning Edmunds, Qualcomm, Deutsche Bank, Intel, Johnson & Johnson, and UBS.
These weren't IT departments looking for a cheaper help desk ticket system. These were sophisticated technology buyers who saw something in Luddy's architecture that the existing ITSM market had not provided: a genuine platform. Not just a tool for IT — but a layer of workflow automation that could run anything. Any request. Any approval chain. Any process where one person needed something and another person needed to respond.
The technical insight was embedded in a deceptively simple design decision: seat-based licensing with no seat caps. IT could deploy ServiceNow. But if HR wanted it too, or marketing, or legal — there was no structural barrier. The IT manager who loved the product became an internal advocate. The platform spread organically through organizations, department by department, use case by use case.
In 2009, Sequoia Capital led a Series D funding round. Partner Pat Grady had identified what Luddy had built: not a help desk replacement, but the beginning of a workflow automation layer for the entire enterprise.
Doug Leone, Sequoia's managing partner, met with Luddy and asked what valuation he wanted.
Luddy named his number.
Leone hit the bid without negotiating.
By 2011, ServiceNow was growing fast enough to be buried under its own success.
The infrastructure was held together with the technical equivalent of tape. The company's cloud platform — the cloud platform that was supposed to make enterprise IT simple — was running on hardware that included, in some configurations, used Dell servers sourced from eBay. When Deutsche Bank started seriously using the platform, the outages began. Not minor glitches. Serious, unexplained failures that had no good explanation for an enterprise banking client.
Frank Slootman, the enterprise software executive who had run Data Domain and built it to an acquisition by EMC for $2.4 billion, agreed to meet with Sequoia about the CEO role.
His first impression of ServiceNow was that it was, in his words, "the most boring business on the planet."
But the velocity was real. The customers were evangelical in a way he hadn't seen. So he took the job.
His assessment within weeks: the company was approximately 90 days from going out of business due to infrastructure instability.
"I didn't think we were going to live through this," Slootman said. "There are no good explanations. This is insanity."
Within his first 90-120 days, Slootman made a decision that created immediate cultural friction — he fired someone over sports tickets, a demonstration to the entire organization that executive directives were not suggestions. Luddy, watching this, called Doug Leone.
"This isn't working," he said.
"Give it 90 days," Leone told him.
VP of Engineering Dan McGee solved the infrastructure crisis through homogenization — standardizing the software stacks across all systems, eliminating the patchwork of incompatible configurations. The outages stopped.
Slootman then did something equally important: he repositioned the product. ServiceNow wasn't a help desk replacement. It was, in his framing, "the ERP for IT." That repositioning changed the sales conversation. Instead of selling to help desk teams — small budgets, narrow scope — ServiceNow was now selling to entire IT organizations. The available licenses per customer multiplied 40 to 50 times.
Fred Luddy stepped aside as CEO, moved into the Chief Product Officer role, and returned to what he'd always been best at: building.
"I don't have the skills to be CEO," he said, "and furthermore, I have no desire to acquire them."
December 2011. ServiceNow is growing rapidly, but the IPO hasn't happened yet. VMware, then one of the dominant forces in enterprise technology, approaches with an offer.
$2.5 billion.
Both Slootman and Luddy were inclined to accept.
Luddy explained his reasoning later with an honesty that few founders would admit publicly: "At the time, I was about 55 years old. I'd been bankrupt twice. This is a chance to be not bankrupt."
The board convened. Leone was in Hawaii on vacation. He got the call.
What happened next was a masterpiece of corporate governance judo.
The board initially argued that private companies didn't need to run a process before accepting an acquisition offer. Leone, from Hawaii, made one phone call: to Bill Chandler, a Wilson Sonsini attorney who had literally written the Delaware law governing private company sale processes. Chandler called into the board meeting.
The deal was effectively dead.
"I knew that then and there, I killed the M&A transaction," Leone said.
Luddy later reflected on it: "I'm glad that he was right about the 10 Bagger, which is almost one tenth of what we're valued at now."
June 29, 2012. Fred Luddy stood on the floor of the New York Stock Exchange and watched ServiceNow's ticker, NOW, go live.
The company valued at $2.5 billion in the VMware offer was now worth $3.7 billion by year-end. By 2014, it hit the $10 billion mark that Leone had predicted when he killed the deal. As of 2024, ServiceNow's market capitalization exceeds $150 billion. The company posted $10.984 billion in revenue in 2024. Twenty-seven thousand employees. Ranked #1 on Forbes' Most Innovative Companies list in both 2018 and 2025.
Frank Slootman left ServiceNow in 2017 to eventually become CEO of Snowflake, where he'd engineer another landmark success. Fred Luddy transitioned from CPO to Chairman, then to board member. He gave $60 million to Indiana University — the school he'd dropped out of after a year — to establish the Luddy School of Informatics, Computing, and Engineering. He funded an AI research center there.
The kid who taught himself Fortran overnight in a machine shop in New Castle, Indiana. The kid whose father told him he was stupid and would never amount to anything. The kid who ran away to California at 16 to pick strawberries for cash.
He gave sixty million dollars to name a school of engineering after himself.
That's not irony. That's patience.
Most origin stories center on the innovation. The product. The pivot. The fundraise.
Fred Luddy's story centers on something quieter: what it means to stay faithful to the thing you know how to build, even when the last time you built it, the people around you burned it down.
He didn't invent a new category. He returned to the one he'd spent thirteen years in — the one that had just humiliated and bankrupted him — and decided to build it better. In the cloud. Without the complexity. Without the consultants. Without the fraud.
His central idea was almost embarrassingly small: what if enterprise software actually worked for the people using it? What if it was simple enough that you didn't need an army of implementers? What if it just ran?
What he was really building — and this took years to fully articulate — was a workflow layer. Not just IT tickets. Not just HR requests. Not just security incidents. A single platform where any kind of structured work — any situation where someone needs something and someone else needs to respond — could be automated, tracked, and improved.
The ERP of workflow. For every department. For every enterprise.
And underneath all of it: one guy, two weeks before he turned 50, opening a new file because he didn't know how else to process what had happened to him.
"My drive has always been about putting a smile on someone's face," he said, "because their lives got a little less painful."
He was talking about software.
He might as well have been talking about everything else.
