The GTM companion that verifies and remembers

Your list is full of buyers.
DevSignal tells you which are real,
and remembers what wins.

Paste a list or start from a repo. DevSignal verifies every company on real need, hands you the one move, and learns from every outcome, so your next call is on the account most likely to convert.

Built for founders and GTM teams at open-source dev-tool companies.

App, or an MCP server inClaude·Cursor·Windsurf·Any MCP client
agent's list
verified
filtered out
Georgia Tech
Coinbase
lodash
the community
Stripe
DevSignalverify · remember
Coinbasedata-intensive, fits
Stripereal B2B, fits
Georgia Techacademic
lodashOSS library
the communitygeneric term
2 of 5 are real buyers
Grounded inGitHub·Hacker News·Reddit·Hiring boards·Funding news·Code search
realneed graded
Fit scored from public technographic evidence, not category guesses
datedevery claim
Every time-sensitive fact carries when it happened, or we say nothing
rememberswhat converts
Learns from every won and lost outcome, pooled anonymously across customers
freeto start
No card. Use it as an app, or as an MCP server for your agent

How it works

From a noisy list to the one move, in three steps

01

Bring a list, or a repo

Paste companies, a CSV, or an Apollo/ZoomInfo/CRM export. Or drop a GitHub repo and DevSignal reads the real companies behind the stars. No CRM connection, no setup.

02

It verifies, grades, and dates

Every company checked for real, graded on real need from public evidence, with the one dated timing signal found or an honest nothing. Junk dropped with a cited reason.

03

Act, and it remembers

You get the verified buyers, the one move for each, and the message drafted. Mark what converts, and the next read is sharper.

Import & verify

Paste your list. See what is real before you spend a call.

Bring a scraped list, a CSV, or an Apollo/ZoomInfo/CRM export. DevSignal reads it, drops the junk (universities, OSS repos, no-fit companies) each with a cited reason, then grades who actually needs you and dates the timing signal. The receipt leads with what it killed, and the outreach you would have wasted.

Toggle to Contacts and the same flow re-verifies an exported contact list: buyer titles, company fit, and whether the email domain accepts mail.

import · 5 companiessample
→Georgia Techdropped
·academic institution, not a company
→lodashdropped
·OSS library, no company behind it
→the communitydropped
·generic term, cannot be qualified
→Coinbaseverified
·data-intensive, fits the ICP, funded Jun 4 2026
→Stripeverified
·processing scale creates a real lakehouse need
2 real buyers · 60% of the list was noise
The read

Every account, read for you. And the one move to make.

Open any account and DevSignal shows the read: why they fit with cited reasons, the score and exactly how it was computed, a dated activity timeline, and the play that worked for a similar company. Then the one move, with the message drafted and the warmest person to send it to.

A thin account gets an honest hold, not a fabricated draft. One click prints the whole thing as a one-pager.

read · LendingKartsample
→why they fitstrong fit
·B2B fintech, 1M+ loan disbursals, real data scale
why nowhiring data engineers
the movelead on lakehouse cost
reachwarmest engineer + draft
·the score, and exactly how it was computed
·a dated timeline, and a play that worked for a peer
GTM agent

Give it a GTM job. It runs verified tools and hands back a receipt.

Tell it what you want in plain words, or pick a saved job: vet a list, research an account, find buyers, re-verify your pipeline, position against a rival. It plans the steps, you confirm, then it runs the same verified engine.

It never free-roams. Every step is grounded, so a hallucinated name gets killed with a reason instead of landing in your pipeline.

agent · vet and rank a listsample
planverify → fit → signal → predict
→real buyers12 verified
·graded on real need, dated signal, conversion odds
→filtered out28 dropped
·9 no fit, 11 not a company, 8 academic or OSS
70% of the list would have been wasted outreach
Merge debt

See the backlog a dev-org is drowning in. Before you email them.

Point DevSignal at a prospect's public GitHub org and it quantifies the unmerged, unreviewed work: open PRs by age, time to first review, time to merge, and the stale dependabot and renovate PRs, foregrounded. Every number is dated and links to the GitHub query it came from.

Two tiers, always labelled. Measured, with real numbers from a real org, or Inferred, when public data cannot measure it. Never an estimate dressed up as a fact.

