incident / Founders and product leaders with a specific concern
A competitor released similar software. What should you document?
Start with what you can observe: which feature, text, output, or workflow appears similar, which versions you compared, and when you saw it. Similar commercial outcomes can result from copying, common requirements, shared components, or independent development.
Create a neutral observation log
- Record product names, versions, public URLs, and observation dates in your internal records.
- Preserve your own relevant release history and development records through an approved process.
- List alternative explanations and unavailable evidence alongside each similarity.
Separate public behavior from private implementation
A SaaS interface may be observable while the server implementation is not. Do not assume identical behavior establishes identical code. Ask which lawfully available evidence could distinguish your hypotheses before commissioning a broad investigation.
The legal context
Copyright does not protect ideas or functionality alone. Trade-secret claims involve different requirements, including the information involved and how it was obtained or used. Existing counsel should evaluate the appropriate theory before a demand or accusation.
Source references
General U.S.-focused information, subject to the facts and applicable jurisdiction. No legal advice, representation, or outcome is promised. Research checked 2026-10-10; review substantive facts with qualified counsel.