Prospects compare managed and hourly arrangements without understanding the difference, and cannot assess technical skill. Explaining the models, publishing response commitments, and writing without jargon are what convert.

What the buyer can actually judge

Not technical competence. They have no way to assess it and they know it.

What they can judge: whether you explained something clearly, how quickly you respond, whether the pricing is comprehensible, and whether other businesses like theirs use you.

Which means the site's job is not to demonstrate expertise through terminology. It is to be comprehensible, specific, and reassuring about response.

A site full of technology names and acronyms is written for peers, and the buyer reading it concludes only that they will not understand the invoices either.

Explaining the models

The most useful content, because buyers do not know the difference and it determines everything.

Hourly or as-needed. You pay when something breaks. Low commitment, unpredictable cost, and the supplier has no incentive to prevent problems.

Managed, on a monthly fee. Predictable cost, ongoing monitoring and maintenance, and the supplier's incentive is that nothing breaks.

Blended arrangements, where monitoring and maintenance are included and project work is separate.

Explaining the incentive difference plainly is genuinely persuasive and rarely done. A buyer who understands why a monthly arrangement makes prevention worthwhile can evaluate the price properly.

It also filters. A business wanting somebody to call occasionally is not a managed services client, and saying so saves both parties.

Pricing

Publishable enough to be useful.

For managed arrangements: a per-user or per-device monthly figure, or a range, with what is included and what is not.

For hourly work: the rate, minimum billing increments, and after-hours rates.

What moves it: number of users, servers, complexity, whether there are multiple sites, and compliance requirements in regulated sectors.

The inclusion boundary is where disputes originate. What counts as support against a project, whether hardware and licensing are extra, and whether onboarding is charged separately all belong on the page.

Response commitments

The thing buyers actually compare and the thing most sites state vaguely.

Response time by severity, meaning how fast somebody responds to a complete outage against a single user with an inconvenience.

Coverage hours, and what happens outside them.

Whether response means a human or an automated acknowledgement, which is a distinction buyers have learned to ask about.

And who they reach: a named person, a team, or a queue. For a small business the named person is a genuine differentiator and worth stating.

The sectors and sizes you serve

Specificity that converts, since buyers want somebody who understands their situation.

What size of business, in employees or devices, since a supplier built for five-person offices and one built for two hundred are different companies.

Which sectors, particularly where compliance requirements apply. Health, legal, financial, and public sector clients have obligations that shape everything, and a supplier who knows them has a real advantage.

Where you have a minimum, saying so prevents the enquiry from a two-person business that cannot be served profitably.

The security question

Now central to this category rather than an add-on.

What is included: backup and whether it is tested, endpoint protection, patching, multi-factor enforcement, and staff awareness training.

What happens in an incident, meaning your response process and whether you have handled one.

Where clients have their own obligations, such as privacy legislation applying to health or personal information, being clear about what you handle and what remains theirs is important and frequently muddled.

Being honest about the limits matters here. A supplier implying that a managed arrangement makes a client secure is overstating something that cannot be guaranteed, and buyers who have been through an incident recognise it.

The switching question

Since most prospects already have somebody.

What onboarding involves, how long it takes, what you need from the incumbent, and what happens if the relationship with them is poor.

That last point is common. A business unhappy with its current supplier frequently worries about access, passwords, and documentation held by somebody they are about to leave.

Explaining how you handle a difficult transition addresses the specific fear that keeps businesses with suppliers they dislike.

Also worth stating plainly: that the client owns their own systems, accounts, and data, and that you document access so they could leave you, which is an unusual thing to say and a strong signal.

The rest

Whether support is remote, on site, or both, and what triggers an on-site visit. Geographic coverage. Client references or case descriptions where permitted. And a plain statement of what you do not do, since the category spans everything from desktop support to infrastructure and no supplier covers all of it, which is the same support-quality argument set out in judging a host by its support.

Frequently asked questions

What can an IT buyer actually judge?

Not technical competence. Whether you explained something clearly, how fast you respond, whether pricing is comprehensible, and whether similar businesses use you.

Why explain the pricing models?

Because buyers do not know the difference, and the incentive distinction matters: an hourly supplier has no reason to prevent problems and a managed one does.

What pricing should be published?

A per-user or per-device monthly range for managed work, hourly rates with minimum increments for as-needed, and clearly what is included and what is not.

What do buyers compare on?

Response commitments by severity, coverage hours, whether response means a human or an acknowledgement, and whether they reach a named person or a queue.

What should be said about security?

What is included, what happens in an incident, and honestly what cannot be guaranteed. Buyers who have been through one recognise overstatement.

What addresses the switching fear?

Explaining onboarding, and how you handle a transition where the incumbent is uncooperative about access, passwords, and documentation.

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.

Prospects who cannot tell managed from hourly?

We explain the models and publish the response commitments, which is what buyers are actually comparing.

Start a Conversation