Skip to content
GullySales
← All articles

Notes for owners · Industry playbooks

How MSPs write a proposal the finance head will sign

How to write a managed IT proposal a finance head can compare with a salary: what it covers, what it excludes and how support is raised.

The GullySales team · Updated 13 Nov 2026 · 6 min read

Editorial illustration for How MSPs write a proposal the finance head will sign
On this page
  1. Who actually reads a managed IT proposal?
  2. What should the proposal say the fee covers?
  3. How do you handle the freelancer comparison?
  4. What should you ask in the first meeting?
  5. Where do these proposals stall?
  6. How does the first agreement turn into a renewal?
  7. What does discovery need to produce?
  8. How should risks be written so the finance head can act on them?
  9. What should the onboarding section say?
  10. What if the client asks for a discount?
  11. How do you write about security and compliance without overreaching?
  12. Who signs on your side, and what do they check?
  13. What to do next

An MSP proposal gets signed when the finance head can put it beside an IT executive's salary and see what they are getting for the difference. So write down what the per-user fee covers, what it does not cover, how help is raised and who answers, and what happens when the person who normally helps is away. Say it in plain words on two pages, and leave the brand logos for the website.

Who actually reads a managed IT proposal?

Two people, two questions. The founder or operations head started the conversation because something changed: the IT executive resigned, the company outgrew the freelancer, a European customer sent a security questionnaire. They want to know that someone will pick up the phone.

The finance head decides. They are not weighing technology. They are asking whether this fee is cheaper than an in-house hire, whether it is fixed or will creep, and what they are exposed to if it goes wrong. A proposal written for the first reader alone can die at the second.

What should the proposal say the fee covers?

Put it in a table the finance head can read in a minute.

ItemSay plainly
Users and devices coveredNumber of users, laptops, desktops, and which are included at the quoted fee
Support hoursWhich days and hours the help desk is open, and what out-of-hours cover exists
How to raise a ticketPhone, email or WhatsApp, and which one is the official channel
Response targetsWhat you will aim to reply within for urgent and routine issues, in your own words, agreed after discovery
Included workPatching, endpoint protection, backup monitoring, account setup and removal
Excluded workNew office setup, hardware purchase, major migrations, projects, and how each is quoted
Admin accessWho holds the passwords and what the client receives on exit
Term and noticeThe agreed term, the notice period and how renewal works

The exclusions row matters most. Later disputes come from something the client assumed was in the fee. If you write it first, you remove the surprise.

How do you handle the freelancer comparison?

You will be compared with a freelancer or a part-time engineer who costs less a month. Do not fight the number. Move the conversation. Ask the finance head to put four questions next to it. What happens when that person is ill? Who knows the admin passwords? Is there a record of what was fixed and when? Who is accountable if data is lost?

A written proposal can answer those four in a paragraph. A verbal pitch rarely does.

For example, a CA firm in Coimbatore with twelve staff calls a freelancer whenever printers or email fail. Then a client asks the partner how the firm protects their data. No answer. Your proposal states the user count, the backup arrangement, who holds the credentials and a simple record of issues handled, and the partner does not need to understand backup technology to see what the freelancer's setup lacks.

What should you ask in the first meeting?

Do not open with your services. Ask who looks after IT today and how they were found. Ask what broke last and what it cost the business that day. Count users, devices and locations. Ask whether any customer, auditor or insurer has requested something the company could not provide.

Write the answers into the proposal using the client's own words. A proposal that quotes their last outage back to them reads as written for them.

Where do these proposals stall?

At the finance head. The founder said yes, the proposal went to accounts, and nobody has asked what accounts needs. Offer a short call with the finance head, or a one-page summary they can read without the founder in the room: fee, what it replaces, what it excludes, term.

Follow up on a date you set at the meeting, and record it. Your sales process should include a stage between "proposal sent" and "signed", so that quiet proposals show up on a list instead of being forgotten. See also how to follow up on a quotation.

How does the first agreement turn into a renewal?

Keep a plain record: tickets raised and closed, devices added, risks you flagged and what was done. Walk the founder or finance head through it before renewal, not after they have started asking questions. A client who has seen what the fee bought rarely goes shopping.

It is also where referrals come from. The CA, the co-working neighbour and the industry association chat are the places your next client asks who looks after IT. A pleased client will pass on a name if you have made it easy to say.

What does discovery need to produce?

A proposal is only as good as the discovery behind it. Visit the office, or sit on a call with the screen shared, and collect a few facts that the fee depends on: how many people work there, how many devices and of what age, which software the business depends on, where files are stored, how email is run, and who holds the administrator logins today. Ask to see the router and the backup arrangement. Some firms discover during this conversation that nobody knows where the admin password is.

