Every hand-raise, worked the same day.

Inbound, step by step: notice every signal of interest, qualify and route it, respond fast, recover the demand that slipped between systems, and nurture the ones who are not ready yet.

23 skills, curated by hand.

01 · Capture

Notice every hand-raise.

Demo requests, website visits, post engagement, connection requests, DMs, profile views, creator posts and ad clicks, each turned into a researched lead instead of a notification.

Signals0

Ariel Cohen

Founding Growth Engineer

Handle a demo request

Use this skill when someone requests a demo through your website — a "Book a demo" form, a webhook carrying little more than a work email — and the question is what happens in the next sixty seconds. Enriches the person and company, decides fit and buyer persona separately, and routes the request down one of three paths: the qualified hand-raise that gets a booking email, the right company with the wrong person, and the account that should be sent to a free trial rather than a calendar. Covers inbound demo requests, form-fill routing, hand-raise qualification, MQL hygiene, and self-serve versus sales-assisted triage.

Signals29

Ido Goldberg

Co-Founder & CPO

Visitor radar

Acts on content or website engagement from prospects. Qualifies the person, identifies the engagement hook, and drafts contextual follow-up based on their interest.

Signals27

Ariel Cohen

Founding Growth Engineer

Handle LinkedIn post engagement signal

Use this skill when monitoring comments and reactions on a team member's LinkedIn posts. Comments get the full treatment — ICP + persona gating, CRM and account-memory logging, lead scoring, and a high-value path to connection requests and Slack alerts — while lone reactions are logged as a light touch unless the account is top-tier or a repeat engager. Repeat engagers escalate to high intent after an active-buyer check, with a personalized multi-channel draft queued for review.

Signals29

Ido Goldberg

Co-Founder & CPO

Post radar

Acts on engagement with monitored LinkedIn profiles. Qualifies commenters or reactors, checks fit, and drafts contextual follow-up tied to the actual post.

Signals1

Ariel Cohen

Founding Growth Engineer

Handle LinkedIn connection request signal

Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through dedup / internal / relationship / ICP checks, attaches the signal to the CRM, and scores it with active-signal overrides: a decision maker at a serious company is MQL-eligible on this lone signal, a weak persona caps at the awareness tier, and a request from a closed-lost account is treated as a reactivation candidate rather than ignored. Every ICP-relevant outcome posts to a visibility channel; replies and accepts stay human. It never sends outreach.

Signals27

Ariel Cohen

Founding Growth Engineer

LinkedIn DM signal classifier

Use this skill to scan a team member's LinkedIn DMs daily and turn conversations into routed signals. It classifies each chat into a bucket (customer support, commercial, pipeline, re-engagement, prospect, partner, VC, community, and more), updates account memory and the CRM, scores qualified signals and routes them to your MQL channel, and closes every scored signal with a suggested next move — a drafted reply for the thread owner or an approval-queued sequence for the rest of the buying committee. It never auto-sends outreach.

Signals39

Ariel Cohen

Founding Growth Engineer

Handle LinkedIn profile view signal

Use this skill when a profile-view webhook (e.g. LeadShark) fires for a new view on a team member's LinkedIn profile. It resolves the viewer's identity and company, applies dedup, internal, relationship, and ICP gates, and routes qualified viewers into the MQL pipeline — treating a profile view exactly like a website visit. The CRM is never polluted: only fully resolved, ICP-matched viewers reach a CRM write.

Signals24

Ariel Cohen

Founding Growth Engineer

Influencer post engager capture

Use this skill when a tracked influencer publishes a LinkedIn post focused on your product (sponsored, review, or organic mention) and you want to capture the engagers as leads. It verifies the post is genuinely about you, scrapes the full engager list, filters to ICP-fit companies and buyer personas, runs lead scoring, and posts per-lead alerts plus a reconciled digest. Detection and scoring only — no outreach.

Signals0

Brianne Thomas

VP Marketing at Elastic Path

LinkedIn Ads CTR signal

Use this skill to turn LinkedIn Ads engagement into prioritized, pre-drafted outbound. Runs daily to pull LinkedIn Ads analytics, find the companies clicking your ads above a CTR threshold, suppress customers/open-deals/recently-touched accounts, and draft outreach informed by whichever ad themes are landing right now — all saved as drafts for human review, never sent automatically.

02 · Qualify and route

Get it to the right person, fast.

Sort each lead by what kind of hand-raise it is, fill in what the form left out, score against the ICP, then route with assignment rules and a speed-to-lead target everyone can see.

Signals30

Alex Vacca

