Disputes between a small business and its clients rarely involve interesting law. They involve a question nobody wrote down.
Was that revision included? When was payment actually due? Who owns the files? What happens if the client goes quiet for two months and then wants to restart?
Each of those is a paragraph. Collectively they are the difference between a disagreement resolved in an email and one that consumes a fortnight.
The handshake arrangement
Common, and fine until it is not
- Scope understood differently by each side
- Payment timing assumed rather than agreed
- Revisions unlimited in practice
- Ownership of the work never discussed
- No agreed way to end the engagement
- Disputes argued from memory and tone
A written agreement
Two pages is usually enough
- Scope stated, with exclusions named
- Payment schedule and late terms fixed in advance
- Revisions bounded, with a rate for more
- Ownership addressed explicitly
- Termination route defined for both sides
- Disputes resolved by reading a clause
Scope, and what is not included
Scope causes more small business disputes than everything else combined, and it fails in a predictable way. Nobody demands a large amount of extra work. They ask for small things, repeatedly, each of which is easier to absorb than to challenge.
Two techniques make scope hold.
State what is included in concrete terms. Not "website design" but the number of pages, the number of concept rounds, what the client supplies and what you produce.
State what is not included. This is the half people leave out, and it is the half that does the work. Naming the obvious exclusions - ongoing maintenance, content writing, third-party costs, hosting, training - prevents the assumption that anything unmentioned was covered.
Then add the sentence that makes both enforceable: work beyond the stated scope is quoted and agreed separately in writing before it starts.
Payment terms that mean something
When payment is due, stated as a number of days from a defined event - invoice date, delivery, milestone completion. "On completion" invites an argument about when completion occurred.
A deposit or staged payments. For work of any length, a deposit before starting and milestone payments through the engagement spread the risk of non-payment rather than concentrating all of it at the end.
What happens when payment is late. Interest, a late fee, or suspension of work - whichever you intend to apply. State the consequence rather than relying on being able to improvise one later, and check your state's rules on what rate may be charged.
Who pays expenses, and whether they need approval above a threshold.
What happens if the client pauses. Long gaps are common and cause real difficulty. Agree what a pause means for the schedule and whether a restart fee applies.
Ownership of the work
This causes more genuine confusion than anything else on the list, because both parties hold a reasonable but incompatible assumption. Clients often assume that paying for work means owning everything associated with it. Providers often assume they keep their own tools, components and methods.
Where the agreement is silent the default depends on the type of work and on state law, and it is frequently not what either side expected.
Address it directly:
What transfers to the client, and when - commonly on full payment rather than on delivery, which also gives the payment terms teeth.
What the provider retains - underlying tools, libraries, templates, general methods and know-how.
What the provider may show in a portfolio or as a reference, and whether the client must approve that.
Where a brand name, logo or mark is involved, ownership interacts with trademark questions that run on their own rules, and the USPTO publishes an introduction to how marks work. For work of real value, this is a clause to have reviewed rather than drafted from a template.
Ending it
Every engagement ends. Agreeing the route in advance, while both parties are content, is far easier than negotiating it during a breakdown.
Notice. How much, and in what form.
Payment on termination. What is owed for work completed and work in progress.
Handover. What is delivered, in what format, and by when.
What survives. Confidentiality and ownership terms normally continue after the engagement ends; say so.
A termination clause is not a sign of pessimism. It is the part of the agreement that makes a bad engagement recoverable instead of ruinous.
Client service agreement checklist
Name both parties by their correct legal names
The entity, not a trading name. Get it from the register if unsure.
State the scope in concrete, countable terms
Pages, rounds, deliverables, sessions - not adjectives.
List what is excluded
Maintenance, content, third-party costs, training, hosting.
Bound the revisions and price the extras
A number, plus a rate for anything beyond it.
Require written agreement for out-of-scope work
Quoted and accepted before it starts.
Set payment due dates from a defined event
Days from invoice or milestone, not 'on completion'.
Take a deposit and stage the payments
Spreads non-payment risk across the engagement.
State the consequence of late payment
Interest, fee, or suspension. Check your state's limits on rates.
Address ownership explicitly
What transfers, when, and what you retain.
Say when ownership transfers
On full payment is common and reinforces the payment terms.
Cover confidentiality both ways
Often mutual in practice.
Define termination, notice and handover
For both sides, while both sides are content.
Say which state's law applies
Particularly where the parties are in different states.
Keep the signed copy with the client file
With the invoices and the correspondence.
Contract law is state-specific and the enforceability of particular clauses, including late payment charges and ownership terms, varies. Have an agreement reviewed by a licensed attorney in your state before you rely on it.
The clauses people skip
Which state's law applies. Easy to omit and awkward when the parties are in different states. Agreeing it in advance avoids a preliminary argument about where a dispute is even heard.
How disputes are handled. Whether there is a required conversation first, mediation, or arbitration. Arbitration clauses carry real consequences and are worth understanding rather than copying.
Whether the other party is a contractor or something else. If you are engaging people to help deliver the work, how those workers are classified is a separate question with its own tests, and the contract wording does not settle it.
Whether the client is the entity you think it is. Agreements signed with a trading name rather than a legal entity cause difficulty at exactly the wrong moment.
When it goes wrong anyway
Even a good agreement gets tested. What it gives you is a straightforward conversation: here is what we agreed, here is what happened.
Where payment stops, a documented demand is normally the next step, and it resolves a meaningful share of disputes on its own because it converts an awkward conversation into a clear one. Where it does not, small claims handles amounts within its limit - and if the client is a company rather than a person, identifying the right entity to name comes before anything else.
When to take advice
This covers the clauses that matter most in ordinary service arrangements. It is not a substitute for an agreement drafted or reviewed for your work, your state and your risks.
Speak to a licensed attorney in your state before relying on a template for anything substantial, where the work involves valuable intellectual property, where you are being asked to sign a client's own agreement containing indemnities or liability terms you do not fully understand, or where an existing engagement has broken down. A single review of a standard agreement you will reuse across every client is one of the better-value pieces of legal work a small business can buy.