A professional service agreement (PSA) defines the rules of engagement between your agency and every client you take on.

Get it right, and you have a document that prevents scope creep, guarantees payment, and gives you legal ground to stand on when things go sideways.

Most agencies use a generic contract they found online, swap in their company name, and hope for the best.

That’s how you end up doing 40% more work than you quoted, chasing invoices for 90 days, and losing ownership of frameworks you built years before the client showed up.

If you run an agency or lead a small services team, this guide breaks down exactly what belongs in your PSA, clause by clause, with example language you can use today.

What is a professional service agreement?

A professional service agreement is a legally binding contract between a service provider and a client.

It spells out what work gets done, how much it costs, who owns the output, and what happens if either side wants out.

For agencies, the PSA is the single most important document in every client relationship.

It’s not a formality.

It’s the thing you point to when a client says “I thought that was included” or “we assumed you’d handle that too.”

A strong PSA covers seven areas: scope of work, change orders, payment terms, intellectual property, confidentiality, termination, and liability. Skip any one of these, and you’re exposed.

A PSA is not the same thing as a proposal. Your proposal sells the work. Your PSA governs it. They’re separate documents with separate jobs.

PSA vs. MSA vs. SOW: which one do you actually need?

Agencies throw around “MSA,” “SOW,” and “PSA” like they’re interchangeable. They’re not. Using the wrong one costs you flexibility or leaves gaps in your legal coverage.

	Professional service agreement (PSA)	Master service agreement (MSA)	Statement of work (SOW)
What it does	Governs a single project or engagement	Sets overarching terms for an ongoing relationship	Defines specific deliverables, timelines, and fees for one project
When to use it	One-off projects or first-time clients	Long-term clients with multiple projects	Under an MSA, to scope each new project
Scope	Self-contained: covers legal terms + project details	Legal terms only, no project specifics	Project specifics only, no legal terms
Best for agencies that	Take on project-based work with defined start/end dates	Have retainer clients or recurring engagements	Already have an MSA and need to add new projects fast
Renegotiation	New agreement per project	Rarely renegotiated; new SOWs added underneath	New SOW per project, same MSA

The practical answer for most agencies: Start every new client with a PSA. If the relationship grows into ongoing work, upgrade to an MSA + SOW structure so you don’t renegotiate legal terms every time you kick off a new project.

If you’re a 5-person agency doing project work for SMBs, a well-built PSA handles 90% of your contracts.

You don’t need an MSA until you’re juggling multiple concurrent projects for the same client.

A common mistake: some agencies try to use a proposal as their PSA. Proposals are sales documents.

They describe what you plan to do and what it costs. But they rarely include IP clauses, liability caps, termination rights, or dispute resolution.

If your “contract” is just a signed proposal, you’re legally exposed.

Keep them separate. Send the proposal first. Once the client says yes, send the PSA for signature.

The 7-clause agency PSA stack

Most PSA templates online were written for enterprise procurement departments or law firms.

They’re 20 pages of boilerplate that doesn’t address the things that actually burn agencies: scope creep, disappearing clients, and IP disputes over work you built on your own dime.

The 7-clause agency PSA stack strips a professional service agreement down to the seven sections that matter most for agency-client relationships. Every clause exists to solve a specific problem agencies face.

Clause 1: Scope of work

This is where most agency contracts fail. Not because the scope section is missing, but because it’s too vague.

“Provide digital marketing services” is not a scope of work. Neither is “website redesign” or “brand strategy engagement.” These descriptions are invitations for the client to interpret the scope however they want.

Your scope clause needs four things:

What you will deliver. List every deliverable by name, format, and quantity. Not “social media content” but “12 Instagram static posts per month, delivered as Canva files.”

What you will not deliver. Exclusions are as important as inclusions. If your website project doesn’t include copywriting, say so. If your SEO retainer doesn’t cover paid ads, write it down.

