TL;DR: ICP job title validation rules replace keyword matching with a scoring system across four dimensions: primary role keywords, seniority signals adjusted for company size, department alignment, and negative filters that veto false positives. Test the rules against closed-won and closed-lost data before running them on live lead lists.

ICP Job Title Validation Rules: How to Build a Scoring System That Qualifies Leads

Last updated: May 2026

Most outbound teams build their ICP job title list the same way: copy a few titles from a sales deck, paste them into Apollo or LinkedIn Sales Navigator, and start prospecting. The problem is that two contacts with the same title at similar companies can have completely different buying probability. One just renewed a two-year contract with your competitor. The other is rebuilding their stack after a failed hire. Simple keyword matching treats them identically. Job title validation rules don't.

Why Job Title Matching Alone Fails Your ICP

The default ICP job title approach is demographic: pick titles that sound right, run them as keyword filters, get a list. The list looks right. The outreach doesn't convert.

Here is why. Job titles are inconsistent across companies. "Head of Growth" at a 15-person startup means something different than "Head of Growth" at a 300-person company. "Revenue Operations Manager" is sometimes a strategic role, sometimes a CRM admin. "VP of Sales" at a PE-backed company may manage a 20-person org. At a bootstrapped SaaS company it might be the third hire.

Title matching catches everyone with those words in their title. Validation rules score them. That shift from filter to scoring function is what separates teams generating 3% reply rates from the ones producing meaningful pipeline from the same tools. As one practitioner documented publicly on LinkedIn: same copy, same tools, reply rates tripled after switching from demographics-first targeting to signal-and-rules-based scoring.

The Four Dimensions of a Job Title Validation Rule

Most ICP frameworks describe job titles as a list of strings. Your system checks whether a prospect's title contains those strings. That is keyword matching with a different name.

A job title validation rule is a scoring function with four independent dimensions. Each dimension answers a different question about the title. Together they produce a composite assessment that predicts ICP fit rather than demographic similarity.

The four dimensions are:

Role fit (highest weight): Does this title indicate the person does the job function you sell to? A "VP of Sales" at a company you sell sales tools to is a role fit. A "VP of Sales" at a company you sell HR software to may not be your buyer at all.

Seniority signals: Does this person have the authority to buy? Seniority is not just about title prefix. It is about organizational context. A Manager at a 20-person company often has more buying authority than a Director at a 3,000-person company.

Department alignment: Does this person sit in the function you sell to? "Revenue Operations" is sometimes in sales, sometimes in marketing, sometimes floating independently. Mapping the title to a department tells you whether the person's day-to-day work actually aligns with your product.

Negative filters (veto power): Does the title contain signals that disqualify regardless of other dimensions? A title that passes role fit, seniority, and department may still be a false positive if it contains words like "coordinator," "intern," or "analyst" that signal low buying authority.

Negative filters don't subtract from a score. They veto. A title that triggers a negative filter fails validation regardless of how it performs on the other three dimensions. This is the key structural difference between a scoring system and a simple keyword filter.

Practitioners building lead scoring systems for high-volume outbound consistently report the same insight: ICP is not a description of who looks right. It is a scoring function that predicts who will buy. The four-dimension framework operationalizes that insight into rules you can test and refine against real data.

How to Write Primary Role Keywords That Work

Primary role keywords are the terms that indicate your buyer's function. They are the foundation of the validation system and the place most teams get wrong.

Most teams build this list from the top of their head or from a product marketing slide. A better approach: pull the LinkedIn titles of decision-makers from your last 20 to 30 closed-won deals. List every word that appears more than twice. Those are your primary role keywords.

For a tool targeting growth and marketing leaders at B2B startups, that keyword list might include: growth, marketing, demand, acquisition, GTM, content, revenue, brand, digital.

A few rules for writing primary role keywords:

Use stems, not exact titles. "Growth" as a keyword catches "Head of Growth," "VP of Growth," "Growth Lead," and "Growth Marketing Manager." An exact title match for "VP of Growth" misses every company that uses different title conventions.

Separate primary from secondary signals. "Growth" is a primary signal indicating function. "Head" is a secondary signal indicating seniority. Running them as separate dimensions lets you weight them independently, which is especially important when company size affects what seniority words mean.

Test against a hold-out set. After writing your keyword list, run it against 30 contacts you know well. How many of your best customers pass? How many known non-buyers pass? The ratio tells you whether your keywords are too broad or too narrow before you waste a campaign.

Avoid generic keywords that attract noise. "Business," "enterprise," and "operations" sound relevant but match enormous false positive populations. Keep primary keywords tied to the specific function you sell to, not to business activity in general.

You can refine this list further by checking it against the ICP scoring system you use to weight candidates in your pipeline. The same keywords that drive your scoring rules should anchor your title validation logic.

Seniority Validation: Beyond Director and Above

