One tool. Five kinds of email.

Your prospect read 40 cold emails this week. Yours has eight seconds to feel different before they archive it.

You can't research every prospect. But every prospect you don't research sounds like every other email in the inbox.

Templates feel safe and convert at 1 percent. Specificity feels risky and converts at 8.

Idea for Linear's enterprise pipeline

Hi Karri, noticed Linear just rolled out the Asks integration to enterprise customers this month. The pattern I've seen with that kind of release: the AE team starts hearing 'can it also do X' from existing accounts, and the answer becomes a roadmap problem fast. We built a tool that turns those conversational asks into structured product feedback. Helped Notion's AE team last quarter cut the time from 'customer asked' to 'on the roadmap' from 6 weeks to 11 days. Worth fifteen minutes to see if it'd help here?

Maya · Operator at Bridgewise

LinkedIn easy-apply has a 1 percent response rate. A good cold email is 5 to 10x that.

But every applicant uses the same template the same career service handed out. The recruiter can spot it in 4 seconds.

You're applying to twenty companies. Researching every one of them on top of doing your current job is not a real plan.

Saw your team's vector store rewrite

Hi Anjali, your blog post on rebuilding the vector search layer at Notion caught me. The hybrid approach with metadata filtering matches what I shipped at my last role on a smaller scale: I rewrote our document retrieval to use a similar pattern and cut p99 latency by 40 percent. I'm exploring infra-leaning ML roles. If your team is hiring or about to, I'd love fifteen minutes to learn what you're building next.

Kishan · github.com/kishanpreetam

A professor gets 30 to 80 prospective student emails a month. They open the ones that prove the sender read their work.

Reading every faculty page across fifteen programs you're applying to is unrealistic. You have classes.

The 'I'm interested in your research' email gets deleted in 3 seconds. The 'I read your 2025 paper on X and had a question about Y' email gets a reply.

Question about your CRISPR delivery paper

Dear Professor Chen, your 2025 paper on lipid nanoparticle delivery for in vivo gene editing answered something I've been wrestling with since my undergrad capstone on off-target effects. The endosomal escape problem you raised at the end, in particular: have you explored whether targeted ligand conjugation might shift the escape efficiency, or is that already in scope for your current lab? I'm applying to your Computational Biology PhD program for fall 2026 and would value fifteen minutes to discuss whether my background fits your current directions.

Kishan, Northeastern MS Analytics '25

A VC partner gets 200 to 500 cold pitches a week. Their EA filters most. Their inbox folder eats the rest.

Generic 'I'd love to share what we're building' emails go nowhere. A specific reference to their thesis or recent investment proves you respect their time.

You don't have a research firm to brief you on every partner across forty firms on your list.

Noticed your bet on developer infrastructure

Hi Sarah, your portfolio's leaned hard into developer tools for AI-native workflows: Hex, Modal, Wandb. Scrapitch sits at exactly that intersection: free tool for personalized outreach, three-agent pipeline, sub-ten-second generation. We've hit 1,200 generations a day in the first month with zero paid acquisition. The pattern you wrote about in your AI-native developer thesis last quarter, the one about consumer-grade UX being the new moat, that's what we're chasing. Would you have fifteen minutes to look at where we're heading?

Kishan · founder, Scrapitch

The strongest networking emails reference a specific thing the recipient did or said. The weakest ones just ask for time.

You met someone at a conference, exchanged cards, and a week later you're staring at a blank compose window.

The line between 'asking for time' and 'feeling presumptuous' is thinner than people admit. Specificity is what makes it work.

Coffee chat after your talk at Lattice

Hi Diego, your talk on rebuilding perf reviews landed. The line about replacing rubrics with stories stuck with me, especially the part about engineering managers being uncomfortable with narrative until they realized rubrics were just narrative with worse signal. I'm rebuilding something similar at my org right now and the same uncomfortable conversations are happening. Would love fifteen minutes whenever it works for you. Coffee on me if you're in Boston, or just a video call if easier.

Kishan · north end, boston