10th Circuit Affirms Dismissal of Trade Secret Claims in Snyder v. Beam Technologies

Trade secret law has a simple personality trait: it does not reward carelessness. In Snyder v. Beam Technologies, the U.S. Court of Appeals for the Tenth Circuit delivered a sharp reminder that even valuable business information can lose legal protection when the person claiming secrecy treats it like a shared office spreadsheet instead of a guarded competitive asset. In other words, you cannot leave the vault door open and then act surprised when the court declines to call it a vault.

The case turned on a familiar type of information: a customer list. More specifically, it involved a national insurance broker list that plaintiff John Snyder said was misappropriated by his former employer, Beam Technologies. Snyder brought claims under the federal Defend Trade Secrets Act, or DTSA, and the Colorado Uniform Trade Secrets Act, often shortened to CUTSA. On appeal, the Tenth Circuit clarified an important legal distinction between ownership and possession, but it still affirmed dismissal of the trade secret claims because Snyder failed to take reasonable steps to keep the information secret.

That combination makes this decision especially useful for employers, executives, sales teams, and lawyers. The court did not say customer lists can never be trade secrets. It said something far more practical: customer lists can be protected, but only when the facts show real secrecy discipline. Trade secret protection is not powered by wishful thinking, dramatic testimony, or a last-minute declaration that a spreadsheet was “obviously confidential.” It is powered by actual safeguards.

What Happened in Snyder v. Beam Technologies?

According to the appellate opinion, Snyder had previously worked for Guardian Life Insurance Company and downloaded a nationwide broker list containing more than 40,000 names. After leaving Guardian, he later joined Beam Technologies. While at Beam, he created derivative spreadsheets tied to certain states, but the full broker list ended up being shared with multiple Beam employees. That detail became the legal grenade in the room.

Snyder later sued Beam, alleging that the company misappropriated the broker list in violation of the DTSA and CUTSA. He also asserted additional state-law claims, including fraudulent misrepresentation and promissory estoppel. The district court granted summary judgment against Snyder on the trade secret claims, reasoning that he failed to show ownership of the list. It later went further in a separate ruling under Rule 702 by excluding Snyder’s damages expert and, in the same stroke, barring essentially all evidence and witnesses on lost wages for the remaining claims.

On appeal, the Tenth Circuit split the baby, legally speaking. It affirmed dismissal of the trade secret counts, but not for the exact reason the district court used on the CUTSA claim. The appellate court explained that the district court leaned too heavily on “ownership” under Colorado law, even though older Tenth Circuit precedent indicates that possession, not strict ownership, may be enough under CUTSA. Still, Snyder ultimately lost the trade secret claims because the court found that he had not taken reasonable measures to maintain secrecy.

Why the Trade Secret Claims Failed

1. Secrecy Is a Requirement, Not a Vibe

Under both federal and Colorado trade secret law, information must be secret and valuable, and the claimant must take reasonable measures to keep it secret. That last element matters more than many litigants seem to think. A court does not just ask whether the information was useful. It asks whether the claimant behaved like the information was genuinely confidential.

In Snyder’s case, the appellate court focused on several facts that cut against secrecy. He did not mark the spreadsheets as confidential. He did not password-protect the documents themselves. He did not restrict internal access. He did not require confidentiality agreements from the Beam employees who received the materials. He did not warn recipients that the broker list was proprietary. And after realizing the full list had been distributed, he did not meaningfully try to claw it back. That is not a great fact pattern if you are trying to persuade a federal appellate court that you handled a trade secret with care.

The court’s message was blunt: storing material on personal devices or even on a password-protected laptop is not enough by itself. Trade secret protection usually requires a broader pattern of conduct showing that disclosure was limited, guarded, and accompanied by clear confidentiality expectations. In Snyder’s case, the information was sent to multiple coworkers without restrictions, and the court concluded that no reasonable jury could find those actions met the minimum threshold for reasonable secrecy measures.

2. A Customer List Is Not Automatically a Trade Secret

Many businesses assume customer lists are trade secrets by default. Courts do not. A customer list may qualify when it reflects valuable, nonpublic business intelligence and is protected like a true internal asset. But if it looks more like a collection of names that was passed around casually, its trade secret status gets shaky fast.

That is one reason the Snyder decision matters beyond the specific dispute. It reinforces a broader trend in Tenth Circuit trade secret cases: courts want specificity, confidentiality, and proof that the information was actually treated as special. This was also a theme in Double Eagle Alloys v. Hooper, where the Tenth Circuit emphasized that trade secret plaintiffs must identify their alleged trade secrets with sufficient particularity and support secrecy with evidence, not broad labels or vague categories.

