You quoted for the build over coffee, the client said "get started", and you had a staging environment running before a contract was ever mentioned. If that is how your engagements usually begin, you have company: developers and IT service providers routinely start work on the strength of a quote and a scope discussion. The question is what happens later, when the client's idea of "done", the deadline, or the final invoice stops matching yours.
An oral agreement can still bind you
In Australia there is no general rule that a contract must be in writing. An oral agreement can be a binding contract, and a chain of emails confirming price and scope can form one too. So the risk of working without a signed IT services agreement is not that you have no contract. It is that the contract is whatever each party can later prove.
The terms that decide a dispute are usually the ones nobody wrote down. If the client says the job included unlimited revisions and you understood two rounds, both versions can be genuinely held. Scope, deadlines, price adjustments, whether a phone call approved a variation: all of it is open to reconstruction from emails, messages and recollections months after the fact.
Take a straightforward example. You agree over email to build an inventory system for a retailer for $40,000, with a handover date and two rounds of revisions mentioned in passing. Six months later the client is withholding the final invoice, arguing that the "fix the stock issues" request was part of the original price. You are confident it was new work. Neither of you is lying. There is simply no document that settles it, and a third party, whether a lawyer, mediator or judge, can only weigh the email trail and the recollections.
That has practical consequences. A lawyer advising either side must trawl the correspondence to piece the terms together, and your version will differ from the client's. If the matter reaches court, the fight is as much about what the contract said as about who breached it. The process is slower and more expensive than it needed to be, and the uncertainty makes settlement harder.
What a written agreement forces you to pin down
A written IT services agreement does not need to be long to do its main job: converting the assumptions in your head into terms both parties signed. The clauses that earn their keep pin down what would otherwise be contested:
- Scope of work: what you will deliver and what is out of scope, stated as deliverables rather than outcomes, so a later request to "make it faster" cannot quietly become a new requirement.
- Timeframes and milestones: when work starts and lands, and what happens when the client's delays push the schedule out.
- Price and payment: what the fixed price covers, how variations are priced, when invoices are payable and what happens if payment is late.
- Acceptance: how the client confirms that a milestone or the finished product meets the brief, and what happens if they never respond, so "it is not finished yet" cannot run on indefinitely.
- Changes: a written process for varying scope, price or dates, so a verbal "can you also add..." cannot silently expand the job.
- Subcontracting: whether you can bring in other developers and who answers for their work.
- Intellectual property: who owns the code, designs and documentation when the project ends.
The last point is the one clients most often misunderstand. Under s 35 of the Copyright Act 1968 (Cth), the author of a work is its first owner. Software written by an independent contractor is owned by the developer who wrote it, and paying for the build does not by itself transfer that ownership. An IT services agreement typically fixes this by assigning ownership of the work to the client on full payment, while licensing back anything you need to reuse, such as libraries, tools and templates. Agreeing that up front prevents the argument that otherwise arrives at handover, when the client assumes the code is theirs and you know it is not.
Writing these points down also reduces the chance of a dispute in the first place. Each party discovers the mismatched expectations while the deal can still be adjusted, instead of after the work is delivered.
The dispute resolution clause: a ladder with a catch
A good IT services agreement does not only define the deal. It defines how a falling-out will be handled, in a dispute resolution clause that most commonly follows the same four steps:
- A party gives written notice identifying the dispute and what it wants done.
- The parties have a set period, commonly 14 to 21 days, to negotiate in good faith.
- If negotiation fails, the parties attempt mediation, or refer the matter to arbitration.
- Either party may then commence proceedings in the appropriate court.
The value of the ladder is that it tells both sides what happens next. Knowing the process prevents a dispute from becoming a war of accusation by email that drags on for months while development stalls.
The last two rungs need careful drafting, because a clause that compels arbitration can itself be struck down. In AghaeiRad v Plus500AU Pty Ltd [2025] FCA 1602, the Federal Court found a mandatory arbitration clause in a standard form online trading agreement to be an unfair term even though it applied symmetrically to both parties. Its practical effect was to shut customers out of court and out of class actions, and the cost of arbitration made it an unrealistic forum for most claims.
The lesson is that a dispute resolution clause should give the parties a structured path to resolution, not a way of denying the other side access to a court. Two drafting points follow:
- The clause should expressly preserve the right to seek urgent relief, such as an injunction to stop a breach, without first running the ladder.
- The clause should state what follows from missing a step. If it is drafted as a condition precedent to litigation, a party that skips the process can find its court claim barred.
For IT work between businesses of roughly equal bargaining power, these clauses are usually straightforward. Where a standard form contract is involved, they need more thought, which is where the regime below comes in.
The law now polices your template
Since the 2023 reforms, Australian consumer law directly regulates what can go into the kind of contract you and your clients actually use. Part 2-3 of the Australian Consumer Law (ACL), which is Schedule 2 of the Competition and Consumer Act 2010 (Cth), makes an unfair term in a standard form consumer contract or small business contract void: s 23. The term is treated as if it never existed, and the rest of the contract continues to bind the parties if it can operate without it.
A small business contract is one where at least one party employs fewer than 100 people, or had turnover under $10 million in its last income year: s 23(4). That covers most Australian IT providers and most of their clients, so the regime applies in both directions: to the client's standard form template you are asked to sign, and to your own template if you use one.
A term is unfair if it would cause a significant imbalance in the parties' rights and obligations, is not reasonably necessary to protect the legitimate interests of the party relying on it, and would cause detriment if it were applied: s 24. A term is presumed not to be reasonably necessary unless the party relying on it proves otherwise. Clauses that let one side vary the contract, extend deadlines or cap liability unilaterally are the kinds of terms that attract scrutiny.
The stakes are now real. Since the 2023 reforms, proposing an unfair term in a standard form consumer or small business contract can attract a civil penalty of up to $100 million for a body corporate, three times the value of the benefit obtained, or 30% of adjusted turnover, and up to $2.5 million for an individual: s 224. An unfair term is no longer merely unenforceable. It is a potential fine for the business that proposed it.
Where an Artificer Legal lawyer earns their fee
You do not need a bespoke 40-page agreement for every engagement, and you do not need a lawyer to send a one-page scope and payment schedule. But several judgement calls are worth taking advice on:
- The IP structure: whether the client takes an assignment or a licence, and what you keep for reuse across projects.
- The liability position: how a cap on liability and any indemnities are framed, and what they realistically cover when something goes wrong.
- Acceptance and variation drafting, the clauses that decide whether "finished" means finished.
- Whether a client's standard form template contains terms that are unfair, and what that means for both of you.
- How the escalation clause is wired: notice periods, the good faith language, the mediator or arbitrator, and the carve-out for urgent relief.
An Artificer Legal lawyer can review your template before you send it, mark up the client's template before you sign, and tell you where your existing arrangements sit, including whether the email chain you are working on already binds you. That assessment is usually quick, and it tells you what a short form agreement can realistically fix.
Skipping the paperwork still leaves you in a contract
The sharpest point in all of this is that skipping the paperwork does not leave you outside the contract. It leaves you inside a contract whose terms are whoever-can-prove-what, with no agreed process for the moment the relationship stops working. The cost of that assumption is not paid while the deal is going well. It is paid in the dispute, when scope, deadlines and ownership are all up for reconstruction, and when a dispute resolution clause that nobody read decides how the fight unfolds.
A written IT services agreement exists to make the deal provable and to give both sides a path when it breaks. That is what the scope, the IP clause and the dispute resolution ladder are for. None of it is ceremony. It is the difference between a dispute you can navigate and one you have to reconstruct from emails.
To recap: an oral agreement can bind you; a written agreement pins down scope, timing, price, variations and ownership; its dispute resolution clause gives both sides a way forward; and the unfair contract terms regime now polices standard form contracts with penalties attached. If your client work runs on quotes and emails, a short form agreement removes the largest source of risk in the relationship.