Copy Examples

Services page examples for IT consultants

A services section has two jobs: help the right person recognise their problem, and stop the wrong enquiry before it reaches you.

Ten of them follow, written for IT consultants rather than filled in from a template. Your customer is a small business whose last IT person left without notes, and what they are weighing up before they get in touch is being locked into a provider who holds all the passwords and none of the documentation.


Straight list with a lead-in

## What we do We are IT consultants working across [your area]. **Network setup and support** — [one line on what this involves for you] **Cybersecurity** — [one line on what this involves for you] **Cloud migration** — [one line on what this involves for you] **Backup and recovery** — [one line on what this involves for you] **Helpdesk** — [one line on what this involves for you] Not sure which you need? We start with an audit of what you have before we propose anything.

Use this as the default. It is clear and it ranks.

Organised by the problem

## What we can help with **[The problem, in their words]** → Network setup and support **[The problem, in their words]** → Cybersecurity **[The problem, in their words]** → Cloud migration **[The problem, in their words]** → Backup and recovery **[The problem, in their words]** → Helpdesk If what is wrong is not on this list, call anyway. We will tell you honestly whether it is ours to fix.

Use this when people describe a symptom, not a service name.

With prices

## Services and prices **Network setup and support** — from [$X] **Cybersecurity** — from [$X] **Cloud migration** — from [$X] **Backup and recovery** — from [$X] Prices are starting points, confirmed in writing before any work begins. You own your systems and your documentation.

Use this if you will publish prices. It filters out the wrong enquiries before they reach you.

One flagship, then the rest

## Network setup and support This is most of what we do, and it is what we are best at. Writing it all down so the client is never trapped is the difference between doing it and doing it properly. **We also do:** cybersecurity, cloud migration, backup and recovery and helpdesk. We start with an audit of what you have before we propose anything.

Use this when most of your revenue comes from one service.

What is included

## What is included Every engagement includes: - You own your systems and your documentation - We state our response times in writing - We do not lock you into a long contract - [one more thing you always include] **Services:** network setup and support, cybersecurity, cloud migration, backup and recovery and helpdesk. If something is not included, we say so in the quote rather than on the invoice.

Use this where customers have been stung by things that turned out to be extra.

For each customer type

## Who we work with **[Customer type one]** — network setup and support and cybersecurity. **[Customer type two]** — cloud migration, backup and recovery and helpdesk. We are certified and insured. We start with an audit of what you have before we propose anything.

Use this if you serve two clearly different groups.

Process-led

## How it works **1. Get in touch.** We start with an audit of what you have before we propose anything. **2. We agree it in writing.** Scope and price, before anything starts. **3. We do the work.** Network setup and support, cybersecurity and cloud migration — whatever the engagement needs. **4. We finish.** We do not lock you into a long contract.

Use this when the how matters as much as the what.

Short

**Network setup and support** · **Cybersecurity** · **Cloud migration** Certified and insured. You own your systems and your documentation. Book an IT audit.

For a homepage strip — Use this where services sit as three cards on the homepage, not a page of their own.

With the limits stated

## What we do — and what we do not **We do:** network setup and support, cybersecurity, cloud migration, backup and recovery and helpdesk. **We do not:** [the things you turn down — be specific]. If that is what you need, [name someone who does it well] is who we would call. Saying so up front saves us both a phone call.

Use this to stop wasting time on enquiries you will only turn down.

Emergency and scheduled split

## Emergency [Response time], [hours]. Network setup and support and anything that cannot wait until Monday. ## Planned work cybersecurity, cloud migration, backup and recovery and helpdesk. Booked in, quoted in writing, done on the date we agreed. We are certified and insured for both.

Use this when urgent work and planned work are genuinely different offers.

Writing for IT consultants: what actually matters

What should an IT consultant’s website say that a generic one does not?

Three things, in this order. That you are certified and insured. That you understand the thing people are actually worried about, which for IT consultants is being locked into a provider who holds all the passwords and none of the documentation. And what happens next: an audit of what you have before we propose anything. Everything else on the page is decoration by comparison.

What does a small business whose last IT person left without notes check first?

The credential, then the proof. For IT consultants it sounds like this. You own your systems and your documentation. We state our response times in writing. We do not lock you into a long contract. Put at least one of those above the fold rather than on a separate page nobody opens.

What is the most common mistake on an IT consultant’s website?

Writing about the business instead of the customer. "We have been established since 1998" answers a question nobody asked. "We start with an audit of what you have before we propose anything" answers the one they are actually holding. If you only fix one thing, fix that.

How long should the copy be?

Shorter than you think, except where trust is being built. An About page of 120 well-chosen words beats 500 vague ones. The exception is anything explaining being locked into a provider who holds all the passwords and none of the documentation — there, specifics earn their length.