IT services proposal template for MSPs selling to small businesses
An IT services proposal template is a fixed structure that a managed service provider uses for every offer it sends: the client’s problem, the scope, service levels, price, start date and terms. Without one, proposals drift into long lists of tools and features that a business owner cannot judge. With one, every proposal answers the same questions in the same order, and it is easier to write, check and walk through.
This template is for MSPs selling to small and mid-sized businesses, roughly 10–50 staff, in the UK and the US. It follows the findings meeting in our MSP sales process: if the owner has not already agreed the problem and the priorities, a proposal will not fix that.
What should an IT services proposal include?
| Section | What it answers | Keep it to |
|---|---|---|
| Summary | What we propose and why, in one paragraph | Five sentences |
| Your situation | The problem in the client’s words | Short paragraph |
| Scope | Users, devices, sites and services covered | A table |
| What is not included | Exclusions and how extras are handled | A short list |
| Service levels | How to get help, when, and how fast you respond | A table |
| First projects | Fixes from the assessment, in order | A numbered list |
| Onboarding | Steps and dates for the first weeks | A short timeline |
| Price | What is charged, how it changes | One table |
| Data and security | How you handle their data and access | A short paragraph |
| Terms and next step | Term, notice, who signs, by when | Bullet points |
Ten sections sound like a lot, but most fit on a page each or less. Owners read the summary and the price; the rest is there so nobody is surprised later.
How do you write each section?
Summary
Write it last. Say what you propose, for whom, and the main change it brings.
(Fictional client.) We propose fully managed IT support for Harbour Dental’s two practices, covering staff devices, Microsoft 365 and backups, starting on the date agreed below. The aim is fewer interruptions at reception and one number to call when something breaks.
Your situation
Repeat what the owner told you on the first call and in the findings meeting. Use their words, not yours. If they said "the Wi-Fi drops every afternoon", write that rather than "network performance issues". Our list of discovery call questions for MSPs helps you collect this before you write.
Scope
List what you will look after. A table works best:
| Item | Included | Notes |
|---|---|---|
| Staff users | Named count | Joiners and leavers handled by request |
| Laptops and desktops | Named count | Business-owned devices only |
| Microsoft 365 or Google Workspace | Yes | Licences billed separately or included, say which |
| Backups | Yes | What is backed up and how often |
| Network and Wi-Fi | Main office | Other sites by agreement |
What is not included
This section prevents most later disputes. Name the usual grey areas: personal devices, specialist software, printers, phone systems, out-of-hours work and projects. Say how you handle them: quoted separately, billed by the hour or not supported.
Service levels
Describe how the client asks for help (phone, email, portal), your working hours and your response times by priority. Only promise what your team can deliver every week, including holidays. A small table with three priority levels is enough.
First projects
Turn the findings into a short, ordered list: what you will fix first and why. This shows the owner that the assessment led somewhere.
Onboarding
Give the steps and rough dates for the first weeks: access and documentation, device enrolment, backups checked, introduction for staff. Our onboarding checklist for MSPs covers this in detail.
Price
State what you charge for, the unit (per user, per device or a fixed bundle), what makes the price change, and how you invoice. Keep one table. If you are still choosing a model, our guide to per-user, per-device and tiered pricing compares them.
Data and security
Some clients ask how their supplier handles their data. In the UK, Article 28(1) of the UK GDPR says that where processing is carried out on behalf of a controller, "the controller shall use only processors providing sufficient guarantees to implement appropriate technical and organisational measures in such a manner that processing will meet the requirements of this Regulation and ensure the protection of the rights of the data subject". See the UK GDPR text on legislation.gov.uk.
This is a quote, not advice on your role or contract. A practical habit: say in one short paragraph how you control access to client systems, and point to your data processing terms if you have them. Ask your own adviser what those terms should contain.
Terms and next step
Give the term, notice period, start date and who needs to sign. End with one action and a date: "If this looks right, reply to confirm by Friday and we will send the agreement."
How do you review a proposal before sending it?
IT services proposal review checklist
- The summary fits in one short paragraph
- The client’s problem is written in their words
- Scope lists users, devices, sites and services
- Exclusions are named, with how extras are charged
- Service levels are realistic for your whole team
- First projects follow from the findings
- Onboarding steps have rough dates
- Price has one unit and clear change rules
- Data and access paragraph included
- One next step with a date
- Read once by someone who did not write it
Which mistakes make IT proposals fail?
| Mistake | What the owner thinks | Fix |
|---|---|---|
| A long list of tools and product names | "I can’t judge any of this" | Describe outcomes; name tools only where they matter |
| No exclusions | "Everything is included", until the first extra invoice | Name the grey areas and how they are charged |
| Service levels nobody can keep | Trust drops in the first busy week | Promise what your whole team can deliver |
| Price in several units | "What will I actually pay?" | One unit, with clear rules for change |
| No start date or next step | The proposal sits in an inbox | One action and a date at the end |
| A generic template with another client’s name | "They don’t know us" | Use their words from the first call |
A proposal that reads as if it was written for this client, using what they told you, does more than any design. Keep a master template, but rewrite the summary, the client’s situation and the first projects every time.
Example service levels table
Fill in your own targets; the structure below is a starting point, not a recommendation.
| Priority | Example | Response target |
|---|---|---|
| Urgent | Nobody can work, or a security incident | [your target] |
| High | One person cannot work | [your target] |
| Normal | Requests and questions | [your target] |
How do you present the proposal?
Do not send a proposal cold and wait. Book a short call, share your screen and walk the owner through it section by section. Stop after the scope and the price and ask: "Does this match what you expected?"
Agree a decision date before you hang up. If a few days pass without a reply, our follow-up email after a sales meeting templates help you check in without pressure. If the owner pushes back, our guide to MSP sales objections has honest answers.
The same structure works for other professional services. Accountants who move clients from compliance to advisory work can use our guide on how to sell advisory services as an accountant.
Where does Arbyn Partners fit?
Arbyn Partners books meetings for B2B firms in the UK and the US, including MSPs, with business owners or decision-makers who have a real need, not a competitor or an existing client of yours. We fill your diary with first calls; the proposal and the rest of the sale are yours. You pay only for qualified meetings that take place: £150 in the UK and $200 in the US. The first qualified meeting is free, one per company, and there is no retainer. See our page on lead generation for MSPs.
More about Arbyn Partners is on our homepage.
FAQ
What is an IT services proposal template?
A fixed structure for every offer an IT provider sends: summary, the client’s situation, scope, exclusions, service levels, first projects, onboarding, price, data and security, and terms with a next step.
How long should an IT services proposal be?
Short enough to walk through on one call. Most sections fit on a page or less; the summary and price matter most to the owner.
Should a proposal list every tool we use?
No. Owners judge outcomes, scope and service levels. Name tools only where they matter to the client, such as Microsoft 365 or backups.
What should the exclusions section cover?
The usual grey areas: personal devices, specialist software, printers, phone systems, out-of-hours work and projects, and how each is handled.
Should I mention data protection in an IT proposal?
A short paragraph on how you control access to client systems and a pointer to your data processing terms helps. Ask your own adviser what the terms should contain.
Can Arbyn Partners help MSPs get more proposals out?
We book first meetings with owners or decision-makers who have a real need. You pay £150 in the UK or $200 in the US per qualified meeting held, and the first one is free.