On this page
- Treat the internship as fieldwork, not market access
- Student startup customer discovery starts with a narrow problem
- Find interviewees without crossing professional lines
- Run interviews that produce evidence, not compliments
- Turn interview notes into a decision
- Build a discovery routine before you build product
- Sources
During an internship, you may sit within a few metres of the people who buy, use, approve, reject, or work around a product every day. That access can become student startup customer discovery if you treat the internship as structured fieldwork rather than a line on your CV. Your goal is not to pitch an idea between meetings. Your goal is to leave with evidence about a problem worth solving.
Treat the internship as fieldwork, not market access
An internship gives you proximity, not permission. You may observe a sales team lose deals, an operations team repeat a manual task, or customers ask the same question in every support call. Those patterns are useful signals, but they are not proof that your startup idea deserves to exist.
Start by separating what you see into three buckets: a visible symptom, the person affected, and the cost of leaving it unresolved. “The team uses spreadsheets” is a symptom. “Regional sales managers spend two hours reconciling distributor orders each evening” is a better observation. “They miss stock issues because the report arrives late” starts to identify a consequence.
Keep a private field notebook. Do not copy company documents, customer lists, pricing data, code, or confidential information. Record only your own observations, anonymised workflows, and questions that you can test independently. Your startup cannot depend on information you were not entitled to take.
Use this test: if you cannot describe the problem without naming your employer, its customers, or its internal data, you have not yet understood the problem well enough to build around it.
At Nebula, we see early founders confuse access with validation. Access gets you closer to the work. Validation begins when people outside your immediate workplace describe the same pain in their own words.
Student startup customer discovery starts with a narrow problem
Most student founders begin too wide: “small businesses need AI,” “students need better finance tools,” or “Indian retailers need digitisation.” These statements cannot guide an interview, a product decision, or a first sale. Narrow the problem until a specific person can recognise it without explanation.
Write a one-line problem hypothesis before you speak to anyone: “Independent pharmacy owners struggle to track expired inventory across multiple suppliers.” The statement may be wrong. That is fine. Its job is to make your next conversation sharper.
Your internship can help you identify a useful starting segment. Look for people who have a recurring job, a repeated workaround, and a consequence when the workaround fails. Avoid segments chosen only because they are easy to reach, such as classmates who have no reason to pay for the solution.
- User: Who performs the work or feels the pain?
- Buyer: Who controls the budget or approval?
- Trigger: What event makes the problem urgent?
- Current workaround: What do they do now?
- Cost: What time, revenue, risk, or effort does the workaround create?
Student entrepreneurship programmes elsewhere make customer interviews a core part of venture development. Cornell’s eLab describes teams conducting customer discovery interviews while refining their business plans, which is the right order: learn from the market before polishing the plan. Cornell Entrepreneurship
Find interviewees without crossing professional lines
Your employer’s customers are not automatically your startup research pool. Asking them to discuss a personal project through your work role can create an ethical problem and damage trust. Use the internship to understand which roles matter, then recruit participants through channels that belong to you.
Start with alumni, family business contacts, professional communities, college networks, and public outreach. Ask for a 20-minute learning conversation, not feedback on your product. A direct message works when it is specific: identify the role, name the workflow you are studying, and make clear that you are not selling anything.
For an India-focused idea, recruit across meaningful differences. A workflow in Chennai may operate differently in Coimbatore, Madurai, Pune, or a smaller town. Do not call a pattern universal because you heard it from three people in one office. Compare role, business size, geography, and level of decision-making before you draw a conclusion.
| Bad request | Better request |
|---|---|
| “Can I show you my app idea?” | “Could I learn how you handle invoice follow-ups today?” |
| “Would you use this?” | “When did this last happen? What did you do next?” |
| “Is this a big problem?” | “What happens if this task is delayed for a week?” |
Keep your employer informed if your internship agreement requires it. Protecting confidential information is not paperwork. It is the baseline for becoming a founder people can trust.
Run interviews that produce evidence, not compliments
Your first customer conversation should feel closer to investigative reporting than a pitch meeting. Ask about past behaviour, specific incidents, and decisions already made. People are generous with encouragement for students; encouragement is not buying intent.
Open with context. “Walk me through the last time you had to manage this process” is stronger than “Do you face this issue?” Follow the timeline. Ask what happened first, who got involved, what tool they used, where the process broke, and what happened after that. The detail tells you whether the pain is real.
- “Tell me about the last time this task became difficult.”
- “What were you trying to get done?”
- “What did you use before trying the workaround?”
- “Who else had to approve or fix it?”
- “What did the delay or error cost you?”
- “Have you paid for a solution, hired someone, or built an internal process?”
Do not ask respondents to design the product. They know their work better than you do, but they do not owe you a product roadmap. Your task is to identify repeated jobs, constraints, and existing spending. If someone asks what you are building, give a short answer after the interview questions, then return to their experience.
Customer discovery and commercialisation are taught together in the George Mason MIX programme through its connection with NSF I-Corps. That pairing matters: discovery should lead to a business decision, not a folder of interview notes. George Mason University
Turn interview notes into a decision
Discovery fails when every conversation ends with “interesting insights.” You need a decision rule before you start. After each interview, record the role, incident, current workaround, consequence, buying process, exact language used, and the strength of the evidence. Do this immediately; memory edits details into a cleaner story than what actually happened.
Then compare interviews side by side. Look for repetition, not isolated drama. Five people using different words to describe the same bottleneck may point to a real opportunity. Five people agreeing that your idea sounds good does not.
Do not build after one strong call. A vivid story can create founder bias. Build a pattern across comparable people, then test whether they will take a concrete next step.
Your next step should match the evidence. If the problem is unclear, interview another segment. If the problem repeats but the buyer is uncertain, map the buying process. If people already pay for a workaround, test a small paid pilot. If nobody has felt the pain recently, stop defending the idea and change direction.
This is where student founders gain an advantage. You can run short learning cycles before committing months to code. Our three-phase operating process begins with venture validation because product work without a clear market signal creates expensive confusion later.
Need a sharper route from evidence to investor readiness? Apply for Nebula 1.0, our current 2-week fundraising sprint.
Build a discovery routine before you build product
The strongest outcome from an internship is a repeatable research habit. Set a weekly cadence while you still have access to real workflows: capture observations during the week, recruit two or three independent interviewees, review patterns on the weekend, and choose one assumption to test next. Consistency beats a one-day burst of activity.
Create a simple evidence tracker. Each row should contain a participant type, the problem event, the workaround, the stated consequence, and a quote in their own words. Tag each item as observation, interview evidence, or assumption. This prevents you from treating your interpretation as a customer fact.
Do not rush into an MVP because your internship is ending. A prototype is useful when it tests a defined uncertainty: whether users can complete a task, whether a buyer will pay, or whether your proposed workflow fits their constraints. It is wasteful when it exists only to make the idea feel more real.
You can use the end of the internship to make clean asks: introductions to relevant public communities, permission to stay in touch as a learner, or feedback on a problem statement. Do not ask for investment, endorsements, or access to confidential buyers before you have earned credibility.
We co-build with founders across validation, product, fundraising, and go-to-market. If your interviews show a repeated problem and you are ready to turn it into a venture case, Apply for Nebula 1.0. Bring your evidence, not a polished story.
Sources
Enjoyed this? Get the next one in your inbox.
Fundraising guides and validation frameworks, every two weeks. No spam.
Frequently asked questions
Can I interview customers from my internship company for my startup?
Only if you have clear permission and do not use your work role, confidential information, or employer relationships for a personal venture. Recruit independently wherever possible.
What should student founders ask in customer discovery interviews?
Ask about a specific past incident, the workflow, current workaround, people involved, consequences, and any money or effort already spent to solve the problem.
When should a student founder build an MVP?
Build an MVP after repeated interviews show a specific problem and you can name the uncertainty the product will test, such as usability, willingness to pay, or workflow fit.
Ready to build your startup?
We work with a small number of founders each year — mentorship, fundraising support, and a co-founder network included.
Start a conversation
Talk to the founder directly. We reply within two working days.
Applying to Nebula 1.0? Apply here →