Service Agreements for Oregon Businesses: The Contract Between You and Your Clients
Every service business runs on the same promise — we do the work, you pay for it. The service agreement is where that promise gets terms. Done right, it prevents the two disputes that kill client relationships: what the work includes, and what happens when payment doesn't come.
This is Part 1 of the Contracts That Actually Protect You series. Part 2 covers independent contractor agreements — the people who work for you; Part 3 covers partnership and co-owner agreements — the contracts between owners themselves.
If you provide services for money — consulting, design, marketing, trades, bookkeeping, development, coaching — you have a service agreement with every client whether you wrote one or not. An email thread, a phone call, and a first invoice form a contract too. The question is never whether terms exist; it's whether anyone can prove what they are when it matters.
And it matters at two predictable moments. The first arrives mid-project, when the client asks for something you didn't price and believes they already bought it — they thought ongoing support and unlimited revisions; you thought a defined project. The second arrives after delivery, when the invoice ages and your leverage left the building with the deliverables. Nearly every service dispute I see is one of those two stories, and both are preventable with terms decided before the engagement starts.
Here's what a real service agreement settles.
Scope: Define Done
The single most valuable section of any service agreement is the one that defines what the work includes — and, just as deliberately, what it doesn't.
That means deliverables described specifically enough to be checked against, deadlines or a delivery cadence, and an acceptance mechanism: what constitutes completion, how the client signs off, and how long they have to raise problems before the work is deemed accepted and payment is due. Without acceptance language, "I'm not happy with it" becomes an indefinite excuse not to pay.
It also means limits stated out loud: how many revision rounds are included, what response times are and aren't promised, what counts as support versus new work. Clients don't abuse vague scope maliciously — they fill silence with assumptions, and every assumption favors them.
Change orders are where scope stays honest. The agreement should say that work outside the defined scope requires a written change — even a confirmed email — with its price. The discipline matters more than the format: businesses that quietly absorb "one quick addition" at a time routinely deliver twice the project for the original price, and the resentment that builds is a business killer with no contract remedy, because nothing was ever documented.
Client obligations belong in scope too. If the work depends on the client providing content, access, approvals, or decisions, the agreement should say so and address what happens to deadlines and fees when they don't. A stalled client shouldn't be able to stall your payment.
Payment: Terms That Protect the Person Doing the Work
Payment provisions do their job before the invoice is ever late.
Structure the money around your risk. Deposits before work begins, milestone payments tied to deliverables, or retainers replenished monthly all share one principle: never let the amount you're owed grow larger than the client's incentive to pay it. Delivering a completed project against a promise of payment in thirty days hands the client all the leverage.
State the mechanics. Invoicing schedule, due dates, accepted payment methods, and consequences of lateness — interest at a stated rate, suspension of work after a defined period of nonpayment, and the right to withhold further deliverables. A work-suspension clause is the most practical collection tool a service business has, and it only exists if the contract creates it.
Know Oregon's rule on attorney fee clauses. Many businesses add a clause awarding attorney fees if they have to sue to collect. Worth including — but understand that under ORS 20.096, Oregon makes one-sided fee clauses reciprocal: if your contract gives you fees when you win, the client gets fees if they win. That's not a reason to omit the clause; it's a reason to know that the clause raises the stakes in both directions, which itself discourages weak claims from either side.
Ownership and Use of What You Deliver
Service businesses routinely give away more than they mean to — or promise less than the client assumes. The agreement should say who owns the deliverables and when: on full payment is the provider's standard, so an unpaid client isn't holding your work with clear title. It should distinguish the client's deliverables from your pre-existing materials and reusable components — templates, frameworks, code libraries — which you license for use in the deliverable but keep. And if you want to show the work in your portfolio, say so in the agreement rather than asking permission later.
The Protective Layer: Liability, Warranties, and Endings
The clauses nobody reads until something goes wrong are the reason written agreements exist.
Limitation of liability. A cap tying your total exposure to the fees paid under the agreement is standard in services and worth having in nearly every engagement — without it, a modest project can carry immodest risk.
Warranties, scoped honestly. Promise what you control: that the work will be performed professionally and will conform to the agreed specifications. Disclaim what you don't: the client's business results. The agreement that quietly guarantees outcomes is the one that turns a disappointed client into a plaintiff with a contract claim.
Termination. Either side should have a defined exit: notice, payment for work performed through the end date, kill-fee terms for project work abandoned mid-stream, and delivery of what's been paid for. Engagements end; the agreement decides whether they end with an invoice or an argument.
Where disputes happen. Choice of Oregon law and a venue clause keeping disputes in your county are two sentences that prevent the absurd outcome of litigating a $6,000 invoice in another state.
If your clients sign up through your website rather than a signed document, the same terms have to live there and actually bind — as covered in the website terms of service post, online terms have their own formation requirements, and terms nobody agreed to protect nobody.
Bottom Line
A service agreement is the operating system for every client relationship: it defines done, structures payment so leverage never fully leaves your hands, keeps ownership of your own tools, caps your downside, and gives both sides a clean exit. Businesses running on email threads and goodwill have all the same disputes — they just have them without evidence.
The version of this document worth having is drafted once, for your actual services and your actual risks, and then reused across every engagement — which makes it some of the highest-leverage legal work a service business ever buys. At Track Town Law, I draft and review service agreements for Oregon and Idaho businesses — billed hourly and scoped with you before any work begins. Book a free consultation here.
This post is for general informational purposes only and does not constitute legal advice. Contract terms are fact-specific. Contact a licensed Oregon business attorney to review your client agreements.
