IntroLoop

Inspiration

A fund’s network is one of its most valuable assets. But helping founders still depends on a partner noticing an update, remembering the right person, asking a colleague, and chasing an introduction.

Meanwhile, the signals are scattered: a LinkedIn announcement, an investor email, a job posting. Together, they reveal where a startup needs help.

We built IntroLoop to turn those signals into action—and make the fund’s support visible beyond the check.

What it does

IntroLoop connects portfolio intelligence with the fund’s relationships to suggest timely, relevant introductions.

Our demo follows Emma, founder of Relay AI. Her startup announces an insurance partnership, reports pilots blocked by security reviews, and posts a Solutions Engineer role. IntroLoop identifies the explicit need: advice from someone who has navigated insurer deployments.

Sarah, her investor, receives a suggestion through Instinct. She selects Maya, an experienced operator connected to her colleague Daniel.

Daniel’s own Instinct asks whether he is comfortable reaching out. Once he agrees, Maya receives an email with IntroLoop confirmation buttons. Her response updates both assistants. Sarah can then introduce Emma and Maya.

Afterward, IntroLoop asks Emma for feedback and updates her founder record with the connection, meeting status, and outcome.

How we built it

We built an interactive prototype using HTML, CSS, and JavaScript, with a click-controlled workflow spanning two Instinct conversations, email confirmations, and a founder CRM.

The prototype uses fictional portfolio updates and network records. It models the full introduction lifecycle: identifying a need, selecting a contact, confirming the relationship, requesting permission, making the introduction, and collecting feedback.

IntroLoop actions update the conversation and CRM state within the demo. External integrations, email delivery, and agent communication are simulated.

Challenges we ran into

The biggest challenge was deciding what each signal actually proves. A partnership announcement suggests progress; a founder’s email can explicitly identify a need. A shared contact suggests a route; Daniel’s confirmation establishes whether he is willing to help.

We also had to make a multi-person workflow feel simple. Each participant sees only the context and action relevant to them, while the investor receives concise progress updates.

Finally, an introduction sent is not the same as a useful meeting. We built separate outcomes for a useful conversation, a poor fit, and a meeting that has not happened yet.

Accomplishments that we're proud of

We demonstrated a complete loop from scattered updates to founder feedback, with coordination across two investors’ assistants.

The experience stays in familiar interfaces: chat for investors, email for external contacts, and a CRM record that updates as the work happens.

Most importantly, the final record captures what the founder said happened—not just how many messages were sent.

What we learned

The right introduction depends on three things: a clear need, relevant expertise, and someone willing to make the connection.

The opportunity extends beyond recommending contacts. Coordinating permission and following through are essential parts of delivering value.

Founder feedback also makes the network more useful over time by recording which connections helped, in which context.

What's next for IntroLoop

Connect authorized email, calendar, portfolio data, and CRM systems, then pilot the workflow with a fund’s platform team.

We would start with one concrete use case: connecting portfolio founders with experienced operators who can help unblock enterprise deployments.

We would measure time to an accepted introduction, partner coordination time, meetings held, and founder-confirmed usefulness. Over time, IntroLoop could support hiring, customer introductions, partnerships, and fundraising—building a clearer picture of how a fund’s network helps its founders.