1. What you are actually deciding
  2. The factors to weigh
    1. The shape of the relationship
    2. The contract value and who your client is
    3. The promises you make about response times
    4. How much of your client's data you touch
    5. The template you hand to small business clients
    6. What happens when the retainer ends
  3. How an Artificer Legal lawyer helps you make the call
  4. The contract you already have

A client who has sent you odd jobs by email for two years asks you to take over their whole IT environment: monitoring, patching, backups, helpdesk and after-hours response, all for a flat monthly fee. The work means remote access to their network, a promise to show up when things break, and revenue you will start budgeting staff around. This is the moment most IT firms start wondering whether they need a managed services agreement, and the honest answer is that the question is not as simple as it sounds.

What you are actually deciding

No Australian statute requires an IT firm to sign a managed services agreement before it looks after another business's systems. A contract for services can be formed by a quote, an email or even a handshake, and plenty of firms operate that way for years. So the real question is not whether the law forces you to have a written agreement. It is whether the informal arrangements you already rely on are carrying more risk than you realise.

The decision underneath the question is a choice between three ways of doing business:

  • Ad hoc engagements: every job quoted separately, scoped in an email, invoiced when done, with no ongoing commitment either way.
  • A managed services agreement: one written contract that sets out the services, the fee, the response times and the limits of liability for the whole relationship.
  • A managed services agreement plus statements of work: the master agreement holds the standing terms and a statement of work for each client or project sets the specific scope, which is the structure larger IT firms use when clients run different environments.

The options are not mutually exclusive, and firms often move through them in order as clients grow. But the informal option is not a neutral default. The emails and quotes you send are already forming contracts, whether you think of them that way or not. A managed services agreement does not create obligations that would not otherwise exist. It decides what those obligations are, in writing, before a dispute does it for you.

The factors to weigh

The shape of the relationship

An agreement earns its keep when the work stops looking like a series of jobs and starts looking like an ongoing service. The features that push the balance towards a written managed services agreement are:

  • Recurring revenue: a monthly or annual fee means you are committing resources in advance and the client is committing to pay.
  • Remote access: once you hold credentials to a client's network, both sides need to know what you may and may not do with them.
  • Response commitments: any promise to respond within a set time, or to keep systems available, is a promise a court can hold you to.
  • Multiple contacts: several people at the client raising tickets makes scope disputes routine.
  • Third-party systems: supporting software and hardware you do not own or control creates liability you cannot fully manage by good work alone.

Compare the two approaches directly:

  • Informal terms: the client's expectations come from whatever was said in a sales email. Scope creep is resolved by arguing about what was included. Your liability is whatever a court infers the parties intended.
  • Managed services agreement: scope, exclusions, response times and liability caps are defined in writing. Disputes are resolved by reading the document, not by reconstructing a conversation.

The tipping point is the retainer. The moment a client pays you to be there whether or not anything breaks, you have taken on a duty to respond, and the terms of that duty deserve to be written down.

The contract value and who your client is

A managed services agreement is a freedom-of-contract document in most business-to-business deals, but not all of them. The Australian Consumer Law (ACL), which sits in Schedule 2 of the Competition and Consumer Act 2010 (Cth), treats a person who acquires services as a consumer when the amount paid or payable is $100,000 or less, or when the services are of a kind ordinarily acquired for personal or household use (s 3). Whether the client is a company does not matter. What matters is the price of the services, so the total contract value is the figure to watch.

That threshold sits inside the normal range of managed services pricing. A client paying $3,000 a month for a 12-month term is paying $36,000 for the services, which is under the line. That client is a consumer for the purposes of the ACL, and the statutory consumer guarantees apply to your work, including the guarantee that services are rendered with due care and skill (s 60). The ACL then makes it void to exclude, restrict or modify those guarantees in the contract (s 64). A clause that says "no liability for any failure to perform" simply does not operate for that client, no matter how clearly it is drafted.

For contracts above $100,000 the consumer guarantees do not apply, and the parties are largely free to allocate risk as they choose. Two qualifications matter. First, in any proceeding under the ACL the client is presumed to be a consumer unless you prove otherwise (s 3(10)), so the burden of showing that a contract sat above the threshold is yours. Second, the freedom of contract that exists above the threshold is not unlimited, as the next two factors show.

The promises you make about response times

Section 18 of the ACL prohibits engaging in conduct in trade or commerce that is misleading or deceptive, or likely to mislead or deceive. It applies to every supply of services, not just supplies to consumers, and it covers representations made before the contract as much as terms inside it.

This is where over-promising hurts. An agreement that promises 24/7 response when you only staff business hours, or marketing that says unlimited support when the retainer covers a defined list, is a representation that can be misleading. The same logic runs through the scope you set. If your agreement says you monitor the servers but says nothing about the printers, and the client later claims you were responsible for them, the written scope is your answer, provided it was communicated before the deal was done.

