Buyer Guides · 7 MIN

How to hire a software development company in the USA: contracts, IP and state privacy law

What a US company should settle before hiring a software development company: the MSA and SOW, IP assignment, state privacy terms, tax forms and accessibility.

By NactorePublished 10 Nov 2026All articles

Hiring a software development company in the USA comes down to a small set of documents and four checks. The documents are a master services agreement, a statement of work for each project, and a data processing addendum if the vendor touches personal data. The checks are who owns the code, which state privacy laws reach the contract, which tax form the vendor hands you, and whether the product must meet an accessibility standard. This guide covers each with the federal and state sources behind it. If you are buying AI work specifically, our guide to hiring an AI development company covers evals and model risk. This one covers the general software contract.

Key takeaways
  • US copyright law treats contractor-written software as a work made for hire only in narrow cases, so a signed assignment is the safe default.
  • A transfer of copyright ownership is valid only in a signed writing, which an invoice or an email thread does not reliably provide.
  • California's CCPA regulations list what a service provider contract must say, and the version effective January 1, 2026 adds help with cybersecurity audits and risk assessments.
  • Other states, such as Virginia, set their own processor contract terms, so one addendum should cover the strictest common set.
  • A US vendor gives you a Form W-9 and a foreign entity usually gives a Form W-8BEN-E, collected before the first payment.
  • Nactore is a technology and growth company based in India that builds and ships software for US clients, works from your contract templates, and keeps the records your auditors will ask for.

Which contract documents should you sign?

Keep the master agreement stable and negotiate each project in its own statement of work. That way a new project never reopens liability or IP.

DocumentWhat it coversWhat to watch for
Master services agreement (MSA)Liability, IP, confidentiality, payment, termination, governing lawLiability caps that exclude data incidents entirely
Statement of work (SOW)Scope, milestones, acceptance tests, team, price for one projectAcceptance defined as "substantially complete" with no test plan
Data processing addendum (DPA)How personal data is handled, security, subprocessors, deletionBusiness purposes written in generic terms
IP assignment (in the MSA or separate)Transfer of rights in deliverablesNo carve-out for the vendor's pre-existing tools
Security exhibitAccess control, logging, incident notice periodNo number of hours for incident notice

Our list of 25 questions to ask before signing maps neatly onto these documents.

Who owns the code a vendor writes for you?

Not automatically you. Under the definition in 17 U.S.C. 101, a commissioned work by an independent contractor is a "work made for hire" only if it fits one of nine listed categories and both sides sign a written agreement saying so. Custom software does not sit cleanly in that list. Section 204(a) adds that a transfer of copyright ownership is not valid unless it is in writing and signed by the owner of the rights or its authorized agent.

So the contract should do three things.

  1. Assign. Use present-tense language that assigns all rights in the deliverables to you, effective on payment, and ask for confirmatory documents if you later need them.
  2. License the background. The vendor keeps its pre-existing libraries and tools and grants you a perpetual, royalty-free license to use them inside the deliverable.
  3. List the open source. Require a list of third-party and open-source components with their licenses, so nothing surprises you in a future due diligence review.

Which state privacy laws reach the vendor contract?

There is no single federal privacy statute for most businesses, so state law shapes the processor terms. California is the usual reference. Section 7051 of the CCPA regulations effective January 1, 2026 says the service provider contract must prohibit selling or sharing the data, name the specific business purposes rather than referencing the whole contract, and let you take reasonable steps to check compliance, which can include assessments or audits at least once every 12 months. The vendor must also tell you if it can no longer meet its obligations.

The 2026 regulations go further. Their examples say the contract may require the vendor to help with your cybersecurity audit, your risk assessment and your automated decisionmaking obligations. For a business with 2026 revenue above $100 million, the first cybersecurity audit report is due by April 1, 2028, so vendors you sign now will be inside that audit.

Virginia shows how other states differ in detail. Its Consumer Data Protection Act, at section 59.1-579, requires a processor contract with clear processing instructions, a confidentiality duty, deletion or return at the end, information to demonstrate compliance, cooperation with assessments, and written flow-down to subcontractors. Ask your counsel which states you trigger and write one addendum to the strictest common terms. Health data adds HIPAA, covered in what vendors must sign under HIPAA.

What tax paperwork do you collect from the vendor?

The IRS says Form W-9 is how a payee provides its correct taxpayer identification number, so collect it from a US vendor. A foreign entity documents its status with Form W-8BEN-E. Collect the right form before you pay the first invoice. The withholding questions behind the W-8BEN-E are in our guide to paying foreign software vendors.

Does your software need to meet an accessibility standard?

If you sell to state or local governments, yes. The Justice Department's ADA Title II rule makes WCAG 2.1 Level AA the technical standard for their web content and mobile apps. An interim final rule of April 20, 2026 moved compliance to April 26, 2027 for governments serving 50,000 or more people and April 26, 2028 for smaller ones and special districts. Expect public-sector buyers to ask you for proof. Put WCAG 2.1 AA into the SOW's acceptance criteria and ask the vendor for an accessibility test report with each release. Private-sector duties are less settled, so ask counsel.

Pro tip

Send your MSA to shortlisted vendors before the scope call and ask for their redlines. How a vendor marks up IP and liability tells you more than its pitch deck.

How do you work with a team in another time zone?

India does not change its clocks, and most of the US does, so India sits 9.5 hours ahead of US Eastern time in summer and 10.5 hours ahead in winter. Standard office hours on both sides barely meet. Write a fixed overlap window into the SOW, such as two hours in your morning, and require written daily updates so work moves while you sleep. The full numbers by coast are in US and UK time zone overlap with India teams, and the contract and payment side is in software development in India for US companies.

Frequently asked questions

Is software a contractor writes for me automatically mine?

Usually not. Unless it fits a statutory work-made-for-hire category with a signed agreement, the contractor owns the copyright until it signs a written assignment to you.

Do I need a DPA if the vendor never sees production data?

If the vendor works only on synthetic or masked data, the processor terms have little to attach to. Write that limit into the SOW and add the DPA before access changes.

Does the vendor need to be a US company?

For most commercial work the deciding factors are contract terms, security evidence and time overlap. Some government and regulated contracts restrict where work happens, so check your own prime contract.

Is this legal advice?

No. It is a plain-language guide with official sources. Confirm your setup with US counsel and your accountant.

Paper first, then code

A good US software engagement looks boring on paper: an MSA you rarely reopen, a SOW per project, an assignment that moves the IP on payment, and a DPA written to the strictest state you sell into. With that settled, every meeting is about the product. Nactore builds, ships, ranks and grows products as one partner, measured on your growth.

Want software built under a contract your lawyers will sign? Book a free 30-minute call.

Want to apply this to your business?

Book a free 30-minute call. We will tell you what we would do first.