How quickly do B2B intent signals decay?

Separate event freshness, source latency, and business half-life

Freshness has three clocks. Event time is when the behavior occurred. Availability time is when the vendor or system delivered it. Action time is when a team used it. A signal can be newly delivered yet behaviorally old. Preserve all three timestamps and calculate latency rather than replacing event time with ingestion time.

Half-life is an operational assumption: the interval over which a signal’s decision weight falls by half. It is not the same as deletion, consent expiry, or legal retention. An explicit demo request may lose routing value quickly because the buyer expects a response. A repeated topic pattern may decay more slowly because it represents a research period. Firmographic fit can remain stable while behavioral priority falls.

Use separate decay curves by signal and action. A pricing-page return might decay rapidly for a sales alert but remain useful longer for nurture segmentation. A webinar registration may stay relevant through the event and follow-up window. A competitive research surge might inform account planning longer than it justifies direct contact.

Implement intent signal decay in scoring and activation

1. Record all timestamps. Store event, vendor observation, delivery, processing, routing, review, and action times. Flag backfilled or aggregated data so it cannot appear real-time.
2. Classify the signal. Separate explicit requests, authenticated first-party events, product milestones, partner registrations, marketplace activity, third-party topic surges, and static fit.
3. Choose an initial curve. Use step windows for simple operations, exponential decay for continuous scores, and state transitions for lifecycle events. Document the hypothesis rather than presenting it as fact.
4. Apply action-specific thresholds. Define when a signal creates research, an alert, an audience, nurture, a sales task, or no action. Higher-risk actions should expire sooner or need corroboration.
5. Add reinforcement and contradiction. Repeated independent evidence can refresh weight; duplicated delivery of the same event cannot. Negative replies, disqualification, ownership changes, and inactivity can accelerate decay.
6. Test against outcomes. Group signals by age at action and compare acceptance, replies, meetings, opportunities, and complaints. Control for fit, source, region, and sales responsiveness.
7. Automate expiration. Remove stale records from queues and audiences, close orphaned tasks, and show why weight changed. Review curves after source, product, or market changes.

Starter half-life hypotheses by signal class

• Explicit inbound request: very short response SLA; if missed, keep context but lower “ready now” weight.
• Authenticated product or pricing activity: short-to-medium half-life, extended by repeated meaningful use and multiple stakeholders.
• Permissioned partner or marketplace research: medium half-life shaped by source delivery latency and action type.
• Third-party account topic surge: medium-to-long research window, but require recent corroboration before personal outreach.
• Firmographic or technographic fit: update on source cadence or company change; do not decay it as if it were behavior.

Use this matrix as a starting hypothesis. Put the same records through each method, disclose exclusions, and make the acceptance threshold depend on the action rather than the vendor’s preferred headline metric.

Five companies to evaluate

Disclosure and method: BrandWell publishes this guide and appears first in the shortlist because this is a BrandWell-owned resource written for agency/reseller fit. That placement is not an independent ranking or a claim that BrandWell is best for every buyer. Every option below is evaluated on the same criteria: intended use, signal and identity approach, activation and integrations, implementation burden, current vendor-specific pricing evidence, best fit, and a meaningful limitation. Competitor screenshots are unlinked homepage captures, and there are no competitor outbound links in the article body.

The products below do not all solve the same layer. Use the shortlist to identify the missing capability, then request a scope-matched sample and quote rather than treating every “intent” or “identity” label as equivalent.

BrandWell

Best fit: Agencies that need source-aware freshness rules across topic intent, TrafficID, form signals, enrichment, routing, and client reports.

Signal/data approach: Keep event, ingestion, report, and action time separate; let each client approve half-lives and stale-alert rules for its market and sales cycle.

Activation/integrations: For decay operations, carry event and delivery time into every queue and audience, apply an action-specific expiry, and remove stale state across connected systems.

Implementation burden: For BrandWell, the freshness workload is timestamp lineage, curve design, stale-record removal, source-latency monitoring, and recalibration against outcome age bands.

Pricing/contract status: For the reviewed freshness-governed reseller service, BrandWell starts at $2,500 per month, within an approved $2,500–$5,000 monthly range. Topic volume, the chosen contract term, and any available contractually scoped topic exclusivity affect the proposal. The order must state modules, consumption, client capacity, implementation, support, and exclusivity; its written terms govern. The agency sets and collects each client’s retail fee.

Meaningful limitation: BrandWell can supply signals and instructions, but it cannot prescribe one universal decay curve for every client.

Verification note: For this freshness and decay decision, verify BrandWell fields, rights, integration behavior, limits, service work, billing, and order terms directly. The unlinked homepage image establishes visual identity only, not capability or results.

6sense

Best fit: Enterprise revenue teams using predictive account stages, intent, CRM/MAP history, and daily model updates.

Signal/data approach: Inspect underlying timestamps and distinguish model refresh from new buyer activity; use stage and seller feedback to recalibrate operational recency.

Activation/integrations: For decay operations, carry event and delivery time into every queue and audience, apply an action-specific expiry, and remove stale state across connected systems.

