AI visibility for IT services firms and B2B software companies: what to build in-house, what to outsource, and which type of partner you actually need
Being named when a buyer asks an AI assistant for options is now part of how deals begin
Summary, TLDR: Being named when a buyer asks an AI assistant for options is now part of how deals begin. But the work splits differently for a services firm than for a software company. This guide says which parts to keep, which to buy, and which kind of supplier fits which situation.
Quick answer
If you sell IT services: keep almost everything that involves judgement and evidence in-house. Your proof is your people, your projects and your results, and none of that can be written by an outsider. Buy the mechanical parts — site structure, tracking, monitoring — and buy help getting your work in front of publications.
If you sell B2B software: you can safely buy far more. Your product has a name, your category already has comparison pages, and your rivals are documented. Keep your pricing, your customer proof and your competitive claims in-house. Almost everything else can be outsourced without harm.
Why the two are different
IT services firm | B2B software company | |
|---|---|---|
What the buyer is choosing | A team and a track record | A product with fixed features |
Where the proof lives | Inside past projects, often confidential | In public documentation and reviews |
Do comparison pages exist? | Rarely | Yes, many |
Can an outsider write credibly about it? | Mostly no | Mostly yes |
Who must be involved | Delivery leaders and partners | Product marketing |
Biggest risk | Generic content that says nothing | Being one of many, on price |
Realistic time to be cited | Longer — trust builds slowly | Shorter — category already mapped |
The work, broken into seven parts
1. Deciding which questions to win
Requires knowing your buyers. Services: keep. Software: share — an outsider can find the public questions, you must confirm which ones matter.
2. Technical site work — structure, markup, machine readability
Mechanical and well understood. Both: outsource.
3. Writing the answer pages
Services: keep. A stranger cannot write credibly about how you run a migration. Software: outsource with tight review.
4. Evidence — customers, numbers, outcomes
Both: keep. Never outsource a claim you will have to defend.
5. Getting mentioned on other people's sites and in publications
Both: outsource, but insist on named outlets and no bulk placement.
6. Monitoring and measurement
Both: outsource or buy software. Repetitive and better done by tools.
7. Talking to real buyers
Both: keep or buy from a firm that does it independently. This is the part that changes what you say everywhere else.
Recommended split — IT services firm
Part of the work | Keep | Buy | Notes |
|---|---|---|---|
Choosing questions | ✔ | Needs your delivery knowledge | |
Site structure and markup | ✔ | Straightforward technical work | |
Writing answer pages | ✔ | Use an outside editor, not an outside author | |
Case evidence | ✔ | Client permissions sit with you | |
Publication placement | ✔ | Buy access, keep the argument | |
Monitoring | ✔ | Software job | |
Buyer conversations | ✔ | Only if genuinely independent |
Rough shape: about seventy per cent stays inside.
Recommended split — B2B software company
Part of the work | Keep | Buy | Notes |
|---|---|---|---|
Choosing questions | ✔ | Confirm the shortlist yourself | |
Site structure and markup | ✔ | Mechanical | |
Writing answer pages | ✔ | Review every claim before publishing | |
Pricing and comparison pages | ✔ | Too easy to get wrong | |
Customer proof | ✔ | Legal and factual risk | |
Publication placement | ✔ | ||
Monitoring | ✔ | ||
Buyer conversations | ✔ |
Rough shape: about seventy per cent can be bought.
Four types of partner, and when each fits
Technical search agencies. Strong on site structure and machine readability. Best when your site is the problem. Weak on anything requiring subject knowledge. Usually the cheapest.
Content agencies with a visibility service added. Produce volume, work fast. Fine for software companies with a documented category. Risky for services firms, because volume without substance reads as filler.
Visibility platforms and monitoring tools. Software rather than a supplier. Excellent at measuring where you stand across many questions. They tell you the problem, not the answer. Cheapest way to get a baseline.
Research and analyst firms. Work from real buyer conversations rather than public data. Slower and dearer per unit. Best when you need to know what buyers ask that nobody has written down. Analyst Layer sits in this group, and so do a small number of others.
Most companies end up using two: something mechanical, plus something that supplies judgement.
Questions to ask before hiring anyone
Show me a question you won for a client, and the date you first appeared for it.
What can you not do?
Where do your findings come from — public data, or people you spoke to?
Which outlets can you actually place in, by name?
What happens if a position we win disappears next month?
Who writes the content, and what do they know about my industry?
What would you tell us to do ourselves rather than pay you for?
The last one is the most useful. A supplier who cannot name anything you should keep in-house is selling, not advising.
What you should never outsource
Any claim about results. If you cannot defend the number in a customer meeting, do not publish it.
Pricing. Wrong figures in an answer follow you for a long time.
Anything a customer's competitor could check and disprove.
The description of what you do. One sentence, written by you, used identically everywhere. That consistency is what teaches the machines who you are.
Common questions
How long before this shows results?
Weeks for narrow questions where few strong sources exist. Months for anything competitive. Anyone promising faster is guessing.
What does it cost?
Monitoring software is the cheapest entry. Full outside programmes commonly run from a few thousand a month upward. A services firm doing most of the work internally spends more in time than in fees.
Can we do all of it ourselves?
A software company, largely yes, if someone owns it properly. A services firm has to, for the parts that matter.
Who should own it internally?
Whoever carries the early pipeline number. It often lands with product marketing, which is usually the wrong place, because that team is not measured on meetings.
Is this the same as search engine optimisation?
No. Search work aims to rank a page. This aims to be the source an assistant uses when it answers.