Signal Types Reference

Linkt detects 17 different types of business signals. This reference explains each type, when they're triggered, and how to use them for sales intelligence.

Signal Type Overview

Signal Strength

Every signal includes a strength indicator:

Strength Interpretation

HIGH strength signals indicate:

• Major financial events (large funding rounds, acquisitions)
• C-level leadership changes
• Significant expansion or contraction
• Active procurement (RFPs, contract renewals)

MEDIUM strength signals indicate:

• Director-level changes
• Product updates and partnerships
• Geographic expansion
• Industry recognition

LOW strength signals indicate:

• Early rumors or speculation
• Minor organizational changes
• Single job postings
• Incremental updates

Detailed Type Reference

Funding

Capital raising events including venture funding, grants, and debt financing.

Triggers:

• Series Seed through IPO announcements
• Government grants and awards
• Debt financing and credit facilities
• Secondary funding rounds

Example Signal:

{
  "signal_type": "funding",
  "summary": "TechCorp announced $45M Series B funding led by Sequoia Capital, bringing total funding to $60M.",
  "strength": "HIGH",
  "references": ["https://techcrunch.com/techcorp-series-b"]
}

Sales Implications:

• Budget availability for new initiatives
• Growth mode indicates expansion plans
• New board members may influence decisions
• Post-funding companies often invest in tooling

Best Practices:

• Reach out within 2-4 weeks of announcement
• Reference growth plans in outreach
• Connect funding to your value proposition

Leadership Change

Executive and board-level personnel changes.

Triggers:

• CEO, CFO, CTO, CMO appointments
• VP-level role changes
• Board member additions or departures
• Interim leadership announcements

Example Signal:

{
  "signal_type": "leadership_change",
  "summary": "DataFlow Systems appointed Sarah Chen as new Chief Technology Officer, previously VP Engineering at Stripe.",
  "strength": "HIGH",
  "references": ["https://dataflow.io/blog/new-cto"]
}

Sales Implications:

• New leaders often evaluate existing vendors
• Fresh perspectives on technology decisions
• 90-day window for introducing new solutions
• Previous company experience informs preferences

Best Practices:

• Research the new leader's background
• Reference their previous company experience
• Time outreach for their first 90 days
• Offer value during their evaluation period

Layoff

Workforce reductions and restructuring events.

Triggers:

• Mass layoff announcements
• Department eliminations
• Restructuring news
• Hiring freeze announcements

Example Signal:

{
  "signal_type": "layoff",
  "summary": "GlobalTech announced 15% workforce reduction affecting 200 employees, primarily in sales and marketing.",
  "strength": "HIGH",
  "references": ["https://reuters.com/globaltech-layoffs"]
}

Sales Implications:

• Budget constraints likely in effect
• May need efficiency-focused solutions
• Remaining team may be overwhelmed
• Could indicate strategic pivot

Best Practices:

• Approach with sensitivity
• Focus on cost reduction value
• Consider postponing aggressive outreach
• Offer efficiency-focused solutions

Product Launch

New products, features, or significant updates.

Triggers:

• New product announcements
• Major feature releases
• Platform expansions
• Product rebrands or pivots

Example Signal:

{
  "signal_type": "product_launch",
  "summary": "CloudCorp launched new AI-powered analytics platform targeting enterprise customers, expanding from SMB focus.",
  "strength": "MEDIUM",
  "references": ["https://cloudcorp.com/blog/new-platform"]
}

Sales Implications:

• Company is investing in growth
• New products need supporting tools
• May signal market expansion
• Technical needs may be evolving

Best Practices:

• Understand the new product's requirements
• Position as enabler for launch success
• Connect to their go-to-market needs

Partnership

Strategic alliances, integrations, and collaborations.

Triggers:

• Technology partnership announcements
• Integration launches
• Co-marketing agreements
• Channel partner additions

Example Signal:

{
  "signal_type": "partnership",
  "summary": "SalesFlow announced strategic partnership with Salesforce, launching native integration on AppExchange.",
  "strength": "MEDIUM",
  "references": ["https://salesflow.com/news/salesforce-partnership"]
}

Sales Implications:

• Indicates ecosystem alignment
• May signal technology direction
• Partnership deals often require new tools
• Shows willingness to invest in integrations

Best Practices:

• Check if your solution complements the partnership
• Reference integration capabilities
• Understand their partner ecosystem

Acquisition

Mergers and acquisitions activity.

Triggers:

• Company acquisition announcements
• Merger completions
• Asset purchases
• Acquisition rumors (lower strength)

Example Signal:

{
  "signal_type": "acquisition",
  "summary": "DataCorp acquired competitor Analytics Inc for $200M, expanding into the enterprise analytics market.",
  "strength": "HIGH",
  "references": ["https://bloomberg.com/datacorp-acquisition"]
}

Sales Implications:

