Your second project with the same client shouldn't need a new contract — but without a master services agreement, it does, and every clause you won the first time is back on the table. This generator builds a clean, ready-to-sign one-page MSA in minutes — master terms and renewal, the SOW mechanism with order of precedence, billing rails, IP ownership, a liability cap, and termination that pays you through the notice period. Fill in the fields, preview it live, and copy or download it — free.
The one-page MSA updates live as you type — free to preview. Enter your email to copy or download it.
Enter your email to unlock your finished MSA — copy the formatted text to your clipboard or download it as a file (opens in any browser, prints to PDF). We'll also send you consulting launch tips — no spam, unsubscribe anytime.
Preview is always free · Email unlocks copy & download
The generator above builds all seven parts automatically. Here's what each one does and why it matters.
Name both sides, then state what the document is: the master framework that governs every engagement between you and this client from signature forward. The whole economic point of an MSA is that the second project starts with a one-page SOW instead of a 12-clause negotiation — this paragraph is what makes that true.
When it starts, how long it runs, and — the part consultants get wrong — how it renews. The standard shape is an initial 12-month term that auto-renews unless either party gives notice 30 days before the term ends: you're never locked in, and the framework never silently lapses mid-project. Fixed-term and open-ended options exist for relationships that genuinely don't renew.
This is the heart of an MSA: each engagement is a signed Statement of Work incorporated into the master by reference. The order-of-precedence clause settles fights before they start — the MSA controls over any SOW, an SOW controls over anything else, and no SOW amends the master unless both parties initial the change. Without it, you have two documents each claiming to win.
Set the rails once at the master level — the billing basis (fees in each SOW, a master hourly rate, or a retainer), the invoicing cadence, and Net terms — so no invoice is ever a fresh negotiation. Add teeth: interest on overdue amounts and the right to pause the affected SOW rather than terminate the relationship. Every future SOW inherits all of it.
State the rule once and let it govern every SOW: deliverables transfer on full payment of the SOW that produced them, on written acceptance, or never (client gets a license). Either way, carve out your Background IP — the pre-existing tools, templates, and methods that make you fast — or you'll slowly sign away the machinery of your own business.
The most-negotiated clause in any MSA, and the one solo consultants most need. A client's claim for consequential damages — their lost revenue, their missed launch — can dwarf your entire fee, so both sides cap total liability, typically at fees paid in the prior 12 months, with indirect damages excluded entirely. It's mutual, cheap to offer, and the first thing procurement will expect to see.
Either party can end the framework on notice (30 days is the MSA norm), every open SOW ends with it — and the client pays for work performed through each SOW's termination date, the sentence that makes your final invoices enforceable. The clauses that should outlive the relationship (IP, liability, governing law) are named as survivors. Then both parties sign, once.
They stack: the MSA is the frame, each SOW is a project inside it, the contract stands alone, the change order amends any of them. Sign the biggest document the relationship actually justifies.
What it does: The relationship framework: master terms and renewal, the SOW mechanism with order of precedence, billing rails, IP, a liability cap, and termination — signed once, governing every SOW after it.
When to use it: A client with repeat work, a multi-project roadmap, or an ongoing relationship — the moment a second project is plausible, the MSA pays for itself.
What it does: The engagement document that hangs inside this framework: background, in-scope/out-of-scope lists, deliverables, milestones, assumptions, and acceptance criteria for one project.
When to use it: Under a signed MSA, for every new project — one page of scope instead of a new contract.
What it does: A standalone single-engagement agreement: parties, services, term, fees, termination, IP, and confidentiality in one document with no master/SOW structure.
When to use it: A one-off project with a client you're unlikely to see again — everything in one document, no framework needed.
What it does: The single-engagement foundation with contractor-status clauses front and center: not-an-employee language, enumerated services, deposit, IP, and termination.
When to use it: Your first paid engagement, or any client who needs the employment-relationship question answered in writing.
What it does: A one-page amendment that references the governing document — this MSA, a contract, or a specific SOW — and records adjusted scope, a signed fee impact, and a revised timeline.
When to use it: Mid-project, when the scope of a signed SOW moves. It amends the SOW; the MSA keeps governing.
Every one of these shows up the moment a consultant graduates from one-off projects to repeat clients. The generator above defaults away from all six.
Without a master framework, project two with the same client re-opens every negotiation you already won on project one — the liability cap, the IP wording, the payment terms — while the client's team changes and forgets what was agreed. The MSA exists so the second project starts with both parties signing one page of scope. If you've exchanged more than two contracts with one client, you needed this document two contracts ago.
When a client's project manager writes an SOW with 45-day payment terms or IP-transfers-on-delivery wording, it now contradicts the master. Without a precedence clause you don't have a framework — you have two documents in a shoving match, and the shoving match happens exactly when money is on the line. This generator bakes the winner in: the MSA controls over any SOW, and no SOW amends the master unless both parties initial the change.
The engagement is a $15,000 SOW; the client's revenue through the system you're advising on is $40 million. Uncapped, their consequential-damages theory — your analysis delayed our launch — points at all of it. The cap (fees paid in the prior 12 months is the market default) is what makes solo consulting survivable arithmetic. It's mutual, so offering it first costs you nothing and signals you know how enterprise paper works.
If every SOW sets its own invoicing and terms, every invoice is a negotiation and your accounts-receivable cycle is whatever a different project manager feels like that month. Set the rails once at the master level — billing basis, invoice cadence, Net terms, interest on overdue amounts, the right to pause an SOW after 15 days' non-payment — and every future engagement inherits them without a conversation.
The client gives notice on the master while two SOWs are mid-delivery. If the agreement is silent on what happens next, your final invoices for that in-flight work are theoretical — and if auto-renewal has no non-renewal window, you can be locked into (or locked out of) a second year without noticing. One sentence fixes the money: the client pays for all services performed through each SOW's termination date.
Plenty of consultants get handed a master agreement by a bigger company's procurement team. The three sections that will be tilted: liability (capped for them, uncapped for you), IP (transfers on delivery, not payment), and termination (they can exit on 15 days, you owe 60). Mark those three up before you sign anything — every one of them is negotiable, and none of them will be offered to you voluntarily.
An MSA is the frame; each link below is a picture you hang in it — price it, scope it, sign it, amend it, bill it. These free tools cover every step.
The document that hangs inside this framework — background, in-scope/out-of-scope lists, deliverables, milestones, assumptions, and acceptance criteria for one engagement, on one formatted page.
The original SOW builder — a full nine-section scope document with milestones and acceptance criteria. Pair it with this MSA when a project needs more scope depth than one page.
A signed SOW under this MSA just moved? Reference the governing document, list the adjusted scope, and set a revised fee and timeline — a one-page amendment with live delta math.
Ending the whole relationship, SOWs and all? Send written notice under the master's termination clause — for-convenience / for-cause / end-of-term / non-renewal wording, the notice clock, work in progress, and the final invoice on one formatted page.
The client wants post-engagement restrictions alongside the master? Build a covenant that holds up — a narrowly-defined restricted market, non-solicit and no-serve-competitor restrictions, a period a court respects, carve-outs, and stated consideration on one page.
The single-engagement foundation instead of a master framework — contractor status, enumerated services, payment terms with a deposit, IP assignment, and termination on one page.
Pair a performance layer with this master — response times, a resolution target, support hours, escalation, reporting, and capped service credits on one page.
Need extra capacity under this master? Bring a subcontractor in properly — a defined workstream, flow-down of the master's terms, fees, IP assignment to you, and a client non-solicit on one page.
Win the work before you paper the relationship — the full guided proposal builder with client context, problem statement, scope phases, deliverables with timeline, four pricing models, terms with a validity window, and signature blocks on one page.
Price the work before you paper it — line-item services with qty and rate, an optional monthly retainer line, a validity period, and live totals. Accepted quote numbers flow straight into the next SOW.
Referencing a separate signed NDA in the confidentiality sentence? Generate one — mutual or one-way, with a survival period and standard exclusions, formatted and ready to sign.
The relationship outgrew even the master's billing options? Build the dedicated retainer agreement — monthly or hourly retainer terms built for ongoing engagements.
SOW delivered — now bill for it under the master's payment rails. From/bill-to, hourly or fixed-fee line items, payment terms mirroring this MSA, and a due date. Free.
Niche quiz, rate calculator, proposal, quote, contract, SOW, MSA, change order, contractor agreement, engagement letter, retainer agreement, invoice, and more — every tool on the site, all free.
A great MSA protects a relationship — the Consulting Launch Kit creates them. Get a one-line positioning statement, 3 productized offers with pricing, a rewritten bio, a cold-outreach email sequence, a proposal template, and a 30-day plan to land your first 3 clients — personalized to your niche and delivered instantly. Just $29.
Get the launch kit — $29 →One-time · No subscription · 7-day money-back guarantee