Copy Examples

FAQ page examples for IT consultants

An FAQ page is where the objections go that the rest of the site is too polished to name. Answer the money question first or the visitor leaves to find it.

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.


What does it cost?

**What does it cost?** [your honest starting figure], and we audit what you have before proposing anything. What moves the number is [the two or three things that actually change the price] — so the quote comes after we have seen the engagement, not before.

Always answer this. The visitor who leaves to find it does not come back.

How soon can you come?

**How soon can you start?** Usually within [timeframe]. If we are booked further out than that, we say so rather than holding your date loosely.

Use this where availability is the deciding factor.

The objection, named

**[the question they are too polite to ask]** The honest answer is that being locked into a provider who holds all the passwords and none of the documentation is a real risk in this trade. What we do about it: you own your systems and your documentation, and state our response times in writing.

Use this for the worry people have but do not ask about.

Are you licensed and insured?

**Are you certified and insured?** Yes. Certified on what we support, insured, and documented so you are never hostage to one person’s memory. Ask and we will send the documents before we start.

Use this wherever a credential is checked before anything else.

What happens when I get in touch?

**What happens after I contact you?** We start with an audit of what you have before we propose anything. We agree the scope and the price in writing before anything begins, and nothing starts until you say so.

Use this to take the friction out of the first contact.

What if something goes wrong?

**What if something goes wrong?** We put it right at our cost. [your guarantee, in one sentence]. We would rather fix it than argue about it, and that is easier to promise on a page than to do — so ask us for a reference from someone it happened to.

Use this where the risk is what stops people booking.

Do you do [adjacent thing]?

**Do you also do [the adjacent service people ask about]?** [Yes, and here is how] — or: no, we do not, and [who you would call instead] is who we would ring. Saying so up front saves us both a phone call.

Use this to catch the enquiries you want and deflect the ones you do not.

How do I prepare?

**Is there anything I should do beforehand?** [the one or two things that genuinely help]. Beyond that, nothing — we bring what we need.

Use this where a little preparation makes the job cheaper or faster.

How do I pay?

**How and when do I pay?** [your terms: deposit, on completion, invoice]. We do not ask for payment for work we have not done.

Use this where payment terms are a real question and silence reads badly.

Why are you more expensive?

**Why are you more expensive than the cheapest quote?** Usually because the cheap quote leaves something out. You own your systems and your documentation — that is in our price. Writing it all down so the client is never trapped is the part you cannot see on a quote sheet and the part you notice a year later.

Use this only if you are, and only if you can answer it well.

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.