How many revision rounds are included. Two rounds per deliverable is standard. Anything beyond that gets billed hourly. State the rate.

Client responsibilities. What does the client need to provide, and by when? Brand guidelines, login credentials, content approvals, feedback on drafts.

If the client doesn’t hold up their end, you need language that extends your timeline automatically.

Here’s example scope language for a web design project:

“Provider will design and develop a 10-page responsive website using WordPress. Deliverables include homepage design, 9 interior page templates, mobile optimization, and a 30-minute training session on the CMS. Two rounds of design revisions are included per page. Copywriting, stock photography, and ongoing maintenance are excluded from this engagement.”

Clause 2: Change order process

Scope creep is not a client problem. It’s a contract problem.

If your PSA doesn’t have a change order clause, you have no mechanism to say “that’s extra” without it feeling adversarial. The change order process makes scope changes routine, not confrontational.

Your change order clause should specify that any request outside the defined scope requires a written change order before work begins. The change order should include the additional scope description, revised timeline, and additional cost.

No verbal approvals.

No “we’ll figure it out later.”

The line that saves agencies money: “No work on any change request will begin until both Parties have signed the Change Order.”

That single sentence turns every out-of-scope request into a business conversation instead of a surprise invoice.

Here’s what this looks like in practice. A design agency is building a 10-page website.

Three weeks in, the client asks to add an e-commerce section with 50 product pages.

Without a change order clause, the agency either does the work for free (killing margin) or says “that’s extra” and the client feels blindsided.

With a change order clause, the conversation is simple: “We’d love to add e-commerce. Per our agreement, I’ll send over a change order with the additional scope, timeline, and cost.

Once you sign it, we’ll get started.”

No awkwardness. No argument. The contract did the hard work for you.

Build your PSA in a tool that tracks every clause. Upbase lets you store contract templates, link them to client projects, and track change orders alongside your task management, so nothing falls through the cracks.

Clause 3: Payment terms

Late payments are the number one cash flow killer for agencies under 20 people. Your PSA is your first line of defense.

Deposit before kickoff. 25-50% upfront is standard for project work. Retainers should be billed in advance of the service month. Never start work without money in the account.

Milestone-based payments. For projects over $10,000, tie payments to deliverables, not dates. “50% upon signing, 25% upon design approval, 25% upon launch” is clearer and more enforceable than “net 30.”

Late payment consequences. Include an interest rate on overdue invoices (1.5% per month is common) and the right to pause work if an invoice is more than 15 days past due.

Kill fee. If the client cancels mid-project, what happens? Your PSA should specify that all completed work gets paid for, plus a percentage of the remaining contract value (10-25% is typical).

Payment terms are not negotiable details you figure out later.

They belong in the contract from day one.

For retainer clients, your payment clause looks different. Bill at the beginning of each month for that month’s work. Include language that specifies unused hours don’t roll over (unless you want them to).

And define what happens if the client wants to reduce retainer hours mid-engagement.

Most agencies require 30 days’ notice for retainer changes.

Clause 4: Intellectual property

IP is where agency contracts get messy fast, especially for agencies that build reusable frameworks, templates, or proprietary tools.

The standard approach: the client owns the final deliverables upon full payment. You retain ownership of your pre-existing IP.

Your pre-existing IP includes any tools, templates, code libraries, frameworks, or methodologies you developed before or independent of the client engagement.

The client gets a license to use those things as they appear in the deliverables, but they don’t own them outright.

This matters. If you built a reporting dashboard template that you use across 15 clients, one client can’t claim exclusive ownership of it just because you used it on their project.

Portfolio rights also belong here. Most agencies want the right to showcase client work in case studies and portfolios. Include a default provision that allows this, with the option for the client to opt out in writing. Don’t make portfolio use something you have to ask for after the fact.

Clause 5: Confidentiality

You’ll see client financials, marketing strategies, login credentials, and internal communications.

