How Student Founders Can Use Alumni Interviews for Discovery

A student founder building a placement tool can spend three weeks guessing what graduates need, or spend three days hearing why alumni still use spreadsheets, WhatsApp groups, and personal referrals. Student founders alumni customer interviews turn a familiar campus network into evidence you can use before writing product code. The aim is not to collect encouragement from people who share your college badge. It is to find recurring behaviour, costly workarounds, and a buyer who will act.

Why alumni are a useful first market for discovery

Alumni are accessible, but access alone does not make them useful. They are useful when their work, career stage, or past experience puts them close to the problem you want to study. A graduate working in procurement can help you understand vendor workflows. A recent alum who moved cities can describe the mess of finding housing, healthcare, or peer support. The interview starts with their lived behaviour, not your product idea.

Use alumni as a starting sample, not as proof that a market exists. Your college network carries shared context: the same campus, courses, and social norms. That can make people more willing to take a call. It can also make them unusually polite. You need to separate “this sounds useful” from “I had this problem last Tuesday and spent money or time solving it.”

Student founders often have an advantage here because they can get a warm introduction without pretending to have authority they have not earned. A report on student entrepreneurship describes a founder finding a repeated post-surgery problem only after interviews with nurses, physicians, surgeons, and patients. The lesson is direct: repeated evidence from people close to a problem beats a clever first assumption. Read the reported example.

Student founders alumni customer interviews start with a narrow segment

“Alumni” is not a customer segment. It is a directory. Before sending messages, choose one group defined by a job, context, and recent trigger. For example: HR managers at 50–200 person companies who hired interns in the past six months; final-year graduates who relocated for their first job; or independent clinic owners who adopted a new booking process this year.

Your first interview set should contain people who have recently experienced the problem. Recency matters because memory gets polished over time. Ask for people who made a decision, performed the work, or paid for the workaround. A senior executive may describe the issue well but may not be the user. A junior operator may feel the pain daily but have no buying authority. You need to know which one you are speaking to.

• Define the user: Who performs the task?
• Define the buyer: Who controls the budget or approval?
• Define the trigger: What event makes the problem urgent?
• Define the old way: What do they use today when your product does not exist?
• Define the boundary: Who looks similar but should not be in this first sample?

A narrow first segment makes patterns visible. If you interview alumni across banking, design, medicine, and manufacturing about “career problems,” every answer will sound different. If you interview one role facing one workflow, you can compare answers without forcing them into a story.

Recruit with a message that does not sell

Your outreach should make a small, honest ask. Do not lead with a pitch deck, a product demo, or “we are building the future of.” Alumni do not owe you time because you attended the same institution. They are more likely to respond when you state the specific topic, why their experience matters, and how much time you need.

Ask for an introduction only after checking whether the person is actually close to the problem. A batchmate may know an alum at a large company, but a loose connection is not a reason to interview the wrong person. Keep a simple research tracker: name, role, segment, source of introduction, date contacted, interview status, and the problem signals you heard.

Send individual messages. Refer to one real reason you selected them, but do not overdo flattery. If there is no reply, follow up once with two time options. Then move on. Discovery depends on a broad enough sample, not on winning access to one impressive alumnus.

Alumni networks can also become a route to later introductions. A 2026 account of an education company describes former students returning to mentor current students as their careers developed. Treat that possibility as a by-product of useful conversations, never the opening demand. See the reported alumni-network example.

If you have interviews booked but cannot turn scattered notes into a decision, our three-phase process gives founders a way to move from problem evidence to product, funding, and scale decisions. Apply for Nebula 1.0 when you want pressure on the fundraising story as well as the evidence behind it.

Run interviews for past behaviour, not approval

The most common discovery error is asking a respondent to design your startup for you. “Would you use an app for this?” invites a hypothetical answer. “Do you think this is a good idea?” invites kindness. Neither tells you what happens when the problem appears during a busy workday.

Start with the last time the problem occurred. Ask them to replay the sequence from trigger to outcome. What happened first? Who was involved? What tools did they open? Where did the process slow down? What did the delay cost in time, money, risk, or missed opportunity? Ask for examples until you can picture the workflow without them using abstract phrases such as “it is difficult.”

Ask this	What it reveals	Avoid this
“Tell me about the last time this happened.”	Real sequence and context	“Do you have this problem?”
“What did you do before and after?”	Current workflow and handoffs	“Would our product save time?”
“What have you tried already?”	Existing alternatives and urgency	“Would you pay for this?”
“Who had to approve the decision?”	Buying process and authority	“Can you introduce us to your CEO?”

Record with permission, then write notes immediately after the call. Keep quotes separate from your interpretation. If an alumnus says, “We use Excel because our team changes every month,” do not translate it into “they need AI workflow software.” The quote is evidence. Your product thesis is still a hypothesis.