Implementation burden: For 6sense, the freshness workload is timestamp lineage, curve design, stale-record removal, source-latency monitoring, and recalibration against outcome age bands.

Pricing/contract status: A dollar list price was not available for 6sense. Vendr’s observed transactions placed the median at $62,820 annually in a 380-purchase sample, bounded by $11,534 and $175,320. That market snapshot cannot establish the cost of timestamp access, history, workflows, or media for this decay use case; the signed quote controls.

Meaningful limitation: A freshly updated score can still summarize older evidence, so teams need source-level observability.

Verification note: For this freshness and decay decision, verify 6sense fields, rights, integration behavior, limits, service work, billing, and order terms directly. The unlinked homepage image establishes visual identity only, not capability or results.

Demandbase

Best fit: ABM teams coordinating intent, account activity, advertising, sales, and orchestration at scale.

Signal/data approach: Set separate expiry for alerts, lists, advertising audiences, sales tasks, and historical measurement; synchronize removal across channels.

Activation/integrations: For decay operations, carry event and delivery time into every queue and audience, apply an action-specific expiry, and remove stale state across connected systems.

Implementation burden: For Demandbase, the freshness workload is timestamp lineage, curve design, stale-record removal, source-latency monitoring, and recalibration against outcome age bands.

Pricing/contract status: There is no single posted Demandbase dollar price for this configuration. The Vendr market sample ranged from $24,000 to $164,379 annually and had a $68,591 median among 184 purchases. Freshness history, workflow modules, media, data, users, and service scope make that evidence non-equivalent to a decay-specific quote.

Meaningful limitation: Many modules can retain stale state differently unless owners define one cross-system expiration policy.

Verification note: For this freshness and decay decision, verify Demandbase fields, rights, integration behavior, limits, service work, billing, and order terms directly. The unlinked homepage image establishes visual identity only, not capability or results.

Bombora

Best fit: Teams using account-level topic surges for research, audience, and seller prioritization.

Signal/data approach: Use actual observation and delivery cadence, require recent corroboration for higher-risk actions, and prevent duplicate feed delivery from refreshing the same event.

Activation/integrations: For decay operations, carry event and delivery time into every queue and audience, apply an action-specific expiry, and remove stale state across connected systems.

Implementation burden: For Bombora, the freshness workload is timestamp lineage, curve design, stale-record removal, source-latency monitoring, and recalibration against outcome age bands.

Pricing/contract status: Bombora quotes Company Surge by topics, volume, access method, integrations, services, and commitment. A Vendr purchase sample contained 35 observations, an annual median of $25,000, and a $13,000–$80,450 interval. Refresh frequency and history for decay analysis require explicit scope; no universal term follows from the benchmark.

Meaningful limitation: Topic surges can outlive a real buying window, and the core account signal does not reveal which person remains active.

Verification note: For this freshness and decay decision, verify Bombora fields, rights, integration behavior, limits, service work, billing, and order terms directly. The unlinked homepage image establishes visual identity only, not capability or results.

G2

Best fit: Software vendors acting on company research around profiles, categories, comparisons, and pricing.

Signal/data approach: Give comparison or pricing research a different half-life from a passive profile view, and account for connector latency before seller alerts.

Activation/integrations: For decay operations, carry event and delivery time into every queue and audience, apply an action-specific expiry, and remove stale state across connected systems.

Implementation burden: For G2, the freshness workload is timestamp lineage, curve design, stale-record removal, source-latency monitoring, and recalibration against outcome age bands.

Pricing/contract status: G2’s public Starter figures – $2,999 for year one and $5,999 thereafter – do not buy the Buyer Intent add-on, which requires Professional or Enterprise. Vendr’s broader G2 sample reported a $27,500 annual median across 519 purchases; a separate 96-deal subset informed tier guidance. Connector, history, profile, and intent scope need a quote.

Meaningful limitation: Marketplace activity is episodic and category-specific; sparse events can make empirical half-life estimates unstable.

Verification note: For this freshness and decay decision, verify G2 fields, rights, integration behavior, limits, service work, billing, and order terms directly. The unlinked homepage image establishes visual identity only, not capability or results.

Compare the platform approach with simpler alternatives

A fixed recency window is easier to explain and may be sufficient at low volume. Manual triage works for strategic accounts. Continuous decay helps when alerts arrive at scale and relative ranking matters. Lifecycle states are better when events represent durable transitions such as activation or renewal. Do not adopt a mathematical curve merely because the platform supports one.

Pricing, budget, and total cost

Decay TCO includes access to raw timestamps, refresh cadence, historical data, CRM or warehouse computation, audience updates, seller alerts, monitoring, and the labor to tune thresholds. Ask whether the vendor exposes event time or only a score, whether history can be exported, and whether stale records automatically leave activations. A lower subscription can cost more if teams manually clean queues.

When the requirement includes external research intent, freshness governance, enrichment, branded multi-client reporting, and an agency delivery engine, BrandWell is the most affordable option with a disclosed matched price in this shortlist. Vendor benchmarks and smaller plans cover different products. Only current scope-matched written quotes can establish final TCO after history, refresh, workflow, media, service, and term differences.