They’ll see your processes, pricing models, and team structure. Both sides need protection.

Your confidentiality clause should define what counts as confidential information, state that both parties will keep it private, and list the standard exceptions (publicly available information, independently developed information, and legally required disclosures).

Set a duration. Confidentiality obligations should survive the contract for 2-3 years. Indefinite confidentiality clauses are hard to enforce and make clients nervous.

One thing agencies often miss: make sure your confidentiality clause doesn’t accidentally prevent you from using the client’s brand name. If your confidentiality language is too broad, referencing the client in your portfolio could technically violate it.

That’s why the portfolio rights clause in the IP section matters.

Clause 6: Termination

Every contract needs an exit door. The question is whether that door leads to an orderly transition or a legal fight.

Your termination clause needs three scenarios:

Termination for cause. Either party can end the agreement if the other side materially breaches the contract and doesn’t fix it within a cure period (10-15 business days is standard). Non-payment counts as a material breach.

Termination for convenience. Either party can walk away for any reason with 30 days’ written notice. This protects both sides. Clients aren’t locked into an agency they’re unhappy with, and agencies aren’t stuck with a client who’s become toxic.

What happens after termination. The client pays for all work completed through the termination date. The agency delivers all completed and paid-for work. Both sides return each other’s confidential information. Pre-existing IP stays with the agency.

The clause that protects your team’s time: “Upon termination, Client shall pay Provider for all Services performed and expenses incurred up to the effective date of termination.”

Without this language, you risk eating the cost of work already done.

Clause 7: Liability and indemnification

This is the “what happens when things go wrong” clause. It’s not fun to write, but it’s critical.

Limitation of liability. Cap your total liability at the total fees paid under the agreement. Without this cap, a client could theoretically sue you for damages that far exceed what they paid you.

For a $15,000 website project, you don’t want to be on the hook for $500,000 in “lost revenue” because the site went down for a day.

Indemnification. Each party agrees to cover the other’s losses if their own negligence or breach causes a problem. If the client gives you copyrighted images and you get sued, the client covers your legal costs.

If you deliver code that infringes on a third party’s patent, you cover the client’s costs.

No indirect damages. Exclude consequential, incidental, and punitive damages. You’re responsible for delivering what you promised, not for every downstream business impact the client can imagine.

How to write scope language that prevents scope creep

Scope creep doesn’t start when a client asks for extra work. It starts when your scope language leaves room for interpretation.

Here are three rules for writing scope that holds up:

Use quantities, not categories. “Social media management” can mean anything. “8 LinkedIn posts per month, each with a custom graphic and 150-word caption” cannot be misinterpreted.

Define the process, not just the output. If your process includes a discovery phase, wireframing, two rounds of feedback, and a launch checklist, write each step into the scope.

When a client skips discovery and wants to jump straight to design, you can point to the contract and explain why the process exists.

List what’s excluded. For every deliverable you include, there’s an adjacent service clients assume is included. Website design projects attract requests for copywriting, SEO, ongoing hosting, and content updates.

Call out each exclusion.

It’s not negative.

It’s clear.

The best scope language answers this question: if a neutral third party read this clause, would they know exactly what’s included and what’s not?

If the answer is no, rewrite it.

Here’s a before-and-after to show the difference:

Weak scope language: “Provider will manage Client’s social media presence across relevant platforms.”

Strong scope language: “Provider will create and publish 12 Instagram posts and 8 LinkedIn posts per month. Each post includes one custom graphic (1080x1080px for Instagram, 1200x627px for LinkedIn) and a caption of up to 200 words. Community management, paid advertising, influencer outreach, and platform analytics reporting are excluded.”

The weak version invites the question “Does that include responding to DMs?” The strong version already answered it.

Common PSA mistakes that cost agencies money

Using the same contract for project work and retainer work. A project PSA and a retainer PSA need different payment structures, different scope definitions, and different termination terms. A project ends when deliverables are complete. A retainer renews monthly. Don’t force one structure to do both jobs.

