Tink

Transcript context: attendee email is tom@gettink.ai; the product/persona is rendered as “Tink” and sometimes garbled as “tank” in the transcript.

Current truth

Stage: warm discovery / education thread, not yet a build or paid engagement. tom-chevalier is interested, but Tink has not prioritized connector development yet.
Product direction: Tink is training a persona for autonomous candidate outreach and job discovery. Current channel is cold email, using enrichment and intent data to improve targeting.
Launch state: outreach engagement is promising, but the product still has bugs and is not fully launched.
AI-entry experience: Tink has built a landing/chat experience for intent-led queries such as “I need help finding a job,” so it could carry a conversation from Claude/ChatGPT into Tink when the connector channel becomes a priority.
Decision posture: Tom does not yet see a clear first-mover advantage. He is likely to wait until there is more conviction about how connector discovery works and how Tink can win.
Category nuance: recruitment is two-sided. Enterprise recruiting prompts (talent teams, ATS, interviews) and job-seeker prompts can surface very different competitors; Tink likely needs bespoke prompt tracking rather than relying on a broad recruitment-category view.

What is Tom’s exact role/title at Tink?
Which side of the market should Tink optimize for first: job seekers, hiring teams, or both with separate prompt sets?
Which platform should Tink prioritize first if it moves: Claude connector, ChatGPT app, or wait for stronger ChatGPT organic surfacing?
Is there a real early-mover / memory advantage from being connected and used before the channel matures?

[2026-06-16] (call) tom-chevalier and elliot-garreffa discussed whether Tink should prioritize ChatGPT/Claude connector development. Tom described Tink’s autonomous outreach/job-discovery persona, cold-email start, enrichment/intent-data targeting, and intent-query landing experience. Elliot walked through the agent-discovery market, Claude’s organic connector surfacing, OpenAI/Codex tool-calling improvements, and the Ghostteam registry/category view. Tom’s key objection: he wants conviction on how to succeed before allocating development; no clear first-mover advantage yet. Elliot committed to keep sharing ecosystem/data updates and to walk Tom through pro-tier setup/build options when Tink is ready.