Is pre-existing materials and tools normal in a software / web development agreement?

A software / web development agreement should carve out your pre-existing materials and tools from the IP assignment and address open-source components. Without that carve-out you may be signing away the reusable assets that make your business efficient.

What’s market-standard

The freelancer retains ownership of anything created before or outside the engagement, and of general-purpose tools, and grants the client a license to use them as delivered. Open-source components are governed by their own licenses.

Warning signs

• Silence on pre-existing IP combined with a broad assignment
• Client owns 'all materials used to produce the Deliverables'
• No mention of open-source or third-party licenses
• Freelancer must indemnify for open-source that the client asked for

Wording you can send

'Pre-Existing Materials' means anything owned or licensed by the Provider before or independent of this engagement, including tools, libraries, and templates. The Provider retains ownership of Pre-Existing Materials and grants the Client a perpetual, non-exclusive license to use them as incorporated in the Deliverables. Open-source components remain subject to their respective licenses.

What it means for you

Whether the contract recognizes that you bring reusable assets (code libraries, component systems, project templates, frameworks) and lets you keep owning them.

Not legal advice. Gig Clause is software, not a law firm or a professional service, no attorney reviews, drafts, or is otherwise involved in anything it produces. It automatically highlights common contract issues and suggests negotiation language. Using it does not create an attorney-client relationship. For decisions with significant financial or legal consequences, consult a qualified attorney licensed in your jurisdiction. Clause standards vary by industry and location and change over time.