Founder & CEO @ Frontal

Inbound triggers

Use this skill when building inbound follow-up sequences, categorizing marketing leads, or prioritizing inbound response. Thirty inbound premises from Flip The Script — content and events, product interest, social and intent, sponsored influencers — plus the inbound response framework and priority order.

RevOps24

Rutger Katz

Founder @ Neon Triforce — AI-Ready Revenue Systems

Choose an enrichment provider and build a waterfall

Use this skill when inbound leads arrive incomplete (missing company size, industry, revenue), the TAM list lacks data for scoring, or the CRM cannot route and segment without enrichment. Maps coverage gaps, compares single-source and waterfall provider strategies, and builds an integration roadmap with cost guardrails and quality gates. Produces a provider recommendation matrix, a waterfall architecture, and a go or no-go checklist. Rule: no single provider has full coverage; a waterfall across two or more providers in sequence beats any one source on match rate. Trigger phrases: data enrichment, leads come in with no company info, enrichment coverage, firmographic data, which enrichment tool, data freshness.

RevOps1

Udi Cohen

Director of Revenue Operations

ICP score and route

Score any lead or account against your ICP criteria, verify key contacts via Lusha, and return a routing recommendation — AE, SDR, or nurture — with a confidence level and the specific data points that drove the decision. Runs on a single lead or across a full list in one pass. Requires a Lusha connection.

RevOps25

Rutger Katz

Founder @ Neon Triforce — AI-Ready Revenue Systems

Lead routing

Lead routing strategy, assignment logic, round-robin patterns, territory design, speed-to-lead SLA frameworks, and routing automation for B2B revenue teams. Use when the user mentions lead routing, lead assignment, round-robin, territory assignment, lead distribution, speed-to-lead, lead SLA, lead queue, routing rules, routing logic, account-based routing, geographic routing, skills-based routing, load balancing, lead handoff, inbound lead routing, outbound lead routing, routing tools (LeanData, Chili Piper, Default), or lead cherry-picking. Also trigger on 'leads aren't getting to the right rep,' 'our routing is broken,' 'leads sit in a queue,' 'reps cherry-pick,' 'speed-to-lead is too slow,' or 'we need to redesign territories.' BOUNDARY: Covers routing STRATEGY and LOGIC (CRM-agnostic). For CRM-specific implementation, see revops-hubspot or revops-salesforce. For enrichment that feeds routing, see data-enrichment. For lead scoring, see marketing-operations.

RevOps0

Rutger Katz

Founder @ Neon Triforce — AI-Ready Revenue Systems

Marketing operations

Marketing operations for B2B revenue teams: lead scoring, attribution, campaign tracking, and handoff protocols. Use when the user mentions marketing operations, marops, lead scoring, MQL definition, MQL to SQL handoff, lead routing, attribution modeling, multi-touch attribution, W-shaped attribution, marketing sourced pipeline, campaign operations, UTM taxonomy, demand gen ops, channel mix, marketing SLA, speed to lead, ICP fit scoring, SPICED lead scoring, ICP fit matrix, selection fit, urgency fit, qualification tier scoring, T1 T2 T3 leads, or ICP fit scoring. Also trigger when someone says 'sales says our leads are garbage' or 'we can't attribute revenue to campaigns.' BOUNDARY: Covers marketing OPERATIONS (lead management, attribution, campaign ops). For HubSpot, see revops-hubspot. For funnel math, see revops-metrics. For ICP BUILDING methodology (GAP method, customer interviews), see icp-builder.

Events0

Gerrit Kesten

Co-Founder, job.rocks

Webinar to qualified pipeline

Use this skill after a B2B webinar has registrations or engagement data but before treating every registrant as a sales lead. Produces reconciled lifecycle states, fit and intent scores, a prioritised sales-review queue, segment-specific follow-up, and a measurable handoff from webinar registration to qualified pipeline and booked meetings.

03 · Respond

Answer fast, and walk in prepared.

Read what each reply actually means, ignore the auto-replies, get the meeting booked at a good time, and brief yourself before the first call.

Outreach35

Ido Goldberg

Co-Founder & CPO

Handle reply

Processes inbound replies to outbound sequences. Classifies intent, drafts the right response or stop action, and updates CRM and Swan state without auto-sending.

Outreach2

Lucas Godtfredsen

Founder, GTM Now

An auto-reply is not a reply

Use this skill when classifying inbound responses to outbound — out-of-office, vacation and parental-leave auto-responders, delivery notices, and other machine-generated mail that looks like engagement. Produces a triage decision that keeps the sequence alive, keeps the metrics clean, and reschedules the next touch to when the human is actually back.