The most common seniority filter in outreach tools is a simple title prefix check. Director, VP, C-suite: in. Manager, Coordinator, Analyst: out.

That blunt filter works at companies with 500 or more employees and clearly defined title hierarchies. It fails most of the addressable market for B2B startups, which skews toward smaller organizations.

At a 30-person company, the "Head of Marketing" is typically the sole marketer making every purchase decision. At a 1,000-person company, a Director of Marketing may have a $500 discretionary budget and routes every purchase through a procurement process. The titles look similar. The buying authority is completely different.

Better seniority validation accounts for company size:

Under 100 employees: include Manager-level titles for your target function. Someone with "Marketing Manager" at a 40-person startup is almost certainly the economic buyer or the person who drives the decision.

100 to 500 employees: raise the floor to Director or above for most product categories. The organization has enough structure that Manager-level is not typically the budget owner.

Over 500 employees: require VP and above for non-founding roles in most B2B outbound contexts. At this size, Director-level approval processes make them slower to close and harder to reach.

For Founders, Owners, and Co-founders: seniority passes at any company size regardless of whether a function keyword appears in the title. These roles have buying authority by definition.

The practical implementation: pair your job title rules with company employee count data. Build a lookup table that maps company size ranges to seniority floors, then apply both checks before a contact qualifies. Most contact databases include headcount ranges, so this is a straightforward enrichment step when building your prospecting list.

Department Mapping and Cross-Functional Titles

Job titles are not standardized. "Revenue Operations" means different things at different companies. "GTM Lead" at one company is the strategic equivalent of a VP of Sales. At another it is a sales ops analyst. Validation rules that rely on raw title text will misclassify these consistently.

Department mapping solves this by assigning ambiguous titles to a canonical function before scoring.

A department mapping table for outbound ICP might look like:

• Sales: account executive, sales development, business development, revenue (as a primary function)
• Marketing: marketing, demand gen, growth, content, brand, digital, acquisition
• Operations: RevOps, revenue operations, sales ops, GTM ops, marketing ops
• Leadership: founder, CEO, president, owner, co-founder, general manager

Cross-functional titles like "Head of Sales and Marketing" or "VP of Growth and Demand Gen" score on multiple departments. A validation rule handles these by checking whether the title maps to any qualifying department, rather than requiring a single exact department match.

The core benefit of department mapping over raw keyword matching: it handles variation. "Demand Gen Manager" and "Head of Demand" and "Demand Generation Director" all map to the marketing department even though they share no common keywords. Without a mapping step, you need to enumerate every variant, which is maintenance-heavy and incomplete.

Build your mapping table from real data. Pull 100 titles from your existing customer base. Manually assign each to a department. Look for the words that cluster reliably within each department group. Those clusters are your mapping rules.

This same department structure feeds directly into the B2B lead qualification framework for your broader ICP, connecting title validation to the full criteria set your team uses to score incoming leads.

Negative Filters: The Rules Teams Skip

Most teams spend all their time on positive criteria: who qualifies. They skip the equally important question: who definitely does not qualify, even if they look like they do.

Negative filters are the rules that eliminate a contact from your qualifying list regardless of how it performs on positive dimensions. They do not penalize. They veto.

Common negative patterns for B2B outbound:

Function-level false positives. "Sales Development Representative" contains "sales" and "development" but is not a buyer. It is a top-of-funnel role that contacts buyers on behalf of other companies. Without a negative filter, SDRs flood your list when you target sales leaders. Similarly, "Marketing Coordinator" matches "marketing" but lacks buying authority at any company size.

Seniority suffixes that signal individual contributors. "Coordinator," "analyst," "associate," "specialist," and "assistant" as title components indicate low buying authority at most company sizes. These words appearing anywhere in the title, not just as a final suffix, should trigger a veto.

Consulting and freelance signals. "Consultant," "freelance," "contractor," and "advisor" in a title indicate the person does not control a company budget. They may influence decisions but rarely sign contracts or approve spend.

Student and intern markers. "Intern," "student," "trainee," and "graduate" indicate non-buyers categorically.

Technical contributor roles (function-specific). For non-technical products, "engineer," "developer," and "architect" often indicate evaluators who influence but don't sign. This is function-specific: some ICPs sell directly to technical buyers, so apply this negative only if technical roles genuinely don't close for you.

The structural rule: negative filters veto. A VP-level title that contains "intern" anywhere in it fails validation. A contact with strong role fit, correct seniority, and right department still gets eliminated if any negative filter triggers. That is intentional. False positive elimination is the whole point.

Review your last 20 closed-lost deals and pull the contact titles. Any patterns that appear frequently in lost deals but not in won deals are candidates for negative filters.

Testing and Refining Your Job Title Rules

Writing validation rules without testing them is guesswork. The rules should be treated as hypotheses and validated against real data before they run against live lead lists.

Here is a straightforward testing loop:

Step 1: Gather labeled data. Pull your last 40 to 50 closed-won deals. Pull 40 to 50 closed-lost deals where the objection was price, fit, or disinterest (not budget freeze or timing constraints). These are your positive and negative examples.

Step 2: Run your rules against both sets. Count how many closed-won contacts pass your rules (this is your recall rate). Count how many closed-lost contacts pass your rules (this is your false positive rate).

Step 3: Set targets. For most outbound use cases, aim for recall above 80% on closed-won contacts (your rules should catch the types of buyers you already have) and a false positive rate below 30% on known non-buyers. If your rules are catching fewer than half your closed-won contacts, the positive criteria are too narrow. If more than half your closed-lost contacts are passing, the negative filters are incomplete.

Step 4: Iterate. Titles that failed recall from your closed-won set indicate gaps in your positive keyword list or seniority thresholds. Add them. Titles that appeared in the false positive bucket from your closed-lost set identify missing negative filter patterns. Add those to the veto list.

Step 5: Re-test after each change. A single keyword addition can shift recall significantly in either direction. Treat each iteration as a separate test run.

The goal is not perfection. A validated ruleset that removes 40% of false positives before your team starts outreach saves hours of wasted sequencing work. The testing investment pays back quickly.

This same validation methodology applies to the broader signal-based outreach approach: combine title validation rules with behavioral signals to identify which ICP contacts are actually in-market right now, not just who looks right on paper.

Automate ICP Job Title Validation Workflows

The validation rules and scoring frameworks above handle classification. But running outbound involves more work than just defining the rules. The busywork: scraping lead lists from Apollo or LinkedIn at scale, applying your validation ruleset to hundreds or thousands of contacts, enriching titles that are missing or out of date, flagging job changes when contacts move into or out of your ICP, and building personalized sequences by title tier so your "VP of Marketing" track gets different messaging than your "Founder" track.

This is the execution layer that most teams handle manually, one spreadsheet at a time.

Miniloop handles that busywork. We build and run outbound workflows for your team:

• ICP-scored lead lists pulled from Apollo and LinkedIn, filtered against your job title validation rules before your team ever sees them
• Title enrichment for contacts with missing or generic titles ("Founder" without a department context, "Consultant" without a function)
• Job change monitoring so your list stays current when contacts move into qualifying roles or out of them
• Sequence logic by seniority tier, so your outreach to "Manager at seed-stage" companies differs from your outreach to VP-level buyers at Series B companies
• CRM sync for every contact that passes validation, so your sales team starts from a clean, scored list

Whether you are running outbound yourself, building the system before your first sales hire, or supporting a small SDR team that needs cleaner data, Miniloop handles the execution work behind your ICP targeting.

Try Miniloop or browse templates.

Putting It Together: A Sample Job Title Ruleset

Abstract frameworks only go so far. Here is a complete example ruleset for a specific use case you can adapt.

Use case: B2B SaaS tool selling to growth and marketing leaders at seed-to-Series-B startups (10 to 200 employees).

Primary role keywords (any match contributes positively): growth, marketing, demand, GTM, acquisition, content, revenue, brand, digital

Seniority thresholds (paired with company size):

• Companies under 100 employees: Manager level and above qualifies
• Companies 100 to 500 employees: Director level and above qualifies
• Founder, Co-founder, Owner: pass at any company size

Department: marketing or growth function

Negative filters (any match vetoes regardless of positive signals): coordinator, analyst, junior, associate, intern, specialist, student, freelance, contractor, sales development representative (as a full phrase)

How specific titles score:

"VP of Growth" at a 45-person SaaS company. Passes role keyword (growth). Passes seniority (VP). Company under 100, so Manager+ qualifies and VP clears the floor. Passes department (growth function). No negative filter match. Result: strong ICP pass.

"Growth Marketing Coordinator" at a 200-person company. Passes role keywords (growth, marketing). Matches negative filter (coordinator). Result: vetoed, regardless of positive role signal.

"Head of Content" at a 25-person startup. Passes role keyword (content). Passes seniority (Head at a sub-100 company). Passes department (marketing function). No negative filter match. Result: ICP pass.

"Sales Development Representative" at any company. Passes sales keyword superficially but SDR is a known false positive. Add "sales development representative" as a full-phrase negative filter. Result: vetoed.

This ruleset is a starting point. Run it against your own closed-won data, check recall, and add the keywords and filters your customer base reveals. The four-dimension structure stays the same. The specific rules will be yours.

Related Reading

• How to Build a Sales Prospecting List
• How to Build a Lead List in 2026: The Complete Guide
• How to Run Outbound Sales in 2026: The Complete Playbook
• Best PhantomBuster Alternatives in 2026 (Tested for LinkedIn & Lead Gen)

Related Resources

• Templates - workflow templates index
• Integrations - integrations index
• AI Automation Tools - Connect your apps and automate with AI
• AI Agent Platform - Build and deploy autonomous AI agents