Doxuno
BusinessIE

Software Development Agreement Template — Ireland

Commissioning bespoke software development in Ireland? Our free Software Development Agreement template is purpose-built to cure the Copyright and Related Rights Act 2000 commissioned-work IP trap — by default the Developer keeps the copyright unless you have an express assignment. The free version includes the essential IP assignment + moral rights waiver plus project scope, milestones, fees and timeline. Expert unlocks acceptance testing, source code escrow, warranty + bug fix, maintenance & support, confidentiality + non-solicit, and AI / ML components disclosure under the AI Act 2024/1689.

Free to useInstant PDFNo account required

PDF (free) + editable Word (.docx) with Expert

SOFTWARE DEVELOPMENT AGREEMENT
Copyright And Related Rights Act 2000 + Patents Act 1992 — Ireland
CLIENT
Liffey Digital Group Limited
14-16 Lower Mount Street, Dublin 2, D02 KF42
CRO 612345
By: Aisling Byrne, Chief Technology Officer
DEVELOPER
Shannon Code Studios Limited
5 Eyre Square, Galway, H91 K2C9
CRO 634567
By: Conor Walsh, Founder and Lead Developer
Project: River Logistics Platform v2
Total fee: €80000 (excl. VAT)

This Software Development Agreement (the "Agreement") is made between the Client and the Developer identified above for the development of River Logistics Platform v2. The Agreement is governed by the Copyright and Related Rights Act 2000 (the "CRRA 2000"), the Sale of Goods and Supply of Services Act 1980, the Patents Act 1992, the GDPR + Data Protection Act 2018 (where the Deliverable processes personal data), and (where the Deliverable includes AI components) the AI Act (EU) 2024/1689 and the EU Data Act 2023/2854.

