How to Message Startup Founders for an Internship

You have no uncle in HR, no alumni referral, and your placement cell's internship list stopped updating in August. Cold outreach to founders is the one channel that still works without a network — but only if you stop sending paragraphs about how hardworking you are. This guide gives you the sourcing routine, the four-line message structure, the follow-up cadence, and the exact replies to send when a founder says "no budget" or "not right now."

India has over 1.4 lakh DPIIT-recognised startups, and a large share are seed or pre-Series A — small teams where one extra pair of hands genuinely matters. That is your opening. Large companies hire interns through portals and campus drives; early-stage founders hire through their inbox. The catch is that their inbox is also where everyone else is sending "Respected Sir/Ma'am, I am a hardworking student seeking an opportunity."

Where do you actually find early-stage Indian founders to message?

Start with portfolio pages, not job boards. Accelerator and VC portfolio directories — Y Combinator's company list, Accel, Blume Ventures, 100X.VC, Antler India — are filtered lists of companies that have already raised money and are therefore hiring or about to. Add Product Hunt's India launches, Wellfound (formerly AngelList) for seed-stage roles, and LinkedIn with the search founder AND seed AND India filtered to companies under 50 employees. Twitter/X is underrated: founders who post build-in-public threads about shipping a feature are telling you exactly what they need help with.

Your college alumni list is the highest-conversion source and the one students ignore most. Search LinkedIn for your college name plus "founder." A 2019 graduate running a 12-person SaaS company will open a message from a junior from the same campus far more often than a stranger will. If you're mapping this to a broader plan, pair it with the off-campus internship strategy for Indian students so the outreach feeds a pipeline instead of being a one-off burst.

Run this as a 20-minute sourcing block, twice a week. Fifteen minutes to build a list of 10–15 founders with a note on what each company does, five minutes to log them in a sheet with columns for company, channel, date sent, follow-up date, and status. The sheet is not bureaucracy — it is the only thing that stops you from messaging the same founder twice or forgetting to follow up with the one who replied.

What should your first message to a founder say?

Four lines, under 100 words. Line one is a specific observation about their product, a recent post, or a bug you noticed — not flattery. Line two states what you can contribute in the next two to four weeks. Line three is one link that proves you can do it. Line four is a low-friction ask: a 15-minute call, or permission to try a scoped task. That is the whole structure.

Here is what it looks like in practice. Subject line: Noticed a checkout bug on [product] — built a fix. Body: "Hi [Name] — I used [product] yesterday and the coupon field breaks on mobile Safari when you paste a code. I rebuilt that flow in a sandbox and wrote up the fix here: [link]. I'm a third-year CSE student in Coimbatore and I can ship small frontend fixes like this within a week. Open to a 15-minute call, or I can send the patch as a PR?"

Notice what is absent. No "I am passionate about technology." No "I have strong communication skills." No paragraph about your college ranking. Founders skim on mobile between meetings; four lines fit on one screen. The observation proves you actually used the product, which already puts you ahead of 90% of the messages in that inbox.

The proof link matters more than any adjective. One deployed project, one merged pull request, one teardown doc beats a resume PDF every time. If you don't have that yet, spend two weeks on building a GitHub portfolio that founders actually open before you start outreach — a good message with no proof link converts poorly, and a bad message with a great link still gets opened.

LinkedIn DM, email, or Twitter/X — which channel should you use?

Match the channel to the founder's public behaviour. If they post on LinkedIn three times a week, DM there — your message sits next to their content, not buried in an inbox of 400. If they run a build-in-public thread on X, reply to the thread with something useful first, then DM. If the company site lists a founders@ or careers@ address, email works and gives you a subject line, which is the single biggest lever on whether it gets opened.

Skip Instagram DMs and WhatsApp entirely unless the founder has publicly shared those channels for work. Those are personal surfaces, and using them reads as boundary-crossing rather than hustle.

Subject lines that get opened are specific and slightly unusual. "Noticed a checkout bug on [product]" works. "Built a small fix for [product] — 2-min read" works. "Internship application" does not. "Seeking internship opportunity at your esteemed startup" does not. The subject line's only job is to earn the next two seconds; the body earns the reply.

Etiquette rules that quietly decide your reply rate

• No "Hi Sir/Ma'am." Use their first name. Founders in their twenties find the honorific awkward, not respectful.
• No paragraph longer than three lines. If it doesn't fit a phone screen, it won't be read.
• One ask per message. Asking for an internship, a referral, and feedback in the same note guarantees none of the three.
• Attach nothing on the first touch except a link. Attachments from strangers get ignored or trigger spam filters.
• Send between 9 and 11 a.m. IST on a weekday. Founders triage messages before their first standup.