So yes, a customer list can be a trade secret. But no, a spreadsheet does not become a trade secret just because someone says it is one after litigation begins. Courts are not magicians, and they are especially unwilling to pull rabbits out of unsecured Excel files.

3. The Ownership-versus-Possession Distinction Still Mattered

One of the more interesting parts of the opinion involves the difference between the DTSA and CUTSA. The district court had treated ownership as a required element of both trade secret claims. The Tenth Circuit said that approach did not fit its own precedent under Colorado law. For CUTSA, earlier authority points to possession of a valid trade secret as the relevant concept, not necessarily strict ownership in the conventional sense.

That clarification is important because trade secret cases often involve complicated chains of creation, access, licensing, and employment history. Information may be possessed by one party, created by another, licensed by a third, and used in a business setting that is messier than a clean law school hypothetical. By distinguishing CUTSA from the DTSA, the court signaled that Colorado law may be more flexible than the federal statute on who can bring the claim.

Still, this legal clarification did not save Snyder. The court held that even if possession could satisfy CUTSA, the claim still failed because secrecy was not reasonably maintained. That makes Snyder a useful cautionary case: a plaintiff can win a legal argument on one element and still lose the whole war because the operational facts are bad.

Why This Decision Matters for Employers

For employers, the lesson is straightforward and a little uncomfortable: trade secret law will not rescue weak internal practices. If a company wants customer data, pricing models, source code, formulas, sales playbooks, or broker contacts to receive trade secret protection, it needs to build a repeatable system around confidentiality. Policies should not live only in an employee handbook collecting digital dust.

At a minimum, businesses should think about layered controls. Mark sensitive materials as confidential. Restrict access on a need-to-know basis. Use passwords and permission settings at the document level, not just the laptop level. Require confidentiality agreements where appropriate. Train employees on handling secret information. Audit sharing practices. And when an accidental disclosure happens, respond immediately instead of shrugging and hoping the issue goes away.

The Snyder decision also matters because it shows how quickly a court can zoom in on everyday conduct. A missed label. A loose email. A shared attachment. A failure to notify recipients. A failure to follow up after mistaken disclosure. None of those facts may seem dramatic alone. Together, though, they can turn a trade secret case into a dismissal.

Why This Decision Matters for Employees and Executives

Employees should not read Snyder as a free pass to carry lists from one employer to another. Far from it. Trade secret and confidentiality disputes remain dangerous territory, especially when information originated with a prior employer. If anything, Snyder shows that information ownership and lawful possession can become tangled quickly, and courts will examine how the data was obtained, stored, shared, and described.

Executives and sales leaders should take special notice. Customer-facing teams often work with data that sits in the gray zone between personal relationships and company assets. A salesperson may know clients personally, but the compiled database of contacts, history, notes, and strategic information is often a different story. Treating those materials casually can create litigation from both directions: a former employer may sue for theft, or a later plaintiff may find the court unwilling to recognize the information as protected because secrecy safeguards were too weak.

The Quietly Important Rule 702 Twist

Although the trade secret claims stayed dismissed, Snyder did win something meaningful on appeal. The Tenth Circuit reversed the district court’s Rule 702 order to the extent it barred all evidence and witnesses on lost wages. The appellate court said that a ruling framed as an expert-admissibility issue cannot quietly morph into a dispositive summary judgment ruling on damages without fair notice and the usual procedural protections.

That part of the opinion matters for civil litigators far beyond trade secret law. It warns trial courts and litigants against using evidentiary motions as stealth summary judgment devices. If a party is going to lose an entire category of damages, the party should generally be given proper notice and a fair chance to present factual material in response. Procedure still matters, even when the merits look bleak.

So while Snyder lost the trade secret battle, the opinion still handed plaintiffs’ lawyers a procedural reminder worth saving. Federal appellate courts do not love ambushes dressed up as expert motions.

What the Case Says About Trade Secret Strategy in 2025 and Beyond

Snyder fits neatly into a larger pattern in trade secret litigation. Courts increasingly expect plaintiffs to do three things well: identify the alleged secret with specificity, prove the information has economic value because it is not generally known, and show real-world efforts to preserve secrecy. Miss one prong and the case gets harder. Miss two and you may be packing for summary judgment.

