Show HN: Loop – Find out what happened weeks after your warm intro | Hacker News Reader

Show HN: Loop – Find out what happened weeks after your warm intro

getlooped.cc

6 pointsSaltyAstronaut7 comments

Loop helps you close the loop on email introductions. It is added to the CC line (loop@getlooped.cc) on any intro email and after 2-3 weeks it will follow up with each side privately to determine the status or outcome of the connection, including any follow-on intros that were made from one side to the other.

Other than actively adding Loop to CC, it is permissionless. It requires no account or external app - running entirely through regular email workflow.

Over 90% of the time the same etiquette that sends the connector to BCC after the intro, will do so for Loop as well - so it only has visibility on the first two emails to determine who is the connector, who the sides are, what are their roles and when to emerge with the ask.

Aside from the challenge of maximum datapoint extraction with minimal data at hand, it also had to be built with more than a dozen timing, attribution and meaning guardrails so it wont act irreversibly on inferred state.

Some examples include out of office messages, personal assistants, weekends/holidays, intros of 3 or more people, replies from the same person with a different email address or emails that are actually not intros at all where it was CC'd by accident.

I built loop because I do about ~20 intros per month and realized that I rarely hear back on how they are going (e.g. - if a deal is on the table) or what the outcome eventually was. This visibility makes me a better connector and dealmaker, and it puts me top of mind for attribution without me needing to do awkward reach outs.

Loop can also be used for intros you receive, so I use it to see who keeps opening doors for me + gather statistics.

Stack: Next.js 16 (App Router) + React 19 + TypeScript on Vercel, Postgres (Supabase) via Prisma, Auth.js for login, Resend for inbound + outbound email, and Claude Haiku classifying the incoming mail. Sentry + Vercel Cron as well.

Open articleView on HN

This is one of those ideas that feels obvious in hindsight. I make a decent number of intros, and I almost never find out what happened unless I awkwardly ask weeks later. Love that this works with existing email etiquette instead of requiring everyone to adopt another tool.

Ok this is amazing. Feedback on intros is so important, and I really need something like this for my professional workflow. Wondering on the experience from the receiving end and how receptive they are? I've used some email-based scheduling assistants and they are chaotic with communications.

Thanks for the kind words!

scheduling bots got their bad reputation from a few concrete failure modes Loop was actually designed around. it sends an email from a clearly-labeled automated address, it's not pretending to be a person. It asks one simple, one-tap question, not an open-ended thread. It also never chases you with another email. The only people who ever hear from it twice are ones who explicitly tapped "still in motion, check back with me," and even then it's capped to 2x.

Reputation was the number one thing in mind so that Loop adds to your credibility as a connector and not the other way around.

One thing I will mention here is that when I make an intro, I always add one line - "Adding loop to see if this intro was helpful down the road, feel free to BCC us from here". This makes the process more intentional. Either way, recipient responses have been positive.

+1 for trying to stay as minimal as possible. Great principles. How did you manage to do the answer tapping mechanism in the thread? Is it a similar interface to Google Scheduler?

Replies are managed through a magic link (one-tap answers). You can also just reply in-thread in natural language and loop will pick it up.

My job is measured based on quality of intros. I definitely resonate with the need for this solution. Does log the data in a dashboard or provide any central data? Is there an mcp?

Thanks, that's exactly the use case I built it for.

Yes to the dashboard. It's completely optional so you can theoretically never open an account but if you do, you'll find all the intros in one space (sent and received). It offers more visibility on when loop emerges, allows for manual edits and more control over outcome notifications. There's also statistics like what types of people you get introduced to (investors, founders etc) your heatmap, loop rate (how many intros resolved with a real outcome) for quality measurement and more.

No MCP yet. You're right that data shouldn't stay trapped behind a dashboard/inbox. I'm genuinely curious what shape would be useful to you specifically. Something like "which of my intros are stalled," a reciprocity view ("who's a good connector for me"), or more of a raw export?

Reply on news.ycombinator.com