What an IT Company Website Needs

People land on an IT company or managed service provider website for one of two reasons: they are looking for a provider, or they already have one and something is broken. A good site serves both. It shows what each plan covers, which businesses you support, what security standing you actually hold, and how to reach help fast. This guide covers the pages and details that do that work.

The rules and technical points here come from the Microsoft AI Cloud Partner Program badge usage guide and Microsoft's Solutions Partner program FAQs, the AICPA & CIMA SOC 2 page, RFC 9116 (the security.txt standard) and the FTC's Endorsement Guides: What People Are Asking. All were checked on November 15, 2026. The rest is our view from building websites for businesses. This is not legal advice.

The short answer

An IT company website needs a page for each service or plan that says what is included and what is not, the industries and company sizes you serve, security claims limited to what you hold today, partner badges used the way each vendor allows, case studies your clients approved, and two clearly separate paths: one for new business and one for existing clients who need support. Templates can get you started, but the content above is what a buyer compares.

Services and support plans

Most IT buyers are comparing you with two or three other providers. Make that easy. Give each service its own page: managed IT support, cybersecurity, cloud and Microsoft 365, backup and recovery, networking, projects such as office moves or migrations. On each page, say what the client gets in plain words, not a list of tools.

For managed plans, a short table works well: what each tier includes (help desk hours, on-site visits, monitoring, patching, backups, security tools), what is billed separately, and the pricing model (per user, per device or a flat monthly fee). If you publish response times, publish the ones your contract promises, with the hours they apply to. If you prefer to quote prices only after an assessment, say that, and say what the assessment involves. Our guide to showing prices on a service website covers the choices.

Name the limits too. "Unlimited support" means little if after-hours work, new hardware or project work costs extra; a buyer who finds that out later will not trust the rest of the page.

Industries and company size

"We support businesses of all sizes" tells a buyer nothing. If most of your clients are law firms, medical offices, manufacturers or nonprofits, say so, and add an industry page where you have real experience: the software those clients run, the compliance questions they ask you, and how you handle them. State the company size you fit best, for example by number of users or locations, and the area you cover on site. A buyer who sees their own situation on the page is much more likely to ask for a quote.

Security claims you can back up

An IT company that overstates its own security has a bigger problem than most businesses, because security is part of what it sells. Our rule: only name a certification, audit or framework your company holds today, use its exact name, and keep it current.

SOC 2 is the common example. The AICPA's guide for these engagements is titled "SOC 2® Reporting on an Examination of Controls at a Service Organization Relevant to Security, Availability, Processing Integrity, Confidentiality, or Privacy", and the AICPA says "CPAs can use the AICPA’s various SOC offerings to provide assurance reports that provide users with valuable information that is needed to assess and address the risks associated with outsourcing services." In other words, a SOC 2 is a report from a CPA's examination of your controls, not a badge you download. If you have one, say so and explain how prospects can request it, usually under an NDA. If you are working toward one, say "in progress" and nothing more. If you use a vendor that holds SOC 2, that is the vendor's report, not yours.

A small thing that shows you take security seriously: a security.txt file. RFC 9116 says organizations "MUST place the "security.txt" file under the "/.well-known/" path", that the Contact field "MUST always be present", and that the Expires field "MUST always be present and MUST NOT appear more than once". It adds: "It is RECOMMENDED that the value of this field be less than a year into the future to avoid staleness." Set a reminder to update it. For the basics of securing the site itself, see our website security basics.

Vendor partner badges

Partner badges from Microsoft, cloud providers and security vendors help, but each vendor has its own rules, and you should read them before a badge goes on the site. Microsoft's badge usage guide is a good example of how specific they get:

  • "All Solutions Partner badges must be generated in Logo Builder in the Partner Center. Modifications to badges and wording outside of Logo Builder are strictly prohibited."
  • Partners must name the solution area ("We are a Microsoft Solutions Partner for Security") and "avoid describing themselves or their organizations simply as a “Microsoft Solutions Partner.”" The guide adds: "Do not shorten to “MSP.”" That is an easy slip for a managed service provider to make.
  • Use of the badges "must cease when qualifications, including Solutions Partner status and specializations, are no longer maintained", and "Usage must cease if network membership becomes inactive or when instructed by Microsoft."

Microsoft's FAQ explains the timing: "On your anniversary date, not beforehand, we check if you still meet the requirements." Put that date in your calendar and check the website after it. For any other vendor, find its partner brand guide, follow it, and do not use a vendor's logo at all if you are only a customer or reseller without a program that allows it.

Case studies and testimonials

In our view, case studies are among the most persuasive pages on an IT site, because they show how you handle a real problem: a ransomware recovery, a migration, a messy handover from the last provider. Get the client's written approval before naming them, and leave out details that would help an attacker, such as system names, versions or the gaps you found. An anonymous case study ("a 40-person accounting firm") is fine when every detail is true.

Be careful with results. The FTC says: "Endorsements claiming specific results usually will be interpreted to mean that the endorser’s experience reflects what others can also expect. Statements like “Results not typical” or “Individual results may vary” won’t change that interpretation." So if a testimonial says downtime dropped to zero, either that is typical for your clients or the page needs to say what is. Our guides to writing a customer case study and to reviews and testimonials go deeper.

Support and contact paths

An existing client with a down server should never have to fill in a sales form. Put a clear "Get support" link in the header that leads to your support portal, support email and support phone number, with the hours each one is staffed and what counts as an emergency. Keep "Talk to us about IT support" as the separate path for new business.

For the sales path, a short form works best: name, company, number of users, what prompted the search and the best way to reach them. Say what happens next and how quickly you reply. Our guide to contact and quote forms covers the details. If you have a status page or service announcements, link them from the support page too, so clients can check before they call.

A short checklist (our view)

  • A headline that names who you support and where.
  • One page per service; plan tables with inclusions, exclusions and pricing model.
  • Response times only as your contract states them, with hours.
  • Industry pages only where you have real clients.
  • Security claims limited to what you hold today; SOC 2 only if you have a current report.
  • A /.well-known/security.txt with Contact and an Expires date under a year out.
  • Partner badges generated and worded the way each vendor's guide says; removed when status lapses.
  • Case studies with written client approval and no details useful to an attacker.
  • A "Get support" path in the header, separate from the sales form.

Frequently asked questions

Should an MSP publish its prices?

In our view it helps: a starting price per user or per device, with clear inclusions, lets buyers compare. If you price only after an assessment, say so and explain what the assessment covers, so the page still answers the question.

Can we mention SOC 2 if our cloud vendors are SOC 2 audited?

You can say which vendors you use and that they publish SOC 2 reports, but do not imply your own company holds one. A SOC 2 is a CPA's report on a specific organization's controls.

Can we say we are a Microsoft Solutions Partner?

Only if you hold the designation, and Microsoft's guide asks you to name the solution area, for example "a Microsoft Solutions Partner for Security", generate the badge in Logo Builder, and stop using it when your status lapses.

Does an IT company website need a security.txt file?

No law requires it, but it is a simple way to give security researchers a reporting contact. RFC 9116 puts it at /.well-known/security.txt and requires a Contact field and an Expires field.

Building a site for another professional firm? See our guides to a consulting firm website and B2B website lead generation. If you want help with yours, our website development team builds sites like this, and you can see everything we do on our services page.