merge debt · example orgsample
→52 stale items to clearweek one
·37 bot PRs plus 15 PRs older than 90 days
open PRs84 human, 37 bot
time to first review3.4 days
open PRs / contributor3.8
measured from public GitHub, every figure sourced
Pilot ROI

Turn a pilot into a dollar figure a CFO signs.

Model engineer-hours saved, cost per merged ticket before versus after, monthly net saving, and the acceptance rate you have to clear to break even. Every intermediate number shows the arithmetic that produced it, including the AI inference cost.

Pure math, no fabricated numbers, and the breakeven point is drawn on a curve, not asserted. Share a scenario as a read-only link.

pilot · example orgsample
breakeven23.1% acceptance
→net saving at 55%+$14.4k / mo
·148 engineer-hours saved a month
cost / merged ticket$200 to $69.55
inference cost included, so the net is honest

The whole cockpit

Everything you need to run the motion, in one place

Contact re-verify

Re-check a CRM or Apollo export: which titles are not buyers, which companies do not fit, and which email domains accept mail. Honest about the ceiling, it confirms the domain, not a specific mailbox.

Pipeline dashboard

Your whole pipeline, honestly: fit mix, intent tiers, the funnel, recurring themes, contact reachability. It does not guess industry, revenue, or headcount.

GTM playbook

Diagnose your metrics (LTV:CAC, CAC payback, NRR, runway) with the classic traps flagged, plus a browsable library of GTM frameworks.

Customers & contacts

Your won customers and the ones named on your own site, plus one real, nameable contact per account. Never a fabricated stakeholder.

Competitor signals

Track a rival: who adopts their OSS, the comparison threads, the problem-space discussions, and how to position against them.

Signals feed

One compound row per account, ranked by conviction: the forks, the hiring, the competitor moves, and the public triggers, stacked with a plain why-now.

Chat over your pipeline

Ask who is warmest, what changed since last time, or how to approach an account. Answers cite the evidence, and threads persist.

Slack alerts

A daily Slack ping when a tracked account heats up or a new signal lands. The one integration that is live today.

The moat

It remembers what actually converts

Every won and lost outcome sharpens the next read, pooled and anonymised across customers. No public source has this. No stateless agent session can build it.

A bigger scraped database goes stale the day the data is wrong. A record of what actually closed only gets sharper.

It starts as an honest heuristic from fit and conviction, and turns into real rates once your outcomes fill the pool. It always shows the sample size behind the number.

conversion likelihoodsample
→likelihoodhigh
fitstrong
signalsfunded, hiring, launched
convictionhigh
·learned from real won and lost outcomes
·pooled across customers, never your company names
·honest heuristic until the pool fills, sample size always shown

For agents

Prefer to work in your agent?
It is also an MCP server.

The same verification engine installs as an MCP server, the standard way to give an AI agent new tools. Claude, Cursor, or any MCP client can call its six tools while it works, so it stops guessing and starts checking. And when an agent researches companies through your tools, that demand is yours to see, captured from your own key, never scraped. The engine and your keys stay on our side.

The six tools your agent gets

verify_companies
qualify_fit
detect_signal
find_buyers
read_repo
conversion_likelihood
Start free

How it works

1Paste one config block into your agent's MCP settings.
2Drop in your DevSignal key.
3Your agent calls the tools automatically as it works.
See the .mcp.json config

The whole install, one block:

{
  "mcpServers": {
    "devsignal": {
      "command": "node",
      "args": ["./devsignal/index.js"],
      "env": {
        "DEVSIGNAL_URL": "https://devsignal-rho.vercel.app",
        "MCP_API_KEY": "your-key"
      }
    }
  }
}
Public signals only, no contact scraping
Your prospect list stays yours
Bearer-key auth, no per-user session
Public signals only
Your list stays yours
App or any MCP agent
Free to start, no card

Stop guessing which buyers are real.

A GTM companion that knows your company, verifies every lead on real need, and remembers what wins. Free to start, as an app or an MCP server.

DevSignal

The GTM companion that verifies and remembers. Fit-graded, cited, dated.

Account
Start free
© 2026 DevSignal. Reads public signals only.App + MCP server