A Signal Is Not Binary
The difference between an event and a signal
An event is a raw fact: “Company X posted a job listing.” An intent signal is that event interpreted, filtered, and contextualized for your specific offering: “Company X, an SMB with 150 employees in the consulting sector in the greater Paris area, posted 4 senior developer positions simultaneously, indicating rapid growth that potentially requires a project management tool.”
Between the raw event and the actionable signal, there are 222 configuration parameters.
Why so many parameters?
Take a simple example: the “hiring” signal. Without configuration, this signal detects every job listing posted by every company worldwide. That is unusable. With configuration:
- How many hires? A single hire is not significant. 5 simultaneous hires reveal rapid growth. The threshold is a parameter.
- What type of role? An intern hire does not carry the same meaning as a CTO hire. The seniority filter is a parameter.
- Which department? A marketing hire is irrelevant to an accounting software vendor. The department filter is a parameter.
- What company size? Hiring 5 people at a 50-person SMB (+10%) is more significant than 5 hires at a 5,000-person enterprise (+0.1%). The size filter is a parameter.
- Which industry? The same hire has different value depending on whether the company operates in your target sector. The industry code filter is a parameter.
- Which geographic area? A hire in London is irrelevant to a local provider based in Manchester. The geographic filter is a parameter.
Multiply these dimensions across the 108 signal types, and you arrive at 222 possible configurations.
Parameter Categories
Trigger parameters
These parameters define the threshold at which an event becomes a signal:
- Volume: minimum number of hires, minimum funding amount, minimum headcount growth rate
- Timing: reference period (growth over 3 months vs. 6 months), detection frequency
- Intensity: distinction between incremental change and a disruption (new CEO vs. new manager)
Filtering parameters
These parameters define the scope within which the signal is detected:
- Industry: industry codes, activity keywords, sector exclusions
- Company size: headcount (min/max), revenue, category (small business, SMB, mid-market, enterprise)
- Geography: departments, regions, countries, distance from a point
- Tech stack: technologies mentioned in job postings or on the company website
- History: first detection vs. recurring signal, company already contacted or not
Scoring parameters
These parameters feed the Balance model:
- Signal weight: value assigned to each signal type based on its relevance to your offering
- Recency coefficient: decay rate after 48 hours
- Tier thresholds: minimum score for Tier 1, Tier 2, Tier 3
- Combinations: bonus when multiple signals converge on the same company
Contextualization parameters
These parameters enrich the signal before delivery:
- Enrichment: Deep Search level (basic, standard, in-depth)
- Contact: type of decision-maker to target (CEO, CTO, HR Director, CFO)
- Channel: recommended outreach channel (email, LinkedIn, phone)
- Template: suggested message template based on signal type
Concrete Configuration Examples
Configuration: “SaaS vendor targeting post-funding scale-ups”
| Parameter | Value |
|---|---|
| Signal | Funding round |
| Minimum amount | €2M |
| Industry | Tech, SaaS, Digital |
| Headcount | 20-500 |
| Geography | France + Belgium + Switzerland |
| Contact | CTO / VP Engineering |
| Scoring | 10/10 |
| Tier | 1 (ABM) |
Configuration: “Generalist recruitment agency”
| Parameter | Value |
|---|---|
| Signal | Multiple hires |
| Threshold | 5+ simultaneous postings |
| Industry | All (excl. temp staffing) |
| Headcount | 50-2,000 |
| Geography | Greater Paris area |
| Contact | HR Director / Talent Manager |
| Scoring | 9/10 |
| Tier | 1 or 2 depending on volume |
Configuration: “Insurer targeting growing companies”
| Parameter | Value |
|---|---|
| Signal | Headcount growth |
| Threshold | +20% over 6 months |
| Industry | All |
| Headcount | 50-500 |
| Geography | Metropolitan France |
| Contact | CFO / HR Director |
| Scoring | 8/10 |
| Tier | 2 |
The Creation Phase: Configuring with Method
Configuring the 222 parameters is not done at random. It is the first phase of the Rodz methodology: Creation.
- Offering audit: understand precisely what you sell and what need you solve
- Existing client analysis: identify the signals that preceded purchases from your best clients
- Initial configuration: set up 3 to 5 signal configurations covering the most frequent use cases
- Testing: run detection on a limited scope for 4 to 6 weeks
- Validation: process at least 274 prospects per configuration before drawing conclusions on effectiveness
The complexity of the 222 parameters is abstracted by the Rodz interface, which guides configuration step by step. The Rodz team’s expertise supports clients through critical decisions. To go further, check out our tutorial on configuring your first signal via the API, as well as the complete Rodz API reference with full details on endpoints and available parameters.
Frequently Asked Questions
Do I need to configure all 222 parameters myself?
No. The Rodz team guides each client through the Creation phase. Default parameters cover 80% of needs. The remaining 20% are adjusted based on your offering, your market, and your initial results. The initial configuration takes 1 to 2 weeks.
Can configurations be modified along the way?
Yes, and it is recommended. The Capitalization phase is specifically about analyzing results by configuration and adjusting parameters. A signal that fails to generate positive responses after 274 prospects can be reconfigured or replaced.
Why 222 and not 50 or 500?
The 222 parameters cover every necessary dimension without redundancy. Each parameter has a measurable impact on signal relevance. Below that number, detection would be too coarse. Above it, the added complexity would not deliver meaningful gains.