How do you follow up without becoming spam?

Three touches over ten to fourteen days: day 0, day 4, day 10. Then stop. The rule that keeps this from being spam is that each follow-up adds a new artifact, not a reminder. "Just bumping this" is the message that gets you muted. "I shipped the fix I mentioned and opened a PR — here's the link" is the message that gets you a reply.

Touch two on day four should be one sentence plus one new thing: a screenshot of the bug fixed, a short write-up of how you'd approach their onboarding flow, a link to a small tool you built that relates to their stack. Touch three on day ten is a graceful close: "I know you're heads-down — I'll stop here. If a frontend slot opens up in the next month, I'd love to be considered. Either way, here's the teardown doc in case it's useful." That last line sometimes gets a reply precisely because it removes the pressure.

If you hear nothing after three touches, mark them closed and move on. Do not message again in the same quarter. Founders remember names, and the student who respected the silence is the one they reply to six months later when a role opens.

How many founders should you message before you get a reply?

Treat it as a funnel, not a lottery. A realistic early ratio for a student with a decent proof link is roughly one reply per ten to fifteen well-researched messages, and one serious conversation per three or four replies. That means thirty to fifty targeted messages over three to four weeks to land a handful of real conversations. Two hundred copy-pasted DMs will produce fewer, because the personalisation is what earns the open.

Track it honestly. If you've sent twenty messages and got zero replies, the problem is almost never your profile — it's the message. Rewrite line one to be more specific, swap the proof link for something more relevant to the company's stack, and send the next ten.

What do you do when the founder says "no budget" or "not right now"?

Reply within 24 hours with a short, graceful note. Thank them, then offer a two-week scoped project you can do for free or for a small stipend, and ask if they can refer you to one other founder who might be hiring. "No budget" almost always means "no budget for a full-time intern," not "no work that needs doing." A defined two-week project — fix this onboarding flow, write these five SEO pages, clean up this dataset — is a cost they can say yes to.

If they hand you a trial task, treat it as a paid interview. Ship it early, write a short note explaining your decisions, and ask what they'd want changed. When the task lands well, that is your moment to raise the stipend conversation: "I enjoyed this — if there's a scope for the next month, I'd be glad to continue. What would a stipend look like for that?" Ask once, plainly, without apologising.

The referral ask is the most underused move in student outreach. A founder who can't hire you today knows ten other founders. "If you know someone building in this space who needs a frontend intern, I'd be grateful for an intro" costs them nothing and occasionally changes your year. Before you take any offer, though, read up on startup vs service company internships so you know what you're optimising for.

How to verify an early-stage startup before you share documents

Before you send Aadhaar, PAN, or bank details, verify the company exists. Check the MCA portal for the CIN and incorporation date. Look at the founder's LinkedIn history — a profile with three years of posts and a real network is a good sign; a two-month-old profile with 40 connections is not. Search for funding news in your preferred business daily. If the company has a public website, a working product, and a founder with a traceable history, you're on solid ground. If any of those are missing, ask for a written internship letter before sharing anything personal.

Stipend reality check: early-stage Indian startups vary wildly. Some pay nothing and offer real ownership; some pay a modest monthly stipend; some pay per-project. None of these are automatically a red flag, but open-ended unpaid work with no defined deliverable is. Get the scope in writing — what you'll ship, who you report to, hours per week — before you start. If you want to benchmark your own communication before you send anything, you can test your professional communication skills and see where your writing lands.

What if you're from a non-CS branch or have a low CGPA?

Pitch for the roles where CGPA matters least: growth, content, operations, design, community, founder's office. Early-stage startups hire for output, not transcripts, and a founder's-office intern who can run research, draft customer emails, and keep a project tracker is genuinely useful from week one. Your message structure stays the same — observation, contribution, proof, low ask — but the proof link changes. A teardown of their pricing page, a short competitor analysis, a set of draft social posts: all of these work as proof for non-technical roles.

Do not apologise for your branch or your CGPA in the message. Mentioning it defensively draws attention to it. If a founder asks, answer honestly and move straight to what you can do. Students who've made this switch successfully usually follow the playbook in non-CS branch to tech roles — the framing matters more than the branch.

One more thing on resumes: if you're applying to startups, your resume should be one page, project-first, with links inline. The resume tips for tier-3 college students cover the specifics, but the short version is that a startup founder reads the top third of your resume and decides. Put the proof there.