Professional Services Agreement Template (Free, Word)

What a professional services agreement actually does

A professional services agreement governs the delivery of expertise rather than goods: consulting engagements, accounting and bookkeeping work, IT implementation, design and marketing retainers, engineering studies, recruiting searches. Unlike a product sale, the thing being bought is partly defined as the work proceeds — which is exactly why services relationships generate so many disputes. The two sides routinely discover, three months in, that they had different assumptions about what was included, when it would be done, who owns the output, and what happens when the client's priorities shift.

A good PSA front-loads those conversations. It is not long for the sake of being long — most solid PSAs for small and mid-sized engagements run 6–12 pages — but it answers, in writing, every question the parties would otherwise argue about: What exactly is being delivered? How is it accepted? What does it cost, and when is payment due? Who owns the work product? Who pays if a third party sues? How does either side get out?

One structural decision comes first. For a single engagement, a self-contained PSA works fine. For an ongoing relationship with multiple projects, the standard pattern is a master services agreement (MSA) holding the legal terms (IP, confidentiality, indemnity, liability, termination) plus individual statements of work (SOWs) holding the commercial terms for each project (scope, deliverables, schedule, fees). The MSA + SOW structure means you negotiate the lawyers' clauses once and only negotiate scope and price per project. If you expect repeat work, build the MSA structure from day one — converting later is messier than starting right.

Scope of services: the clause that prevents scope creep

Scope disputes are the most common professional-services dispute, and they are almost always a drafting failure rather than bad faith. The scope clause (or SOW) should contain four things:

• Deliverables, not effort. "Provider will deliver a migration plan, a configured production environment, and two training sessions" is enforceable. "Provider will assist with the migration" is an argument waiting to happen. Where the engagement genuinely is time-and-materials advisory work, say so explicitly and define it in hours, not outcomes.
• Acceptance criteria and an acceptance window. State how the client signals acceptance (written sign-off), how long they have to review (5–10 business days is typical), what happens on silence (deemed acceptance after the window protects the provider; clients will push back), and the rejection-and-cure loop for deficient deliverables.
• Assumptions and client dependencies. If the schedule depends on the client providing data, access, approvals, or staff time, write those dependencies down and state that provider delays caused by missed client dependencies extend the schedule and may be billed.
• A change-order process. Anything outside the written scope requires a signed change order stating the delta in fees and schedule before work begins. This single sentence is the difference between billing for out-of-scope work and donating it.

Fees, invoicing, and payment terms

