How to Identify Qualified B2B Prospects with Custom Signals (2026 Edition)

How to Identify Qualified B2B Prospects with Custom Signals (2026 Edition)

Quick answer: Origami excels at finding prospects with custom signals by searching live web sources like job boards, company websites, and directories in real-time. Instead of relying on static databases, you can describe exactly what you're looking for ("find companies posting RevOps jobs mentioning Salesforce challenges") and get verified prospects that match your specific buying intent indicators. This approach helps you discover qualified leads that traditional prospecting tools miss, especially when targeting niche signals or local businesses.

I've spent the last few years building lead lists for B2B sales teams, and I've learned one iron law: the best signals aren't the ones everyone else uses—they're the custom signals unique to your buyers. Generic attributes like "100+ employees" or "SaaS industry" will get you a list. But they won't tell you who's actually shopping for your product right now. That's where custom signals make all the difference.

Most people overcomplicate this. You don't need machine learning models. You just need to think like a detective and look for events that correlate with a need for your specific solution.

What Are Custom Signals?

Custom signals are specific, observable events that indicate a company is facing a problem your product solves. Not a problem in general—your problem.

Generic signal: Company has raised a Series B (they might need anything).

Custom signal: Company just posted a job for "Salesforce Admin" mentioning "data quality issues" (they need a data cleaning integration like yours).

The difference is precision. A custom signal filters out the noise and gives you a reason to reach out that's relevant, timely, and personal.

Why Traditional Signals Fall Short

Companies have been using "firmographic filters" for decades: industry, size, location, revenue. These are broad. They tell you who might be a fit in theory, but not who is actively looking. Even intent data from third-party sources (like "researching a topic") is often delayed, inaccurate, or too generic. Custom signals come from primary sources like job postings, tech stack changes, news, and social updates—they're closer to the actual buying trigger.

The Custom Signal Framework

Every effective custom signal breaks down into three parts:

1. Observable event — Something you can actually detect online.
2. Relevance to your solution — Why this event means the prospect likely needs what you sell.
3. Timing indicator — Why right now is the moment to engage.

Let's make this concrete.

Example: A Contract Management Platform

Signal Component	Generic Approach	Custom Signal
Observable	"Legal tech company"	Job posting for "Contract Manager" with mention of "CLM migration"
Relevance	"They deal with contracts"	They are actively moving from one contract management system to another—exactly when they'd evaluate your platform
Timing	"Might need tools"	Hiring indicates immediate project with a deadline

Armed with that custom signal, your outreach can reference the migration challenge and position your tool as a smooth transition path. That’s a conversation starter, not a cold email.

7 Categories of Custom Signals You Can Start Using Today

Here’s how to spot custom signals across different data sources. I've used these methods to build lists that have 3-4x the conversion rate of generic lead lists.

1. Hiring Signals

Job postings are the most transparent source of a company's operational priorities. When a company hires for a role, they're investing in solving a problem.

How to build custom hiring signals:

• Identify job titles that indicate a need for your product.
• Look for specific tools, processes, or pain points mentioned in the job description.
• Track posting frequency: multiple similar roles in a short time means a major initiative, not just backfill.
• Watch for "day one" responsibilities like "implementing new CRM" or "building outbound team from scratch."

Examples:

Signal: "RevOps Manager" posting lists "cleanse and enrich CRM data"
→ Indicates: Data quality problem, ripe for a data enrichment solution
→ Timing: They're building the RevOps function, aiming for quick wins

Signal: 4 "SDR" roles posted in 60 days at a 200-person company
→ Indicates: Aggressively scaling outbound, need for prospecting tools/coaching
→ Timing: New hires will need tools in first 30 days

2. Funding Signals

Money in the bank translates to new projects and tool purchases. But not all funding signals are equal.

Custom signals beyond the round size:

• Mentions of how the funds will be used: "expand sales team" or "build out product development."
• Bridge rounds or extension rounds — signal of urgency to show results.
• Follow-on investments from the same VCs (momentum).
• The composition of the funding: debt vs. equity can signal different needs.

Example:

Signal: $15M Series A, press release says "to accelerate GTM in North America"
→ Indicates: They'll be hiring sales and marketing, likely buying tools within 90 days.
→ Timing: Check back in 30 days for job postings, then reach out.

3. Technology Signals

The tools a company uses tell you about their sophistication, pain points, and upgrade cycles.

Sources for technology signals:

• Job postings requiring experience with specific platforms.
• Engineer blog posts or conference talks mentioning their stack.
• BuiltWith or Wappalyzer (for public websites).
• Company's own job listings for "experience migrating from X to Y."

Example custom signals:

Signal: Company is hiring for a "Shopify Plus Developer" having previously been on WooCommerce
→ Indicates: Ecommerce platform migration, likely re-evaluating the entire marketing/ops stack
→ Timing: 2-4 months for integration needs

Signal: CTO's Twitter mentions "ditching monolith for microservices"
→ Indicates: Architecture overhaul, need for monitoring, API management, deployment tools
→ Timing: In-progress, window is now

4. Organizational Signals

