Lead generation for IT services companies: the market report
Most IT services firms grow on referrals until referrals stall. This report covers who buys, where to find them, and how to build an outbound program around them.
David Herendi
·
·
13
min read

Lead generation for IT services companies usually runs on referrals for years, and that works until the referrals slow down. A partner who used to send clients goes quiet. A big client takes the work in-house. The founder, who closed most deals personally, has no time left to sell. At that point the firm needs a way to open new accounts on purpose, and most IT services firms have never built one.
This report is for founders and heads of sales at IT consulting firms, managed service providers (MSPs) and software engineering services companies, and covers the buyers, the data, the channels, the messages, the DACH and CEE specifics, and a first 90 days of outbound.
The IT services market in one paragraph
Eurostat puts the value added of ICT services in the EU at over €697 billion in 2023, which is 4.47% of the EU's gross value added (Eurostat, "ICT sector: value added, employment and R&D", 2023 data, dataset isoc_bde15ag, extracted April 2025). That figure is broader than IT services alone, because Eurostat's ICT services also include telecommunications, software publishing and the wholesale of ICT equipment. The closest slice to this report is "computer programming, consultancy and related activities" (NACE 62), which made up an estimated 52% of ICT services value added and employed around 4.5 million people in 2023 (same source). The market is large and crowded, so the buyer's problem is rarely finding an IT partner. It is telling them apart.
Why referral-led growth stalls for IT firms
Referrals are the best leads an IT services firm gets. They arrive warm and often skip the formal vendor search. But you cannot control when they come or how many.
Referral growth stalls for four structural reasons:
The network is finite. Your referrers only think of you when your problem comes up in their conversations.
Referrals bring the wrong mix. A firm that wants to sell cloud migration keeps getting asked for support contracts.
The founder is the sales team. Referral deals close on the founder's credibility, which does not transfer to a hire.
There is no pipeline to read. Without a target list, you find out a quarter is weak when it is half over.
Outbound does not replace referrals. It adds a second source of pipeline that you control, aimed at the accounts and services you choose.
Who buys IT services

