Copy Examples

Elevator pitch examples for IT consultants

An elevator pitch fails when it describes the business instead of giving the listener a reason to ask a second question. These end somewhere the other person can pick up.

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.


The one-liner

We are IT consultants in [your town] — we handle network setup and support and cybersecurity for a small business whose last IT person left without notes.

Use this when you have one sentence and no idea who you are talking to.

Problem first

The thing people worry about with IT consultants is being locked into a provider who holds all the passwords and none of the documentation. That is the part we deal with. We are IT consultants, and we audit what you have before proposing anything.

Use this where the problem is instantly recognisable and the service is not.

Names who it is for

We work for a small business whose last IT person left without notes. Mostly network setup and support and cybersecurity. If that is not you, you probably know someone.

Use this at an event where most people are not your customer, to find the ones who are.

Credential first

We are certified and insured. Certified on what we support, insured, and documented so you are never hostage to one person’s memory. We mostly do network setup and support and cybersecurity.

Use this in a room where qualification is the thing that buys attention.

The contrast

Most IT consultants [what the default does]. We are the one that writes it down so you are never trapped. That is more or less the whole difference.

Use this when your market has a clear default and you are not it.

With a number in it

We are IT consultants — [number] years, [number] engagements, and you own your systems and your documentation.

Use this when you have a real number. Do not invent one.

The origin

We started because being locked into a provider who holds all the passwords and none of the documentation was normal in this trade and it did not need to be. So that is the business: IT consultants where we audit what you have before proposing anything.

Use this when the reason you started is short and true.

Ten seconds

IT consultant. Network setup and support, mostly. [your town].

Use this when someone asks what you do and is already half-turned away.

Ends with the ask

We are IT consultants doing network setup and support and cybersecurity. If you ever hear someone say [the thing your customers say], that is us.

Use this when the point of the conversation is a referral, not a sale.

The warm version

[their question] — we are IT consultants. The part people usually ask about is writing it all down so the client is never trapped.

Use this where the pitch would land badly and a conversation would not.

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.