← Back to Portfolio
LEAD GENERATION

B2B Targeted Lead List Build

Digital Agencies / SaaS

B2B Targeted Lead List Build — project image by Prosengit Kundu
CATEGORY
Lead Generation
FOCUS
B2B lead generation — ICP-filtered, verified prospect database
TIMELINE
1–2 weeks per batch
TYPE
Client Project
PROJECT GOAL

What this project set out to do

Project type: B2B lead generation. Objective: build a lead list that sales teams trust — companies filtered against a strict ideal customer profile, decision-maker contacts researched manually, and every email verified before delivery. Services involved: prospect research, contact research, email verification and data cleaning. Business purpose: fill outbound pipelines in any country with accurate, outreach-ready prospects.

MY ROLE

Responsibilities & tools

ICP definition, company sourcing, contact research, verification, organization and delivery.

Tools & technology: LinkedIn, Google Maps, industry directories, email verification workflow, spreadsheet/CRM delivery
WORK COMPLETED

Deliverables in detail

  • Ideal customer profile definition with explicit disqualifiers
  • Company research from directories, LinkedIn and Maps
  • Decision-maker identification (name, title, relevance check)
  • Contact data collection with source noted per row
  • Email verification and risk scoring before delivery
  • De-duplication and standard formatting (one row per contact)
  • Personalization notes for outreach first lines
OUTCOME

Honest status of this work

A clean, verified, organized lead database delivered to a B2B client — decision-maker titles, verified emails, source notes and personalization hooks on every row.

PROJECT REVIEW

How the work was evaluated

The research deliverable needed to be usable by the next person in the sales process. Clear inclusion rules, source traceability, normalization and verification were therefore more important than collecting the largest possible number of rows.

The project brief identifies the work as Client Project, in the Digital Agencies / SaaS context, with a stated timeline of 1–2 weeks per batch. Those labels are preserved exactly. This review expands the reasoning around the documented scope; it does not add a client name, confidential detail, ranking, revenue figure, conversion rate or other result that is absent from the source record.

From brief to an executable scope

The focus was B2B lead generation — ICP-filtered, verified prospect database. A useful scope translates that focus into assets and checks that another person can review. It also separates delivery from business outcomes. Delivery can be verified through files, settings, pages, research fields or campaign structure. Business impact requires observation after implementation and can be influenced by the offer, market, budget, competition and client follow-up.

Before execution, the practical questions are straightforward: What must be delivered? Which access or source material is required? Who approves it? What would make the item complete? What remains outside scope? Answering these questions reduces revision loops and protects both the client and freelancer from vague expectations.

Deliverable-by-deliverable quality notes

  • Ideal customer profile definition with explicit disqualifiers. This item was reviewed as part of the stated project scope. Its completion check focused on whether the deliverable supported the project goal and could be understood or used by the client after handover, rather than adding an unsupported performance claim.
  • Company research from directories, LinkedIn and Maps. This item was reviewed as part of the stated project scope. Its completion check focused on whether the deliverable supported the project goal and could be understood or used by the client after handover, rather than adding an unsupported performance claim.
  • Decision-maker identification (name, title, relevance check). This item was reviewed as part of the stated project scope. Its completion check focused on whether the deliverable supported the project goal and could be understood or used by the client after handover, rather than adding an unsupported performance claim.
  • Contact data collection with source noted per row. This item was reviewed as part of the stated project scope. Its completion check focused on whether the deliverable supported the project goal and could be understood or used by the client after handover, rather than adding an unsupported performance claim.
  • Email verification and risk scoring before delivery. This item was reviewed as part of the stated project scope. Its completion check focused on whether the deliverable supported the project goal and could be understood or used by the client after handover, rather than adding an unsupported performance claim.
  • De-duplication and standard formatting (one row per contact). This item was reviewed as part of the stated project scope. Its completion check focused on whether the deliverable supported the project goal and could be understood or used by the client after handover, rather than adding an unsupported performance claim.
  • Personalization notes for outreach first lines. This item was reviewed as part of the stated project scope. Its completion check focused on whether the deliverable supported the project goal and could be understood or used by the client after handover, rather than adding an unsupported performance claim.

