AI Company Fit Radar
An interactive decision surface for thinking through where an AI builder or operator really fits, what proof to send, and how to make outreach feel sharper than a generic recruiting note.
A lot of recruiting and outreach breaks down before the first conversation because the pitch is too abstract. There may be real fit, but the artifact is wrong, the language is vague, or the company has not been read clearly enough.
This tool is a small product version of how I think about that problem. Change the kind of company, the research posture, the workflow maturity, the tooling culture, and the hiring urgency. The output shifts the likely fit, the right proof asset, the outreach angle, and the conversation I would want to start first.
AI Company Fit Radar
A small recruiting and outreach simulator for deciding where an AI builder or operator really fits, what proof to send, and how to frame the first conversation.
AI product bridge builder
Research gravity plus shipping pressure.
This is strong fit territory. The team has enough research gravity to make the work interesting and enough shipping pressure to need product judgment, workflow design, and hands-on prototyping.
Lead with Claude Code and Codex as workflow accelerators, then show the product judgment underneath them.
Send an interactive lab, a sharp first-person note, or a scoped prototype that translates capability into a usable system.
AI labs product builder using Claude Code and Codex
Position yourself as the bridge between research promise and product reality: someone who can package capability, tighten workflow boundaries, and help the team ship with taste.
Ask where their model capability feels real internally but still under-packaged externally or operationally.
The company has both intellectual pull and operational urgency, which is where product-operator leverage matters most.
Do not pitch generic PM language. The strength here is builder judgment plus workflow clarity.
Lead with a concrete artifact before a long background story.
Mention Claude Code and Codex only after naming the workflow they improve.
Show taste for evals, workflow boundaries, and product packaging.