An IT services purchase is rarely one person's decision. The buying committee usually includes some mix of five roles, and each reads your message for a different reason.
CTO. Owns technology strategy. Wants to know you understand the stack and will not create more work.
Head of IT. Owns infrastructure, support, security and vendors, and often buys MSP contracts. Cares about uptime and not getting blamed.
Head of engineering. Owns software delivery and buys extra engineering capacity. Cares about quality and how fast your people fit in.
CFO. Signs off on larger contracts. Cares about total cost and contract terms.
Procurement. In larger companies, runs vendor onboarding and security questionnaires. Rarely starts a deal, but can stop one.
The roles matter less than the timing. IT services are bought when something changes, and five triggers start most purchases:
Hiring. A company posting several engineering or IT roles has more work than people.
Cloud migration. A move to AWS, Azure or Google Cloud creates project work and skills gaps.
Compliance deadlines. EU member states had until 17 October 2024 to transpose the NIS2 cybersecurity directive (European Commission), and the Digital Operational Resilience Act (DORA) has applied to EU financial entities since 17 January 2025 (EIOPA). Both put security and third-party risk on new agendas.
Funding. A new round brings budget, growth targets and a gap between what was promised and the team in place.
End of support for a platform. Microsoft ended Windows 10 support on October 14, 2025 (Microsoft). Organizations can buy Extended Security Updates by the year for up to three years after that, priced per device and doubling each year (Microsoft Learn, as of November 2026). Every company still running it has a deadline.
Good outbound for IT services starts from these triggers, not from a list of industries.
IT consulting vs MSP vs software engineering services: what changes
"IT services" covers three different businesses. The buyer, the timing and the message change with each one.
IT consulting | MSP | Software engineering services | |
|---|---|---|---|
What the client buys | A project with a defined outcome, such as a migration | An ongoing contract to run and support infrastructure | Engineering capacity, as a team or added developers |
Who usually starts it | CTO or head of IT | Head of IT, often with the CFO | Head of engineering or CTO |
Deal shape | Project budget, tied to a budget cycle | Recurring fee, often multi-year | Monthly fee per person or team |
What slows it | Budget approval and competing priorities | The current provider's contract, procurement and security review | Proving your engineers fit the team's stack |
What the message leads with | A point of view on the problem the trigger creates | The cost and risk of the current setup, timed to the contract cycle | Available capacity in a named stack, and start dates |
An MSP's outreach window is set by the prospect's current contract, so keep accounts warm and come back at the right moment. Software engineering services are the easiest to sell on a hiring trigger, because the job post names the missing skills.
Where to find them
Each common data tool covers a different part of the problem, and none covers all of it.
LinkedIn Sales Navigator
LinkedIn calls Sales Navigator a sales tool "built on LinkedIn's B2B network", with search across 1+ billion members using 50+ filters, lead and account alerts for job changes and, on the Advanced plans, a buyer intent view (LinkedIn Sales Navigator, as of November 2026). It is built for finding and messaging people on LinkedIn, so plan on a separate source if you need email addresses.
Apollo and Clay
Apollo is a contact database with search and outreach built in. It advertises 240M+ contacts and 30M+ accounts, buying signals such as intent, job changes and website visits, and waterfall enrichment (Apollo, as of November 2026), and says its 65+ search filters combine technology, firmographic and intent criteria in one search (Apollo, as of November 2026).
Clay is an enrichment and workflow tool rather than a database. Its site says one contract buys data from 200+ data and AI vendors in Clay's marketplace, and it offers waterfall enrichment, which searches one tool after another until it finds a valid match (Clay, waterfall enrichment, as of November 2026). It helps when the signal you need is unusual.
Technographic data
Technographic data shows which technologies a company uses. BuiltWith scans public websites and says it tracks more than 128,231 internet technologies (BuiltWith, as of November 2026). That covers what runs on the website. TheirStack detects technologies from job postings instead, rating confidence by how often a technology is mentioned (TheirStack, as of November 2026). For IT services, job-post data is often more useful, because the databases, cloud platforms and internal tools you would migrate or run show up in job ads far more often than on a homepage.
Job-post signals
Job posts show the stack and the gap at once. A company advertising for a senior Azure engineer for months has a migration that is short of people. Read the post itself, not just the title, and the opening line of your message is often written for you.
Data gaps in mid-market Europe
Coverage of European mid-market companies is uneven across contact databases. Before you buy, run a sample of your real target accounts through the tool and count how many decision makers come back with a verified email. That tells you more than any headline database size.
German commercial websites must publish an Impressum naming the company's authorized representatives (§ 5 Digitale-Dienste-Gesetz, gesetze-im-internet.de), which gives you the managing directors of most GmbHs. Titles differ too. In a German mid-market company, the person who signs an IT contract may be the Geschäftsführer or the IT-Leiter, not someone with "CTO" on their profile.
Channels that work
No single channel carries an IT services program. Each one has a job.
Email carries the argument: a trigger, a point of view and a specific offer the buyer can forward to a colleague. It is also the channel with the most legal variation across Europe (see the DACH section).
A connection request and a profile visit make your name familiar before the email or call. Where cold email is restricted, LinkedIn messages become a primary channel. Sales Navigator includes 50 monthly InMail credits for people outside your network (LinkedIn Sales Navigator, as of November 2026).
Phone
Phone is the fastest way to find out whether a trigger is real. A short call after an email either opens a conversation or tells you the timing is wrong. Some markets restrict advertising calls (see the DACH section).
Partner and marketplace motions
For many IT services firms, the cloud vendors are a bigger source of deals than outbound. AWS Marketplace lets software vendors and consulting partners list professional services in five categories (assessments, implementation, premium support, managed services and training), with charges on the buyer's AWS bill (AWS Marketplace, as of November 2026). Other cloud vendors run partner programs too, such as the Google Cloud Partner Network. Partner status also gives your outreach proof.
Message patterns that get replies
Building a full sequence is covered in our outbound sales playbook. We do not quote reply rates, because published benchmarks vary too much between lists, markets and senders.
Lead with a point of view, not a capability list
Every IT services firm can list cloud, security, data and development. A point of view is a short, specific claim about their situation. If a company's job posts show a long search for platform engineers, its migration is probably running on a team already at capacity. The message names that situation, says what usually goes wrong there, and ends with a question the buyer can answer in one line.
Use case-shaped proof
Proof works best in the shape of a case: a similar company, the same starting point, what was done and what changed. Keep it anonymous if you need to, but keep it concrete. A line in the shape of "we moved a mid-sized logistics company's ERP to Azure" says more than "we have deep cloud expertise", because the buyer can picture it.
Make capacity offers specific
For software engineering services, the most direct message is availability. Name the skills, how many people, and when they can start, tied to the hiring trigger.
Write to the role, not the company
A compliance deadline is a risk for the head of IT, a scope question for the CTO and a budget line for the CFO. When you reach several roles at one account, write each message about that person's part of the problem.
Selling into DACH and CEE
Two directions matter here. CEE firms sell west into Germany, Austria and Switzerland, and firms from everywhere sell into CEE itself. Both need some adjustments.
Language and formality
For German and Austrian mid-market companies, write in German, and write formally, with "Sie" and the surname. English suits international companies and engineering teams, but reads as a mass campaign to a traditional Mittelstand owner. In CEE, local language is the safer default for domestic companies, and English works for regional offices of international groups.
For CEE firms selling into DACH, proximity is a real argument. Budapest, Prague and Warsaw share a time zone with Munich and Vienna. Say so plainly rather than leading with price.
A GDPR and national law note
This is general information, not legal advice, and it covers Germany and Austria only. Switzerland and each CEE country have their own rules to check. Review your program with counsel in every country you target.
Under the GDPR, processing personal data for direct marketing "may be regarded as carried out for a legitimate interest" (Recital 47, GDPR), and recipients can object to direct marketing at any time, after which their data can no longer be used for it (Article 21(2) and (3), GDPR). In practice that means a documented legitimate-interest assessment, a clear opt-out and a suppression list you respect.
German and Austrian rules on electronic marketing are stricter. In Germany, § 7(2) no. 2 of the Act against Unfair Competition (UWG) treats advertising by email without the recipient's prior express consent as an unreasonable nuisance, and the text does not limit that to consumers. § 7(3) allows email to existing customers about similar products under strict conditions, which does not cover cold prospects. Advertising calls to business recipients need at least presumed consent under § 7(2) no. 1 (§ 7 UWG). In Austria, § 174(3) of the Telecommunications Act 2021 prohibits electronic mail for direct marketing without prior consent, without excluding business recipients, and § 174(4) has a similar narrow existing-customer exception. § 174(1) also requires prior consent for advertising calls, with no separate rule for businesses (§ 174 TKG 2021). That is why LinkedIn carries more of the work in these two markets, with calls in Germany limited to cases where presumed consent can be shown and no cold advertising calls in Austria. Ask counsel whether LinkedIn messages fall under the same rules in your case.
A 90-day outbound program for an IT services firm
A first program should answer one question. Which account type, trigger and message produce real conversations? Here is a sensible default.
Days 1 to 30: build the foundation
Pick one segment. One service line, one company size band, one or two countries.
Write the buyer map. The two or three roles you will reach per account, and the triggers you will watch for.
Build the first list. Start with accounts showing a trigger now, and verify contacts on a sample before buying data at scale.
Set up sending infrastructure. Separate sending domains, authentication and warm-up, so outreach does not risk your main domain.
Draft two angles. Two points of view on the same trigger, checked by someone who has sold the service.
Days 31 to 60: launch and listen
Send in small batches, so you can read the replies, not just count them.
Run the channels together. Email for the argument, LinkedIn for familiarity, phone for key accounts where the law allows.
Log every objection. "We have a provider" and "not this year" tell you whether the trigger or the timing is wrong.
Decide at the midpoint. Move the volume to the angle that produces conversations, and write a new challenger.
Days 61 to 90: tighten and extend
Add the second role at engaged accounts, usually the CFO or head of engineering.
Build the follow-up list. "Not now" accounts go on a timed follow-up, which matters most for MSP contracts tied to renewal dates.
Connect the partner motion. If you hold a cloud partner status, bring active opportunities to the vendor's account team.
Write down what worked. Which trigger, role and angle. That is the brief for the next 90 days.
If you would rather not build this in-house, our guide to outsourced SDR teams explains how that model works.
Illustrative example: a first program for an IT consulting firm selling into DACH
This is a hypothetical walkthrough, not a client story. It shows decisions, not results.
Picture a CEE IT consulting firm with a strong Azure practice that wants German mid-market clients. Its first decision is the segment. "German companies moving to the cloud" is too wide for a sharp message. Manufacturers in southern Germany hiring Azure or infrastructure roles is narrower, and the hiring trigger shows both the stack and the gap.
The second decision is the buyer. In a family-owned manufacturer, the Geschäftsführer may sign while the IT-Leiter feels the problem, so the firm maps both.
The third decision is the channel mix. German law restricts advertising email without prior consent, and advertising calls to businesses need at least presumed consent. So the firm builds around LinkedIn, adds calls only where presumed consent can be shown, writes in formal German, and takes legal advice before any email or call.
The fourth decision is the message. A team that has searched for Azure engineers for a long time is probably carrying a migration without enough people, so the firm offers a short assessment of where that migration stands, instead of a capability list.
At the midpoint, if conversations show prospects are blocked by an existing contract rather than by staffing, the firm shifts its angle to the contract cycle and puts those accounts on a timed follow-up.
Conclusion
Referrals will stay the best leads an IT services firm gets, but they cannot be the only source. Pick a segment, map the buying committee, watch for triggers, and reach the right people with a specific point of view through the channels each market allows. For a done-for-you version, see our outbound sales service.
Run an IT services firm and want a pipeline that does not depend on referrals? Book a call and we will map your buyer committee and first 90 days.
faq
frequently asked questions
How do IT services companies generate leads?
Most start with referrals, partner introductions and repeat work from existing clients. To grow past that, they add outbound: a defined list of target accounts, a buyer map per account, and a mix of email, LinkedIn and phone timed around buying triggers such as cloud migrations, compliance deadlines, new funding or a platform reaching end of support.
Does cold email work for IT services and MSPs?
It can, when the list is narrow and the message is tied to a real trigger. Check the law in each target country first. Germany and Austria require prior consent for advertising email, including to businesses, with only a narrow exception for existing customers. Austria also requires prior consent for advertising calls, so programs there lean on LinkedIn, and German programs add calls only where presumed consent can be shown.
Who should an IT services firm target in outbound?
Start with the person who owns the problem you solve: the CTO, head of IT or head of engineering. Then map who else signs off. The CFO cares about cost and contract terms, and procurement runs vendor onboarding and security review in larger companies. Reach two or three of these roles per account rather than relying on one contact.
How long is the sales cycle for IT services deals?
It depends on what you sell. Extra engineering capacity for a team that is already hiring can move quickly. A new managed services contract usually waits for the current contract to end and passes through procurement and security review. Consulting projects sit between the two and often depend on budget cycles. Plan outreach around those timelines, not around your own quarter.
David Herendi
Founder
Ready to scale your growth?
Book a 30-minute call. We'll map your funnel, your ICP, and where outbound and marketing could move the number fastest.
Or email david@scalee.digital
The customer-acquisition engine for B2B growth.
contact
david@scalee.digital
Gorkého 10, 81101 Staré Mesto, Slovakia
© 2026 Scalee. all rights reserved.
Privacy · Terms
scalee.digital