MSAs, project quotes and risk sign-offs for managed service providers
A managed service provider signs a few big documents with each client and a steady stream of small ones: hardware quotes, project change requests, authorizations to test their network, and the occasional letter where the client turns down your advice. SignMaster handles both kinds, with an API and webhooks for the parts you'd rather automate.
Updated November 5, 2026 · 3 min read
On this page
What an MSP gets signed
| Document | Who signs | Notes |
|---|---|---|
| Master services agreement | The client's owner or officer, then you | The legal terms, signed once |
| Service schedule or SOW | The client | Per-user or per-device pricing, scope and onboarding |
| Service level agreement | The client, with the MSA | Response and resolution targets by priority |
| Hardware and software quotes | Whoever approves spending | Approved before you order |
| Security testing authorization | Someone with authority over the systems | Scope, dates, addresses and contacts |
| Risk acceptance letter | The client's owner or officer | When they decline a recommendation |
| Offboarding and data return | The client | What you hand back and what you delete |
The template library has a master services agreement and a service level agreement to start from. Use this template opens either in SignMaster with the blanks marked.
New client, start to finish
- 1
Send the stack as one envelope
MSA, service schedule and SLA travel together. Put the client's office manager first to fill in contacts and user counts, the owner second to sign, and yourself last to countersign.
- 2
Protect the sensitive ones
For the network diagram or the testing authorization, require an access code SignMaster emails to the signer before the document opens.
- 3
Let reminders do the chasing
Set a sign-by date before your onboarding kickoff. If the owner is traveling, a signer group lets any one of the client's officers sign.
- 4
Close the loop
Everyone gets the sealed PDF with its certificate. On paid plans, with Save signers to Contacts on, the client's signers land in your contacts, with phone and company filled from their fields.
When the client says no
You recommended offsite backups, multi-factor sign-in or replacing the firewall that's past support, and the client said not this year. Write that down. A one-page risk acceptance names the recommendation, the risk in plain words and the client's decision, signed by someone who can make it. If something goes wrong later, the conversation starts from that page, not from memory. Send it by link and set reminders, because nobody rushes to sign this one.
Policies for the client's staff
Clients often ask you to roll out an acceptable use or security awareness policy. Get the staff list as a CSV and bulk send the acknowledgment, one envelope per employee, so the client has a signed copy from each person.
Automate the rest
- Webhooks on Crew and Company send signed JSON when an envelope is sent, viewed, completed, declined, voided or expired. Point them at your PSA if it accepts webhooks, or at Zapier, Make or n8n. See webhooks.
- The REST API creates envelopes from templates and reads their status, for quotes your own tools generate. See the API.
- Connect an AI lets you ask Claude or ChatGPT which client agreements are still unsigned, and start drafts. Anything that emails people waits for your approval. See Connect an AI.
Pricing
Account managers, project leads and the service desk manager who send documents each need a seat. Crew is $49 a month for 5 people and includes the API, webhooks and your logo on signing pages. Company is $99 a month for 15 people, and extra seats are $8 a month. New workspaces get 14 days of Crew free. Compare plans.
What it doesn't do
- It isn't a PSA, RMM or documentation platform, and it has no built-in connector to one.
- It doesn't bill clients or collect payments.
- It doesn't store client passwords. Don't ask for them on a signing page.
- It sends signing links by email; copy a link to send it another way.
Questions? Answers.
How do I get a client to sign off on declining a security recommendation?
Send a short risk acceptance letter that names the recommendation, the risk and the decision, to someone with authority to accept it. The sealed PDF records who signed and when.
Can SignMaster send signed agreements into my PSA?
Through webhooks, on Crew and Company. If your PSA accepts a webhook, point SignMaster at it; otherwise use Zapier, Make or n8n in between. There's no built-in PSA connector.
Can my client's employees sign an acceptable use policy?
Yes. Bulk send the policy from a CSV of staff. Each employee gets their own envelope and link, and the results file shows who has signed.
Is there an API?
Yes, on Crew and Company: create envelopes from templates, check their status and manage webhooks. See the developer docs.