Technical and practical checks

  • Check 1: Test a sample against every ICP requirement before scaling the research.
  • Check 2: Keep company facts, contact facts, source and verification date in clearly defined fields.
  • Check 3: Normalize formats and remove duplicates without hiding uncertainty or guessing missing information.
  • Check 4: Hand over suppression, privacy and responsible-use notes with the organized file.

Quality assurance should follow the real delivery environment. That may mean reviewing mobile pages, validating a spreadsheet sample, checking search terms in an account, or opening exported creative at platform size. A tool report is supporting evidence; it is not a replacement for using the deliverable as the intended person would.

Measurement without invented results

The documented outcome for this project is: A clean, verified, organized lead database delivered to a B2B client — decision-maker titles, verified emails, source notes and personalization hooks on every row. This wording describes what was delivered. Where the source does not include post-delivery numbers, this case study does not manufacture them. A responsible next phase would establish a baseline, define the relevant business action and observe a suitable period before drawing conclusions.

Useful measurement depends on the project category. Website work may track form health, speed and qualified enquiries; SEO work may review indexation, relevant query visibility and organic actions; advertising may connect platform conversions to accepted leads; research may track verification and sales acceptance; design may assess readability, consistency and response in context. These are measurement options, not claimed results for this project.

What this case study can help a prospective client decide

A prospective client can use the scope to compare needs, not to assume an identical project. The most useful information to share before requesting a quote is the business goal, audience, current assets or accounts, required deliverables, target market, deadline and known constraints. That makes it possible to recommend a focused starting point and identify dependencies before a price is confirmed.

Project questions

Can the same approach be used in another industry?

The planning principles can transfer, but the research, language, audience and acceptance criteria must be adapted. Reusing a process is sensible; copying assumptions, creative or keywords without market evidence is not.

Does this case study guarantee the same outcome?

No. It documents the existing project scope and delivered status. Search, advertising, sales and website outcomes depend on factors beyond a single deliverable. Any new project should begin with its own baseline and written scope.

What should be provided for a similar quotation?

Share the goal, relevant URL or account context, audience and location, available content or data, deadline and preferred communication route. Use the contact page to discuss the scope, or compare the documented starting points on the pricing page.

← Google Ads Search Campaign Blueprint Prospect Research & Data Cleaning →

Have a similar project in mind?

Share your goal and I will suggest a practical, focused starting point — with clear pricing before any commitment.

Discuss Your ProjectSee Pricing

Building an outbound list that a sales team can use

This assignment was not a volume exercise. The goal was to give a B2B agency or SaaS sales team a dependable starting point for outbound work: companies that fit an agreed ideal customer profile, the right decision-makers within those companies, and contact data that has been checked before it reaches a campaign. That focus matters because a large spreadsheet is not automatically a useful prospect list.

Start with fit, including who to leave out

The research began by turning the ideal customer profile into working rules. Industry, company type, geography, team size and likely need were considered alongside explicit disqualifiers. Defining exclusions up front prevents time being spent on businesses that look similar on paper but are not commercially relevant. It also gives a sales team a clear basis for reviewing why a company was included.

Company records were assembled from LinkedIn, Google Maps and relevant directories, then reviewed rather than copied blindly. For each viable company, the work moved from account-level research to the people most likely to own, influence or evaluate the service. Titles were checked for relevance, and the source of the contact information was retained so the delivered data had a traceable research trail.

Make every row usable at the point of outreach

Email addresses passed through a verification workflow before delivery, with risky records clearly separated from safer ones. De-duplication and standardized fields made the file easier to import into a spreadsheet or CRM without creating multiple versions of the same contact. The list also included short personalization hooks, giving outreach writers a practical observation to develop rather than a blank opening line.

The recorded outcome is a clean, organized database with decision-maker titles, verified email status, source notes and personalization context on each row. It is intentionally a handoff for outbound preparation, not a claim that an email sequence has already produced meetings or revenue. Campaign copy, sending reputation and follow-up still determine what happens after the list is used.

Useful reading before planning the next batch

The companion guides on building a targeted lead list, generating B2B leads and B2B lead generation for international markets explain the strategic decisions that should happen before research is scaled.

Need an outreach-ready list for a defined offer and market? Send the ICP, target geography and required contact roles through the contact page, and I will outline a practical research batch and delivery format.