Veeva V. Epic: Kicking the Can in Dane County

Key Takeaways

• Veeva leveraged “in terrorem” argument to enforce equity clawback.
• Epic’s stock purchase agreements framed as coercive financial scheme.
• Veeva argued it isn’t bound by arbitration or class‑action waivers.
• Standing strengthened by Wisconsin precedent Heyde v. Dove Healthcare.
• Veeva acknowledges competitive overlap with Epic’s product line.

Pulse Analysis

The dispute between Veeva Systems and Epic Systems centers on a Wisconsin lawsuit that challenges Epic’s restrictive covenants, including an equity clawback designed to deter talent migration. Veeva’s opposition brief argues that the clawback functions as an "in terrorem" mechanism, effectively enforcing the non‑compete without needing a separate lawsuit. By highlighting a candidate who withdrew from an interview citing the clause, Veeva demonstrates real‑world impact, positioning the provision as a de‑facto barrier to competition. This approach leverages state case law that employers may be liable when employees perceive contractual overreach.

Beyond the clawback, Veeva attacks Epic’s stock‑purchase agreements, labeling them as "financial coercion" that ties compensation to restrictive covenants. The brief cites an unpublished Wisconsin opinion to question the alignment of the Selmer/Hobson precedent with statutory language, and points out Epic’s failure to attach its own unpublished rulings, a procedural breach under Wisconsin rules. Veeva also dismantles Epic’s arbitration defense, asserting that because Veeva is not a party to the agreements, it cannot be bound by arbitration or class‑action waiver provisions, forcing Epic to choose a single legal argument.

The broader stakes are significant for the health‑tech ecosystem. A ruling that curtails aggressive non‑compete enforcement could loosen talent mobility, encouraging innovation across EHR platforms. Conversely, upholding Epic’s mechanisms would reinforce employer dominance in a market where product integration and data ownership are critical. The case also offers a template for other tech firms navigating state‑specific covenant enforcement, making the outcome a bellwether for future litigation in the sector.