For companies, that means trade secret strategy should begin long before litigation. The best trade secret lawsuit is usually the one you never have to file because your data governance, exit procedures, confidentiality rules, and access controls were disciplined enough to deter misuse or make proof easy. Trade secret protection is not just a legal theory. It is an operational habit.

For lawyers and legal teams, Snyder is a helpful opinion to cite when arguing that casual disclosure destroys secrecy, and when drawing the line between possession and ownership under different statutes. It is also a strong reminder to examine the plaintiff’s conduct with the same skepticism usually aimed at defendants. The label “victim of misappropriation” does not immunize sloppy handling.

Practical Experience and Lessons From Similar Trade Secret Fights

In real-world disputes related to customer lists, broker databases, pricing records, and sales spreadsheets, the same pattern shows up again and again. The business says the information is priceless, highly confidential, and essential to its competitive edge. Then discovery begins, and the documents reveal a less glamorous reality: the files were emailed freely, stored on personal drives, copied into presentations, forwarded to broad internal groups, and shared with vendors who never signed a confidentiality agreement. At that point, the courtroom mood changes. The issue stops being whether the information is useful and becomes whether anyone actually treated it like a secret when it mattered.

One common experience in trade secret disputes is that internal culture tells the real story. Companies with strong trade secret cases usually have boring but effective habits. Their files are labeled. Their permissions are limited. Their onboarding materials explain confidentiality clearly. Their exit interviews include return-of-property steps. Their managers know not to ask a new hire to bring over old employer data. Their IT logs can show who accessed what and when. None of this is exciting. No one throws a parade for document classification. But when litigation arrives, these ordinary habits become the backbone of credibility.

By contrast, weak cases often involve a mismatch between what the company says in court and what it did in practice. Leadership may insist that the customer list was secret gold, but sales teams were allowed to export it without approval. Executives may describe pricing models as closely held, but those models were attached to emails with wide distribution and zero warnings. Sometimes the information was stored in shared folders with permissions so broad they might as well have included the office coffee machine. When that happens, opposing counsel does not need a magic trick. They just need the audit trail.

Another recurring experience is that accidental disclosure is rarely fatal by itself, but failure to respond usually is. Courts understand that people make mistakes. A wrong attachment gets sent. A tab stays hidden in a spreadsheet. A file lands in the wrong inbox. The difference between a survivable mistake and a damaging one is what happens next. Did the sender immediately notify recipients, request deletion, restrict further use, and document the response? Or did everyone pretend nothing happened until years later, when the term “trade secret” suddenly became fashionable during litigation? Snyder lands on the wrong side of that divide.

There is also a practical lesson for employees who move between competitors. People in sales and business development often believe the most valuable asset they carry is their memory of customer relationships. Courts sometimes agree that general knowledge, skill, and personal goodwill belong to the individual. But a compiled database, especially one built from employer systems, is a different animal. Taking it, using it, or redistributing it can trigger serious claims. On the flip side, if an employee later tries to claim that same information as a personal trade secret, Snyder shows how hard that argument becomes when secrecy steps are thin and the information originated in an employer’s records.

Ultimately, the lived experience behind trade secret litigation is not mysterious. The cases usually rise or fall on discipline. The law cares about process because process is how secrecy becomes provable. That is the enduring takeaway from Snyder v. Beam Technologies. A court may sympathize with a messy employment breakup. It may even agree that the information had potential value. But if the record shows casual handling, unrestricted sharing, and no meaningful effort to preserve confidentiality, the judge is unlikely to call the information a trade secret. In trade secret law, hope is not a control, and vibes are not a compliance program.

Conclusion

The Tenth Circuit’s decision in Snyder v. Beam Technologies is a sharp, modern lesson in trade secret law. The court clarified that under Colorado law, possession may matter more than strict ownership for certain claims. But that nuance did not rescue Snyder because the court found the real problem elsewhere: he did not take reasonable measures to protect the alleged secret. He shared the materials too broadly, too casually, and without the kinds of restrictions courts expect to see.

For businesses, the ruling is both warning and roadmap. If a customer list or broker database is truly valuable, treat it that way before a dispute starts. Label it. Limit it. Protect it. Train around it. React quickly when disclosure happens. For litigants, the case confirms that trade secret claims are won with evidence of disciplined confidentiality, not just after-the-fact descriptions of value. And for anyone tempted to rely on a loose spreadsheet and a strong sense of injustice, Snyder offers a firm legal reality check.

SEO Tags