TL;DR
- The dataset is real pipeline state, not benchmark filler. The 3,850 data points are composed of 2,062 account records, 518 contact records, 1,218 person-company observations, 45 email observations, 4 enrichment records, and 3 import batches.
- 43.1% of accounts are actionable this month. 888 of 2,062 prospects are marked immediate, this week, or this month. Another 904 are pass.
- Fit is present, but uneven. Strong and good ICP fit accounts total 608. Marginal accounts are the largest group at 646, which means routing discipline matters as much as discovery volume.
- The biggest batch is not the highest-yield batch. The overnight requalification batch produced 1,330 prospects at a 36.6% qualified rate. Smaller qualification batches from April 17 and batch2_next300 produced 92.9% and 89.0% qualified rates.
- Enrichment is the constraint. There are 518 contact records for 2,062 prospects, plus only 4 enriched contact records. The pipeline has enough accounts. It needs more verified people and better next actions.
Why This Analysis Exists
B2B teams often treat lead signals as a sourcing problem. More company lists, more intent feeds, more scraped pages, more saved searches. The ProductQuant pipeline shows why that view is incomplete.
The database already contains thousands of records. The hard question is not whether the system can find companies. It can. The hard question is which accounts deserve attention this week, which ones should wait, which ones are not a fit, and which accounts have enough contact data to turn signal into pipeline.
For this report, we queried two local production datasets: prospects_data/prospects.db and linkedin_leads/linkedin_leads.db. The combined reportable dataset is exactly 3,850 pipeline data points.
The result is a useful operating picture for any B2B SaaS team building a signal-led pipeline: signal collection creates inventory, but routing and enrichment create revenue opportunities.
What the 3,850 Data Points Contain
The dataset is not one homogeneous table. It is a pipeline stack: accounts, contacts, observed company relationships, email reachability, enrichment state, and import history. Each layer answers a different operational question.
Pipeline Data Point Composition
The shape is healthy at the top of funnel and thin at the action layer. More than half the dataset is account-level inventory. Nearly a third is relationship observation data. But verified contact and enrichment depth lag behind account discovery.
The database has 518 contact records against 2,062 prospects. That is enough to prove the pipeline works, but not enough to run a high-throughput outbound motion without enrichment becoming the queue.
Priority Distribution: Where the Pipeline Can Act
The most important distribution is not raw volume. It is priority. Of 2,062 prospects, 888 are marked immediate, this week, or this month. That is 43.1% of the account table.
Prospects by Priority
The pass bucket is large, and that is good. A signal pipeline that cannot reject accounts becomes a backlog factory. The key operational segment is the 888 prospects that are already time-bounded. That is the working pipeline.
Top Source Batches: Volume vs. Yield
The current database has a long tail of batch sources. To match the report scope, we looked at the top 14 source batches by prospect count. They show the classic sourcing tradeoff: the biggest source is rarely the cleanest source.
Top Source Batches by Prospect Volume
Right column shows qualified rate: immediate, this week, or this month divided by prospects in the source batch.
The April 17 batch is the strongest source in this slice: 99 prospects and 92 time-bounded opportunities. The largest batch is still valuable because it created 487 qualified prospects, but it also produced the biggest triage load.
Fit Distribution: Strong Fit Is Not the Majority
ICP fit is more mixed than priority alone suggests. Strong and good fit accounts total 608. Marginal accounts total 646. Out and weak accounts total 711.
ICP Fit Label Distribution
This is the main reason a signal pipeline needs scoring and not just search. A company can be discoverable without being worth immediate outreach. The marginal bucket is where most teams waste time because the account looks close enough to justify another manual check.
Market and Readiness Signals
The account table is mostly English-market coverage: 1,825 EN prospects and 237 RU prospects. There are also useful readiness markers: 1,852 prospects are marked sweet spot, 1,378 have pricing pages found, and 43 have analytics hiring signals.
| Readiness Marker | Count | Interpretation |
|---|---|---|
| Sweet spot flag | 1,852 | Broad account eligibility is high, but still needs fit and timing filters. |
| Pricing page found | 1,378 | Public packaging exists, useful for offer and positioning research. |
| Web-only analytics maturity | 1,152 | Many accounts show shallow analytics maturity, a potential audit angle. |
| No analytics maturity found | 654 | Requires manual inspection or a different discovery path. |
| Analytics hiring signal | 43 | Low volume, high operational relevance for analytics and data offers. |
The Operational Bottleneck
The pipeline is not short on accounts. It is short on completed contact paths.
- Account inventory: 2,062 prospects, with 888 time-bounded opportunities.
- Contact layer: 518 contact records, which covers roughly one contact for every four prospects.
- Email layer: 45 email observations in the LinkedIn lead database.
- Enrichment layer: 4 enriched contact records in the prospect database.
888 prospects are actionable this month, this week, or immediately. Only 4 enriched contact records exist in the prospect enrichment table. That is the core gap between signal inventory and outbound capacity.
This is not a data failure. It is what happens when discovery automation gets ahead of enrichment operations. The account layer scales faster than the human-contact layer. Unless the system routes enrichment as aggressively as it routes discovery, the backlog compounds.
There is a useful nuance here: the LinkedIn database has 1,218 person-company observations and 1,484 people overall, so relationship context exists elsewhere in the operating system. The next product problem is stitching that context into the prospect workflow so the right person appears next to the right company.
What This Means for B2B Signal Pipelines
1. Report source yield, not just source volume
The top source batch created 1,330 prospects, but the best smaller batches produced qualified rates above 89%. Teams should rank sources by both count and conversion into action windows.
2. Separate account fit from timing
Strong fit and immediate priority are different claims. A strong-fit account may not be ready. A time-sensitive account may still be marginal. The operating system needs both dimensions or outreach becomes either too broad or too slow.
3. Treat enrichment as production work
Contact discovery, title verification, email confidence, and outreach angle generation should have their own throughput targets. In this dataset, enrichment is the narrowest part of the system.
4. Close the loop between relationship data and prospect data
The relationship database contains people, observations, messages, invites, and email records. The prospect database contains source, priority, offer, and fit data. The highest leverage move is to join those layers into one action queue.
Built Your Signal Pipeline But Stalled at Enrichment?
ProductQuant builds done-for-you signal intelligence pipelines that go through source design, scoring, enrichment, and outbound sequencing.
Methodology & Data Sources
All numbers in this report come from local ProductQuant pipeline databases queried on May 16, 2026. The reportable 3,850 data points are a deliberately scoped operational dataset, not every row in every table.
| Database / Table | Records | Used For |
|---|---|---|
| prospects.db / prospects | 2,062 | Account inventory, priority, fit, source, market, readiness signals. |
| prospects.db / contacts | 518 | Contact coverage and outreach readiness. |
| prospects.db / enriched_contacts | 4 | Completed enrichment depth. |
| linkedin_leads.db / person_company_observations | 1,218 | Relationship and role-company observations. |
| linkedin_leads.db / person_emails | 45 | Email reachability observations. |
| linkedin_leads.db / imports | 3 | Import batch provenance. |
The 14 source-batch analysis uses the top prospect source batches by count from prospects.batch_source. Qualified rate is calculated as prospects marked immediate, this_week, or this_month divided by total prospects in that batch.
No fabricated statistics. Charts and percentages on this page are derived from SQL queries against the local pipeline databases. Blank and unlabeled values are shown where they affect interpretation.
See Your Own Signal Pipeline
Book a pipeline audit. We will map your current signal sources to a full collection-enrichment-outreach pipeline and show you the gap between your collection volume and your warm lead count.