Write the findings into a short section of the proposal headed What we found. It shows the finance head the proposal is based on their office, not on a template, and it records the starting point against which later work is measured.

How should risks be written so the finance head can act on them?

A technical risk list means little to someone in accounts. Translate each risk into a business consequence and a decision. "No tested backup of the accounting data" becomes "if the main computer fails, the books may be unrecoverable; the fix is a backup that is checked, and it is in the fee". "Shared administrator login" becomes "former staff could still enter the system; the fix is individual logins".

List only the risks you saw. Do not exaggerate, and do not frighten the client into signing. Write what you saw, what could follow and what you propose to do, then say which items fall inside the fee and which would be quoted separately. The finance head can then approve the included items and choose on the others.

What should the onboarding section say?

Clients worry about the first weeks, when the change from the old arrangement to yours happens. Describe the steps without promising dates for them: collecting the inventory of devices and accounts, taking over the administrator credentials in the client's presence, installing the tools, testing the backup and introducing the help desk to the staff. Name who at the client's side needs to be available for each step, and mention what the staff will notice.

State clearly who owns the credentials and the documentation. The client owns them, and the proposal says so. That sentence removes a fear that has kept some owners with a poor provider for years.

What if the client asks for a discount?

The request comes at the finance head's desk, and it is reasonable to expect it. Do not cut the fee first. Ask what the client wants to change. Fewer users covered, reduced support hours or a longer term each have a cost and a consequence, and you can show the finance head the effect of each on the scope table. A discount that removes nothing from the scope teaches the client that the first number was inflated, and the next renewal begins with the same haggle.

If you do move on the fee, write the change into the proposal and keep everything else the same. Record the reason, so that a future proposal for a similar client stays consistent.

How do you write about security and compliance without overreaching?

Clients are asking more about security because their own customers ask them. Write what you do, in plain words, without promising outcomes. Say that endpoint protection is installed and monitored, that updates are applied, that user access is reviewed, and that backups are tested. Do not say that the client will be safe, compliant or protected from every attack. Compliance with a customer's questionnaire or a regulation depends on the client's own policies and on the advice of their auditor or legal adviser, and a proposal should say so.

Who signs on your side, and what do they check?

Before the proposal leaves, read it as the delivery lead and ask whether the team can do everything it says with the people and tools it has. A promise in the document that the engineers cannot keep becomes a dispute in the second month. Have one person outside the sales conversation read the exclusions and the response wording, and correct them before the client sees them.

What to do next

Take your last proposal and read it as a finance head would. Does it say what is excluded? Does it say who holds the credentials? If either answer is no, rewrite that page first.

If you want a second read on where your proposals stall and how enquiries reach you, tell us what you need and we will read it before we call.

Put the reading to work

Try this with your own records.

Bring a recent proposal and the buyer's original requirement. Mark the questions that remained unanswered and the assumptions your team made about scope or approval.

How to review the result

Ask someone outside the sales conversation to identify what is being offered, what is excluded, and how the buyer can decide. Check that the proposal matches the recorded requirement.

Questions

Questions owners ask.

Should an MSP publish its per-user fee?
It depends on how many variables sit behind the fee. If your scope is standard, a stated starting fee filters out buyers early. If scope varies widely, publish what the fee covers and what changes it, and quote after a short discovery call.
How do we compete with a freelancer who charges less?
Do not match the rate. Put the missing pieces next to it: who covers leave, what happens when the freelancer is unreachable, who holds the admin passwords, and how an incident is recorded. Finance heads respond to risk they can see written down.
What should be in the first meeting with a growing company?
Ask who looks after IT today, what broke last, how many users and devices there are, and what a customer or auditor has asked for. Leave the product list out. The answers decide what the proposal should say.
How do we keep a managed IT client at renewal?
By showing them what you did, in their language, before they ask. Keep a record of tickets raised and fixed, devices added and risks flagged, and review it with the founder or finance head before the renewal comes up.

Where this fits

Three pieces of sales work, in this order.

This work sits inside sales process design. One written way to sell, from first enquiry to repeat order.

  1. Step 1

    Sales audit

    Find where deals are being lost and what to fix first.

    Start here if you cannot say where orders are lost.

  2. Step 2 · you are here

    Sales process design

    One written way to sell, from first enquiry to repeat order.

    Start here if every salesperson sells differently.

  3. Step 3

    Sales management

    A target, a review routine and someone who owns the number.

    Start here if the team has targets and no routine.

Tell us what you need Your brief is read before we call. Scope, fee and term in writing.

Your next practical step

Tell us what you are trying to grow, and we will read it before we call.

Eight short steps, mostly taps. Skip anything you would rather answer on the call.