Skip to content
signal/scout Open app
CLI-first social listening

Your feed got attention. Now find the people worth knowing.

Signal Scout turns LinkedIn engagement into a ranked, explainable follow-up list—fully driveable from the CLI and ready for deeper analysis.

No HarvestAPI account required for customers.

signal-scout — zsh

$ listen sync --since 30d

✓ 11 engagements normalized
✓ 7 people resolved · replay-safe
✓ sync_01K completed in 1.8s

$ listen analytics --segment ideal-client

7PEOPLE
4ICP MATCH
3HIGH INTENT

Next: listen engagers list --intent high

11

Engagements

Deterministic fake snapshot

7

People

Resolved across reactions and comments

4

ICP matches

Each score is explainable

3

High intent

Ready for thoughtful follow-up

A tighter daily loop

From noisy activity to a reasoned follow-up queue.

One surface for humans and scripts. Every answer can be traced, filtered, and exported.

  1. 01 / LISTEN

    Sync without babysitting

    Ingest recent engagement with replay-safe operations and a durable identifier you can poll or automate.

    listen sync --since 30d
  2. 02 / UNDERSTAND

    Know why they match

    Segment by role, company, and intent. Inspect the evidence behind every ideal-client score instead of trusting a mystery badge.

    listen icp explain person_42
  3. 03 / ACT

    Export the useful answer

    Send a redacted, analysis-ready snapshot to DuckDB or your own workflow. Sensitive fields stay opt-in.

    listen export --format parquet

Analytics that answers back

Ask the business question, not the dashboard question.

Count commenters from the last month. Segment them against your ideal-client profile. Trace every inclusion. Then export the same canonical snapshot to DuckDB.

-- analysis.sql

SELECT icp_match, count(*)
FROM read_parquet('engagers.parquet')
WHERE engaged_at > current_date - 30
AND engagement_type = 'comment'
GROUP BY icp_match;

icp_match
people
true
4

Headless by design

The API wrapper should remove work—not hide the answer.

Signal Scout keeps provider complexity behind a private service boundary while exposing a stable customer API and a complete CLI.

CapabilityBasic wrapperSignal Scout
Customer setup Provider account 2 product variables
Access Dashboard first Every feature in CLI + API
ICP scoring Opaque filter Evidence and explanations
Analytics Preset charts DuckDB-ready raw exports
Privacy Unclear defaults PII-redacted by default

Straight answers

Before you connect a feed.

Do customers need a HarvestAPI account?

No. HarvestAPI is private server infrastructure. A customer receives only SIGNAL_SCOUT_API_URL and SIGNAL_SCOUT_API_KEY, then uses the Signal Scout CLI or product API.

Is the live provider connected in this demo?

Yes. The hosted Signal Scout API is live. HarvestAPI remains private server infrastructure, and customers receive only Signal Scout credentials for the CLI and product API.

Can I use everything without a dashboard?

Yes. Sync, analytics, engager list and detail, ICP explanations, and exports are all CLI operations with JSON-friendly contracts.

Why DuckDB-ready exports?

You keep the freedom to ask new questions locally—such as commenters in the last month who match your ICP—without waiting for another dashboard widget.

Ready when the signal is

Start with the live API, not a provider account.