Skip to documentation

Connect your coding agent and find your first qualified person.

A complete first-run path for turning product context into an evidence-backed shortlist with your coding agent.

Before you start

  • A product sourceYour website is enough; docs or a README can add context.
  • A supported coding agentCurrent examples include Codex and Claude Code; see the developer reference for client-specific requirements.
  • A platform sessionSign in to LinkedIn, X, or Reddit in your browser only when research begins.

Complete the first run

01

Create a private Connection

Open Try LeadCue and copy the complete prompt generated for your coding agent.

02

Paste it into a fresh task

Your client installs or updates the LeadCue plugin, connects the private URL, and makes the first detectable MCP request. The page should stop showing “Waiting for your coding agent.”

03

Describe what you built

Share the source that explains the product best. LeadCue asks you to sign in only when the ICP and results become durable.

04

Review the proposed ICP

After lightweight supply exploration, confirm the real buyer, recent intent signals, exclusions, recency window, and evidence standard.

05

Verify the first saved result

Open the person, qualification reason, direct candidate-authored source, and any custom information you explicitly requested.

Confirm that it worked

Connection detected

The private Connection page records an MCP request, not merely a clipboard copy.

ICP reviewed

The saved ICP reflects the narrowest workable buyer and evidence rules for this batch.

Evidence opens directly

Every saved person links to their own qualifying standalone post.

Shortfalls stay honest

If supply is insufficient, the result reports the gap instead of weakening the ICP.

Connect when you are ready to use the live workflow.

The generated private prompt installs the current plugin and keeps the complete machine contract inside the client.

Connect LeadCue