Signal centralizes journalist discovery, targeting, sync, and workflow execution. This page shows how the system works, how key metrics are measured, how the 48-hour refresh cycle is defined, and how access is controlled. Not vague trust language. Inspectable operating logic.
Signal leads with system behavior, not abstract promises. Claims are tied to refresh cycles, scoped metrics, workflow constraints, and named controls.
"Fast" is weak. "Under 3 seconds from discovery to CRM" is useful. Signal uses concrete frames whenever possible.
Metrics are scoped to a defined environment. Current beta workflows. Active mailboxes. Defined reporting windows. No inflated universal claims.
Signal uses hard product rules where risk matters. A 40-email-per-day cap. Paced sending delays. Minimum-required access. Clear boundaries beat soft guidance.
Signal uses a 48-hour refresh cycle as the primary freshness model. Indexing is the technical method behind it. Not static records refreshed months later.
100%
of discovered journalists published within 30 days
Current beta sample<2%
average bounce rate
Current beta mailboxes<3s
discovery to CRM
Active sync eventsAll metrics are scoped to a defined environment and reporting window. Each metric carries a named environment, a reporting window, a metric definition, and an implication. Signal does not present observations without context.
Signal does not present beta observations as universal outcomes. It does not turn narrow samples into category-wide claims.
The buyer-facing term for how Signal keeps data current. Every journalist record is refreshed within a rolling 48-hour window.
Under the hood, Firecrawl indexes the live web, extracting journalist activity, publication timestamps, and topic signals from source pages.
When Signal says data is "current," it means recently refreshed within the 48-hour cycle. Not continuous real-time. Not live-to-the-second. A defined refresh window with a named method.
Record says journalist covers AI infrastructure. Recent work actually shows policy coverage. Stale database still treats as fit.
48-hour refresh cycle catches the shift. Beat reassignment reflected before next outreach cycle. You pitch the right person for the right topic.
Protects domain reputation by keeping volume within a controlled range. A product rule, not a suggestion.
Introduces delays between sends to avoid rigid machine-like timing patterns that providers can flag.
Signal is designed for focused outreach to qualified journalists, not bulk email distribution.
Deliverability controls exist because sending behavior has consequences. Lower daily volume reduces domain stress, limits damage from weak lists, and preserves long-term deliverability. All metrics are scoped to current beta mailboxes.
Your mailbox and CRM stay your systems of record. Signal connects to run a defined workflow — it does not own your data.
All third-party access uses OAuth authorization flows. No stored passwords. No shared secrets.
OAuth tokens are encrypted at rest with AES-256 GCM. A concrete, evaluable control — not vague language.
Signal only requests the permissions needed to run the workflow. Narrower scope reduces exposure.
Every claim Signal makes follows a scoping rule. Here is how to interpret each type.
Tied to the 48-hour refresh cycle
When Signal says data is 'current,' it means recently refreshed within the 48-hour cycle. Not continuous real-time. Not live-to-the-second. A defined refresh window with a named method.
Measured from event to sync
When Signal says '<3 seconds,' it means the time from journalist discovery to CRM sync event. Measured on active sync events in the current environment. Not a universal latency promise.
Scoped to the reporting window
Metrics like bounce rate and recency are measured within a defined reporting window, on current beta mailboxes and workflows. Environment, sample size, and definition are stated.
Operational, not abstract
ROI is calculated from actual workflow savings — hours reclaimed from list cleaning, manual CRM handoff, and journalist qualification. Not from projected revenue or abstract value.
6 Hard Product Rules
Not more claims. Better boundaries.
Review how Signal applies the 48-hour refresh cycle, controlled sending, direct CRM sync, and constrained access inside one PR workflow built for current execution.