What it is
A Master Service Agreement (MSA) is the framework contract between an agency and a large client that sets the legal and commercial terms of the relationship itself, not of any single hire. It covers liability and indemnity, data handling and confidentiality, payment terms, SLAs such as response times or fill windows, and how the relationship can be terminated. Once signed, individual mandates run underneath it as statements of work (SOWs) or job orders, each referencing the MSA rather than re-negotiating it from scratch.
This is easy to confuse with terms of business, and the two are related but not the same thing. Terms of business is the UK-style standard agency agreement, fee percentage, guarantee period, rebate scale, typically drawn up for a single client or a single search. An MSA is what that same kind of framework looks like at enterprise scale: multi-entity, often multi-year, covering several subsidiaries, business units or regions under one legal umbrella, and it is the document large clients running a VMS panel or a formal procurement process usually insist on before any supplier is added.
An MSA is signed once and inherited by every job order that follows it. Get it wrong at enterprise scale and the mistake multiplies, it does not stay contained to one placement.
Why it matters
An MSA is negotiated once, usually by procurement or legal, and every job order that follows inherits its terms automatically. Get the liability cap, the data-handling clause or the payment terms wrong at that stage and the mistake does not cost one placement, it compounds across every mandate the account ever sends, sometimes for years. A poorly capped liability clause or a Net90 payment term buried in an MSA can quietly erode margin on volume that looks healthy on paper.
MSAs are also frequently the gate itself. Enterprise clients running a VMS or a formal supplier panel will not route a single requisition to an agency without an executed MSA in place, regardless of how strong the relationship with the hiring manager is. That makes the MSA less a formality and more a prerequisite: no signed MSA, no access to the pipeline of work sitting behind it, however many buying signals fire on the account.
How boilr handles it
boilr does not draft or negotiate an MSA, that stays a conversation between the consultant, procurement and legal, but it makes sure business development never gets ahead of the commercial reality on an enterprise account. Account status shows whether an MSA is executed, so outreach on a buying signal is never wasted chasing a job order that cannot legally be raised yet, and pushes toward the stakeholders who can actually get the MSA moving when one is not.
Once an MSA is in place, its SLAs, payment terms and renewal date live in the Company Brain alongside everything else known about the account, visible to every consultant who might touch that client, not just the one who negotiated it. If a job order or SOW is raised against an account without an executed MSA, or an SLA obligation is at risk of being missed, boilr flags the gap early enough to close it, rather than letting it surface at invoicing or renewal.
