Short answer: never shut down a customer’s site or disable their software access over a billing dispute unless your contract explicitly gives you the right to do so. Taking that step without clear contractual authority exposes you to a Computer Fraud and Abuse Act violation, which is both a civil
Short answer: acceptance criteria are subjective (“the customer decides if it is good enough”) and completion criteria are objective (“we delivered X, here is the proof”). As a vendor, you want completion criteria in every SOW, because that is what gets you paid. As a SaaS attorney, I run into
Short answer: Three things: a written open source policy, a tracking process for the open source code and its license terms, and an annual review to make sure your developers actually follow the policy. If you operate a software-based business, you are likely using some open source code in your
Short answer: registering your software with the U.S. Copyright Office is cheap and easy, and it unlocks two things you cannot get otherwise: your attorney’s fees and statutory damages. For a software company, that is some of the best legal insurance money can buy. Most people do not realize there
Short answer: when you outsource development, five things decide whether you actually own and control what you paid for. They are IP ownership, termination, the expectations gap, where your source code lives, and which law governs. As a software attorney, I work on a lot of these deals. Outsourcing is
Get started with a free initial consultation—fill out the form below to connect with our experts today!