How to Write an IT Support Brief (And Get Better Quotes)

Most business owners who shop around for IT support get back a set of quotes they can’t properly compare. One provider charges per user, another per device. One bundles cybersecurity in, another lists it as an add-on. The difference is usually the brief — or the lack of one. If every provider is quoting against a different set of assumptions, the numbers will never line up.

Writing a clear IT support brief doesn’t take long, but it changes the quality of what you get back. Here’s what to include.

What is an IT support brief?

An IT support brief is a short document that describes your business, your current IT setup, and what you need from a support provider. It’s the starting point for any serious quote — and the only way to ensure different providers are pricing against the same scope.

You don’t need a formal document or a template. A page of clear information, shared consistently with every provider you approach, is enough. The goal is to make it easy for them to quote accurately and for you to compare what comes back.

What to include in your IT support brief

Cover these seven areas and you’ll have everything a good provider needs to quote accurately.

1. Business basics
Your sector, number of employees, and office locations. Providers need to understand what kind of business they’re supporting — a 10-person law firm has different IT needs to a 10-person e-commerce business, even if the headcount is the same.

2. Current IT setup
What devices your team uses (Windows, Mac, or mixed), whether you have any on-premise servers or run entirely in the cloud, and which software your business depends on day to day. If you’re on Microsoft 365 or Google Workspace, say so. If you run specialist line-of-business software — accountancy packages, practice management systems, ERP tools — list them. Providers need to know what they’re inheriting.

3. Number of users and devices
How many people need IT support, and roughly how many devices. This is usually the main pricing variable. If you have remote or hybrid workers, say how many — remote support requirements affect pricing and tooling.

4. Current support arrangement
Whether you’re currently with a provider and looking to switch, coming off an expired contract, or building IT support from scratch. If switching, include your current contract end date and notice period. Providers appreciate the context, and it affects their onboarding timelines.

5. What you need covered
At a minimum: helpdesk support, security, and backup. If you want the provider to handle Microsoft 365 licensing and management, say so. If you need on-site visits as well as remote support, be clear. If there are out-of-hours requirements — shift workers, weekend trading — include that too.

6. Response time expectations
How quickly you expect a response for critical issues, and what a critical issue looks like for your business. A server outage affecting your whole team is a different level of urgency to a single user who can’t print. Giving providers this context helps them match you with the right tier of SLA.

7. Budget range (optional but helpful)
You don’t have to name a number, but a rough range — even “up to £X per month” — helps providers tailor their proposals. If you have no idea what to expect, say that too. A good provider will explain the options rather than simply quote at the top of the range.

How long should your brief be?

One page is ideal. Two pages is fine. Anything longer risks important detail getting buried. If a provider needs more information, they’ll ask — what matters is giving them enough to make a serious start.

Plain English throughout. You don’t need to use technical language or describe your setup in detail beyond what’s above. Providers are used to translating a business description into a technical scope — that’s part of what you’re paying for.

Common mistakes to avoid

Being vague about headcount or devices is the most common problem. Providers can’t price accurately without knowing the scale of what they’re taking on.

Listing requirements without any sense of priority is the second. If 24/7 monitoring is essential, say so. If it would be nice but isn’t a deal-breaker, say that instead. Providers need to know what’s non-negotiable so they don’t waste your time with proposals that miss it.

Omitting specialist software is also common and causes problems later. If you run bespoke or industry-specific applications, mention them upfront. Some providers will flag immediately that they have experience with your software; others will be honest that they don’t. Either answer is useful before you commit to a contract.

What to do with your brief

Share it with every provider you approach. Use the same document, unchanged, for each one — that’s how you ensure the quotes you receive are genuinely comparable. Ask each provider to confirm in writing what their quote includes and excludes, so you’re not comparing two different scopes dressed up as equivalent prices.

If you’d rather not manage this process yourself, we can do it for you. Fill in our short form with your requirements and we’ll match you with providers who fit your sector, size, and budget — and send you comparable, no-obligation quotes.

Compare IT support providers and get free, no-obligation quotes.