Software Development Agreement | 17 U.S.C. 101 Compliant

A software development agreement is a services contract for the creation of custom code: a web application, a mobile app, an integration layer, an e-commerce build. The developer commits to a defined result described in a specification, the client to payment tied to milestones and a written acceptance procedure. It is not a software license, where a vendor keeps ownership of a finished product and grants permission to use it. It sits below a master services agreement with statement of work structure, which sets commercial terms across a relationship and pushes per-project scope into separate work orders.

The classification question underneath matters more than buyers expect. Courts apply the predominant purpose test to decide whether UCC Article 2 governs a mixed deal of goods and services, and custom development usually lands on the services side. So the warranty disclaimer formalities of §2-316 and the four year limitations period in §2-725 may or may not apply. A well drafted agreement settles the point by writing its own warranty, remedy and limitations terms rather than inheriting a default nobody chose.

Copyright attaches to source code the moment it is fixed and vests in the author under 17 U.S.C. §201(a). Section 201(b) moves ownership to the hiring party only for a work made for hire, and §101 allows two routes: an employee acting within the scope of employment, measured by the agency factors set out in Community for Creative Non-Violence v. Reid, or a specially commissioned work inside nine enumerated categories with a signed writing. Software is not one of the nine categories. A work for hire recital signed with an outside vendor therefore fails on its own in most custom builds, which is why technology counsel pairs it with a present assignment of all right, title and interest. Section 204(a) requires that transfer to be in a written instrument signed by the party conveying the rights, and electronic signature satisfies it under the E-Sign Act, 15 U.S.C. §7001.

The two routes diverge later. An assignment can be terminated by the author or their heirs 35 years after execution under §203, while a genuine work made for hire cannot. Patent rights travel separately: after Board of Trustees of Leland Stanford Junior University v. Roche Molecular Systems, wording under which a developer "agrees to assign" future inventions can leave the client holding a promise instead of title, so present tense language is standard. Trade secret protection runs through the Defend Trade Secrets Act, 18 U.S.C. §1836, and the immunity notice at §1833(b) must appear in the confidentiality clause or exemplary damages and fees are off the table. Suing adds a step, since §411(a) and Fourth Estate Public Benefit Corp. v. Wall-Street.com require an actual registration decision before filing. The Cornell Legal Information Institute text of the work made for hire definition in 17 U.S.C. §101 is worth reading before signature.

The common trigger is a company commissioning a build it cannot staff internally: a marketplace, a customer portal, a payments integration, a website rebuild. Agencies on the other side need the document just as much, because a client who never signed an acceptance procedure can reject a delivery on taste rather than on specification. Startups outsourcing a first product version are the second group, for investor reasons. Chain of title gets tested during a seed round, and a missing signature from the contractor who wrote the authentication layer becomes a closing condition.

Two situations deserve a closer look. Staff augmentation drifts: a team hired to supplement in-house engineers starts producing standalone deliverables, and the paperwork still reads like a staffing order with no assignment clause. The other is location. Since the addition of IRC §174A, domestic research expenditure, which expressly includes software development costs, is deductible in the year incurred, while foreign research stays on the fifteen year schedule of §174. Where code is written is now a tax fact, and the contract should make the developer warrant it. Early technical work that predates the entity itself belongs in a co-founder agreement with vesting and IP assignment instead.

• The statement of work and specification anchors everything else. It is an exhibit incorporated by reference with a stated order of precedence, so a sales deck cannot silently expand scope.
• Milestones and payment triggers tie each release of funds to a named deliverable rather than to elapsed time. Fixed fee, time and materials and capped structures are supported, with retainage until final acceptance.
• The acceptance testing clause sets objective criteria, a testing window and a cure cycle for rejected deliverables. A deemed acceptance rule stops a client who tests nothing and says nothing from freezing the project.
• The intellectual property transfer combines a work made for hire designation with an unconditional present assignment, a moral rights waiver and a further assurances covenant that survives termination.
• Background IP and developer tools are carved out and licensed back to the client on a perpetual, irrevocable, royalty free basis. Without that carve out, developers hide their reusable libraries or refuse to sign.
• The open source clause requires disclosure of every third party component with its license, bars copyleft terms that would reach the deliverable without written consent, and provides a bill of materials at each milestone.
• Source code escrow is an optional module with named release conditions and an express statement that it is an agreement supplementary to the license for the purposes of 11 U.S.C. §365(n).
• Warranties, indemnity and liability stay separate: a conformity warranty, an infringement indemnity with defense control, and a liability cap carved out for confidentiality breach. Pre-contract talks belong in a mutual non-disclosure agreement for technical due diligence.

