Developer & Agent Intent IntelligenceTeardown of Reo.Dev

Developers evaluate by doing. Now their agents do too.

Developers are the new buyers. They evaluate by doing - and now by sending their agents to do it for them - weeks before a buyer ever appears in your CRM. Traditional intent data sees none of it. Plume clears the pipeline fog.

An independent glass-box re-imagining of Reo.Dev - with a live Forge DB demo below.

Open the live demo See how it works

Glass-box scoringAgent-native captureExecution-grade UX

Anonymous developer activity

ACAcme Corp94

HOHooli86

TETessellate81

WOWonka Labs73

STStark66

NONovaTech59

INInitech47

GLGlobex21

Named · scored · sales-ready

◂▸

FogClarity

Drag to clear the pipeline fog →

The developer funnel

From a star to a signed check - visibly

ExploringCool

Starred repo

npm install

Single docs visit

EvaluatingWarm

Repeat docs visits

Signed up

Opened an issue

BuildingHot

forge deploy

Multiple devs + CLI

Agent connected

DeployedCustomer

Production deploy

Sustained usage

Expansion docs

The pipeline

Scattered signals → one named, scored account

Ingestion

GitHub · npm · Docker · Docs · MCP

SIMULATED DATA

Identity

deterministic + probabilistic merge

LIVE IN THIS DEMO

Enrichment

firmographics · seniority

SIMULATED DATA

Scoring

type × intensity × recency

LIVE IN THIS DEMO

Activation

CRM · Slack · outreach

ROADMAP

Live engineidentity + scoring, running nowSimulated dataseed events, no real companyRoadmapconnectors + activation, not built

The next wave

The agents are evaluating you. The intent is real - the visibility isn't.

THEN

Developers leave trails

Commits, forks, npm installs, docs reads. Footprints you could see - if you stitched them together.

GitHubCLIDocs

NOW

Developers send agents

Cursor, Claude Code, Copilot query your docs, call your MCP tools, test workflows - and get stuck. The intent is buried in server logs you can't read. Plume's proposed MCP gateway would capture it - turning agent friction into a dual sales + product signal.

Agent queries MCP tool calls Friction loops

Gateway · roadmapAgent signals · simulatedScored by the real engine

Where this wins

Developer-intent-native is open white space

No fog about the fog

What's real here vs simulated

REAL - ENGINES

· Glass-box scoring: pure, tunable, replayable
· Identity resolution: deterministic + probabilistic merges, review band, Art. 17 erasure - enforced in code
· LLM outreach & Q&A via OpenRouter (labeled deterministic fallback without a key)

SIMULATED - THE WORLD

· Every company, developer, raw event and agent query (n = 12 accounts)
· The enrichment directory (names, roles, seniority)
· Precision/recall labels, fit scores and ACV bands - illustrative constants

ROADMAP - NOT BUILT

· Ingestion connectors (GitHub, npm, Docker, docs)
· The MCP gateway itself
· Enrichment providers & live CRM/Slack activation (payload preview only)

Full methodology on the about page.

Watch Acme Corp light up.

A live, glass-box workspace for a fictional database company - replay 14 days of developer & agent signals, tune the scoring model, and generate signal-anchored outreach.

Open the live demo