Service agreement template for small business

This page may contain affiliate links from which Blur Studio earns commissions.

A service agreement is the workhorse contract for almost any small business that sells its time or expertise rather than a physical product, a consultant, a cleaning company, a marketing freelancer, a repair business. Searching for a template usually means one of two things: you're about to take on a new client and want something signed before work starts, or you got burned once on a job with no written terms and you're not doing that again. Either way, here's what actually needs to be in it.

Clauses: scope, price, payment, term, liability

• Scope of work. Exactly what you're doing and, just as important, what you're not doing. "Weekly lawn mowing and edging at the stated address" is specific. "Lawn care" is not, and it's the gap that "lawn care" leaves open that turns into an argument about whether hedge trimming was supposed to be included. Describe deliverables, frequency if it's recurring, and any explicit exclusions. How a scope sits next to a master agreement and a proposal is covered in statement of work vs master services agreement vs proposal.
• Price and payment terms. The total price or rate, what triggers an invoice (on completion, monthly, per milestone), when payment is due (net 15, net 30, due on receipt), and what happens if payment is late, a flat late fee or a stated interest rate, which varies by state in terms of what's legally allowed, so check your state's usury limits if you're setting one.
• Term and termination. How long the agreement runs, and how either side can end it early, how much notice is required, and whether any work already done gets paid for even if the engagement ends partway through. For ongoing monthly work, the retainer agreement template for agencies and consultants adds rules on unused hours.
• Liability and insurance. A limitation of liability clause (often capping damages at the amount actually paid under the agreement) protects you from being on the hook for consequential losses far beyond what you were paid. If the work carries real physical or financial risk, state what insurance you carry and, if relevant, require the client to name you as additionally insured on their policy or vice versa.
• Signatures. Both parties' names, the effective date, and a line for each signature.

Plain-language sample sections

Scope: "Provider will deliver monthly social media content (eight posts per month across two platforms, as specified in Exhibit A) for Client. Any additional platforms or posting frequency beyond this scope will be billed separately at Provider's then-current hourly rate." Payment: "Client will pay $1,200 per month, invoiced on the first of each month, due within 15 days of invoice date. Invoices unpaid after 30 days accrue a 1.5% monthly late fee." Termination: "Either party may terminate this agreement with 30 days' written notice. Client remains responsible for payment for all work completed through the termination date." These three paragraphs, filled in with your own numbers, cover the disputes that actually happen most often in practice, scope creep, late payment, and an unclear exit.

A filled-in liability clause

For a consulting engagement: "Provider's total liability under this agreement, whether in contract, tort, or otherwise, will not exceed the total fees paid by Client under this agreement in the three months preceding the claim. Neither party will be liable for indirect, incidental, or consequential damages." This kind of cap is standard in service agreements and protects a small consultancy from a claim that's wildly out of proportion to what they were actually paid, it's worth including even on a modest engagement, since the cost of a lawsuit doesn't scale down just because the contract value was small.

Two gaps that show up more than they should

The first is a missing or weak dispute resolution clause. Most small service agreements never mention what happens if a disagreement can't be resolved directly, leaving both sides defaulting to whatever a lawsuit would look like, which is slow and expensive for a contract that might only be worth a few thousand dollars. A short clause naming a venue (where any lawsuit would be filed) and, for larger engagements, requiring mediation before litigation, saves real time and money if a disagreement ever does happen. The second gap is around who owns work created mid-engagement if it's terminated early, a half-finished website, a partially written report. State explicitly whether the client owns and can use partial work product on early termination, and whether any additional payment is owed for it, rather than leaving that to be argued out after the relationship has already soured.

Sending and storing

Once the terms are agreed, QuickSigner, an electronic signature tool for uploading a document, placing signature fields, and sending it out to be signed online, gets this signed the same day instead of waiting on a mailed or scanned copy. Electronically signed service agreements are enforceable the same way as a wet-ink signature under the US ESIGN Act and state UETA laws, so there's no legal reason to use paper for this. If you send a new agreement with every client, the Business plan at $5 a month per user, $48 billed annually, adds reusable templates so the boilerplate clauses stay fixed and only the scope, price and client name change each time, confirm current pricing directly since plans can change. Store the signed copy somewhere you can actually find it later, attached to the client record in whatever system you use, not buried in an email thread, since the agreement is what you'll reach for first if a payment or scope dispute ever comes up six months in.

A dispute this would have prevented

A home cleaning company I talked to had been billing a client $340 a month for "weekly cleaning services" under a one-paragraph agreement with no scope detail. After four months, the client stopped paying, insisting the original quote included window washing, which the cleaning company had never actually done and never intended to include at that price. Neither side was lying, they'd genuinely remembered the original phone conversation differently, and with nothing written down beyond "weekly cleaning services," there was no way to settle it other than the client walking away owing $680 that was never collected. A one-line scope addition, "interior cleaning of kitchen, bathrooms, living areas and bedrooms; windows, walls and exterior surfaces not included unless billed separately," would have ended the disagreement before it started, and it would have taken thirty seconds longer to write than what they actually used. This is the pattern behind nearly every scope dispute I see: not a dishonest client, just two reasonable people who remembered an unwritten conversation differently, with no document to settle which version was right.

How I'd approach this

For most routine service work, the structure above, filled in with real specifics rather than generic language, is genuinely enough, I use something close to this for my own smaller engagements. Where I'd get a lawyer to review the specific language: anything with meaningful liability exposure baked into the actual work (physical safety, data handling, financial advice), or a contract large enough relative to your business that a dispute over it could be existential rather than just annoying. The scope section is where I'd spend the most of your own time regardless of contract size, a vague scope is the clause that costs small businesses money most often, far more than liability language ever does in practice. I'd also push clients gently toward milestone or recurring billing over a single lump sum at the end of a longer engagement, not because it's more profitable, but because regular invoicing is a natural check-in point that surfaces a souring relationship early, while there's still time to fix it, rather than only discovering a problem when the final bill goes unpaid. Contract red flags small businesses miss lists what to look for in a contract someone else sends you.