Whether you're looking for an angel investor, a growth advisor, or just want to connect — I'm always open to great ideas.
Get in TouchAI, startups & growth insights. No spam.
TL;DR: Signal-based selling replaces guesswork with evidence — targeting buyers who are already in-market using intent data, product usage signals, and behavioral triggers. B2B startups that build even a basic signal stack see reply rates 3–5x higher than cold outbound and close deals weeks faster. This guide walks through the full system: signal sources, scoring models, automation sequences, and how to do it without a data team.
I spent three years doing cold outbound the wrong way. We had sequences, we had personalization tokens, we A/B tested subject lines. Our reply rate hovered around 1.2%. Our SDRs were demoralized. Every quarter the VP of Sales would show a pipeline coverage chart and we would nod along, knowing the denominator was mostly noise.
The problem was not our copy. It was not our targeting lists. The problem was that we were interrupting people who were not ready to buy. We were calling them at the wrong moment in their buying journey — before they had a problem, before they had urgency, before they had budget conversations internally. No amount of clever personalization fixes that timing problem.
Signal-based selling is the practice of using behavioral and contextual data — signals — to identify buyers who are actively in-market, then reaching them at the exact moment their intent peaks. Instead of blasting a list of 10,000 accounts and hoping some percentage are having the right conversation this month, you monitor for the evidence that a buying conversation is already happening, then walk through the door that evidence opens.
The distinction sounds simple but the operational implications are enormous.
In traditional cold outbound, your sequence looks like this:
The underlying assumption is statistical. If you contact enough people who could buy, some percentage will buy. It is a numbers game. And it works — just inefficiently. Gartner found that the average enterprise buyer spends only 17% of their total buying journey talking to vendor sales reps. Interrupting them before they enter that journey means you are arriving at the party four hours early and sitting alone.
Signal-led selling flips the model:
The result is not just better reply rates. It is a fundamentally different sales motion. When someone is actively researching a category, they want to hear from vendors — they just want to hear from the right ones, at the right time, with the right framing. Signal-based selling puts you in that position.
Before we go into the full signal stack, it helps to understand the three categories that most signals fall into:
Behavioral signals — actions a person or account takes that indicate intent. Visiting your pricing page three times in a week. Downloading a competitor's case study. Job posting for a Head of RevOps. These are observable actions you can monitor and react to.
Contextual signals — external events that change an account's likelihood to buy. A new funding round. A leadership change (new CRO = new tools budget). An acquisition. Regulatory changes in their industry. These signals shift the buying context without requiring any direct action from the prospect.
Product signals — in-product behaviors from existing users, freemium users, or trial users that predict conversion or expansion. A free user inviting three colleagues. A team hitting feature limits repeatedly. A power user exporting data to a format your enterprise tier handles natively. This is the domain of product-led sales, and it is the highest-signal category you can access.
The best signal stacks use all three categories. Most startups start with just one. That is fine — the goal is to start.
Let me walk through each signal source in order of setup complexity and conversion impact. These are the actual signals I have seen work, validated against real pipeline data from startups in the $1M–$20M ARR range.
Your website is already collecting behavioral data. The question is whether you are doing anything with it beyond aggregate page view counts.
High-value pages to track:
The raw data comes from your analytics stack, but the hard part is resolving which company is visiting. Most B2B website visitors are anonymous. Tools like Clearbit Reveal, 6sense, Demandbase, and Warmly use IP-to-company resolution and identity graphs to de-anonymize traffic. You will typically identify 20–40% of your B2B traffic this way — the rest is irreducibly anonymous (home offices, VPNs, mobile).
The signal is not just the visit. It is the pattern. A single pricing page visit from a company is weak signal. Four visits across two weeks from three different people at the same company, including the security docs — that is a buying committee doing their homework.
G2, Capterra, TrustRadius — these are the places buyers go when they have already decided they have a problem and are researching solutions. Being researched on G2 is arguably the highest-intent signal that exists outside of someone filling out your contact form.
G2 sells Buyer Intent data through their G2 Market Intelligence product. If a company employee visits your G2 profile, reviews your competitors, or compares you in a G2 Grid comparison, you can receive that signal (with company-level resolution, not individual identity). This data is also surfaced through 6sense and Bombora as part of their intent networks.
The catch: this data is expensive at the account level, and it requires a G2 presence worth showing up on. If you have fewer than 10 reviews and no category presence, you will not generate much G2 intent signal yet. The work to build that presence pays dividends here beyond just review-site traffic.
Job postings are one of the most underrated and freely available signal sources in B2B sales. A company posting for a "Head of Customer Success Operations" is telegraphing that they are scaling their CS function — which might mean they need CS tooling. A company posting for a "Data Engineer with dbt experience" is telling you they are investing in their data stack.
The insight is that headcount decisions happen well before vendor decisions. If you sell to RevOps teams and you see a company post for their first RevOps hire, you have a 90-day window before that person is fully onboarded and starts evaluating tools — which is exactly when you want to be in their inbox.
Job posting signals worth tracking:
Tools like Clay, Prospeo, and LinkedIn Sales Navigator can automate job posting monitoring at scale.
What technology a company runs tells you a great deal about their maturity, budget, and buying behavior. Technographic data is gathered by tools that scan web properties, job postings, and procurement databases to infer what stack a company is using.
For example:
BuiltWith, Datanyze, HG Insights, and Clearbit all provide technographic data. Clay aggregates many of these sources in one enrichment workflow.
Tech install signals are particularly powerful for integration-led growth: if you build an integration with Tool X, anyone currently using Tool X becomes a warm prospect with a clear value prop entry point.
A funding announcement is not just a press release. It is a buying trigger. Newly funded companies have four behaviors that matter to vendors:
Crunchbase, PitchBook, and Harmonic all provide funding data. The key is speed — most vendors react to funding news within 48 hours, so personalized outreach in the first 6 hours is meaningfully differentiated.
A lightweight hack: set up Google Alerts for "[your ICP industry] funding" and "[city] Series A" to capture this manually when you are not yet ready to invest in full signal tooling.
When a champion from an existing customer leaves for a new company, two things happen: (1) your relationship at the old account needs nurturing, and (2) you have a warm intro at the new account. Champion movement is one of the highest-conversion signal types because it combines social proof (they already implemented and validated your product), familiarity (no cold start), and timing (new job = new tools evaluation).
UserGems specializes in tracking champion job changes and alerting your sales team. Clay can also build this workflow by enriching a list of past users with LinkedIn job change data.
The typical playbook: reach out to the champion in the first 30 days of their new role with a "congrats on the new position" message — no pitch, just relationship maintenance. Then follow up 60 days in when they are building their tech stack.
The signal tooling market has exploded in the last three years. Every week there is a new entrant claiming to replace your entire outbound motion. Here is an honest breakdown of when to use each major tool.
Clay is the most powerful signal enrichment and workflow tool available to startups. It is not an intent data provider — it is a platform that connects to 75+ data sources and lets you build enrichment workflows, scoring logic, and outreach triggers in a spreadsheet-like interface.
What Clay is excellent at:
What Clay is not:
Clay pricing starts at around $149/month but scales with usage credits. For most early-stage startups ($0–$3M ARR), the Growth plan at $349/month gives you enough credits to run meaningful signal workflows.
Common Room is purpose-built for tracking signals across community channels — Slack communities, Discord, GitHub, LinkedIn, Twitter/X, and product usage data. If your GTM has a community component (developer tools, open source, PLG), Common Room is the signal hub.
Where Common Room shines:
Use Common Room if: you are a developer tool, open-source company, or PLG product with community touchpoints. It overlaps significantly with Pocus and Koala for product signals but is stronger on the community dimension.
Warmly is the tool I recommend most often to early-stage founders because it solves a problem they already know they have: "I can see companies visiting my website but I don't know who they are or what I should do about it."
Warmly de-anonymizes B2B website traffic, shows you which pages an account visited, how long they spent, and which contacts from that account are in your CRM. It then lets you set up automated Slack alerts ("Acme Corp visited pricing 3 times today — their VP of Sales is John Smith at [email protected]") and even AI-powered live chat that can engage visitors in real time.
Warmly pricing: starts around $700/month for the base plan, which includes website de-anonymization and intent alerts. There is a free tier for basic identification.
The ROI math is usually straightforward: if your average deal size is $20K+ and Warmly surfaces one previously-invisible prospect per month that you close, it pays for itself by month two.
Pocus is built for product-led sales — specifically for companies where free, trial, or freemium users convert to paid. It aggregates in-product usage data and surfaces "product qualified accounts" (PQAs) to your sales team with clear context on what the account has done, what limits they are hitting, and who the power users are.
The core Pocus workflow:
Pocus is most valuable for companies with $2M+ ARR and an established PLG motion. At earlier stages, you can approximate this with Segment + a simple Slack webhook before investing in Pocus.
Koala is Pocus's scrappier, more affordable sibling. It is built specifically for the early-stage PLG company that wants product signal routing without the enterprise pricing and implementation overhead of Pocus.
Koala installs as a JavaScript snippet, integrates with your auth system, and immediately starts showing you which users and accounts are active, what they are doing, and which ones meet your PQL criteria. The interface is clean and built for AEs, not data teams.
Koala pricing is more startup-friendly — the Growth plan runs around $500/month. If you have a PLG motion and less than $5M ARR, start with Koala and graduate to Pocus when the complexity justifies it.
Here is how I think about stack selection based on stage:
| Stage | Primary Tool | Add Next |
|---|---|---|
| Pre-revenue / Seed | Clay (free tier) + Warmly (free tier) | Manual job posting monitoring |
| $500K–$2M ARR | Clay Growth + Warmly base + Koala Growth | G2 Buyer Intent if G2 presence exists |
| $2M–$10M ARR | Full Clay + Warmly + Pocus + Common Room | Bombora or 6sense for third-party intent |
| $10M+ ARR | Full stack above + 6sense or Demandbase | Custom data warehouse integration |
The mistake most startups make is buying too much too early. A $150/month Clay subscription and manual Warmly alerts will beat a $50K/year intent data contract if you do not yet have the operational processes to act on signals quickly. Buy signal tooling in proportion to your ability to respond to what it surfaces.
Signal scoring is the practice of assigning numerical weights to different signals, then aggregating them into a single account score that determines when and how aggressively you pursue an account. This sounds like something that requires a data scientist. It does not. It requires clear thinking and a spreadsheet.
Start with three dimensions:
Fit score (0–100): Does this account match your ICP? This is static, based on firmographic data.
Intent score (0–100): Is this account showing buying signals right now? This is dynamic, changes weekly.
Engagement score (0–100): Has this account interacted with you before?
Account Priority Score = (Fit × 0.3) + (Intent × 0.5) + (Engagement × 0.2)Intent gets the highest weight because it is time-sensitive. A perfect-fit account with no signals can wait. A medium-fit account with strong signals should be contacted today.
Score thresholds:
If you are using Clay as your signal aggregation layer, here is the basic logic:
// Clay Table: Account Scoring
// Columns: account_id, fit_score, intent_score, engagement_score, priority_score
// Step 1: Pull firmographic data (Clearbit, Apollo)
fit_score = 0
if industry IN target_industries: fit_score += 20
if employee_count BETWEEN 50 AND 500: fit_score += 20
if hq_country IN ["US", "UK", "CA"]: fit_score += 10
if tech_stack CONTAINS ["Salesforce", "HubSpot"]: fit_score += 20
if funding_stage IN ["Series A", "Series B"]: fit_score += 15
// cap at 100
// Step 2: Pull intent signals (Warmly + G2 + job postings)
intent_score = 0
if warmly_pricing_visits >= 2 IN last_14_days: intent_score += 25
if g2_profile_view IN last_30_days: intent_score += 30
if job_posting_for_buyer_role IN last_60_days: intent_score += 25
if funding_announced IN last_60_days: intent_score += 20
// cap at 100
// Step 3: Pull engagement data (CRM + email tool)
engagement_score = 0
if crm_status == "free_user": engagement_score += 50
if last_email_reply IN last_90_days: engagement_score += 30
if webinar_attended: engagement_score += 25
// cap at 100
// Step 4: Calculate priority score
priority_score = (fit_score * 0.3) + (intent_score * 0.5) + (engagement_score * 0.2)
// Step 5: Route to sequence based on tier
if priority_score >= 75: trigger_tier1_sequence()
elif priority_score >= 50: trigger_tier2_sequence()
elif priority_score >= 25: add_to_nurture_sequence()You can replicate this exact logic in Clay using formula columns, conditional enrichment steps, and a Zapier or Make integration to push high-scoring accounts into your CRM or sequencing tool. No data team required — just a few hours of setup and a willingness to refine the weights based on what you observe closing.
The weights I listed above are starting points. After three months, look at your closed-won data and adjust: which signals appeared most frequently in accounts that converted? Increase those weights. Which signals appeared equally in closed-lost? Decrease them or remove them.
A signal without a response is just noise. The entire point of building a signal stack is to change the timing and context of your outreach. Here is how to operationalize the signal → sequence connection for each intent tier.
When an account crosses into Tier 1 — especially if they visited your pricing page multiple times, downloaded a case study, and have an active job posting for your buyer persona — you want a human to reach out, fast, with the signal referenced directly.
The signal-led first touch:
Subject line: Saw [Company] is evaluating [category] tools
Hi [Name],
Noticed [Company] has been looking at [Your Product] — specifically the [feature/pricing/integration] pages. Timing feels relevant: I also saw you're hiring a [job title], which usually means [pain point you solve] is becoming a real project.
Happy to show you how [similar company] used [Your Product] to [specific outcome]. 20 minutes?
[Your name]
This email is short, specific, and non-creepy about the signal. "I noticed you've been looking at us" is not surveillance — it is attentiveness. Buyers who are actively evaluating expect vendors to reach out. The job posting mention shows you did homework without being intrusive.
The sequence for Tier 1:
Five touches over 12 days. Tight, respectful, signal-informed. Compare this to the standard 12-touch, 28-day cold sequences most teams run — the signal-led version has more relevance and less friction.
Tier 2 accounts are showing some intent but not at peak urgency. Maybe they visited your pricing page once, or you saw a G2 profile view without any job posting signal. These accounts go into a semi-personalized sequence that runs longer and is less aggressive.
Tier 2 email structure:
The key difference: Tier 2 sequences should add value before they ask for time. Because intent is lower, you need to earn the conversation by demonstrating you understand the problem before you pitch the solution.
Tier 3 accounts are ICP-fit but not showing active buying signals. They go into a long-running educational nurture sequence — monthly or bi-monthly touches with high-value content, no asks, designed to be there when intent eventually develops.
This is where your growth metrics content, benchmark reports, and industry insight pieces earn their keep. The goal is to be the most helpful brand in the category so that when intent spikes, your name is already top of mind.
The plumbing for this looks like:
Warmly/Clay [Signal]
→ Scores account in Google Sheets / Clay table
→ If score >= 75: push to Salesforce with "Tier 1" flag + Slack alert to AE
→ If score >= 50: push to Smartlead/Apollo as Tier 2 sequence
→ If score >= 25: push to HubSpot nurture workflowZapier, Make, or Clay's native integrations handle most of this without custom engineering. The total setup time for a basic version of this system is two to three days for someone non-technical.
Let me walk through how specific companies — some that I have worked with or observed closely — have used signal-based selling to dramatically improve their sales velocity.
A developer-focused API startup I advised was struggling with pipeline visibility. Their product had 4,200 GitHub stars and a free tier with 1,800 registered developers. The problem: they had no idea which of those developers worked at companies worth pursuing, and their sales team was basically doing cold outbound to a separate list while ignoring 1,800 warm accounts.
We built a simple signal workflow:
The result: 312 accounts met their ICP criteria. Of those, 47 had three or more employees active in the product. Those 47 accounts got a personalized outreach sequence from the founder. In 90 days, 12 converted to paid enterprise contracts averaging $28K ARR. That is $336K ARR from a list of 47 companies — a 25.5% conversion rate, compared to their cold outbound conversion rate of 1.8%.
The variable was not the copy. It was not even the relationship — these were not warm referrals. It was the timing and the context. The outreach led with usage data: "I noticed your team has been using [product] for [X] months — saw [specific usage pattern]. We work with teams like yours on [use case]."
A $4M ARR B2B SaaS company (project management category) had a generous free tier with 12,000 active free teams. Their sales team of three AEs was overwhelmed by inbound demo requests from small accounts while ignoring the more valuable free teams showing expansion signals.
After implementing Pocus with three PQA criteria (5+ members, 3+ projects, used integrations feature), they identified 340 accounts as high-priority from their free tier. They routed those to AEs with full context on what each account had done.
The outcome: 68 of those 340 accounts converted to paid plans within 60 days. Average ACV was $4,800. That is $326K ARR from accounts they already had — from users who had already validated the product's value. Their time-to-close was 14 days on average for PQL accounts, compared to 47 days for inbound demo requests.
A fintech infrastructure company targeting Series A and Series B companies built a signal workflow around funding announcements. Every Monday morning, a Clay workflow pulled the previous week's funding announcements from Crunchbase for companies in their ICP, enriched with contact data for CFO and VP of Engineering, and pushed into a six-touch outreach sequence with personalization tokens referencing the specific funding round.
The subject line formula: Congrats on the [Series X] — question about [specific pain]
Their reply rate on this sequence: 14.3%. Industry average cold outbound reply rate: 2–3%. The delta came entirely from timing — reaching a newly-funded team in their first two weeks, when they are actively making infrastructure and tooling decisions, is fundamentally different from reaching them six months later when those decisions are locked in.
Most discussions of signal-based selling focus on acquisition. That is a mistake. The same signal-reading muscle applies to retention — and in many cases the revenue impact of catching a churning account early is larger than the impact of closing a new one.
Declining product engagement is the most reliable early indicator of churn risk. The specific metrics depend on your product, but the pattern is universal: usage drops before a customer cancels. If a team was logging in five days a week and now logs in once a week, that is a signal — not a certainty, but a signal worth investigating.
Define your engagement baseline for healthy accounts, then set alerts for accounts that drop below it. Most product analytics tools (Amplitude, Mixpanel, Heap) can do this natively. A simple Slack alert when an account's weekly active user count drops 40% week-over-week is a one-hour setup that can save five-figure contracts.
Support ticket patterns are underused churn signals. An account that opens three tickets in a week is either deeply engaged or deeply frustrated — the content of the tickets distinguishes the two. An account that has not opened a ticket in 90 days but previously averaged one per month has either figured everything out or stopped using the product.
Data export activity is a red flag signal. When a customer exports their data in bulk — especially in formats that suggest migration (CSV exports of their full dataset, API calls that look like data dumps) — they may be preparing to leave. This is worth a proactive check-in.
Payment behavior changes are obvious but often ignored until it is too late. A card that starts failing, a billing contact change, or a downgrade request from annual to monthly are all signals that the account is reviewing its commitment. These should trigger immediate customer success outreach, not automated dunning emails.
Champion departure is the highest-risk churn signal. When your primary champion leaves the company, your retention probability drops significantly. Research from Gainsight suggests that accounts where the primary champion departs have 3x the churn rate in the following 12 months compared to accounts with stable champions. Track champion job changes as both an acquisition signal (opportunity at their new company) and a retention alert (risk at the current account).
The same scoring logic from acquisition applies to retention:
Churn Risk Score =
(1 - engagement_trend_30d) × 40 // declining engagement = higher risk
+ support_friction_score × 20 // high friction tickets = higher risk
+ champion_stability × 20 // champion departed = higher risk
+ payment_health × 20 // payment issues = higher risk
// Thresholds:
// Score > 60: Immediate CSM outreach + executive sponsor engagement
// Score 40-60: CSM check-in within 48 hours
// Score < 40: Normal health monitoringThis is rough, but even a rough churn signal model catches accounts earlier than waiting for them to email you cancellation notice. Most churn is predictable 60–90 days before it happens if you are reading the right signals.
The signal-based selling ecosystem sits in uncomfortable legal territory in 2026. GDPR has been enforced aggressively since 2023, with multi-million-euro fines landing on US companies doing business in Europe. CCPA has teeth in California. Canada's PIPEDA, Brazil's LGPD, and India's PDPB add additional layers of complexity.
The good news: building a privacy-respecting signal stack is not only possible — it often produces better results because you are forced to focus on higher-quality, more consensual signals.
Generally safe:
Gray area:
Generally not permissible:
For EU prospects, your signal stack should lean heavily on:
First-party data — signals from your own product, your own website (with proper cookie consent), your own email campaigns. This is the cleanest, most legally defensible signal source.
Aggregated intent data — Bombora's intent data is aggregated at the company level before delivery, making it GDPR-compliant. G2 Buyer Intent similarly provides company-level (not individual-level) signals. These are safer than individual behavioral tracking.
Public signals — funding announcements, job postings, LinkedIn posts, press releases. Public information about companies is generally outside the scope of GDPR's personal data protections (though personal data embedded in those signals, like an individual's name and employer, still has some protection).
Contextual signals — industry events, regulatory changes, technology shifts that affect a company's buying context. No personal data involved.
The cleanest privacy approach is also, arguably, the best sales approach: earn the right to talk to people before you reach out.
Content marketing, community building, conference presence — these create inbound intent signals (people self-selecting to engage with you) that are inherently consensual. When someone downloads your benchmark report and gives you their email, they are telling you they want to hear from you. That is a higher-quality signal than a third-party behavioral profile, and it is unambiguously compliant.
The startups I see building sustainable growth channels are the ones treating privacy as a design constraint that forces better marketing, not a legal box to check.
Every startup faces this decision at some point: do you buy an intent data platform, or do you build your own signal collection and scoring infrastructure?
The short answer for most startups: buy first, build selectively later.
Speed is the primary argument. Setting up Clay + Warmly + Koala takes a few days and immediately produces actionable signals. Building equivalent infrastructure in-house requires a data engineer, a product analytics setup, a web event collection system, and weeks of iteration before you see anything useful.
At early stages, your advantage is speed and learning, not infrastructure sophistication. Buying signal tooling lets you learn which signals actually predict conversion for your specific product and customer base. Once you know that, you can decide whether to build custom infrastructure for those specific signals.
The customer acquisition cost of building vs. buying often favors buying until you hit meaningful scale. A $500/month Clay subscription versus a three-month data engineering project to build equivalent enrichment logic — the math is not close at seed or Series A.
At scale ($10M+ ARR), the limitations of third-party signal tools become real constraints:
Data latency — most intent data providers update weekly. If you are in a high-velocity sales environment, week-old signals lose value.
Signal coverage — third-party tools cannot see inside your product. Your own event stream is always the richest, most accurate signal source for product-led motions.
Cost at scale — Bombora or 6sense enterprise contracts run $100K–$500K per year. At $20M ARR, the ROI math justifies building selective custom infrastructure for your highest-value signals.
Competitive differentiation — if your signal stack is built on the same tools as every other company in your category, you will get to the same accounts at roughly the same time. Custom signals — proprietary data sources, unique aggregation approaches — create timing advantages that are harder to replicate.
The realistic path for a $2M–$15M ARR company:
The first-party layer — your own product events, your own website analytics, your own email engagement — is always worth building directly because no vendor has access to it. Everything else can be bought.
One more dimension of the build/buy decision: not everything should be automated. Some signals warrant human judgment:
Automate: enrichment, scoring, routing to sequences, Slack alerts for Tier 2 and 3 accounts, nurture email sends.
Keep human: Tier 1 account outreach (personalized emails from a real person convert better than automated), executive sponsor engagement for at-risk accounts, champion relationship management, deal negotiation.
The ROI of automation in signal-based selling comes from efficiency at scale — automating the tedious parts (list building, enrichment, sequencing) so that humans can focus on the high-leverage parts (genuine relationship building with high-intent accounts).
Before investing in any signal infrastructure, define your measurement framework:
Leading indicators (measure weekly):
Lagging indicators (measure monthly/quarterly):
In every team I have seen implement signal-based selling properly, three metrics improve immediately: reply rate (3–5x), time-to-close (30–50% faster), and AE satisfaction (not wasting time on unqualified accounts). The fourth metric — win rate — typically improves over 3–6 months as the team learns to read signals accurately and refine their thresholds.
The first 100 customers for most B2B startups come from relationships and founder network. The next 400 come from some combination of inbound, paid, and outbound. Building your signal stack in the $1M–$5M ARR phase sets you up to scale beyond that without linearly scaling your sales headcount.
What is the minimum budget to start signal-based selling?
Genuinely zero, if you are willing to do things manually. Start by monitoring your website analytics for repeat visitors (Google Analytics is free), set up Google Alerts for funding announcements and job postings in your ICP, and track your G2 profile views (free on G2). Then build a simple spreadsheet to log and score what you find. The manual version is slower but teaches you which signals matter before you invest in tooling. Once you are spending more than four hours a week on this manually, Clay's free tier ($0) and Warmly's free tier are your natural next steps.
How is signal-based selling different from account-based marketing (ABM)?
ABM is a targeting strategy — selecting a specific list of accounts and running coordinated marketing and sales against them. Signal-based selling is a timing strategy — reaching accounts when intent peaks, regardless of when you initially selected them. They work well together: use ABM to define your target account list, use signals to determine when to activate against each account. ABM without signals often means spending budget on the right companies at the wrong time. Signals without ABM often means chasing intent at companies that are not actually a good fit.
Will prospects find it creepy if I reference signals in my outreach?
Context matters. Referencing a public job posting ("I saw you're hiring for Head of RevOps") is fine — that is a public signal. Referencing website visits requires more care: "I noticed your team has been looking at our pricing page" is acceptable and is a common B2B practice; "I can see you spent 4 minutes and 23 seconds on our security docs last Tuesday at 3pm from San Francisco" is too granular and will feel surveilled. The rule of thumb: reference signals at the company level, not the individual level. Lead with context, not surveillance.
How many signals do I need before reaching out to an account?
There is no universal answer, but my heuristic is: one strong signal (G2 profile view, champion job change, direct pricing page visit) justifies outreach. Two medium signals (job posting + funding announcement) justify outreach. A single weak signal (one page visit, one email open) does not justify interrupting someone — wait for corroborating evidence. The more signals you see from a single account in a short window, the more confident you can be that a buying conversation is happening internally.
What is the best first signal source to set up for a B2B SaaS startup?
Website intent signals via IP-to-company resolution. Install Warmly's free snippet, connect your CRM, and set up a Slack alert for pricing page visits. This alone will surface accounts you did not know were interested and give your sales team a reason to reach out that is 10x better than "you match our ICP." Do this before investing in any paid intent data. It takes two hours to set up and starts producing results immediately.
How do I handle signal data for European prospects under GDPR?
Focus on company-level, aggregated signals (Bombora, G2 intent) rather than individual behavioral tracking. For your own website traffic, use a GDPR-compliant analytics setup with proper cookie consent (Plausible or Fathom are good alternatives to GA4 for EU compliance). For product signals, ensure your terms of service clearly disclose that usage data is used for account management and sales purposes — this typically constitutes legitimate interest under GDPR for B2B contexts. When in doubt, consult a privacy lawyer before scaling your signal infrastructure into European markets.
My sales cycle is 6-12 months. Do signals still help?
Yes, but the signal use case shifts. In long-cycle enterprise sales, signals help you: (1) identify when an account first enters a buying cycle (job posting for a relevant role, new executive hire) so you can start relationship-building early, (2) prioritize which accounts in your existing pipeline are accelerating vs. stalling (engagement signals from multiple stakeholders = deal is moving), and (3) protect against sudden churn risk (champion departure, declining engagement). For long-cycle sales, signals are less about first-touch timing and more about orchestrating the right touches throughout a multi-month relationship.
Can a solo founder implement signal-based selling without a sales team?
Absolutely — in fact, solo founders often get more out of signal tooling because they can act on signals immediately without internal routing friction. The practical setup for a solo founder: Warmly free tier for website signals, Clay free tier for enrichment, a simple Google Sheets scoring model, and manual outreach from a personal email. Budget two hours per week to review signals and send 10–15 personalized emails. This beats spending 20 hours on cold list building and sending 200 untargeted emails. Quality over quantity is the signal-based selling philosophy, and it suits the solo founder's time constraints well.
Enterprise buyers want to try before they talk to sales. Here's how Notion, Figma, and Vercel built self-serve pipelines to six-figure contracts — and how your startup can too.
How reverse trials — giving users full product access before downgrading — convert 2-3x better than freemium. The complete playbook with case studies from Ahrefs, Loom, and Calendly.
Revenue Operations is the fastest-growing ops role in SaaS — and startups that adopt it early grow 19% faster. The complete RevOps playbook for teams under 50 people.