1.
APPOINTMENT
The Client appoints the Developer to design, develop, deliver and (where agreed under clause J) maintain the software project described in clause 2, on the terms of this Agreement. The Developer shall perform the Services with the reasonable skill and care expected of a competent provider of similar services (section 39 of the Sale of Goods and Supply of Services Act 1980).
2.
PROJECT SCOPE AND DELIVERABLES
Project overview: A cloud-native logistics-tracking web platform with mobile companion apps (iOS + Android), enabling River Logistics customers to track shipments end-to-end, integrate with ERP systems via REST API, and generate compliance reporting for the Department of Transport. The platform replaces the existing legacy system and shall be production-ready within 16 weeks.
Deliverables: D1 — Web application (React + TypeScript front-end, Node.js back-end). D2 — iOS app (Swift). D3 — Android app (Kotlin). D4 — Backend API (RESTful, OpenAPI 3.0 specification). D5 — Infrastructure as Code (Terraform). D6 — Source code (GitHub repository under Client's GitHub organisation). D7 — Technical documentation (architecture, deployment, API reference). D8 — User documentation (admin guide + end-user help).
Technology stack: Front-end: React 19 + TypeScript 5 + Tailwind CSS 4. Mobile: Swift 6 (iOS), Kotlin 2 (Android), shared design system via Figma. Back-end: Node.js 22 LTS + Fastify + Drizzle ORM. Database: PostgreSQL 17 (Supabase). Hosting: AWS (eu-west-1 Ireland region). CI/CD: GitHub Actions.
3.
TIMELINE AND MILESTONES
Start date: 1 September 2026.
Target end date: 31 December 2026.
Milestones: M1 — Architecture and design (week 4) — 20% fee. M2 — Backend + API + database (week 8) — 25% fee. M3 — Web front-end + admin portal (week 12) — 25% fee. M4 — Mobile apps + final integration (week 14) — 20% fee. M5 — Final acceptance + documentation + handover (week 16) — 10% fee.
Time is not of the essence except for any milestones expressly designated as time-critical in writing.
4.
FEES AND PAYMENT
Fee structure: Milestone-based — fee released on completion of each milestone (recommended balance).
Total fee: €80000 (excl. VAT). VAT at 23% applies in addition.
Payment schedule: 20% on signature (€16,000 mobilisation); 20% on Architecture sign-off (M1); 25% on Backend sign-off (M2); 25% on Web sign-off (M3); 10% on final acceptance (M5). All invoices payable within 30 days of issue.
Expenses: Pre-approved expenses (travel, third-party software licences, cloud hosting during development) shall be invoiced at cost plus 0% mark-up, with copies of supporting invoices attached.
Late payments accrue interest under the European Communities (Late Payment in Commercial Transactions) Regulations 2012 (8% above the ECB main refinancing rate) plus €40 fixed compensation per overdue invoice.
5.
INTELLECTUAL PROPERTY ASSIGNMENT
Assignment (curing the CRRA 2000 default): The Developer irrevocably assigns to the Client, with full title guarantee, by way of present assignment of future rights, all intellectual property rights (including without limitation copyright under the Copyright and Related Rights Act 2000, patent rights under the Patents Act 1992, database rights, design rights, and know-how) in all Deliverables created in the performance of this Agreement. The Developer shall execute any further documents reasonably required to give effect to this assignment.
Assignment trigger and moral rights waiver: Assignment of each Deliverable occurs on the earlier of (a) acceptance of the Deliverable by the Client and (b) payment in full of the milestone fee relating to the Deliverable. The Developer retains all rights until the trigger occurs. The Developer also irrevocably waives, to the maximum extent permitted by law, all moral rights under sections 137-138 of the Copyright and Related Rights Act 2000.
Developer's Background IP (retained): The Developer retains ownership of its Background IP (generic code libraries, reusable components, methodologies, and any IP developed independently of this Project before or during the Project). The Developer grants the Client a perpetual, worldwide, non-exclusive, royalty-free licence to use the Background IP solely to the extent embedded in the Deliverables.
The parties acknowledge that, in the absence of this clause, sections 21-28 of the Copyright and Related Rights Act 2000 would leave the Developer (as author) with default copyright ownership.
6.
ACCEPTANCE TESTING AND SIGN-OFF
Acceptance criteria: Each Deliverable is accepted when it (a) implements the specification in clause 2; (b) passes the Test Plan (functional + performance + security tests); (c) is documented per the Documentation standards; (d) is deployed to the agreed environment (staging or production as specified); (e) has no Severity 1 or Severity 2 defects open.
Testing window: the Client has 10 working days (recommended baseline) from delivery to test against the acceptance criteria and notify acceptance, partial acceptance with snag-list, or rejection (with detailed reasons).
Rejection / snag-list procedure: If the Client rejects or notifies a snag-list within the testing window, the Developer shall remedy the issues within 10 working days (or such other period as the parties agree in writing) and re-deliver. On re-delivery, the testing window restarts (capped at 3 cycles per Deliverable). Silence beyond the testing window = deemed acceptance.
7.
SOURCE CODE ESCROW
Escrow Agent: NCC Group plc under their standard tri-party software escrow agreement. The parties shall enter into a tri-party escrow agreement on the Escrow Agent's standard terms within 30 days of the Effective Date.
Deposits: the Developer shall deposit, on first delivery and at quarterly intervals thereafter: (a) the source code in a buildable form; (b) build and deployment instructions; (c) any third-party tools, licences, keys or credentials required for build / deployment; (d) up-to-date technical documentation.
Release triggers: The Escrow Agent shall release the deposited materials to the Client on: (a) Developer insolvency, examinership under Part 10 Companies Act 2014, receivership, liquidation, or analogous foreign proceedings; (b) material breach of the maintenance obligations in clause 9 not cured within 30 days of written notice; (c) acquisition of the Developer by a direct competitor of the Client; or (d) such other event as agreed in the Escrow Agreement.
8.
WARRANTY AND BUG-FIX OBLIGATION
Warranty period: for 12 months (recommended baseline) from acceptance of each Deliverable, the Developer shall remedy bugs that fall within the original specification at no additional charge.
Severity tiers and response targets: S1 (critical — system unavailable): response within 4 hours; resolution target 1 working day. S2 (high — major function blocked): response within 1 working day; resolution target 3 working days. S3 (medium — workaround available): response within 3 working days; resolution target 10 working days. S4 (low — cosmetic): response within 5 working days; resolution target next maintenance release.
Exclusions: the warranty does not cover (a) issues caused by Client modifications, third-party integrations or environment changes; (b) requests for new features or enhancements; (c) compatibility with software released after Acceptance not specified in the original requirements.
9.
MAINTENANCE AND SUPPORT
Scope: Included: (a) bug fixes for Severity 1-3 defects; (b) security patches for OS / dependencies / libraries; (c) compatibility updates for browser / OS / mobile app store changes; (d) hosting / infrastructure adjustments; (e) up to 8 hours/month of minor enhancements (under 1 day each). Excluded: (i) new features over 1 day of work; (ii) major refactors; (iii) migration to new platforms / tools; (iv) integration with new third-party systems; (v) UI / branding changes beyond minor adjustments. Excluded items are billed as Time and Materials at the agreed rates in a separate Change Order.
Fee: Monthly retainer of €2,500 (excl. VAT), payable in advance, covers the included scope. Additional work is billed at the standard Time and Materials rate of €120/hour (excl. VAT). The retainer is reviewable annually; the Developer may propose changes on 60 days' notice.
10.
CONFIDENTIALITY AND NON-SOLICIT
Mutual confidentiality: each party shall keep confidential, both during the Term and indefinitely after termination, all confidential information of the other (including the Client's business information, the Developer's methodology, source code retained as Background IP, and the existence and terms of this Agreement).
Carve-outs: Confidentiality does not apply to information that is (a) publicly known otherwise than through breach; (b) lawfully obtained from a third party without restriction; (c) independently developed by the receiving party; or (d) required to be disclosed by law, court order or regulator (provided the disclosing party is notified in advance where lawfully possible).
Non-solicit of employees: for 12 months (recommended baseline) after termination, neither party shall directly or actively solicit (excluding general advertising) the employment of any employee or contractor of the other who has been materially involved in the Project. This restraint does not prohibit responses to applications made by the employee on their own initiative.
11.
AI / ML COMPONENTS DISCLOSURE (AI ACT 2024/1689)
AI components in Deliverable: The Deliverable includes: (a) LLM-powered chat-assistant feature using OpenAI GPT-4o API (Limited Risk category — Article 50 transparency applies); (b) recommendation engine using Vertex AI embeddings (Minimal Risk); (c) AI-assisted code generation tools used by the Developer during development (GitHub Copilot — disclosed to the Client). No High-Risk AI systems are included.
Training data provenance: All training data used in any custom-trained models is sourced from: (a) the Client's own data (subject to GDPR controller-processor terms in the DPA); (b) properly licensed third-party datasets (licence terms summarised in Annex [X]); (c) publicly available data not subject to copyright restrictions or robots.txt exclusion. No copyright-protected content has been used as training data without licence.
AI Act compliance: the Developer shall comply with the AI Act obligations applicable to its role and the risk classification, including (as applicable) Article 50 transparency (in force 2 August 2026) and Article 53 GPAI obligations (in force 2 August 2025). The Developer shall provide the Client with the technical documentation, instructions for use and any other information necessary for the Client to comply with its own deployer obligations.
12.
TERMINATION
Either party may terminate immediately for: (a) material breach not remedied within 30 days of written notice; (b) insolvency, examinership, receivership or liquidation of the other; (c) cessation or threatened cessation of business. The Client may terminate for convenience on 30 days' written notice; in that event, the Client shall pay (i) all fees accrued up to the termination date, (ii) any reasonable wind-down costs, and (iii) 30% of the remaining unbilled fee as a termination fee. On termination, the Developer shall deliver all completed and in-progress Deliverables to the Client and assign all IP per clause 5.
13.
GENERAL PROVISIONS
Notices: any notice shall be in writing, delivered by hand, registered post or email with read receipt to the addresses given above.
Assignment: neither party may assign without the other's prior written consent, save the Client may assign to a group company on notice.
Variation: any variation (including Change Orders) shall be in writing and signed by authorised representatives of both parties.
Severability: if any provision is held void or unenforceable, the remaining provisions continue in full force.
Entire agreement: this Agreement constitutes the entire agreement between the parties on the Project and supersedes all prior negotiations and arrangements.
Force majeure: neither party is liable for failure caused by events beyond reasonable control.
14.
GOVERNING LAW AND JURISDICTION
This Agreement is governed by the laws of Ireland. The courts of Ireland have exclusive jurisdiction over any dispute arising from or connected with this Agreement, save that either party may seek injunctive relief in any court of competent jurisdiction.
IN WITNESS WHEREOF, the parties have executed this Agreement as of the date indicated.
CLIENT
Aisling Byrne
Chief Technology Officer
Liffey Digital Group Limited
Date: ____________________
DEVELOPER
Conor Walsh
Founder and Lead Developer
Shannon Code Studios Limited
Date: ____________________

Available as a print-ready PDF or an editable Microsoft Word (.docx) file.

What Is a Software Development Agreement?

A Software Development Agreement governs the commissioning of bespoke software — a Client pays a Developer (a freelancer, agency, or specialist firm) to design, build and deliver a defined software product. It is distinct from a Software Licence (which governs use of existing software) or an MSA + SOW (which governs ongoing services across multiple engagements).

In Ireland, the central legal issue is IP ownership. Under sections 21-28 of the Copyright and Related Rights Act 2000, when a Client commissions a Developer to create work, the Developer (as author) RETAINS copyright by default — unless the Developer is the Client's employee OR there is an express written assignment. This means a Client paying €80,000 for custom software can be left with only an implied licence, with no right to assign, sub-licence or assert ownership against third-party challenges. The IP assignment clause is essential, not optional.

The template is suitable for Irish solo developers, agencies (Galway / Dublin tech corridor) and consultancies serving Irish clients, with built-in compliance with the AI Act (EU) 2024/1689 — Article 50 transparency for AI components (in force 2 August 2026), Article 53 GPAI obligations (in force 2 August 2025) — and with patent protections under the Patents Act 1992 for any patentable inventions in the Deliverable.

What's Covered in This Template

The template covers the full bespoke-software lifecycle with Expert unlocking the sophisticated protections.

Client & Developer

Identification with CRO, registered address, signatory.

Project Scope

Project name, overview, deliverables list, technology stack.

Timeline & Milestones

Start date, target end date, milestone breakdown with fee allocation.

Fees & Payment

Fixed price / Time & Materials / Milestone-based; payment schedule.

IP Assignment (essential)

Express assignment + moral rights waiver — cures CRRA 2000 trap.

Background IP Retention

Developer's generic libraries / methodologies retained with Client licence.

Acceptance Testing (Expert)

Acceptance criteria, testing window, rejection / snag-list procedure.

Source Code Escrow (Expert)

Tri-party deposit with NCC Group or Iron Mountain; release triggers.

Warranty + Bug Fix (Expert)

12-month free bug remediation; severity tiers and response targets.

Maintenance & Support (Expert)

Monthly retainer or T&M with defined included / excluded scope.

Confidentiality + Non-Solicit (Expert)

Mutual confidentiality + non-poach of staff (typically 12 months).

AI / ML Disclosure (Expert)

AI Act risk classification + training data provenance.

Termination

For cause + convenience (with termination fee).

Governing Law

Irish law, exclusive jurisdiction; injunctive relief preserved.

How to Create a Software Development Agreement

Generate an institutional-grade Software Development Agreement in minutes — with the CRRA 2000 IP trap already cured.

  1. 1

    Identify Client and Developer

    Legal names, CRO / equivalent registration, registered address, signatories.

  2. 2

    Define Project Scope

    Project name, overview, deliverables list, technology stack.

  3. 3

    Set Timeline & Milestones

    Start, end, milestones with fee allocation per milestone.

  4. 4

    Configure Fees & Payment

    Fixed price / T&M / milestone, total fee, payment schedule, expenses.

  5. 5

    Confirm IP Assignment

    Default wording cures the CRRA 2000 trap; assignment trigger (acceptance / payment).

  6. 6

    Add Acceptance Testing (Expert)

    Acceptance criteria, testing window, snag-list procedure.

  7. 7

    Add Escrow + Warranty + Maintenance (Expert)

    Source code escrow, warranty period + severity tiers, monthly retainer.

  8. 8

    Add Confidentiality + AI Disclosure (Expert)

    Mutual confidentiality, non-solicit, AI components + training data provenance.

Why Doxuno documents are different

Four things that make our templates more thorough than AI-generated drafts and more current than static template libraries.

Accurate

Country-specific legal content

Drafted with legal expertise for each jurisdiction, far more thorough than AI-generated drafts that copy generic clauses across borders.

Always current

Always current with the law

Templates carrying statute references are continuously updated as the law changes. Your document always reflects the current legal framework.

Free PDF

Print-ready PDF

Free to download. Vector text, embedded fonts, statute citations baked in. Print, sign, file. Ready for any signing flow including electronic signature.

Word · .docx

Editable Word (.docx)

Continue editing in Word after download. Add custom clauses, reuse the template for similar agreements, or share with a colleague for collaborative review.

Requires Expert one-time unlock or any paid Doxuno subscription.

Legal Considerations in Ireland

Software development for Irish clients touches multiple regulatory regimes — IP, services, data, AI — each requiring specific contract terms.

This template is for information only and is not legal advice. Custom software development typically involves material financial commitments, IP allocation decisions and regulatory compliance obligations; you should engage Irish commercial / IP solicitors for material engagements.

Drafted for CRRA 2000 + AI Act 2024/1689

CRRA 2000 sections 21-28 — The Commissioned-Work IP Trap

Under the Copyright and Related Rights Act 2000, copyright in software is the author's by default. Section 23(2) creates an exception for employees (works created in the course of employment vest in the employer). For COMMISSIONED work by a Developer who is NOT the Client's employee, no such exception applies — the Developer retains copyright unless there is an express written assignment. A Client paying for software development without an IP assignment is left with only an implied licence — narrow, hard to enforce, and inadequate for resale or transfer to a third party. The template includes an express present assignment + moral rights waiver to cure this default.

Patents Act 1992 — Patentable Inventions in Software

While "software as such" is excluded from patentability under section 9(2)(c) of the Patents Act 1992, software that produces a "technical effect" (data compression algorithms, image processing, control systems) may be patentable. If the Deliverable might include patentable inventions, the IP assignment must cover patent rights expressly (as the template does), and the Developer must comply with the section 16 first-filing obligation. The Ireland-based filing is the standard route, with subsequent international extension via PCT.

Sale of Goods and Supply of Services Act 1980 — Implied Terms

Section 39 of the SGSSA implies that the Developer will perform the Services with reasonable skill and care, within a reasonable time (section 40), and at a reasonable charge if not agreed. Section 55 permits exclusion / modification of these implied terms in B2B only to the extent fair and reasonable. A liability cap with proper carve-outs (IP indemnity, confidentiality breach, GDPR fines, fraud, personal injury) satisfies this fairness test in standard B2B engagements.

AI Act (EU) 2024/1689 — Article 50 Transparency and Article 53 GPAI

If the Deliverable includes AI components, the AI Act imposes phased obligations. Article 53 (in force 2 August 2025) requires General-Purpose AI (GPAI) model providers to disclose transparency information (training data summary, copyright compliance, technical documentation). Article 50 (in force 2 August 2026) requires AI systems interacting with humans to be transparent about their AI nature and to watermark AI-generated content. The contract should require the Developer to disclose all AI components and confirm compliance with applicable obligations; the Client retains responsibility as the deployer.

EU Data Act 2023/2854 — Switching for Cloud-Hosted Deliverables

Applicable from 12 September 2025, the Data Act imposes switching, exit and interoperability obligations on providers of data processing services. If the Deliverable includes hosted SaaS components, the Vendor must support customer switching (max 2-month notice with auto-termination per Article 25). Even where the Deliverable is delivered as source code, hosted components used during development (CI/CD, monitoring, observability) may bring the engagement within scope.

GDPR + Data Protection Act 2018 — If Personal Data Is Processed

If the Deliverable processes personal data (user authentication, customer records, employee data, telemetry), GDPR Article 28 requires a Data Processing Agreement (DPA) governing the Vendor's processing on the Client's behalf. The DPA covers processing subject-matter, duration, type/categories of data, controller / processor obligations, sub-processor terms, audit rights, and end-of-engagement deletion / return. Best practice is a separate DPA incorporated by reference; standalone DPAs are easier to update and reuse across multiple engagements.

Frequently Asked Questions

Create Your Software Development Agreement Now

Generate an institutional-grade Irish Software Development Agreement in minutes — with the CRRA 2000 IP trap already cured. Configure acceptance testing, source code escrow, warranty, maintenance, confidentiality and AI disclosure with the Expert tier.

Free PDF · Editable Word with Expert · No account required