A managed services agreement is best treated as a promise you intend to keep. Set response times you can actually meet, or structure them as a priority schedule that grades incidents by severity. A realistic service level description protects you twice over: it is the legal measure of what you promised, and it is the document that forms the client's expectations in the first place.

How much of your client's data you touch

Managed services usually mean handling personal information on the client's behalf: employee records in the directory, customer details in the accounting system, health information in a medical practice's files. Under the Privacy Act 1988 (Cth), an entity that handles personal information is generally an organisation that must comply with the Australian Privacy Principles, but a small business with an annual turnover of $3 million or less is exempt (ss 6C and 6D). That exemption is still in force at the time of writing, although its removal has been flagged as part of the ongoing reform of the Act, so the position is worth checking before you rely on it.

The exemption never covered every IT firm anyway. A firm is not a small business operator for privacy purposes if it provides a health service and holds health information, if it discloses or collects personal information for a benefit, service or advantage, if it is a contracted service provider under a Commonwealth contract, or if it is related to a larger entity (s 6D(4)). An IT firm supporting a medical practice, or servicing a government agency under contract, is likely to be covered regardless of its turnover.

Your agreement should allocate the data-handling obligations whichever side of the exemption you fall on. Set out what access you have and for what purposes, how you secure client data, what happens if you use subcontractors, and who notifies whom if there is a breach. Clients increasingly expect their IT provider to commit to these points in writing, and the agreement is the natural place for them.

The template you hand to small business clients

A managed services agreement is usually a standard form contract: you prepare it once and hand it to each client on a take-it-or-leave-it basis. That brings the unfair contract terms regime into play.

Under s 23 of the ACL, an unfair term in a standard form consumer contract or small business contract is void. A small business contract is one where at least one party employs fewer than 100 people or has a turnover under $10 million (s 23(4)). Most of your clients will satisfy that test, and so will many IT firms themselves, which matters when a larger client hands you its template instead. A term is unfair when it causes a significant imbalance in the parties' rights, is not reasonably necessary to protect the legitimate interests of the party advantaged by it, and would cause detriment if it were applied or relied on (s 24). The party relying on the term must prove it is reasonably necessary, and a contract is presumed to be standard form unless proven otherwise (ss 24(4), 27(1)).

The regime carries real teeth. Proposing an unfair term, or applying or relying on one, is itself a contravention that can attract a pecuniary penalty of up to $100 million for a body corporate, three times the benefit obtained, or 30% of turnover, and up to $2.5 million for an individual (s 224). The terms that most often cause trouble in managed services agreements are unilateral price increases without notice, automatic renewal clauses with no realistic exit, broad exclusions of liability that reach beyond protecting a legitimate interest, and rights to suspend service that can be exercised without warning. None of these is automatically void. Each needs to be drafted so it is transparent and proportionate to a real interest you are protecting.

What happens when the retainer ends

An ongoing service relationship does not end cleanly unless the agreement says how. The client's network is configured with your credentials, their data sits on systems you administer, and your team holds knowledge of how their environment works. A managed services agreement should cover termination for convenience on notice, termination for breach, and a transition-out process: the return of data and credentials, the handover of documentation, and any exit fee for work done at the end. Without these, an unhappy client can hold your data hostage, or you can be left supporting a system you no longer get paid for because nothing in the contract says when the obligation ends.

A decision about whether to formalise your services does not need to be made on the strength of an article. An Artificer Legal practitioner can work through it with you:

  • Audit what you already promised: we review the quotes, emails and proposals you have sent clients to identify terms you may already be bound by, so the agreement starts from reality rather than a blank page.
  • Stress-test the assumptions: we check which clients fall under the $100,000 consumer threshold, which fall under the small business contract test, and where your privacy obligations sit, so the drafting matches the actual risk.
  • Draft the agreement and statements of work: we build the scope of services, exclusions, response times, payment terms, liability caps and transition-out clauses around how your firm actually operates.
  • Calibrate the liability provisions: we size caps and indemnities against your exposure and your insurance, and make sure the exclusions survive contact with the consumer guarantees and the unfair contract terms regime.
  • Negotiate with the client's lawyers: when a client pushes back on a clause, we tell you which points are worth holding and which are not.

The cost of getting it wrong is not the drafting fee. It is the dispute where a court reads the scope you never wrote down, or the letter about a term in a template you copied from the internet.

The contract you already have

A managed services agreement rarely answers the question "should I have one?" It answers a better one: what have I already promised, and do I want to be held to that version of it? For most IT firms the honest answer is that they are already in contracts with their clients, formed by emails, quotes and proposals, on terms nobody sat down and wrote. The moment you take on a retainer, remote access and a response commitment, you have crossed into territory where the informal version of those terms will cost you more than the written one.

To weigh it up: the agreement earns its keep when the relationship is ongoing, when the contract value sits under the $100,000 consumer threshold, when you make response-time promises, when you handle client data, and when your standard form terms must treat a small business client fairly. If most of those factors point one way, the decision has effectively made itself. If they point in different directions, that is the moment to have a lawyer work through them with you.