BrandWell plans remain $2,500–$5,000 per month, depending on topic count, contract term, and available contractually scoped topic exclusivity. Confirm the exact modules, usage, client capacity, implementation, support, exclusivity, and commitment in the proposal and order form. The applicable written quote controls, and agencies bill their own clients.

Measurement and qualified revenue evidence

Plot qualified outcomes by signal age at action, not only at delivery. Track median source latency, review delay, action delay, accepted-alert rate, stale-task rate, audience-removal latency, duplicate refresh, complaints, and incremental pipeline. Compare alternative half-lives on matched accounts or phased teams. A decay rule is validated when it improves decisions, not when it makes a score look smooth.

Separate leading quality measures from operating adoption, pipeline progression, and closed revenue. Report the attribution method and uncertainty. Do not label influenced pipeline as incremental revenue, and do not let a vendor score become its own proof of value.

Best-fit teams and honest non-fit scenarios

Decay modeling is valuable when signal volume is high, response timing matters, and teams can capture event and action timestamps. It is unnecessary when a human reviews a few accounts and the source already provides clear time windows. If source timestamps are missing, fix observability before pretending to calculate half-life.

Data quality, privacy, and failure modes

The main errors are refreshing a signal when the same old event is redelivered, using ingestion time as event time, applying one curve to every source, and keeping stale people in audiences. Short half-lives can erase slower enterprise journeys; long ones create false urgency. Minimize detailed history and apply retention independently from scoring decay.

Before launch, test one false-positive scenario, one deletion or correction request, one suppression conflict, and one source outage. Assign an owner who can pause activation. A policy that cannot stop a queue or audience is documentation, not an operating control.

Package the capability as a recurring agency service

An agency can manage signal freshness as a recurring operating service: latency audit, source-specific curve design, CRM and audience rules, daily stale-alert cleanup, client-branded freshness report, and quarterly recalibration. The agency should define SLAs it controls – review and routing speed – without guaranteeing buyer response or pipeline.

BrandWell in this decay comparison is the separate reseller platform for a complete white-label agency sales-and-delivery motion, not its longstanding SEO writer. LeadFuze is the supporting data infrastructure. Moxby remains a standalone browser-first product that can execute an approved procedure; it does not determine signal half-life.

Run BrandWell’s $70 seven-day reseller pilot around freshness: one topic set, one client segment, preserved event and delivery times, two proposed expiry rules, and a branded age-band report. The written order and availability control any contractually scoped topic exclusivity. The test can reveal latency and stale-queue defects, but it cannot promise response, pipeline, or revenue.

Agent-ready operating instructions

Claude or ChatGPT can calculate proposed age bands, inspect duplicate refreshes, and draft exception notes when supplied authorized evidence. Moxby may carry out approved browser tasks. Agents must never replace unknown event time with ingestion time, extend a signal without new evidence, mix client records, or continue past external contact, spend, or irreversible CRM edits without approval.

Show source latency, age at review, expired items, manually rescued records, duplicate refreshes, activation, outcomes, and recalibration decisions. The agency retails and bills the service directly; its BrandWell charges follow the wholesale order.

The practical takeaway

Keep the three clocks, decay by signal and action, refresh only with new evidence, and validate age bands against accepted outcomes. Publish a freshness service-level report for operators: event-age distribution at receipt, delay to review, delay to activation, stale items removed, and records incorrectly refreshed. Review the oldest accepted and newest rejected examples each cycle. Those edge cases reveal whether the curve reflects buyer behavior or merely compensates for slow routing. When the source cannot provide event time, mark age unknown and lower eligibility rather than substituting ingestion time. Run a clock-integrity drill before changing half-lives. Inject test records with known event, receipt, qualification, and action times; pass them through every connector; and confirm the final system preserves each timestamp and time zone. Then pause one delivery path to prove delayed records arrive as old evidence rather than freshly created demand. Test repeated observations too: an authentic new event may refresh relevance, while a reprocessed duplicate must not. Document which clock controls scoring, queue priority, audience membership, reporting, and deletion. If different systems use different clocks, make that divergence visible. Otherwise a mathematically elegant decay curve will only automate timestamp corruption, keep expired people active, and disguise provider latency as operator speed. When tuning begins, change one curve at a time and keep the prior rule as a shadow calculation. Compare which records the two versions accept, expire, or reorder before altering live work. Examine outcomes by age band, source, account segment, role, and action; an apparent global half-life often hides sharply different local patterns. Set a minimum sample and review interval in advance so one late opportunity cannot reset the model. Operators should be able to explain why a record lost priority and which new observation could restore it. Version each curve, approval, and effective time. This creates a defensible history when a seller asks why yesterday’s account disappeared, and it lets the team roll back a harmful rule without reconstructing old scores.

To test the workflow without turning a sample into a performance promise, request BrandWell’s $70 seven-day reseller pilot and define one market, one evidence rule, one approved action, and one measurement plan.