trio.so

MSP client kit

Templates for every stage of a client relationship: discovery, contract and SLA, onboarding, QBRs, incidents and offboarding. They reference each other, so you sign, onboard, review and hand over every client the same way.

16 files in Word, Excel and PowerPoint. Free, and yours to brand and reuse.

Where client work goes wrong

Most problems with clients come from steps nobody wrote down. These come up again and again, and each one has a file in the kit.

Every technician onboards a client differently

Someone skips the test restore or leaves the previous provider's agents running, and you find out during the first incident.

06 Onboarding tracker55 tasks in order, each with an owner and a test for when it's done. Go-live comes after every device is enrolled.

Clients argue about what's covered

Without a written scope, every new laptop, office move or evening call turns into a negotiation.

05 Scope and responsibility matrix58 activities marked included, billable or not offered, with who does each one. It's signed as part of the agreement.

The SLA promises numbers nobody defined

If response and resolution mean different things to you and the client, and the clock never pauses, service credits end in a dispute.

04 SLA scheduleA priority matrix, response and resolution defined, clock pauses, escalation, and credits with a cap.

QBRs get skipped or turn into ticket counts

The client never sees the risk trend or the replacement plan, so renewals and projects stall.

10 QBR deck and 11 monthly reportThis quarter next to last, security posture, a four-quarter replacement plan, and decisions with owners.

Exits leave a mess behind

Passwords sent by email, devices unmanaged once your agents come off, no record of what was handed over.

14 Offboarding tracker and 15 handover documentAccess transferred before your tools come off, recovery keys exported, data deletion confirmed in writing.

See inside

Shown here with sample data. In the files, the parts you fill in are highlighted so you can find them.

SLA targets table: response, updates and target resolution for P1 to P4

04 SLA schedule. Response and resolution are defined before the targets, so a missed target means the same thing to both sides.

What's in the kit

Numbered in the order you use them. Open 00 Start here first: it shows how the files connect and how to brand them.

Win

Before the contract

01 Discovery questionnaireDOCX

53 questions for the first technical call: users, devices, email, network, backups, security, budget.

02 Client environment workbookXLSX

Twelve sheets for sites, contacts, users, devices, servers, network, SaaS, domains, vendors, admin accounts and findings. Kept current for the whole contract.

Sign

The contract

03 Managed services agreementDOCX

22 clauses, from fees and data protection to exit and transition, with an order form for services and rates.

04 SLA scheduleDOCX

Impact and urgency matrix, P1 to P4 targets, clock rules, escalation, exclusions and service credits.

05 Scope and responsibility matrixXLSX

58 activities marked included, billable or not offered, with who does each one.

Onboard

Signature to first QBR

06 Client onboarding trackerXLSX

55 tasks in eight phases, each with an owner, a day and a definition of done. Milestones and a RAID log.

07 Kickoff meeting agendaDOCX

A timed 75-minute agenda and the access request list to send ahead.

08 Welcome letter for staffDOCX

The email the client sends its team before go-live, with a printable support card.

09 Security baselineXLSX

50 controls with targets, scope, evidence and an exceptions register.

Run

Every month and quarter

10 QBR deckPPTX

13 slides with speaker notes: summary, SLA, tickets, security posture, assets, roadmap, budget and actions.

11 Monthly service reportDOCX

Two pages a client can read in five minutes.

12 Change request formDOCX

Risk, rollback plan and approvals for any change that affects users.

13 Incident notification templatesDOCX

First notice, update, resolved and post-incident review.

Exit

When a client leaves

14 Client offboarding trackerXLSX

39 tasks from notice to archive, in an order that never leaves devices unmanaged.

15 Transition handover documentDOCX

Everything the next provider needs, without a single password in it.

Get the kit

We'll email you the kit. It usually arrives within a minute.

  • All 16 files in one ZIP, sorted into the five stages, sent to your work email
  • A start-here guide that shows how to brand them in about 15 minutes
  • Works in Microsoft Office and Google Docs, Sheets and Slides

We may follow up about trio.so. You can unsubscribe at any time. Privacy policy

Run every client from one console

trio.so has a multi-client console for MSPs. It manages Windows, macOS, Linux, iOS/iPadOS and Android devices for all your clients, with patching, remote access and compliance checks. These steps from the kit happen there:

  • 06Enrol every client device, then check coverage against the reconciled device list.
  • 09Show encryption, screen lock and patch status per device as evidence for the baseline.
  • 10Pull device, patch and compliance numbers for the QBR and the monthly report.

FAQ

Yes. Edit it and use it with as many clients as you like. A one-line credit to trio.so sits in each footer; you can delete it.

Yes. Replace your MSP name in the headers, then search for the highlighted fields. The guide (00) walks through it.

They're a strong starting point, not legal advice. Contract law differs by country and state, so have a lawyer review them and add your own data processing agreement where the law requires one.

Yes. Upload them to Google Drive and open them there. The Excel dropdowns and status colours carry over.

They're common example values: 30 minutes to respond to a P1, 14 days for OS security updates, 15 minutes for screen lock. Set your own based on your staffing and what your plans include.

That's where we send the kit. We may also follow up about trio.so's MSP console, and you can unsubscribe at any time.