Distribution intelligence for founder-led B2B

Catch every signal.
Find the right conversation.

Catchment is a CRM with an opportunity inbox on the front. It watches the sources you authorize, ranks what changed, and shows you who to talk to next and why now — without handing over the judgment.

Become a design partner See the workspace

Evidence on every recommendation · human approval built in

app.catchment.crm/opportunitiessynced just now

Opportunity inbox

What to act on next

Ranked by evidence · consequential actions wait for a decision

Refresh

Only mineMin confidence 65%

01high · 91%

Northbank posted a Head of Partnerships role

score 88

Two authorized signals inside six days, and a second-degree path through Maya Chen — who replied to you in March.

4 evidence items · freshness 94%SnoozeApprove

02high · 86%

Tidewater closed a Series B

score 81

Funding signal matched to an account you already track. Theo Martin moved into the buying committee last quarter.

3 evidence items · freshness 88%SnoozeApprove

03medium · 71%

Basin Studio re-engaged after four quiet months

score 64

Newsletter click plus a return visit from a known identity. No open deal — this is worth one message, not a sequence.

2 evidence items · freshness 76%SnoozeApprove

3 of 34 open · sample data, real layout

the shortlist, before the day gets loud

The missing layer

A record of the past is not a plan for the week.

A traditional CRM remembers what your team typed in. Catchment keeps watch across the sources you choose and brings forward only what deserves a decision.

Sequence over search

The account arrives with its reason. You stop building lists and start reading a shortlist that already knows why now.

Evidence stays attached

Every recommendation keeps its sources and observation times, so you can disagree with it for a specific reason.

The payload is inspectable

What an agent is about to send is printed verbatim before it leaves the workspace. Nothing runs from a prompt you cannot read.

Outcomes feed the graph

Accepted, dismissed, closed — each decision updates the same graph the next recommendation reasons over.

One continuous workflow

From scattered signals to the right conversation.

Set the sources

Authorize the places worth listening to — CRM history, referrals, inbox activity, events, imported research, public company changes.

Read the shortlist

Identity, timing, relationship strength and past outcomes collapse into a ranked inbox with the evidence still attached.

Act with a record

Hand the work to a teammate or an agent. Ordinary updates move. Consequential actions stop and ask first.

delegate the work, keep the judgment

The workspace does not lie to you.

Ordinary updates move quickly. Sensitive actions stop and ask. Either way the request, the evidence, the decision and the outcome stay on the record.

Source on every signal

Observation time preserved

Agent identity attributed

Approval before anything leaves

Scoped, revocable keys

Decisions kept in the audit trail

Request · verbatimAPPROVAL REQUIRED

POST /api/v1/deals/dl_8241/stage
Authorization: Bearer ck_live_…
Idempotency-Key: 2026-08-27-northbank-01

{ "stageId": "closed_won" }

→ 409 approval_required
{
  "error":      "approval_required",
  "action":     "deal.close",
  "replayWith": "X-Catchment-Approval",
  "requestId":  "req_9f2c74…"
}

Nothing runs from a prompt you cannot read.

Agent-ready by design

One workspace for people and programs.

The same workspace is open to your team, your scripts and your assistants, with the guardrails in the platform rather than in a prompt.

Read the API reference

MCP tools available to assistants

crm_searchcrm_create_contactcrm_update_contactcrm_log_activitycrm_create_taskcrm_move_deal

Bearer

Scoped API keys

Every key is workspace-scoped and limited to the read and write scopes you grant, with rate limits and daily quotas per key.

Idempotency-Key

Safe retries

Mutations are idempotent per workspace. A retried write replays the original response instead of creating a second record.

X-Catchment-Approval

Approval gates

Consequential actions return 409 approval_required until a person signs off, then replay with the approval attached.

Webhooks

Push, not polling

Subscribe to record changes and pipeline movement, then drive downstream automation from the events you care about.

A different starting point

Your CRM records the past. Catchment finds the next move.

The workTraditional CRMCatchment

Find a relevant accountSearch, filters and list buildingSignals surface the account

Understand the timingResearch in another tabEvidence and rationale attached

Find a warm pathAsk around and rely on memoryRelationship paths stay visible

Choose the next actionCreate and maintain a taskA next step is recommended

Keep the system currentUpdate records after the workActions and outcomes update the graph

Built for relationship-led growth

Small teams with valuable conversations.

01Founder-led sales

Protect the conversations only you can have

See the small set of accounts, referrals and follow-ups that deserve founder attention this week.

02Partnerships

Find the warm path into the right ecosystem

Map introductions, shared history and timely company signals before starting a partner conversation.

03Expert teams

Turn reputation into a repeatable pipeline

Connect referrals, events, content engagement and client history without adding CRM administration.

Questions worth asking early

What Catchment is, and is not.

Straight answers about scope, migration, sources and the limits we put on automated work.

Is Catchment a CRM, or something on top of one?

It is a CRM. Contacts, companies, deals, pipelines, tasks and activity all live in Catchment, and the opportunity inbox reasons over that same graph. There is no second system to keep in sync.

Can I migrate from the CRM we use today?

Yes. Bring contacts in by CSV with column mapping and duplicate detection, or write them through the API in bulk. Companies, deals and activity history follow the same path.

Where do the signals come from?

Only from sources you authorize: your own CRM history, referrals and introductions, event and newsletter engagement, imported research runs and public company changes. Each signal keeps its source and observation time.

What stops an agent doing something I would not want?

Scopes decide what a key can touch at all. Beyond that, consequential actions are policy-gated: the request fails with approval_required until an explicit approval header accompanies it, and everything is attributed in the audit trail.

Can our own tools read and write to Catchment?

Yes — 34 documented REST resources covering contacts, companies, deals, tasks, activities, search, imports and discovery, plus an MCP server so an assistant can work in your workspace directly.

Who is this built for right now?

Founder-led B2B teams, partnership teams and expert practices, where a handful of well-timed conversations matters more than volume. We are onboarding a small group of design partners.

bring us the ones you keep missing

Opportunity rarely arrives in one place.

A catchment gathers what lands across an entire landscape and makes its path visible. Your relationships work the same way. We are building the first opportunity inbox with a small group of founder-led B2B teams.

Apply as a design partner