Business Law
Prior Employer Claiming Ownership of Your Startup IP in Pennsylvania
The burden of proof is on your former employer, not on you. Pennsylvania courts require them to establish both a legally protectable interest and a valid legal basis — by agreement or by the nature of your role — before they can restrict what you built after you left. When that letter arrives, investors pause, funding rounds stall, and founders get pulled into discovery. What you do in the first two weeks determines what the dispute costs.
Lebovitz & Lebovitz, P.A. advises Pittsburgh and Western Pennsylvania startup founders on intellectual property ownership disputes, employment agreement analysis, and strategic response to prior employer claims.
Pittsburgh, PA 15218 · Serving Allegheny County and Western Pennsylvania.
A cease-and-desist letter from a former employer arrives during a funding round and everything stops. Investors ask for a legal opinion on IP ownership before they will close. Co-founders get pulled into discovery. The company that was six weeks from closing its seed round is suddenly managing litigation risk instead of building the product. The dispute may be defensible — and often is — but an unresolved IP ownership cloud has consequences that play out in real time while the company is trying to grow. Understanding the legal framework, and engaging counsel before the employer’s narrative becomes the only one on the table, is what determines how the dispute ends.
A Pittsburgh software founder received a cease-and-desist from his former employer eight months after leaving. The employer claimed ownership of his SaaS product under a broad IP assignment clause covering inventions “related to the company’s current or anticipated business.” The founder had worked as a QA engineer. His product served a different vertical, used different technology, and had been built entirely on personal equipment after hours. After presenting employment records showing his actual job duties, the development timeline, and hardware receipts, the employer withdrew the claim without litigation.
A cease-and-desist is a demand, not a court order. What you do in the first two weeks determines what the dispute costs.
Your former employer has to prove the claim. Pennsylvania law places the burden on the employer to establish both a legally protectable interest and a valid basis — by agreement or confidential relationship — for restricting what you built.
Lebovitz & Lebovitz, P.A. advises startup founders facing prior employer IP claims in Pittsburgh and Western Pennsylvania. Call 412-351-4422 or schedule a consultation.
What Pennsylvania Law Says About Prior Employer IP Claims
When a former employer claims ownership of your startup’s intellectual property, Pennsylvania law places the burden of proof on them — not on you.
In Wexler v. Greenberg, 399 Pa. 569 (1960), the Pennsylvania Supreme Court held that a former employer bears the burden of proving two things before it can restrict what you built: a legally protectable trade secret or proprietary interest, and a valid legal basis — either an express covenant or a confidential relationship — to support that restriction. Courts apply common law principles rooted in the law of agency, employment contracts, and equitable doctrine.
An employee’s general skill, knowledge, and technical ability acquired during employment does not automatically become the property of the employer. Without both elements — a protectable interest and a valid legal basis — the former employee has an unqualified privilege to use that knowledge.
That framework means the burden of proof is on the former employer. They must establish that what you built qualifies as protectable and that your relationship to it created an enforceable obligation not to use or disclose it. The employer’s claim that a broad assignment clause covers everything you ever thought about is a starting point for the analysis, not the end of it. Overly broad assignment clauses are regularly limited by Pennsylvania courts as unenforceable restraints on competition.
How to Challenge a Prior Employer IP Claim
Most prior employer IP claims can be challenged on one or more of three practical grounds, each bearing on whether the employer can establish the confidential relationship or contractual basis that Wexler requires. Courts look at scope of employment, use of company resources, and temporal separation. A strong defense usually rests on at least two of the three.
Scope of employment. If the intellectual property you developed is outside the scope of what you were hired to do, the employer’s claim weakens significantly. A software engineer hired to maintain legacy infrastructure who builds a machine learning application on personal time is doing something categorically different from their job duties. What your employment agreement described is relevant, but courts also look at what you actually did.
Company resources. Courts look at this broadly — time worked during business hours, employer-owned computers or servers, employer-licensed software, proprietary data, and input from colleagues. If you used only personal equipment, personal accounts, and personal time, the employer’s claim is significantly weaker. Even minor use of company resources can be cited by the employer, which is why the inventory of what was used and when is important to establish early.
Timing. If the intellectual property was developed after you left the employer, and particularly if it emerged from a line of thinking that predated your employment, the temporal connection to the employer weakens. The more time between departure and development, the harder the employer’s case becomes. Employment agreements sometimes include post-employment assignment clauses — provisions requiring assignment of inventions developed after departure if they relate to the employer’s business. Pennsylvania courts have enforced these when reasonable in scope and duration, and have refused enforcement when they function as perpetual restraints on what a former employee can ever create.
How to Respond to a Cease-and-Desist from a Prior Employer
A cease-and-desist letter is a demand, not a court order. It has no legal force on its own. But how you respond — and how quickly — shapes what happens next.
Do not ignore it. An unanswered cease-and-desist is routinely cited in subsequent litigation as evidence of bad faith or as an implied admission. Do not respond personally. Anything you write becomes a document in potential litigation, and statements made without legal advice can waive defenses or create admissions. Route all communication through counsel.
Do not destroy records. The moment you receive a cease-and-desist, litigation is reasonably anticipated. Spoliation of evidence after litigation is reasonably anticipated can result in an adverse inference instruction — the jury may be told to assume the destroyed evidence would have hurt you — as well as monetary sanctions and in extreme cases dismissal or default judgment. Pennsylvania courts address spoliation through the court’s inherent authority and through Pa.R.C.P. 4019. Preserve development records, commit logs, hardware receipts, calendar entries, email timestamps, and any documentation of what you built and when. Have counsel evaluate the employment agreement before any response goes out. The cease-and-desist almost certainly cites an assignment clause or a non-compete provision. That document needs to be analyzed first.
What Investors Want to See When This Issue Arises
An active IP dispute with a prior employer is a significant diligence issue. Sophisticated investors will not close a funding round with an unresolved IP ownership cloud on the company’s core technology.
What investors want is not a perfect record — they understand founders leave jobs and start companies. What they want is a clear-eyed analysis of the risk, a credible legal position, and a plan for resolution. A credible legal position requires four things: the employment agreement analyzed for scope and enforceability, a documented development timeline showing when the work was done, a resource inventory confirming what equipment and accounts were used, and a scope-of-employment analysis comparing your actual job duties to the technology at issue. A company that surfaces the issue proactively, has engaged counsel, and can articulate the defense is in a better position than one that buries the issue and hopes the investor’s diligence team misses it. If the dispute is material, the investor’s counsel will likely require a legal opinion on IP ownership before closing. Plan for that requirement early — the opinion letter process takes time, and the underlying analysis must be defensible.
Some investors will require IP indemnification from the founders personally — meaning the founders agree to cover the investor’s losses if the IP claim succeeds. Understand what you are agreeing to before signing.
Settlement vs. Declaratory Judgment: The Strategic Decision
When a prior employer makes a credible IP ownership claim, two paths exist: negotiate a resolution or litigate to a judgment. The choice depends on the strength of the employer’s legal position, the cost of litigation relative to the company’s stage, and the effect of ongoing uncertainty on the business.
Settlement is often the right answer even when the employer’s claim is weak. A license agreement, a one-time payment, or a covenant not to sue can clear the ownership cloud quickly and at lower cost than litigation. Investors are often more comfortable with a settled dispute than an ongoing one, even when the company’s legal position was strong. Watch the release language. A narrow release limited to specific named claims leaves the door open for future claims on related IP. A broad release of “any and all claims” may require disclosing other IP you have not yet surfaced. Have counsel review the release scope before signing anything.
A declaratory judgment action — filing suit asking a court to declare that the employer does not own the intellectual property — makes sense when the employer’s claim is facially weak, settlement demands are unreasonable, or the employer is using the dispute as a competitive weapon rather than a legitimate legal claim. It puts the issue before a court on a defined timeline rather than leaving the dispute open-ended and the employer in control of when to escalate. The downside is real: if you file a declaratory judgment action and lose, you have handed the employer an enforceable judgment. That risk must be weighed against the cost of ongoing uncertainty before filing. The strategic decision requires honest assessment of what the employer’s actual evidence is. If they have a signed assignment clause, if company resources were used, and if the timing is ambiguous — those facts change the calculus.
When Prior Employer Claims Kill the Deal
Some IP ownership disputes cannot be resolved quickly enough to save a funding round or an acquisition. When that happens, the company faces restructuring the deal or losing it.
Deals have been restructured into escrow arrangements where a portion of the acquisition price is held pending resolution of IP claims. Deals have been restructured where the acquirer assumes the indemnification obligation and takes the litigation risk in exchange for a price reduction. Deals have been killed entirely when the employer’s claim appeared strong enough that the underlying technology’s ownership was genuinely in doubt. The founders who navigate this outcome best are the ones who engaged counsel early, documented their defense thoroughly, and gave the investor or acquirer enough information to make an informed decision about the risk. Transparency, backed by a well-prepared legal position, is the most credible posture available.
What a Business Attorney Handles in These Disputes
In a prior employer IP dispute, the role of counsel extends across the legal and business dimensions of the problem simultaneously.
On the legal side: analyzing the employment agreement and any IP assignment clauses for scope and enforceability, evaluating the factual record against the framework Pennsylvania courts apply, responding to the cease-and-desist and handling all subsequent employer communications, and advising on whether settlement, declaratory judgment, or another resolution path best fits the company’s situation. On the business side: coordinating with the company’s investors and their counsel on the diligence implications, preparing the IP ownership analysis or opinion letter if required for financing, and managing the disclosure and documentation process so the dispute does not become the story.
Contact Lebovitz & Lebovitz, P.A. if your former employer has claimed ownership of technology you built, if you have received a cease-and-desist and have not yet responded, if an investor has flagged a prior employer IP issue in diligence, or if you need an assessment of the claim before deciding whether to settle or fight.
Prior Employer IP Claims Against Pennsylvania Startup Founders (FAQ)
My employment agreement has a broad IP assignment clause. Does that mean my former employer owns my startup?
Not necessarily. Pennsylvania courts interpret the scope of assignment clauses, and overbroad clauses are regularly limited or refused enforcement. The relevant questions are what the clause actually covers, whether the technology you built falls within that scope, and whether there are independent reasons the clause should not apply — such as the work being done entirely outside employment and with personal resources. A broad clause is a starting point for the analysis, not the end of it.
I used my work laptop once or twice while developing my startup idea. Does that give my employer ownership?
Minor or incidental use of company equipment is one factor, not a dispositive one. Courts look at the totality of the circumstances. If the work was primarily done on personal equipment, primarily occurred outside work hours, and was clearly outside your job duties, isolated use of a company laptop does not automatically transfer ownership. It is a factor the employer can point to, and it should be addressed directly in any defense, but it does not end the analysis.
My former employer had nothing to do with my industry. Can they still claim ownership?
Different industry does not automatically protect you. Scope of employment is the key question, not the employer’s industry generally. If your employment agreement contained a broad assignment clause covering inventions related to the employer’s “actual or anticipated business,” the employer may argue their business was going to expand into your space. Courts have been skeptical of that argument when the connection is remote, but it is not impossible. The strength of the defense depends on how different your startup’s technology and market are from what the employer actually did during your tenure.
The cease-and-desist arrived during our Series A process. What do I tell investors?
Tell them promptly and directly. Investors who discover material legal disputes through their own diligence — rather than from the founders — view the concealment as a serious credibility problem. Present the issue with a clear summary of the claim, your legal position, and the steps you are taking to resolve it. Most experienced investors have seen IP disputes and can evaluate the risk. What they cannot accept is finding out you knew and did not disclose.
Can a former employer stop me from operating my startup while the dispute is pending?
A former employer can seek a preliminary injunction requiring you to stop using the disputed IP while the case is litigated. Obtaining one requires the employer to make a strong showing on the merits of the underlying claim. It is not automatic, but it is a real risk in cases where the employer has a facially strong claim — particularly where there is a signed assignment clause and documented use of company resources in the development process. Under Pa.R.C.P. 1531(b), the employer seeking the injunction must post a bond — or deposit equivalent legal tender with the prothonotary — before a preliminary injunction issues. If the injunction is later dissolved, that bond covers damages sustained by the defendant. The bond requirement is a real procedural obstacle for employers seeking emergency relief.
We settled with the former employer but investors are still asking about it. How do we handle that?
A documented settlement that includes a release of claims or a license agreement is typically sufficient for investor diligence purposes. The settlement should be reviewed by counsel before signing to ensure it actually resolves the ownership question cleanly. If the settlement is narrow — releasing only specific named claims rather than the broader dispute — investors may still have questions. Make sure the settlement documents address what the investor’s counsel will actually ask about.
What is a declaratory judgment action and when does it make sense?
A declaratory judgment action is a lawsuit you file asking the court to declare your rights — in this case, that you, not the former employer, own the intellectual property. It makes sense when the employer is using the threat of litigation as leverage without actually filing suit, when the uncertainty is causing damage to the business, and when the legal merits of the employer’s claim are weak enough that a court ruling would be favorable. It shifts some of the strategic control from the employer to you and puts the dispute on a defined timeline.
For issues that should be addressed before a dispute arises, see our pages on whether your employer owns your side project, independent contractor agreements and IP protection, and founder agreements for Pennsylvania startups. For dispute resolution generally, see business dispute resolution.