• Major technology decisions pending
• System consolidation likely
• Budget may shift significantly
• New stakeholders entering decisions

Best Practices:

• Identify decision makers post-merger
• Position for system consolidation
• Understand integration timelines
• Be patient through transition periods

Expansion

Geographic or market expansion activities.

Triggers:

• New office openings
• International expansion
• New market entry announcements
• Regional headquarters establishment

Example Signal:

{
  "signal_type": "expansion",
  "summary": "TechStart opened new engineering office in Austin with plans to hire 100 developers in 2025.",
  "strength": "HIGH",
  "references": ["https://techstart.com/news/austin-office"]
}

Sales Implications:

• Active investment in growth
• New locations need new tools
• Scaling challenges create opportunities
• Regional presence may matter

Best Practices:

• Offer solutions for scaling challenges
• Reference multi-location capabilities
• Connect to their expansion timeline

Award

Industry recognition and certifications.

Triggers:

• Industry award announcements
• Best workplace recognitions
• Technology certifications
• Analyst rankings

Example Signal:

{
  "signal_type": "award",
  "summary": "CloudSecure named a Leader in Gartner Magic Quadrant for Cloud Security 2025.",
  "strength": "MEDIUM",
  "references": ["https://gartner.com/mq-cloud-security"]
}

Sales Implications:

• Indicates company credibility
• May drive increased demand
• Shows commitment to quality
• Good conversation starter

Best Practices:

• Use as an ice-breaker
• Congratulate in outreach
• Lower priority signal overall

Pivot

Business model or strategic direction changes.

Triggers:

• Business model announcements
• Market focus shifts
• Product strategy changes
• Company rebrand

Example Signal:

{
  "signal_type": "pivot",
  "summary": "ConsumerApp announced pivot to B2B SaaS model, targeting enterprise customers starting Q2 2025.",
  "strength": "HIGH",
  "references": ["https://consumerapp.com/b2b-announcement"]
}

Sales Implications:

• Major strategic change underway
• Likely need new tooling
• Budget may be reallocating
• Team structure changing

Best Practices:

• Understand the new direction
• Position for their new market
• Offer relevant solutions quickly

Regulatory

Compliance issues and regulatory changes.

Triggers:

• Regulatory action announcements
• Compliance violation news
• Legal settlements
• Regulatory approval achievements

Example Signal:

{
  "signal_type": "regulatory",
  "summary": "FinanceApp received SEC inquiry regarding data handling practices, launching internal review.",
  "strength": "MEDIUM",
  "references": ["https://wsj.com/financeapp-sec"]
}

Sales Implications:

• May create compliance needs
• Budget may shift to compliance
• Risk mitigation priorities
• May delay other purchases

Best Practices:

• Offer compliance solutions if relevant
• Be sensitive to timing
• Focus on risk reduction

RFP

Request for proposal and vendor evaluation activities.

Triggers:

• RFP issuance announcements
• Vendor evaluation news
• Procurement process starts
• Technology assessment initiatives

Example Signal:

{
  "signal_type": "rfp",
  "summary": "MegaCorp issued RFP for enterprise CRM replacement, evaluating vendors through Q1 2025.",
  "strength": "HIGH",
  "references": ["https://megacorp.com/procurement/crm-rfp"]
}

Sales Implications:

• Active buying cycle
• Clear timeline and budget
• Competitive situation
• Structured evaluation process

Best Practices:

• Respond quickly to participate
• Understand evaluation criteria
• Highest priority signal type

Contract Renewal

Contract expiration and renewal activities.

Triggers:

• Contract renewal announcements
• Vendor switch news
• Multi-year deal extensions
• Renegotiation processes

Example Signal:

{
  "signal_type": "contract_renewal",
  "summary": "RetailCo's 3-year contract with current ERP vendor expires Q3 2025, evaluation process beginning.",
  "strength": "HIGH",
  "references": ["https://retailco.com/investor/filings"]
}

Sales Implications:

• Defined decision window
• May be open to alternatives
• Budget already allocated
• Incumbent advantage or disadvantage

Best Practices:

• Time outreach before renewal date
• Offer competitive analysis
• Present migration support

Hiring Surge

Unusual hiring activity patterns.

Triggers:

• Large hiring announcements
• Department-specific hiring sprees
• New function buildout
• Recruiting campaign launches

Example Signal:

{
  "signal_type": "hiring_surge",
  "summary": "StartupXYZ posted 50 engineering roles in past month, indicating rapid technical team expansion.",
  "strength": "HIGH",
  "references": ["https://linkedin.com/company/startupxyz/jobs"]
}

Sales Implications:

• Growth mode confirmed
• Scaling challenges emerging
• New team needs new tools
• Budget likely available

Best Practices:

• Time outreach to coincide with team growth
• Offer solutions for scaling teams
• Reference onboarding challenges

Infrastructure

Technology infrastructure changes and incidents.

Triggers:

• Cloud migration announcements
• Infrastructure incident news
• Data center changes
• Platform modernization initiatives

Example Signal:

{
  "signal_type": "infrastructure",
  "summary": "BankCorp announced multi-year cloud migration initiative, moving from on-premises to AWS by 2027.",
  "strength": "MEDIUM",
  "references": ["https://bankcorp.com/technology/cloud-strategy"]
}

Sales Implications:

• Major technology decisions ahead
• Budget for infrastructure tools
• Long evaluation cycles
• Technical stakeholders key

Best Practices:

• Understand their technology roadmap
• Position for modernization journey
• Connect to their specific platform

Compliance

Compliance pressures and certification activities.

Triggers:

• Compliance initiative announcements
• Certification achievement news
• Audit requirement changes
• Industry standard adoptions

Example Signal:

{
  "signal_type": "compliance",
  "summary": "HealthTech announced SOC 2 Type II certification initiative, targeting completion by Q4 2025.",
  "strength": "MEDIUM",
  "references": ["https://healthtech.com/security/soc2"]
}

Sales Implications:

• Specific compliance budget
• Defined timeline
• Technical requirements clear
• May need supporting tools

Best Practices:

• Offer compliance-relevant solutions
• Reference certification support
• Understand their specific requirements

Job Posting

Individual job posting signals.

Triggers:

• Specific role postings
• Senior position openings
• New function creation
• Skill requirement patterns

Example Signal:

{
  "signal_type": "job_posting",
  "summary": "TechCorp posted VP of Sales Operations role, indicating investment in sales infrastructure.",
  "strength": "LOW",
  "references": ["https://linkedin.com/jobs/view/123456"]
}

Sales Implications:

• Indicates specific needs
• New hires evaluate tools
• Department investment signal
• Lower priority individually

Best Practices:

• Look for patterns across multiple postings
• Connect job requirements to your solution
• Lower priority than hiring_surge

Other

Significant events not matching specific categories.

Triggers:

• Unusual news events
• Unique company situations
• Events not matching other types
• Industry-specific occurrences

Example Signal:

{
  "signal_type": "other",
  "summary": "MediaCorp announced new sustainability initiative with $50M investment in carbon-neutral operations.",
  "strength": "MEDIUM",
  "references": ["https://mediacorp.com/sustainability"]
}

Sales Implications:

• Context-dependent
• May indicate priorities
• Review individually
• May warrant custom approach

Filtering Strategies

By Intent Level

High Intent (Prioritize):

high_intent_types = ["rfp", "contract_renewal", "funding", "hiring_surge"]

Medium Intent (Follow Up):

medium_intent_types = ["leadership_change", "expansion", "acquisition", "product_launch"]

Low Intent (Monitor):

low_intent_types = ["award", "job_posting", "partnership"]

Filtering by Type

# Get only funding signals
curl -X GET "https://api.linkt.ai/v1/signal?icp_id={icp_id}&signal_type=funding" \
  -H "x-api-key: your-api-key"

Filtering by Strength

# Get only high-strength signals
curl -X GET "https://api.linkt.ai/v1/signal?icp_id={icp_id}&strength=HIGH" \
  -H "x-api-key: your-api-key"

Combined Filters

# High-intent, high-strength signals
curl -X GET "https://api.linkt.ai/v1/signal?icp_id={icp_id}&signal_type=funding&strength=HIGH" \
  -H "x-api-key: your-api-key"

Sales Trigger Mapping

Map signal types to sales actions:

Immediate Action Signals

Nurture Signals

Monitor Signals

Signal Scoring Example

def calculate_signal_score(signal):
    """Calculate priority score for a signal."""
 
    # Base scores by type
    type_scores = {
        "rfp": 100,
        "contract_renewal": 90,
        "funding": 80,
        "leadership_change": 70,
        "acquisition": 70,
        "expansion": 65,
        "hiring_surge": 60,
        "product_launch": 50,
        "pivot": 50,
        "partnership": 40,
        "infrastructure": 40,
        "compliance": 35,
        "regulatory": 30,
        "layoff": 20,
        "award": 15,
        "job_posting": 10,
        "other": 25
    }
 
    # Strength multipliers
    strength_multipliers = {
        "HIGH": 1.5,
        "MEDIUM": 1.0,
        "LOW": 0.5
    }
 
    base_score = type_scores.get(signal["signal_type"], 25)
    multiplier = strength_multipliers.get(signal["strength"], 1.0)
 
    return base_score * multiplier
 
# Example usage
signals = get_signals(icp_id)
scored_signals = [
    {**s, "score": calculate_signal_score(s)}
    for s in signals
]
prioritized = sorted(scored_signals, key=lambda x: x["score"], reverse=True)

Next Steps

• Topic Monitoring — Set up signal monitoring
• Account Monitoring — Monitor specific companies
• Signals Reference — Signal data structure