Answer
What should be in a service agreement?
Scope, exclusions, price and change basis, timing, payment, and how it ends. Everything else is optional.
What is included, what is excluded, the price and how changes are priced, the timing, the payment schedule, and how either party ends it. Those six cover nearly every dispute that occurs in practice.
Small-business service agreements tend to be either a paragraph in an email or a long document copied from somewhere and never read by either party. Both fail in the same way when something goes wrong, because the disputes that actually occur concentrate in a small number of areas, and neither format reliably addresses them.
Scope and exclusions come first and carry the most weight. What is included, stated concretely enough that a third party could tell whether it was done, and what is not — including the things a reasonable customer might assume. Exclusions feel adversarial to write and are what prevent the argument, because the argument is always about something nobody named.
Price and the basis for changing it come next, and the second half is the one omitted. A price without a stated change basis means every variation is a negotiation conducted mid-job, when both parties are committed and neither is comfortable. Saying how additional work is priced — a rate, a method, a requirement for written agreement before proceeding — converts that into a routine step.
Timing needs both a schedule and an honest statement of what moves it. Service work is affected by access, weather, third parties, supply and the customer's own decisions, and an agreement asserting fixed dates with no dependency stated will be breached by ordinary events. Naming the dependencies is not weakness; it is the difference between a delay that was anticipated and one that reads as a failure.
Payment terms, including when payment is due relative to what, and what happens if it is late. And termination: how either party ends the arrangement, with what notice, and what is owed for work already done. Termination is the term people most dislike discussing at the start and most need when things deteriorate, and its absence is why deteriorating engagements drag on rather than ending cleanly.
Beyond those six, additions should be there because a real risk in your work requires them rather than because a template contained them. Liability limits, insurance, intellectual property in produced material, confidentiality, subcontracting, and any regulated obligations specific to the field all matter in the businesses where they matter and are noise elsewhere. Long agreements assembled from templates are not safer than short specific ones; they are less likely to be read, which is its own risk.
Almost every service dispute is about something the agreement did not mention, and the list of things it usually does not mention is short enough to memorise.
Answer Production Engine, Context Theory
Related questions
Is an email exchange enough?
It can be, if it contains the six terms and both parties clearly agreed. What makes email risky in practice is not the format but that agreement is scattered across a thread and the terms were never gathered in one place. A single summary message setting out the six and asking for confirmation is a legitimate agreement and takes a few minutes.
Do we need a lawyer to write it?
For a standard, repeated service, a well-structured document reviewed once is usually proportionate, and the review is worth more than the drafting. Where the work carries genuine liability exposure, involves regulated activity, or the contract value is significant, the review is not optional. What is rarely wise is adapting a template found online without anyone reading it against what you actually do.
METHOD
Every figure below carries its source and the date it was verified. Nothing on this page is asserted.
The numbers on this page.
| What | Value | Specific to |
|---|---|---|
| Buyers who eliminate vendors publishing no pricing, before contact | 60% | Category-wide |
| Buyers preferring a rep-free purchase path | two-thirds | Category-wide |
| Share of the buying journey completed before contacting a vendor | 60% | Category-wide |
2026 B2B buyer surveys · verified
Gartner · March 2026 · verified
What is specific to this page.
| Kind | Claim | Check it against |
|---|---|---|
| Procurement | Service disputes concentrate in six areas — scope, exclusions, change pricing, timing dependencies, payment and termination — so an agreement covering those addresses nearly every dispute that occurs in practice. | The business's own disputed engagements, classified by which of the six terms was absent or ambiguous. |
| Workflow | A price without a stated change basis makes every variation a negotiation conducted mid-job when both parties are committed, which a stated rate or method converts into a routine step. | The business's own variation history, checked for whether a change basis existed in the agreement. |
| Workflow | Service timing depends on access, weather, third parties, supply and customer decisions, so an agreement asserting fixed dates without stated dependencies will be breached by ordinary events. | The business's own late deliveries, classified by whether the cause was a dependency the agreement named. |
| Procurement | Termination terms are least discussed at the outset and most needed when an engagement deteriorates, and their absence is why poor engagements continue rather than ending cleanly. | Engagements the business wished to exit, checked for whether a notice provision existed. |
Each row would be wrong on another industry's page. Where a sourced figure exists it is in the table above instead; these are the constraints that shape the work and do not happen to be numbers.
Start with the measurement.
Reading about a benchmark is not the same as knowing your own number. The audit produces yours, measured rather than estimated.
$497 · delivered in 5 business days · credited against month one