No cure period before termination. If your contract allows immediate termination for any breach, a client could argue that a missed deadline (even by a day) is grounds to walk away without paying.

Always include a cure period that gives both sides time to fix problems.

Vague IP language around pre-existing tools. If you use Figma templates, code libraries, or strategy frameworks across clients, your PSA must explicitly carve those out.

Otherwise, a client could claim ownership of tools you use with every other client.

Forgetting the “client obligations” section. Your timeline depends on the client providing feedback, approvals, and materials on time. If your PSA doesn’t address what happens when the client goes silent for three weeks, you absorb the cost of the delay.

No late payment teeth. A late payment clause without consequences is decoration. Include interest charges, the right to pause work, and (for extreme cases) the right to withhold deliverables until payment is received.

Tools for creating and managing your PSAs

You don’t need a lawyer to draft every contract from scratch. Start with a solid template, customize it to your engagement, and have a lawyer review your first version.

Here’s what the typical agency stack looks like for contract management:

Tool	What it does	Best for
PandaDoc	Document creation, e-signatures, templates	Agencies that want signing workflows built in
DocuSign	E-signatures and contract tracking	Agencies focused on getting contracts signed fast
HelloSign (Dropbox Sign)	Simple e-signature workflows	Small teams that want something lightweight
Google Docs + template	Free, collaborative editing	Solo consultants and very early-stage agencies
Upbase	Docs, tasks, and client management in one workspace	Agencies that want contracts linked to project delivery

The tool matters less than the habit. Pick one and use it for every engagement.

Stop managing contracts in one tool and projects in another. Upbase keeps your client agreements, project tasks, timelines, and communication in a single workspace. No more digging through email threads to find the SOW a client approved six months ago. See how it works →

Free professional service agreement template

We built a fill-in-the-blank PSA template designed specifically for agencies and service teams. It covers all seven clauses in the agency PSA stack, with placeholder text you can customize in 15 minutes.

Download the free professional service agreement template →

The template includes:

• Scope of work section with deliverables table, revision limits, and exclusions
• Change order clause with sign-off requirement
• Payment schedule with deposit, milestones, and late payment penalties
• IP ownership and pre-existing IP carve-out
• Confidentiality with defined duration
• Termination for cause and convenience with cure periods
• Liability cap and mutual indemnification

Customize it to your engagement, then have a lawyer review your first version. After that, you can reuse it across clients with minor adjustments.

FAQ

What is the difference between a professional service agreement and a contract?

A professional service agreement is a type of contract. The term “PSA” specifically refers to contracts that govern professional or specialized services, as opposed to product sales, employment, or real estate transactions. Every PSA is a contract, but not every contract is a PSA.

Do I need a lawyer to write a professional service agreement?

You don’t need a lawyer to draft the initial version. Start with a template, customize it to your agency’s services, and then have a lawyer review it once. That single review typically costs $500-1,500 and gives you a reusable document you can adapt for every future client.

How long should a professional service agreement be?

For most agency engagements, 4-8 pages is sufficient. Enterprise contracts with complex compliance requirements may run longer. The goal is completeness without unnecessary complexity. If your PSA is 20 pages, most clients won’t read it, which defeats the purpose.

Can I use one PSA for all my clients?

Use the same template, but customize the scope of work, deliverables, payment terms, and timeline for each engagement. The legal clauses (IP, confidentiality, liability, termination) can stay largely the same across clients. That’s the advantage of having a well-built template.

What happens if a client won’t sign a professional service agreement?

Don’t start work. A client who refuses to sign a contract is telling you they want the flexibility to change the rules mid-engagement. That’s a red flag, not a negotiation tactic. Every serious business expects contracts. If they push back on specific clauses, negotiate those clauses. If they refuse the concept of a contract entirely, walk away.