Law Firm Software Development Agreements: Use case and AI Confidentiality
A software development agreement turns a business’s plans into milestones, payments and promises about who owns the code. The customer’s lawyer marks up the developer’s standard draft, and the markup carries the real reason for the dates, the points the customer will give up and what the lawyer thinks of the developer’s weaknesses. Staff paste clauses into ChatGPT or Claude to compare them with a precedent or redraft the escrow terms. This page marks every item in a markup for a manufacturer that rule 9 and privilege bear on, and shows how the same agreement is reviewed on Ermos inside the firm.
The software development agreement
Prepared for the customer on receiving the developer’s standard agreement, and negotiated before work starts.
Software development agreement: markup of draft 2 (6 November 2026)
Customer (our client): Pacific Rim Fabrication Pty Ltd1 · Developer: Quillon Digital Pty Ltd, Level 2, 8 Wharf Lane, Pyrmont NSW 20091 · EV / HR10
Clause 3, services and fee. Quillon will build a production scheduling and job-costing system for a fixed fee of $236,000 plus GST, paid by milestone: M1 design $35,400 (Friday 4 December 2026), M2 scheduling engine $70,800 (29 January 2027), M3 accounts integration $59,000 (12 March 2027), M4 user acceptance and go-live $47,200 (30 April 2027) and M5 final acceptance $23,6002.
Why the dates matter. The system must be live by 30 April 2027 so the Smithfield plant can be scheduled on it from the first Meridian delivery in May, after which Pacific Rim pays $1,800 a day in delay charges under the supply agreement, which is under NDA. Do not tell Quillon; it would price the delay risk into the milestone dates.3
Clause 8, intellectual property. Copyright in the deliverables is assigned to the Customer on payment of each milestone, and Quillon keeps its pre-existing tools and licenses them to the Customer. Comment: Quillon’s developers are the first owners of what they write unless an employee wrote it under a contract of service, and an assignment has no effect unless it is in writing signed by or on behalf of the assignor. Make the assignment present and signed, cover future copyright, and have Quillon warrant that every developer has given a written moral rights consent that extends to Quillon’s successors and licensees.4
Clause 10, acceptance testing. The Customer has 10 business days to test each milestone against the specification. Defects are Critical, Major or Minor, and a milestone is accepted when no Critical or Major defect is open. Comment: Delete deemed acceptance after 10 business days of silence. Marek Dziedzic, the plant scheduler, will be the named tester, but he is on leave from Monday 21 December to Monday 11 January, so stop the clock over that period.5
Clause 12, source code escrow. Quillon deposits the source code and build scripts with an escrow agent within 14 days of M2 and with each release. The deposit is released if Quillon becomes insolvent, stops supporting the system for 30 days or fails to fix a Critical defect within 10 business days. Rhonda Mullins wants escrow because Quillon has six staff and one other large customer.6
Clause 15, liability. Quillon’s liability is capped at the fees paid ($236,000) and excludes lost data. Ask for 150% of fees for breach of confidentiality and an uncapped indemnity for IP infringement. Rhonda Mullins will accept a cap of 100% of fees if the escrow clause stays.7
Standard terms. Quillon sent its standard agreement. If it is a standard form contract and Pacific Rim has fewer than 100 employees (it has 57) or turnover under $10 million, the unfair contract terms rules in the Australian Consumer Law can apply to terms such as the one-sided liability cap and Quillon’s right to change the specification.8
Clause 20. This agreement is governed by the law of New South Wales.9
An invented agreement markup. Hover or tap any highlighted item for the analysis; the full list is below.
Developer agreement issues reviewer
An Agent+ that reads the developer's standard software development agreement and checks it against your customer-side checklist and the customer's instructions. It summarises the fee milestones, delivery dates, ownership of the code and the developer's capacity commitments, and drafts proposed amendments for the solicitor to consider.
What it does
- Reads the developer's agreement and the customer's instructions
- Checks milestones, ownership and delivery terms against your checklist
- Drafts proposed amendments and questions for the customer
What stays with your people. The solicitor chooses which amendments to propose and takes the customer's instructions before anything goes to the developer. The agent prepares; it does not negotiate.
An Agent+ is built once and anyone in the practice can run it. It works from your own documents and runs on Ermos Dominion, the AI unit in your office, or on Ermos Edge, your own instance in an Australian data centre.
What leaves the firm
- 1The customer and the developer
A named manufacturer and the small software company it is about to depend on. Confidential to the client under rule 9 while the project is not public. Rule 9 confidentiality guide.
Frontier Models (ChatGPT, Claude) Transmitted to the provider, generally offshore on personal plans Ermos Edge Stays on your instance in Australia; leaves only inside a permitted excerpt, per question, to the named provider Ermos Dominion Stays on the unit in your office Use case Developer agreement issues reviewer. Reads the developer's standard agreement for the customer and sets out milestones, ownership of the code and delivery terms against your checklist, with changes to raise. See the use case - 2The fee and the milestone schedule
The price of the system, how it is paid and the dates for each stage. The client’s commercial arrangement with the developer, and the figures any competing developer would like to see. Rule 9 confidentiality guide.
Frontier Models (ChatGPT, Claude) The fee and the milestone dates transmitted Ermos Edge Stays on your instance in Australia; leaves only inside a permitted excerpt, per question, to the named provider Ermos Dominion Stays on the unit in your office Use case Developer agreement issues reviewer. Reads the developer's standard agreement for the customer and sets out milestones, ownership of the code and delivery terms against your checklist, with changes to raise. See the use case - 3The real reason for the dates and the delay charge
That the go-live date is driven by an unannounced supply contract and a daily delay charge, with an instruction to hide it from the developer. Confidential to the client under rule 9, and the Meridian contract is itself under NDA. Rule 9 confidentiality guide.
Frontier Models (ChatGPT, Claude) An NDA’s subject matter and the real reason for the dates transmitted; on consumer tiers it can train future models Ermos Edge Stays on your instance in Australia; leaves only inside a permitted excerpt, per question, to the named provider Ermos Dominion Stays on the unit in your office Use case Developer agreement issues reviewer. Reads the developer's standard agreement for the customer and sets out milestones, ownership of the code and delivery terms against your checklist, with changes to raise. See the use case - 4The ownership analysis and the drafting advice
Under section 35 of the Copyright Act 1968 the author is generally the first owner unless an employee wrote the work under a contract of service, and section 196(3) makes an assignment ineffective unless it is in writing signed by or on behalf of the assignor. Section 195AWA governs written moral rights consents. The firm’s advice on the drafting is privileged. Legal privilege guide.
Frontier Models (ChatGPT, Claude) Privileged drafting advice transmitted Ermos Edge The AI can describe the rules but a solicitor must decide the drafting Ermos Dominion Stays on the unit, but a solicitor must decide the drafting Use case Developer agreement issues reviewer. Reads the developer's standard agreement for the customer and sets out milestones, ownership of the code and delivery terms against your checklist, with changes to raise. See the use case - 5The acceptance advice and a named employee’s leave
What to delete, who tests and when he is away. A named employee’s leave dates are personal information, and the advice tells the developer where the customer is exposed. Legal privilege guide.
Frontier Models (ChatGPT, Claude) A named employee’s leave and the customer’s exposure transmitted Ermos Edge Stays on your instance in Australia; leaves only inside a permitted excerpt, per question, to the named provider Ermos Dominion Stays on the unit in your office Use case Developer agreement issues reviewer. Reads the developer's standard agreement for the customer and sets out milestones, ownership of the code and delivery terms against your checklist, with changes to raise. See the use case - 6The escrow terms and the view of the developer
The release events and the firm’s and the client’s opinion that the developer is small and dependent on few customers. A frank view of a named company that the developer would not want to read. Rule 9 confidentiality guide.
Frontier Models (ChatGPT, Claude) A frank view of a named developer transmitted Ermos Edge Stays on your instance in Australia; leaves only inside a permitted excerpt, per question, to the named provider Ermos Dominion Stays on the unit in your office Use case Developer agreement issues reviewer. Reads the developer's standard agreement for the customer and sets out milestones, ownership of the code and delivery terms against your checklist, with changes to raise. See the use case - 7The liability cap and the client’s floor
The cap in the developer’s draft, what the firm will ask for and the cap the client will accept if escrow stays. The negotiating position in a document the developer would love to read. Legal privilege guide.
Frontier Models (ChatGPT, Claude) The liability floor now on a third party’s servers Ermos Edge Stays on your instance in Australia; leaves only inside a permitted excerpt, per question, to the named provider Ermos Dominion Stays on the unit in your office Use case Developer agreement issues reviewer. Reads the developer's standard agreement for the customer and sets out milestones, ownership of the code and delivery terms against your checklist, with changes to raise. See the use case - 8The unfair contract terms note
The ACCC says the unfair contract terms regime applies to new or varied standard form contracts with businesses that have fewer than 100 employees or annual turnover under $10 million, and penalties apply to proposing or relying on unfair terms. The note adds the client’s headcount, a confidential fact.
Frontier Models (ChatGPT, Claude) A public regime note with the client’s headcount attached; low value alone Ermos Edge Public regime either way; a person must check whether the contract is standard form and the client’s size Ermos Dominion Public regime either way; a person must check whether the contract is standard form and the client’s size Use case Developer agreement issues reviewer. Reads the developer's standard agreement for the customer and sets out milestones, ownership of the code and delivery terms against your checklist, with changes to raise. See the use case - 9The governing law clause
Standard wording with no party, figure or fact in it.
Frontier Models (ChatGPT, Claude) Standard wording with no party or figure in it; nothing to expose Ermos Edge Standard text either way; a person must check it matches the deal Ermos Dominion Standard text either way; a person must check it matches the deal Use case Developer agreement issues reviewer. Reads the developer's standard agreement for the customer and sets out milestones, ownership of the code and delivery terms against your checklist, with changes to raise. See the use case - 10The solicitors
Initials that tie the markup to practitioners bound by rule 9 and supervised by a partner. Supervising AI guide.
Frontier Models (ChatGPT, Claude) Transmitted, and the leak is traceable to you Ermos Edge Initials only; the route changes little Ermos Dominion Initials only; the route changes little Use case Developer agreement issues reviewer. Reads the developer's standard agreement for the customer and sets out milestones, ownership of the code and delivery terms against your checklist, with changes to raise. See the use case
What happens in Frontier Models (ChatGPT, Claude)
- The whole document is transmitted to the provider’s servers. On personal plans the user cannot choose where it is stored or processed, and for the major providers that has generally meant outside Australia, under that country’s legal process. Some business plans offer storage in Australia, but the provider still receives the content.
- On consumer tiers, prompts can be retained and used to train future models.
- The provider’s staff and systems can reach the content under the provider’s own policies.
- Once sent, the firm no longer controls it. Retention and deletion happen on the provider’s terms.
The same document on Ermos
Ermos Dominion
The document is drafted on a unit in your office, from your own templates and the matter file. Every marked item stays on the unit, which keeps working with the internet switched off. Nothing in it is transmitted to an AI provider, so there is no disclosure to analyse: the confidentiality work is the same as for your file server.
Ermos Edge
Your documents, the index and your access boundaries stay on your own instance in an Australian data centre. When a staff member asks for this draft, only their question and the excerpts they are permitted to see go to a named Australian provider, who is contractually barred from keeping the content or training any model on it. Nothing is processed outside Australia.
| Frontier Models (ChatGPT, Claude) | Ermos Edge | Ermos Dominion | |
|---|---|---|---|
| Where the document is processed | Provider servers, generally offshore on personal plans | Your instance in an Australian data centre; answers generated in Australia | The unit in your office |
| Who can read it | Provider staff and systems, under policy | Your staff, within the boundaries you set. The named Australian provider processes only permitted excerpts, under contract, and keeps nothing | Your staff only |
| Is it kept | On the provider’s terms | Kept on your instance; the provider is barred from retaining it | Stays on the unit |
| Can it train a model | On consumer tiers, yes | No, by contract | Only your own unit learns from it, on your hardware |
Part of Use cases in law firms. See how this works in practice: Agreement review on Ermos.
Common questions
Do ChatGPT and Claude use the information in a software development agreement?
Is it safe to paste a software development agreement into ChatGPT or Claude?
Does a ChatGPT Business or Claude Team plan make it safe for a software development agreement?
How can a law firm use AI for a software development agreement without sending it to ChatGPT or Claude?
Who owns the copyright in software written by a contractor?
What is source code escrow?
Do unfair contract term laws protect businesses buying software?
See Dominion answering from your own documents.
A demonstration takes 30 minutes, uses no client data, and comes with no obligation.
Book a demo