Portfolio · 01 · Commercial Decision Infrastructure

OutboundFix

OutboundFix is Commercial Decision Infrastructure from Certainty Labs: governed commercial judgment on which accounts deserve sales capacity.

Know which accounts deserve your sales capacity.

Other systems acquire data, enrich it and execute actions. OutboundFix owns the step between them: governed commercial judgment on whether an account should receive sales capacity at all.

outboundfix.io

Product model · SERVICE_AS_SOFTWARE

OutboundFix does the commercial-decision work itself. It gathers the evidence, argues the case against the policy it is given, issues the verdict and keeps the record.

Interfaces

  • MCPBuilt · not enabled
  • APIBuilt · not enabled
  • CLIBuilt · not enabled
  • IntegrationsBuilt · not enabled

Verdicts

PASS
The available evidence supports allocating sales capacity.
RESEARCH_MORE
Get the specific missing evidence before spending sales capacity.
KILL
The account does not currently justify sales capacity.

Decision chain

  1. signal
  2. evidence
  3. counter-evidence
  4. uncertainty
  5. decision argument
  6. verdict
  7. authoritygranted or refused hereHubSpot loop
  8. governed actionHubSpot loop
  9. observed outcomeHubSpot loop
  10. re-evaluation
  • 01–06, 10 · Web workspaceProving
  • 07–09 · HubSpot loopBuilt · not enabled

OutboundFix is not

  • a CRM
  • a workflow builder
  • a lead database
  • an AI SDR
  • a generic GTM platform
  • a mass outbound tool

State of the product

Built

A deterministic runtime issues the verdict

Each account whose research completes receives PASS, RESEARCH_MORE or KILL, written as an immutable decision record with its evidence. AI gathers evidence; it never decides. When research fails or a claim cannot be verified, the outcome is never a PASS or a KILL.

Source: A deterministic runtime issues the verdict

Built · not enabled

API, MCP and CLI are implemented and switched off

The API, the MCP server and the CLI are implemented on the same governed decision boundary and return the same verdicts. All three are switched off in production: the service refuses every request to them.

Source: API, MCP and CLI are implemented and switched off

Built · not enabled

HubSpot and Clay integrations are built and not active

A HubSpot decision loop with human approval before any write-back, and a Clay intake that sends enriched accounts for a decision, are built and tested. Neither is enabled in production.

Source: HubSpot and Clay integrations are built and not active

Built · live

The public site is live and states its own availability

outboundfix.io is live. It presents OutboundFix as Commercial Decision Infrastructure, publishes the entry offer of ten real accounts, and states for each access surface whether it is available, implemented or not yet active.

Source: The public site is live and states its own availability