Nicheloom

Market intelligence for builders — see what's gaining traction before it's crowded.

Loop

Find out what happened weeks after your warm intro

Details

External ID
49083615
Source
HN
Company
—
Product
Loop
Website domain
getlooped.cc
Launched
July 28, 2026
Cohort
—
Upvotes
6
Upvotes percentile
0.2873357228195938
Tags
—
Fetched at
Sept. 7, 2026, 9:26 p.m.
Updated at
Sept. 7, 2026, 9:26 p.m.

Description

Loop helps you close the loop on email introductions. It is added to the CC line ([email protected]) 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.

Enrichment

Theme
email infrastructure and inbox utilities
Vertical
Sales
Function
CRM & pipeline
Audience
B2B
AI stance
AI feature
Project type
Commercial product
Normalized one-liner
follow-up tracking for warm introductions
Manually corrected
False

Could you build this?

Yes This is an inbound email parser (e.g., via SendGrid/Postmark) that schedules delayed follow-ups using standard background queues and parses replies with an LLM.

Discussion

7 comments analyzed.

Competitors mentioned: Google Scheduler, Email-based scheduling assistants

Concerns raised: Receiving end receptiveness and experience, Email scheduling bots have poor reputation for chaos

Feature requests: MCP (Model Context Protocol) integration, Data export beyond dashboard, Stalled intros identification view, Reciprocity view for connector matching

Competitors

Other products that read as similar to this one — 57 launches clear the similarity bar, closest 8 shown.

Attention rank: #53 of 58 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).

Launched 270 days after the earliest competitor.

Other launches for this product

Same idea, different domain

Nobody's really built a crm & pipeline tool for Fintech yet.