Obi for GTM Engineers
AI search, run as a GTM play: from your ICP to the questions buyers ask AI, to the missing piece that gets you recommended.
npm i -g @hireobi/cliThe job
You wire the stack that fills pipeline: signals, enrichment, sequences. Your buyers now shortlist vendors in ChatGPT and Gemini before they reply to any sequence.
Where it hurts today
- AI search sits outside the stack, owned by nobody.
- Generic prompts tracked with no ICP behind them.
- No line from an AI answer to pipeline.
The workflow with Obi
From the agent you already use. Each step is one command.
- Start from won deals
Obi reads your CRM's won deals and your site, then proposes the ICP with its sources.
/obi - Review the questions
Questions written from your sales calls, as your buyer types them into an AI.
obi questions show - Read the scans
Each engine's answer every week, with the sources it cited.
obi questions results - Ship the next action
The plays ranked by urgency, buyer importance and effort.
obi strategies
Where it plugs in
- Attio
Obi reads the won deals to find the ICP, and ties the leads AI brings to revenue.
- Granola
Obi reads the sales calls recorded there, the buyers' real questions and objections.
- PostHog
Obi shows the visits and sign-ups that come from AI.
- GitHub
Obi opens pull requests on the product's repository for the pages and docs it writes.
What stays in your hands
- Obi recommends and drafts. It never publishes, sends outreach or buys anything on its own.
- Every command that starts paid work takes your explicit yes.
- Your secrets and the rest of your workspace stay on your machine.
Start with your own buyers' questions.
Hire for free