Playbook

Lead Generation Plan for IT Services Companies: Build a UK Account List

For an IT services firm that wants a repeatable way to find UK project opportunities.

You leave with an offer brief, a named account list, a buyer map and a weekly review.

By Sampath Mallidi, Founder and Chairman · Reviewed by Swetha Arun, Chief Operating Officer · Updated 16 Nov 2026 · 5 min read · Free, no sign-up

Jump to the first copy block ↓

Preview

On this page

What you'll get

  • 2 copy-ready blocks
  • Spreadsheet-ready
  • 4 tables
  • 5 min read
  • Account list (copy this block)
  • First approach (copy and adapt)

How to use it

  1. Step 1: Write the offer brief in Part 1.
  2. Step 2: Build a list of named accounts using Part 2.
  3. Step 3: Map the buying roles and evidence in Part 3.
  4. Step 4: Choose a first approach for each account in Part 4.
  5. Step 5: Review progress weekly with the simple measures in Part 5.

This plan is for an IT services company that wants to sell a defined service into UK businesses. Start with one offer, such as cloud migration, data engineering or application modernisation. Do not try to sell every capability to every company at once.

The example below is illustrative. Adapt the sector, account criteria and roles to your own offer.

Part 1: Make the offer specific

Complete this before building a list. If the answer could describe any IT supplier, narrow it.

QuestionYour answer
Service[What work do you deliver?]
Buyer problem[What is difficult or costly today?]
Evidence you can show[A permitted example, method or capability]
Best fit[Company type, situation and team]
Poor fit[A clear reason to leave an account out]
First conversation[What useful question could you discuss?]

Avoid claims about savings, delivery speed or client outcomes unless you can support them and have permission to use them.

Part 2: Choose named UK accounts

Start with companies, not contact records. Apply the same criteria to each candidate.

CriterionEvidence to record
Service fitA public sign that the company uses or needs the service
Relevant operationThe team, product or process your work would support
Reason to prioritiseA current change, stated need or known relationship
Reachable buying groupAt least one plausible role to research, with gaps marked
Exclusion checkExisting customer, open opportunity, do-not-contact request or poor fit

Account list (copy this block)

Account list (copy this block)
Company	Website	Service fit evidence	Current reason to prioritise	Likely team	Known people	Open questions	Owner	Next review
[Company]	[URL]	[Evidence]	[Reason]	[Team]	[Names or roles]	[Questions]	[Owner]	[Date]

Do not infer a buying need from a company size or job title alone. Record the source and date for each useful fact.

Part 3: Map the buying group

For each priority account, look for the person who feels the operational problem, the person who owns the budget and anyone who will assess delivery or risk. One person may hold more than one role. Mark a role as unknown when you do not have evidence.

Role to researchWhat to learnEvidence source
Problem ownerWhich workflow or service is affected?Company pages, talks, public posts
Budget ownerWho is accountable for the team or investment?Organisation pages, role history
Technical evaluatorWho checks architecture, security or integration?Technical material, team pages
Procurement or legalWhat review may apply to a new supplier?Public supplier guidance or a direct question

A role map is a research aid, not a claim that the person has agreed to buy.

Part 4: Choose a relevant first approach

Use a fact that is both public and relevant. Explain why it matters to the recipient, then ask one question. Do not pretend to know an internal problem you have not verified.

First approach (copy and adapt)

First approach (copy and adapt)
Subject: [Specific service question]

Hello [Name],

I noticed [public fact and source]. It may be relevant to [specific part of their work], though I may have the wrong read.

We help with [one defined service]. Is [question about the work or ownership] something your team is reviewing, or should I speak with someone else?

Regards,
[Name]

If there is no reliable reason to contact the account, do more research or leave it out. Do not send the same note to every person at the company.

Part 5: Review the work each week

Track activity by account and record what changed. These are process measures, not a forecast.

MeasureThis weekWhat to review
Accounts researched[ ]Are the sources current?
Accounts with a clear service fit[ ]Is the offer narrow enough?
Buying roles identified[ ]Which important role is still unknown?
Relevant approaches made[ ]Does each note use a true account fact?
Two-way conversations[ ]What did the account actually say?
Accounts on hold or removed[ ]Is the reason recorded?

Change one part of the plan at a time. If the list is wrong, fix the criteria. If the account fit is sound but the reason to talk is weak, improve the research before changing channels.

Why this works on named accounts

A broad lead list gives an IT services firm names. It does not tell the team which companies have the problem it solves, who owns that problem or why a conversation should happen now. A named account plan starts with a specific service offer and a short list of companies that could buy it. The work is then to learn each account, identify the people involved and make a relevant approach. This is a planning guide, not a promise of enquiries or projects.
How account-based selling works →

Common questions

Is this a lead generation service?

No. It is a planning worksheet for an IT services team. Intandemly is an account-based selling company, not a lead-generation company.

Should I contact every person at a target company?

No. Research the relevant buying roles and approach people with a reason that fits their work. Stop when someone asks you not to contact them.

Will this plan produce UK projects?

It organises research and outreach, but it cannot promise a result. Outcomes depend on the offer, the market and the decisions made by each account.

Read next

Related articleHow to Get Clients for an IT Staffing Company When Referrals Dry UpRead →
Explore the topic

More from the Academy

Playbook10 min read

After Referrals Dry Up: A 30-Day Client Plan

For founders and sales heads of software and IT services companies whose referrals have slowed.

You leave with a named account list, a research card per Tier 1 account, a 30-day outreach plan and a weekly tracking sheet.

Template6 min read

Target Account List Template

For founders and sales heads who have chosen their accounts and need one place to work them.

You leave with a 25-row sheet, a rule for how many accounts to keep and a weekly review in five questions.

Template8 min read

Buying Committee Map

For sellers working a large account through a single contact.

You leave with nine roles to look for, a map you can paste into a spreadsheet, a brief for each person and a coverage check that shows where the account is exposed.

ToolRuns in your browser

Target Account List Builder

Turn your criteria into a 25-row target account list framework you fill in. Uses only what you enter. Runs in your browser.

ToolRuns in your browser

Account Scoring Tool

Score target accounts on fit, timing and access, and sort them into Tier 1, 2 and 3. Runs in your browser.

Want this in your inbox?

Optional. We use your email only to send you this, nothing else.

Want this run on your key accounts?

Tell us which accounts you need to open. We will show you how we would work them.