Sales0

Nicolas Fry

Founder, TurboDocx

Meeting slot picker

Use this skill when the user hands over someone else's booking link or scheduling link and wants the meeting placed well, not just placed. Reads the user's calendar for the window, classifies the meeting as revenue-facing or internal, and picks the slot that serves it: revenue conversations land where the prospect, customer, partner or investor has runway (first slot after their lunch, first hour of their day), internal and low-stakes meetings get clustered against existing commitments so the longest free block survives. Produces a booked slot with a one-line reason, the day's resulting meeting count, and a drafted confirmation message held for approval. Triggers: "book time with her", "grab time on my calendar", "here's his booking link", "what time should I take this call", "find a slot that works for both sides", "book Monday afternoon with the prospect", or a pasted booking page URL with no other instruction. Different from setting up your own booking links or triaging inbound demo requests: this is the user booking onto a counterparty's page.

Sales0

Nylan Richard

AI Expert in Residence @ FullEnrich

Pre-meeting briefing

Use this skill when the user has an upcoming meeting and wants a comprehensive brief on the person they're meeting. Acts as a senior meeting strategist: pulls rich profile data (work history, education, skills) and company context from FullEnrich, supplements with web search for fresh signals, and delivers a structured brief with expert talking points, suggested questions, and tactical advice on how to run the meeting. Triggers on: "prep my meeting", "I have a call with", "brief me on", "who is [name]", "meeting prep", or any request to research a person before a meeting.

04 · Recover

Catch the demand that leaked.

Form fills that never booked, meetings with no follow-up, and leads that went dark after the handover.

RevOps0

Eliezer Cohen

Head of Global Sales & Partnerships, GoPerfect

Leaked demand recovery

Use this skill when demand may have leaked between systems: a chat or form lead who never completed a booking, a demo request with no meeting, a call held with no follow-up sent, an inbound reply never answered, a trial that ended quietly, a deal closed lost on a blocker that has since changed. Produces a list of confirmed drops with the evidence attached and one drafted recovery message each, queued for a human to send. Fires on "did they ever book", "who fell through the cracks", "what did we drop", "who never got a follow-up", "unworked inbound", "leads that went nowhere", "recover lost inbound", and before any re-engagement send.

RevOps23

Rutger Katz

Founder @ Neon Triforce — AI-Ready Revenue Systems

Design revenue handoffs

Use this skill when revenue leaks between teams: leads go dark after handover to sales, promised commitments disappear after signature, expansion signals stay invisible, CS never learns what sales committed. Designs handoff protocols across the full revenue bow-tie (marketing to sales, sales to customer, customer to expansion) with speed-to-lead SLAs, context-packet architecture, ownership models, and leading indicators of failure. Produces handoff playbooks per transition, context templates, SLAs with measurement dashboards, and detection rules for leaking revenue. Rule: handoffs are where revenue leaks. Trigger phrases: leads fall through the cracks, closed-won handoff, CS-to-sales handback, speed-to-lead, SLA between teams, nobody owns expansion.

05 · Nurture

Keep the not-yet-ready warm.

Flows for people who already know you, and trials that end in a decision instead of drifting.

RevOps0

Tanyo Gochev

Co-Founder & Head of GTM, The Demand Department

Email sequence

Use this skill when designing or fixing an automated multi-email flow for people who already know you — welcome and onboarding series, lead nurture, trial conversion, re-engagement, post-purchase, or any behaviour-triggered drip. Produces the sequence spec: entry trigger, touch count, timing, per-email job, exit conditions, and what to measure. Trigger phrasings: "email sequence", "drip campaign", "nurture flow", "welcome series", "onboarding emails", "re-engagement emails", "lifecycle emails", "what emails should we send", "our nurture isn't converting".

Deals1

Rutger Katz

Founder @ Neon Triforce — AI-Ready Revenue Systems

Trials and POCs that convert

Design and run trials, POCs, and pilots that end in a decision instead of a drift. Use when trials go nowhere, prospects want to test first, or evaluations expire without a verdict. Picks the right evaluation motion, contracts success criteria before granting access, defines and instruments activation, and runs the conversion clock. Produces an evaluation design with success criteria, an activation definition, and a decision-forcing timeline. Rule: a POC is a proof vehicle, never a qualification substitute; granting one to an unqualified deal is how free consulting projects start. Trigger phrases: trial conversion, proof of concept, pilot, trial-to-paid, our trials go nowhere, evaluation plan.