San Diego in the late 1990s was not the obvious place for a fraud of this scale to take root, but it was a perfect place for a software company to learn how to sound inevitable. The region’s technology firms were close enough to Silicon Valley to borrow its language of momentum and close enough to the defense and enterprise markets to sell the dream of order. Peregrine Systems, a company built around IT asset management software, moved inside that atmosphere and made its pitch in the idiom of the era: enterprise growth, recurring demand, and a market hungry to reward any firm that could claim it was becoming infrastructure.
Stephen Gardner sat inside that world as a chief executive expected to do the one thing public markets demanded most in 1999 and 2000: keep the story moving upward. Public filings and later civil and criminal proceedings placed him at the center of the company’s financial presentation, the face investors saw when Peregrine talked about software licenses and services that appeared to justify a soaring valuation. The structural problem was simple and dangerous. In the late dot-com boom, software companies were often judged on revenue growth before the quality of that revenue was examined with enough skepticism. Deals were large, contracts were intricate, and the accounting rules around revenue recognition left room for abuse when managers wanted to call tomorrow’s cash today’s sales.
That gap mattered because Peregrine’s business model depended on transactions that could be made to look ordinary on paper while hiding the private understandings that changed everything. A sale could be booked, a customer congratulated, and the quarter closed before anyone outside the inner circle noticed that the economics had been quietly reversed. The germ of the scheme was not a single theatrical theft but a practical decision: if the company could not meet the growth expectations attached to its stock price, it could create the appearance of meeting them and worry about the consequences later. That is where a legitimate software business begins to bend toward fraud — not in a vault, but in the accounting department and the executive suite.
One of the central structural conditions was the pressure created by quarterly reporting. In a public company, the calendar itself becomes a trap. If a contract lands too late, if a customer hesitates, if a sales forecast misses, the gap is visible in days. Peregrine’s leaders operated in a market where disappointing the Street could destroy market capitalization in hours. That pressure did not excuse the choices that followed; it explained why the choices were made with such determination. The fraud later described in SEC and DOJ materials did not require a single invented customer. It required the company to accept revenue it had already reason to know was shaky, then hide the side arrangements that made the revenue less real than the books claimed.
The setup also depended on a corporate culture in which aggressive revenue reporting was normalized by the era. Accounting rules at the time did not yet carry the hardened post-Enron vigilance that later came with new oversight and public outrage. That created a gray zone in which executives could convince themselves that a side letter was just a sales accommodation, that a return promise was just a commercial courtesy, that a rebate deferred to a later date was not quite the same as cancellation. In a documentary record, that is often how fraud enters the room: not with a confession, but with language designed to make the violation seem technical rather than moral.
Inside the company, the first crossing of the line appears to have been operational rather than rhetorical. According to later government allegations, sales were recorded even when side agreements or other undisclosed terms meant the revenue should not have been recognized as booked. That is the crucial distinction in a case like this. The fraud was not simply that the company wanted to grow; it was that it wanted the market to believe growth had already occurred when the underlying transactions were reversible, conditional, or otherwise incomplete. The lie was not in the existence of customers. It was in the bookkeeping that stripped away the conditions attached to those customers.
The early money flow matters because once false revenue enters a public company’s reported results, it becomes a machine that feeds itself. The stock price can rise. The credibility of management can harden. The company can buy time. Lenders, analysts, and employees begin to treat reported numbers as evidence of health rather than as a question mark. Every passing quarter then becomes a test not of performance but of concealment. In that atmosphere, the operational scheme was no longer hypothetical. It was moving through the books, helping Peregrine look larger and more successful than it truly was.
What made the arrangement especially fragile was that it had to be maintained continuously. One problematic booking could be rationalized; a pattern could not. Each new quarter increased the amount of explanation required. Internal records had to align. Outside auditors had to be placated. The company had to preserve the appearance that its revenues were earned in the ordinary course. The moment that appearance became a habit, the fraud was operational.
By the end of the first phase, Peregrine had done what many fraudulent enterprises do when they are still young enough to seem merely ambitious: it had transformed accounting judgment into a tool of narrative control. The market saw a software company with a growth story. Inside the company, the machinery of concealment had already started to turn. The next challenge was not whether the lie could be told. It was whether enough people could be persuaded to believe it long enough for the numbers to compound.