Software development agreements

Commission custom software: scope, stages, acceptance, changes, ownership and what is handed over.

Set the terms for building software for a client.

  • Business / Legal document

How to get this document

Ready to use

Ready-to-use document + 1-hour consultation

$50.00

Placeholder price — not a confirmed price.

Download the ready-to-use document and get a one-hour consultation with a specialised lawyer.

  • The document as a file you download
  • A one-hour consultation with a specialised lawyer
  • A standard version you complete yourself

Lawyer prepares it

Still not sure? Talk to a lawyer

$70.00

Placeholder price — not a confirmed price.

Don’t worry: book a consultation, tell the lawyer what you need, and they will prepare the document for you.

  • A consultation with a specialised lawyer
  • You describe what you need, in your own words
  • The lawyer prepares the document for you

Key features

  • Scope and requirements

    What the software is for, where the requirements are written, what is out of scope, and named representatives who meet at agreed intervals.

  • Stages table

    Four rows for stage, what it delivers and a date, and dates that move if the client is late with what it must provide.

  • Acceptance and written changes

    A testing period for each delivery, putting right what does not meet requirements, and no work on a change until both agree what it costs and does to the dates.

  • Ownership, tools and components

    Who owns the software and from when, the developer keeping its own tools with a permission for the client, and open-source and third-party components listed with their licences.

  • Handover, security and defects

    What is delivered and where, security practices and incident reporting, and fixing defects for a period after acceptance.

About this document

A software development agreement is between a client who wants software built and a developer who will build it. It records what is being built and what is outside scope, how the work is organised, the stages and dates, what the client provides, how each delivery is accepted, how changes are agreed, the price and who owns the result.

This blank form is completed by hand and signed by both sides. It leaves every price, date and period for the parties. It deals with ownership of the software and the developer's own tools, open-source components, source code and handover, security, defects after delivery and support. How ownership and licensing interact in a given project is worth a lawyer's attention.

Is this document right for you?

Useful when

  • You are commissioning an app, website back end or internal tool
  • You are a developer taking on a project and want terms fixed
  • You want ownership and source-code handover settled before work starts

Commonly used by

  • Businesses commissioning software
  • Freelance developers and small agencies
  • Start-ups building a first product

Not sure? about your situation first.

Alternatives

When to use this

  • A start-up hires a developer to build a mobile app in stages
  • A company commissions an integration with a fixed scope
  • A developer keeps its libraries and licenses them to the client

What happens next

Ready to use

  1. Choose your document

  2. Pay

  3. Download

  4. Book your consultation

Lawyer prepares it

  1. Pay

  2. Tell us what you need

  3. Talk to a specialised lawyer

  4. They prepare your document

Need this document for your specific situation?

Get personalized legal help from a qualified attorney through ArieFirm.

More in Technology & Website

Ready when you are.

Questions

About the software development agreements

  • The form has a blank for who and from when, for example on payment in full. The developer's pre-existing tools stay the developer's, with a permission for the client to use them as delivered.

Still have a question? .