What Request Intro should make easy
- selecting the right target
- confirming the right connector
- explaining why the intro matters now
- writing a short message the connector can actually forward
- adding relevant context, files, and timing
What the composer should prefill
- selected target
- selected connector
- path strength
- mutual count
- path evidence
- concise reason the intro matters now
- estimated response time when enough history exists
- next-step expectations after sending
Minimum useful request
| Part | Why it matters |
|---|---|
| Who you want to meet | The target cannot be ambiguous |
| Why now | Gives the connector context for urgency |
| Why this connector | Confirms the route is intentional |
| Short forwardable message | Makes it easy to help |
| Easy opt-out | Preserves connector trust |
Example forwardable message
Would you be open to introducing me to Jane Founder at Acme Bio? We are both working on climate infrastructure, and the conversation would be useful right now. No pressure if the timing is not right.
Anti-patterns
- asking a connector to infer the whole story from a name and company
- hiding low-confidence routes behind polished copy
- creating a request before choosing the best connector
- sending a long memo instead of a forwardable ask