GTM Engineer

Prithviraj Chowdhury

Anyone can build a list of 1,000. I build the gate that finds the 2 worth contacting.

See the builds

Runs on the stack teams already use

Lists are cheap.
Evidence is the product.

Most outbound stacks optimize for volume. This one optimizes for proof: every account scored on verifiable facts, every send blocked until the receipt exists.

TAM sourcing build

Robotics · AI-safety certification

43 accounts to 2 sends. Every claim receipted.

Accounts scored
43
Cleared the gate
2
Claims corrected
8

43

accounts scored on fit, timing, and evidence for one robotics-safety vendor

2 of 43

cleared the send gate. 41 did not. The gate rejects weak evidence by design.

8

funding claims corrected. Databases said one thing, primary sources said another. Fixed before scoring.

1

do-not-mail address caught by validation before a single send.

Self-directed portfolio build

A verification trace for an AI-safety certification vendor in robotics

The vendor sells safety certification to robotics companies. Their sales problem: every robotics company needs certification eventually, but only a few are entering a cert window right now. This engine finds those few and proves why, before outreach.

  1. ICP
  2. Signals
  3. Evidence
  4. Score
  5. Gate
  6. Outreach-ready

ICP

Define the account

Companies that build machines working near humans, 11 to 300 people, US and EU. Fit is scored on facts that do not change weekly.

Signals

Capture the event

A target posted a safety-certification hiring req. Event type, date, and source recorded. A signal is a timestamp, not a feeling.

Evidence

Verify the receipt

Every event needs a receipt: a live listing, a press release, a filing. Unverified events score zero until proven.

Sample of real anonymized evidence rows from the build
SignalReceiptDateConfidenceFitHeatDecision
cert-execution hiringlive ATS listing2026-07-08High9245Prioritize
safety-risk role postedlive ATS listing2026-07-07High10048Prioritize
product launch presscompany newsroom2026-06-22High8831Verify
funding roundpress release2026-01-15High7412Monitor
standards articletrade press2025-06-25Medium614Monitor
sells safety productown website2026-07-11High00Reject

Receipts are shown as source type and capture date. The URLs exist in the build; publishing them would identify the companies.

Score

Separate fit from heat

Fit says whether the account can ever buy. Heat says whether now is the moment. Kept separate on purpose.

Fit100right kind of company
Heat48in the window now

Gate

Apply the send gate

43 accounts entered. 2 passed. Stale receipts, missing owners, and vendor-not-buyer conflicts all fail closed.

2 pass 41 held back

Outreach-ready

Prepare the output

What survives: a named contact with a validated email, an angle taken from their own hiring req, and the receipt on file.

Walkthrough coming soon

A short video walking the trace end to end.

How I work

  1. Receipts before outreach. A claim without a source URL does not get scored.
  2. Send gates fail closed. Missing evidence blocks the send, it does not soften it.
  3. Buyer first, tools second. The signal is a trigger. The buyer's problem is the product.

Next builds

The full build is inspectable. Ask me anything about it.

View LinkedIn