Phi

Revenue Workflow

Intent Signal Capture and Activation

This workflow ingests intent signals from product usage, partner overlaps, tech stack changes, funding events, and social activity, then scores accounts and triggers automated GTM motions.

AdvancedTime to value · 4 to 6 weeks16 tools

The outcome

Accounts are prioritized by buying readiness and automatically routed into outbound sequences, ABM plays, and rep alerts based on real-time intent.

How it flows

How it flows.

Source
Product Events
Source
CRM Activity
Source
Website Visitors
Source
Content & Webinars
Source
Partner Overlaps
Source
Review Site Visits
Source
Tech Stack Changes
Source
Funding & Hiring
Source
Social & Search Trends
Process
Normalize & Enrich
Process
Score & Stage Assignment
Store
CRM Signal Store
Channel
Outbound Sequence
Channel
Rep Slack Alert
Output
ABM Segment
Channel
Email Automation
Drag to pan · scroll to zoom

    Build it, step by step

    Build it, step by step.

    1. 01

      Define signal purpose and use cases

      Establish what you will do with signal data: score buying readiness, trigger outbound, push rep alerts, track expansion risk, or build ABM segments. This determines which signals matter and how they should be weighted.

      • Decide if signals will drive automated outbound, ad targeting, or manual rep follow-up
      • Map signal types to revenue stages: awareness, consideration, selection, expansion, churn risk
      • Identify stakeholders who will act on signals (SDRs, AEs, CSMs, marketing ops)
    2. 02

      Map signal categories and sources

      Organize all potential signals into first-party (owned), second-party (partner), and third-party (public) buckets. This creates a taxonomy for ingestion and scoring.

      • First-party: product analytics, CRM activity, website behavior, content engagement
      • Second-party: partner overlaps, warm intros, review site visits, LinkedIn ad engagement
      • Third-party: tech stack changes, funding announcements, job postings, social mentions, search trends
    3. 03

      Instrument first-party signal capture

      Connect product analytics, CRM, website, and marketing tools to capture every owned interaction. These are the highest-fidelity signals because they reflect direct engagement with your brand.

      • Ingest product event streams from Amplitude, Mixpanel, or similar into your warehouse or CRM
      • Track CRM activities: email opens, replies, calls logged, tasks completed
      • Monitor website events: pricing page visits, demo form submissions, repeat visits
      • Capture content and webinar engagement: downloads, attendance, poll responses
    4. 04

      Add second-party signal sources

      Pull in partner overlap data, referral activity, review site engagement, and LinkedIn ad interactions. These signals reveal accounts that are already warm or in-market.

      • Connect Crossbeam or PartnerStack to identify shared accounts and mutual customers
      • Track when accounts visit your profile on Capterra, TrustRadius, or G2
      • Monitor LinkedIn ad engagement and connection requests from target accounts
      • Log warm intros and referrals from partners or investors
    5. 05

      Layer third-party buying signals

      Use external data providers to detect tech stack changes, funding events, hiring spikes, and social activity. These signals often precede active buying cycles.

      • Monitor tech stack changes via BuiltWith or TheirStack
      • Pull funding announcements and firmographic updates from PredictLeads, Crunchbase, or PitchBook
      • Track job postings for relevant roles that indicate growth or tool adoption
      • Capture social mentions, keyword trends, and content engagement using Ahrefs or Perplexity
    6. 06

      Centralize signals into a single system

      Route all signals into your CRM or data warehouse with consistent formatting. Every signal should carry an account ID, contact ID, timestamp, source, and signal type.

      • Use Clay or a warehouse ETL to normalize and merge signals from all sources
      • Write signals into CRM custom fields or a dedicated signal object in Attio, HubSpot, or Salesforce
      • Tag each signal with source, event type, timestamp, and associated account or contact
      • Ensure signals append incrementally without overwriting historical data
    7. 07

      Normalize and score signals

      Weight signals by type, recency, and intensity, then roll them into a unified intent score or awareness stage. This makes signals actionable and comparable.

      • Assign point values to each signal type based on historical conversion data
      • Weight recent signals higher using time decay (e.g., 30-day rolling window)
      • Map cumulative scores to awareness stages: Identified, Aware, Interested, Considering, Selecting
      • Store scores in CRM as numeric fields or stage labels for filtering and automation
    8. 08

      Enrich accounts with fit and intent

      Combine intent scores with firmographic and technographic fit data to create a unified GTM profile. This ensures high-intent accounts also meet ICP criteria.

      • Merge signal scores with firmographic data (revenue, employee count, industry, location)
      • Append technographic data (current stack, integrations, tool usage)
      • Assign account tiers, ownership, and persona tags in CRM
      • Track post-sale health metrics (usage decline, champion turnover) for expansion and retention
    9. 09

      Trigger automations on signal thresholds

      Configure CRM workflows to launch outbound sequences, create tasks, send Slack alerts, or start ad campaigns when intent crosses defined thresholds.

      • Enroll accounts into Outreach or Salesloft sequences when awareness stage advances
      • Create CRM tasks for AEs or SDRs when high-value signals fire (e.g., pricing page visit + funding announcement)
      • Push Slack alerts for top-tier accounts crossing into 'Considering' or 'Selecting' stages
      • Trigger retargeting ads or ABM plays in LinkedIn or Google Ads for high-intent segments
    10. 10

      Build ABM segments and retention monitors

      Use combined fit and intent scores to dynamically generate ABM target lists. Also monitor post-sale signals to catch expansion opportunities or churn risk early.

      • Create dynamic CRM views or segments for accounts meeting both fit and intent thresholds
      • Track feature adoption or usage decline in existing customers to surface upsell or churn risk
      • Monitor job changes for champions or economic buyers to trigger re-engagement
      • Sync ABM segments to ad platforms, outbound tools, and rep task queues
    11. 11

      Close the feedback loop

      Feed meeting outcomes, deal won/lost data, and rep feedback back into signal scoring logic. This improves weights over time and reduces noise.

      • Log meeting outcomes (booked, showed, no-showed, converted) in CRM with associated signals
      • Analyze which signal combinations correlate with closed revenue
      • Increase weights for high-converting signals, decrease or remove low-value noise
      • Review signal ROI dashboards monthly and adjust scoring parameters

    The stack

    The stack.

    Want a pod to run this for you?

    Phi pods plug this workflow into your existing stack as Revenue Infrastructure, then operate it.