Twine turns your client's LinkedIn into a searchable map of warm paths. Before you make a single call, you know who knows who — and how warm the connection is.
Your client knows exactly who they want. They've worked with these people. They've seen them present. They've hired them before. That knowledge lives in their LinkedIn — and right now it's invisible to you.
Cold outreach on a warm network is waste. You're not looking for strangers. You're looking for people your client already trusts — you just can't see them yet.
Twine closes the gap.
Your client exports their LinkedIn data — one CSV, five minutes. You upload it to Twine. Their entire network is now a searchable graph.
Twine builds a live network — nodes for every connection, edges weighted by warmth. Messages, recommendations, shared history. Who they actually know, not just who they're linked to.
Search by role or company. Twine shows you every candidate and who should make the introduction — ranked by relationship strength before you pick up the phone.
A 1st-degree connection who exchanged three messages three years ago is not the same as someone who left a written recommendation. Twine knows the difference.
Every edge in the graph carries a warmth score — built from message frequency, recency, recommendations, and who reached out first.
Your intro strategy is ranked before you make the first call. You lead with the warmest path. Every time.
"The best candidates are already in your client's network. Twine just makes them findable."
When the founder hands you their export, Twine becomes your shared map. When the Head of Engineering asks "who do we know at Stripe?" — you have the same answer they do, before the meeting ends.
No guessing. No "let me check your LinkedIn." The network is already in front of you — organised, weighted, and searchable by the people who matter most.
Every client brief becomes a rich map you can navigate from day one. Not better networking. Richer hiring.
Twine runs entirely in the browser. No server ever touches your client's connections file. The graph is built locally and shared only as a password-protected page you control.
You decide who sees it. You decide when it expires.