California sets a trap that surprises out of state buyers. Under Labor Code §3351.5(c) and Unemployment Insurance Code §686, an individual who signs an agreement expressly designating the deliverable as a work made for hire becomes a statutory employee of the commissioning party for workers compensation and unemployment insurance purposes. Companies engaging solo developers there either carry the coverage or rely on assignment language without the work for hire label. Add Business and Professions Code §16600 and §16600.5, voiding non-compete and broad non-solicit terms even in agreements signed elsewhere.

New York regulates the paperwork itself. Article 44-A of the General Business Law, the statewide Freelance Isn't Free Act, requires a written contract with any one person independent contractor above the statutory value threshold, aggregated across a 120 day period, listing services, rate and payment date. Payment falls due within 30 days of completion where the contract is silent, and the hiring party keeps a copy for six years. General Obligations Law §5-1401 lets larger deals choose New York law with no other connection to the state.

Texas links the contract language to sales tax. Under 34 Texas Administrative Code §3.308, contract programming is a non-taxable service only where the programmer transfers all rights, intellectual property included, in the program to the customer. A partial assignment or a broad developer retained license can convert the whole engagement into a taxable sale. Non-compete terms sit in Business and Commerce Code §15.50, and trade secret claims run under the Texas Uniform Trade Secrets Act at Civil Practice and Remedies Code chapter 134A.

Florida applies Statutes §542.335 to restrictive covenants, which demands a pleaded legitimate business interest and presumptively reasonable durations, with recent legislation moving further toward enforceability for senior personnel. Trade secrets sit in chapter 688. Delaware stays the default forum for venture backed clients, since 6 Delaware Code §2708 validates a Delaware governing law clause for qualifying commercial contracts and the Court of Chancery hears injunctive relief over source code quickly. Teams hiring employees rather than vendors should also read Washington RCW 49.44.140, which limits how far invention assignment reaches into personal projects.

You start with the parties and the engagement model, since the questionnaire branches on whether the developer is an individual, a domestic company or an offshore vendor, and the classification, tax and signature blocks adjust to that answer. Next comes the specification: paste an existing scope document, or build one by describing deliverables, environments and the technology stack. The milestone builder converts those deliverables into payment events and asks for the acceptance window and the number of cure cycles you want before rejection turns into a termination right.

The intellectual property section asks whether the developer keeps background components and whether open source is permitted, then writes the assignment, license back and disclosure duties to match. Escrow, maintenance and support are optional modules. You then select governing law from the state list, which adjusts the restrictive covenant, classification and tax clauses. The agreement downloads in editable Word and signature ready PDF, exhibits numbered and cross referenced. Store the signed copy with your US business contracts and incorporation documents.

The costliest mistake is relying on a work made for hire clause alone. The second is signing the assignment after delivery rather than before work starts, because a developer who has already been paid has no incentive to sign and one who has disappeared cannot sign at all. Payment structures cause the next tier of problems: milestones defined by date rather than by deliverable turn every schedule slip into an argument about whether money is owed, and a final payment with no retainage removes the only leverage that survives go live. Acceptance criteria written as adjectives fail too, since nobody can litigate whether a build is intuitive.

Open source is the quiet one. A single copyleft library pulled in during a sprint can, depending on how it is linked and distributed, put obligations on the whole deliverable, and the problem surfaces during an acquisition rather than during the build. Ask for a component bill of materials at every milestone, not at the end. Confidentiality clauses drafted without the §1833(b) notice quietly forfeit exemplary damages. Directing a long term contractor's hours, tools and priorities invites a reclassification assessment that no clause labeled independent contractor status will cure. Where the same people are effectively in-house, a confidentiality and invention assignment agreement for employees is the correct instrument.