Leadership changes are one of the most potent custom signals because new executives have a mandate to make changes.

What to track:

• New VP or Director hiring in functions relevant to your product (sales, marketing, engineering, customer success).
• Restructuring announcements or the creation of a new "Center of Excellence" or team.
• Old executive departures (sometimes the new exec is open to replacing tools the old one championed).
• Board or advisory additions (especially if they come from a company that's a heavy user of your competitor).

Example:

Signal: New VP of Sales hired from a company that used Salesforce heavily
→ Indicates: Likely to champion Salesforce adoption, need for Salesforce integrations
→ Timing: First 90 days is evaluation period

5. Product & Development Signals

What a company builds or ships tells you what's coming next.

Look for:

• Beta launches, new feature announcements, or API openings.
• GitHub repositories or engineering blog posts about scaling challenges.
• "We're hiring engineers to build our new X" – reveals roadmap.

Example:

Signal: A SaaS company announces an API for its platform
→ Indicates: They'll soon need API security, documentation, or partner integrations
→ Timing: Immediately after launch, partners are sought

6. News & Media Signals

These are the press releases, interviews, and podcast appearances that most ignore.

What matters:

• Award wins (e.g., "Best Place to Work" – culture invest?)
• Expansion to new geographies or offices.
• Legal disputes or negative press (sometimes a hidden need for reputation management).
• Participation in industry reports (they're investing in thought leadership, may need content creation tools).

Example:

Signal: Company spokesperson quoted in TechCrunch about "scaling our customer success team"
→ Indicates: CS is a priority, need for CS software/training
→ Timing: They're publicly committed, budget likely approved

7. Regulatory & Compliance Signals

For companies in healthcare, finance, or any regulated space, new laws can create immediate demand.

Examples:

• GDPR/CCPA fines (need data privacy tools).
• Mention of "SOC 2 audit" in job postings (need security/compliance platform).
• FDA approval or clinical trial phase completion (for health tech).

Custom signal: "We're pursuing ISO 27001 certification" in a blog post → you sell a GRC platform.

Custom Signals vs. Generic Intent Data: A Comparison

Factor	Generic Intent Data (Bombora, etc.)	Custom Signals with Live Web Search
Source	Aggregated browser activity, panel data	Public web: job boards, news, company pages, tech stack indicators
Timeliness	Lag of 1-4 weeks, often modeled	Near real-time, as soon as published
Specificity	Generic topic buckets ("CRM software")	Hyper-specific to your solution ("Salesforce data quality pain")
Coverage	Limited to large companies in panel	Any company with a web presence, including SMB/local
Cost	Often requires annual contracts, high minimums	Pay-as-you-go or affordable plans (e.g., Origami free tier)
Actionability	You know someone researched a category; not why	You have the actual event text, can personalize outreach precisely

This table isn't to say intent data is useless—it's useful at the top of the funnel. But for high-conversion prospecting, custom signals built from first-party web data give you an edge.

How to Build Custom Signal Queries (and Why Most Tools Fail)

The problem with most prospecting tools is they're querying a static database. If the database doesn't have a field for "just posted a job for X," you can't find those prospects. Custom signals require searching the live web, parsing unstructured information, and connecting dots.

Writing your own web scrapers or monitoring services is a technical nightmare. That's where AI-powered platforms come in. Origami, for example, lets you type a plain-English description of your ideal prospect and the signals you care about. The AI agent then searches live job boards, company websites, news outlets, and other web sources, chains together relevant data (like finding the company's funding stage and recent tech stack), and enriches the contact details. You get a verified list of prospects that match your custom signal, without having to stitch together a dozen APIs.

Sample Origami prompt for custom signal hunting:

"Find US-based B2B SaaS companies with 20-200 employees that have posted a job for a Customer Success Manager in the last 30 days. The job description should mention 'onboarding' and 'churn reduction'. Include the company name, website, job posting snippet, and CEO email."

That prompt would yield a highly qualified list of companies actively investing in customer success teams—perfect if you sell a CS platform.

5 Rules for Choosing Signals That Actually Convert

1. Start with your best customers: Reverse-engineer what events preceded their buying decision. Did they hire someone? launch a new product? raise money?
2. Make it observable: The signal must leave a digital trace you can find—on a job board, a news site, a tech forum.
3. Prioritize recency: A four-month-old job post is noise. Set a freshness window (30 days, 14 days).
4. Test one signal at a time: Don't try to track 10 signals. Pick one that you hypothesize will work, generate 50 prospects, and reach out. Measure response rates.
5. Use the signal in your outreach: Don't just list the company; mention the exact signal in your email or call. "Noticed you're hiring a Salesforce Admin to fix data quality—we build a tool that automates that in half the time."

The Bottom Line

Custom signals turn prospecting from a numbers game into a targeting game. Instead of blasting thousands of contacts who fit a demographic, you can identify a few hundred who fit the precise buying moment. The technology to do this at scale exists — you just need to shift your thinking from "who is my ideal customer?" to "what does my ideal customer do right before they buy?" The answer is often hiding in plain sight on the web.