Pick the fee structure that matches the risk allocation, then nail down the mechanics. The four standard structures: fixed fee (provider bears estimation risk — only sensible with a tight scope and a change-order clause), time and materials (client bears the risk — pair it with a not-to-exceed cap or budget-alert threshold if the client demands predictability), monthly retainer (for ongoing advisory work — define what the retainer includes, whether unused hours roll over, and the overage rate), and milestone-based (payments tied to accepted deliverables — define each milestone objectively so payment isn't hostage to subjective satisfaction).

The mechanics matter as much as the structure. The clause should state the invoicing cadence (monthly in arrears is the default; an upfront deposit is standard for new clients), payment terms (Net 15 or Net 30 — Net 60+ is a financing arrangement, price it accordingly), late-payment interest (1–1.5% per month or the statutory maximum, whichever is less), and — critically for the provider — a right to suspend work after written notice when invoices are materially past due. Suspension is far more useful in practice than termination or litigation: it forces resolution without ending the relationship. Cover expenses (reimbursable at cost with prior approval over a threshold) and taxes (fees exclusive of sales/use taxes, which are the client's responsibility; provider responsible for its own income taxes).

Intellectual property: who owns the work product

This is the clause that gets DIY templates in the most trouble, because the legal default is the opposite of what most clients assume. Under US copyright law (17 USC 201(a)), copyright vests in the author — the service provider — not the paying client. The "work made for hire" doctrine only flips that default in narrow circumstances, and generic deliverables (reports, code, designs produced by an independent firm) frequently don't qualify. Without an express written assignment, the client may hold only an implied license to its own deliverables. Our technology & SaaS consulting agreement guide covers the case law in depth; the drafting answer is the same across industries:

• Express present assignment, conditioned on payment: "Upon full payment of the fees for the applicable deliverable, Provider hereby assigns to Client all right, title, and interest in the Deliverables." The payment condition is the provider's best leverage; clients should confirm it is payment for that deliverable, not the entire engagement.
• Background IP carve-out with license: The provider keeps pre-existing tools, templates, methodologies, and libraries, and grants the client a perpetual, royalty-free license to use them as embedded in the deliverables. Without this, a provider either contaminates its toolkit or breaches; with it, both sides get what they actually need.
• Residual knowledge: The provider may reuse general skills, know-how, and techniques retained in unaided memory — but not the client's confidential information. Providers need this to stay in business; clients should make sure it doesn't swallow the confidentiality clause.
• Third-party and open-source materials: The provider identifies any third-party components in the deliverables and warrants they are properly licensed for the client's intended use.

Indemnification and limitation of liability

These two clauses travel together and absorb the most negotiation time on larger deals. The principles that keep them sane:

• Indemnities are for third-party claims. An indemnity obligates one party to defend and cover the other when an outsider sues — it is not a catch-all damages remedy between the parties. The standard provider-side indemnity covers claims that the deliverables infringe a third party's IP; the standard client-side indemnity covers claims arising from materials the client supplied. Keep mutual indemnities for bodily injury, property damage, and gross negligence or willful misconduct.
• Cap liability at a multiple of fees. The market norm for professional services is a cap equal to fees paid (or payable) in the 12 months preceding the claim. Providers should resist uncapped exposure on a five-figure engagement; clients should resist caps below fees paid, which make the remedy illusory.
• Exclude consequential damages — mutually. Neither party should be liable for lost profits, lost revenue, or indirect damages. A services firm billing $50,000 cannot rationally insure the client's $5M business outcome.
• Negotiate the carve-outs, not the cap. The real action is in what escapes the cap and exclusion: indemnification obligations, breach of confidentiality, IP infringement, and gross negligence/willful misconduct are the conventional carve-outs. Each one a party adds shifts real risk — treat the carve-out list as the negotiation, because it is.

Term and termination

Every PSA needs three exits. Termination for convenience lets either party (or sometimes only the client) end the engagement without cause on written notice — 10 to 30 days is typical. Providers should pair it with payment for all work performed through the effective date, plus non-cancellable commitments incurred in reliance on the engagement; on fixed-fee work, a wind-down or early-termination fee is reasonable. Termination for cause follows material breach with a cure period (10–15 business days for most breaches; payment defaults sometimes get a shorter fuse), and immediately on insolvency events. Effect of termination is the part templates skip: final invoicing and payment timing, delivery of work-in-progress in its then-current state, return or destruction of confidential information, and an express survival clause keeping confidentiality, IP assignment, indemnification, liability limits, and payment obligations alive after the agreement ends. Without survival language, the clauses you most need post-termination are the ones a court may find died with the contract.

Supporting clauses most templates forget

• Confidentiality: Mutual, covering business, technical, and financial information exchanged in the engagement, with standard exclusions (publicly known, independently developed, rightfully received) and compelled-disclosure procedure. If sensitive discussions precede signature, put an NDA in place first.
• Independent contractor status: The provider controls its own methods, equipment, and schedule; no benefits, withholding, or authority to bind the client. Remember the contract label is evidence, not a defense — if the working relationship looks like employment under the IRS or state-law tests, the clause won't save it.
• Non-solicitation: Neither party hires away the other's personnel during the engagement and for 6–12 months after, carved back for general job postings. Far more enforceable than a non-compete, and usually all either side actually needs.
• Insurance: For engagements with real exposure, require commercial general liability and professional liability (E&O) coverage at stated limits, with certificates on request. Clients procuring technical services increasingly require cyber coverage too.
• Warranties and disclaimers: Provider warrants services will be performed in a professional and workmanlike manner consistent with industry standards, with re-performance as the exclusive remedy for breach; all other warranties disclaimed in conspicuous text.
• Dispute resolution and governing law: Pick a state, pick a forum, and decide between courts and arbitration deliberately. Add an escalation step — executives confer in good faith before anyone files — which resolves a surprising share of disputes at zero cost.
• Assignment and subcontracting: No assignment without consent (carve-out for merger/sale of business); subcontracting either prohibited or permitted with the provider remaining fully responsible.
• Notices, force majeure, entire agreement: Boilerplate, but the entire-agreement clause is what prevents a stray email or proposal deck from being argued into the contract later.

Common mistakes in DIY professional services agreements

• Scope by reference to a proposal. Attaching the sales proposal as the scope imports its marketing language ("world-class," "end-to-end") into an enforceable document. Rewrite scope as deliverables before signing.
• No change-order clause. The provider does the extra work to keep the client happy, then has no contractual basis to bill for it.
• IP silence, or unconditional assignment. Silence leaves the client with an implied license; assignment unconditioned on payment leaves the provider chasing invoices for work the client already owns.
• One-way indemnities and uncapped liability. Common in client-side templates; a provider who signs one has bet the firm on a single engagement.
• No suspension right. Without it, a provider facing unpaid invoices has only the nuclear options of terminating or suing.
• No survival clause. Confidentiality and IP terms that quietly expire with the agreement.
• Recycling the same template across engagement types. A fixed-fee implementation, a T&M advisory retainer, and an embedded staff-augmentation arrangement allocate risk completely differently. One template cannot serve all three.

How to generate a professional services agreement in Word with LexDraft

You can apply everything above in two ways. The fast, free path: LexDraft's service agreement builder walks you through the scope, fee, IP, and termination decisions in your browser and produces a Word-ready professional services agreement built on attorney-drafted standards for US federal and state jurisdictions. Pair it with the clause library to compare standard, provider-favorable, and client-favorable wording for the clauses negotiated hardest — indemnification, liability caps, and IP assignment — and run anything a counterparty sends back through the clause risk checker. All of LexDraft's free generators and checkers live in the free tools hub.

For drafting and negotiating directly in Microsoft Word, the LexDraft add-in builds the full agreement from the templates library, inserts and adapts clauses inline, and redlines counterparty paper without leaving the document — see features and pricing for what the free tier covers. Two boundary checks before you generate: if the "services provider" is an individual working under your direction on your schedule, you may need an employment agreement instead — the employment agreement builder covers that path — and if the engagement is strategic advisory work by an individual consultant, the consulting agreement for professional services firms guide addresses that variant directly.

Frequently asked questions