Know which accounts deserve your sales capacity.

OutboundFix is Commercial Decision Infrastructure for B2B sales and GTM teams. It evaluates each target account against your targeting policy and returns, when its research completes, one of three verdicts — PASS, RESEARCH_MORE or KILL — together with the evidence, counter-evidence, uncertainty and policy version behind it.

It is the layer of a go-to-market stack that decides which accounts deserve sales capacity. Data, enrichment, intent and scoring tools describe accounts; CRMs and engagement tools act on them. Commercial Decision Infrastructure sits between the two and turns evidence and an explicit policy into a recorded, reviewable decision.

PASS: the available evidence supports allocating sales capacity. RESEARCH_MORE: there is not enough justified certainty yet, so the specific missing evidence should be gathered first. KILL: the account does not currently justify sales capacity. Each is a decision under your policy, not a score.

It is the record of one account decision: the verdict, the evidence and counter-evidence with their sources, what remains uncertain, the reasoning, the reason codes and the policy version that produced it. A Decision Record is never edited. New evidence or a new policy version produces a new record that supersedes it.

Sales intelligence and enrichment tools supply data about accounts, and lead scoring ranks them with a number. OutboundFix does neither. It decides whether an account should receive sales capacity under an explicit policy and records why. The output is a verdict with its evidence, not a number to interpret.

No. Clay and similar tools gather and enrich data; OutboundFix decides what the evidence means for sales capacity. An integration in which a Clay table sends accounts to OutboundFix for a decision is built and not yet active. Clay data is kept as context, never as the verdict: the decision comes from OutboundFix Core under your policy.

No. OutboundFix does not own a CRM, a workflow builder or a sales engagement platform. A HubSpot decision loop, in which an approved decision is written back to the company record, is built and tested but is not active for any customer yet.

The verdict is RESEARCH_MORE and the record names what is missing. OutboundFix does not guess: if research fails or a claim cannot be verified against the source page, the outcome is never a PASS or a KILL.

Not today. In the workspace, a verdict changes nothing outside OutboundFix. The HubSpot decision loop is built to require human approval before any write-back, and autonomous action is not enabled.

Each Decision Record keeps its evidence with sources, its counter-evidence, its uncertainty and its policy version, and it cannot be edited after it is written. Feedback you leave on a decision is recorded next to it and never changes the verdict.

You do, when there is new evidence to gather or your policy has changed. For an account whose current decision is RESEARCH_MORE, you can re-evaluate it against your active policy. The result is a new Decision Record that supersedes the earlier one, which is kept. Re-evaluating against your active policy does not use your allowance, and neither does submitting the same domain again in the same billing month (on Free: at any time).

Today, access is through the web workspace. The API, the MCP server and the CLI are implemented on the governed Core V2 decision boundary, and all three return the same PASS, RESEARCH_MORE or KILL decision with its Decision Record. Public production access is not yet enabled. If you need programmatic access, tell us through the Enterprise form.