Start with the quickstart
Create or sign in to your account, connect a supported network source, and verify that Introd has usable relationship evidence.
Open Introd
Continue in the app. Protected pages ask you to sign in before showing workspace data.
Choose what you want to do
Set up your network
Connect a supported source, review sync status, and understand when the network is ready to use.
Find a warm path
Search for a real target and inspect the connector and evidence before taking action.
Prepare an introduction
Carry a verified target and connector into the composer and save an introduction draft for review.
Use the Chrome extension
Sync visible LinkedIn connection data and review the extension’s current status and controls.
Understand path confidence
Learn how evidence, freshness, and missing context affect a recommendation.
Review privacy and security
See the difference between disconnecting a source, clearing local extension data, and requesting account deletion.
The shortest successful path
1
Sign in or create an account
Use app.getintrod.ai. New accounts may be asked to complete access and onboarding steps before a workspace is available.
2
Connect and verify a source
Follow Sync your network. A connected label alone is not enough; confirm a recent successful sync or an explicit next action.
3
Search a real target
Use Search people, then open a result that includes enough relationship context to review.
4
Review before drafting
Check the connector, evidence, and uncertainty. If the path is weak or incomplete, gather more context instead of treating it as a warm introduction.
5
Save a draft
Use Prepare an introduction. Creating a draft does not send a message.
What these docs promise
- Instructions describe supported, reviewable behavior rather than future product ideas.
- Weak or missing relationship evidence is labeled as a limitation, not converted into a confident path.
- Introduction actions remain drafts until a person reviews and intentionally sends them through an approved channel.
- Internal architecture, deployment, credentials, and operator runbooks are not part of the public documentation.