Blog

Last semester I was sitting in a 9 am lecture, half awake, when I realized something weird: everyone around me had a “million-dollar idea,” but none of us had actual users. Just sticky notes and confidence.

So here is the blunt version: you can validate a business idea without spending money by talking to real people, testing their behavior with simple free tools, and getting them to commit time, contact details, or reputation before you commit cash. No logos, no fancy app, just evidence.

What “validation” actually means (and what it does not)

At some point I had to admit to myself: my Google Doc of ideas was not a portfolio, it was a graveyard. The few that survived all had one thing in common: strangers cared enough to act before I built anything serious.

Validation is not your roommates saying “this is cool”, it is strangers doing something that costs them time, attention, or reputation.

Validation is:

• Someone you do not know agreeing to a call to talk about their problem
• A student giving you an email to be notified when you launch
• A club president forwarding your survey or form to their members
• A professor letting you present in their class because the idea is relevant
• A potential user saying “I would stop using X if your thing actually solved Y”

Validation is not:

• Your best friend saying “I would definitely use this” while scrolling Instagram
• People liking your “hypothetical app idea” on Instagram stories
• A group project grade
• A pitch competition win without any users behind it

If no one is slightly uncomfortable or slightly inconvenienced when they say “yes,” you probably have not validated anything.

So the question is: how do you get to that kind of “yes” without spending any money?

Step 1: Turn your idea into a sharp, testable problem

The first thing I realized during a lecture on “market research” is that my ideas were way too vague. “An app for students to manage time better” does not mean anything. You cannot validate fog.

You need a sharp problem statement that sounds like something a real person might say out loud.

Make the problem sound like a complaint

Try this fill-in-the-blank:

“[Type of person] keeps struggling with [very specific, annoying thing] when they try to [goal].”

Examples:

Bad problem	Sharper version
Students need better note-taking tools.	STEM students keep losing track of formulas and past exam questions when revising during finals week.
Clubs struggle with engagement.	Club presidents struggle to get members to actually show up to events they RSVP for.
Food delivery is broken on campus.	Students living in older dorms have to wait outside for drivers because addresses are confusing.

If you cannot phrase your idea as a concrete complaint, you are not ready to validate. You are still brainstorming.

Pick one core behavior to test

A “business” has many moving parts. For free validation, you just care about one behavior:

• Will someone talk to me about this problem?
• Will someone sign up for early access?
• Will someone switch from what they currently use?
• Will someone forward my link to a friend?

Choose one simple behavior to measure in the next 7 days. That is your validation target.

If your idea cannot be broken into a single behavior, the idea is too abstract. Tighten it before testing.

Step 2: Do “problem interviews” like a scientist, not a salesperson

I used to pitch first and ask questions later. Terrible habit. People are polite, especially on campus. They will encourage you, then ignore your product.

You need to interview like a scientist running an experiment.

Who to talk to this week

Start with people who already live in the problem:

• Students in a specific major (for academic tools)
• Club officers (for community or event tools)
• Teaching assistants or tutors (for learning tools)
• International students (for housing, banking, or paperwork tools)
• Cafeteria staff or delivery drivers (for food and logistics ideas)

Aim for 10 to 20 short conversations. You can do that in a week if you stop being shy about sending messages.

How to get interviews for free

Use what you already have:

• Your campus email and mailing lists
• Discord servers and WhatsApp groups
• Reddit (subreddits related to your campus, niche, or student life)
• Instagram stories with a poll or “question” sticker
• Class group chats

Simple message template:

“Hey, I am doing a tiny project on how [type of student] handle [problem]. I am not selling anything, just trying to understand what actually annoys people. Could I ask you 5 questions? It takes about 10 minutes.”

People are more willing to help if they feel like they are contributing to a research-type project, not being pitched to.

What to ask (and what not to ask)

Your goal: get them to talk about their life, not about your idea.

Good questions:

• “Walk me through the last time you tried to [goal]. What happened?”
• “What did you try before? Did anything help at least a bit?”
• “How do you solve this problem right now?”
• “What annoys you the most about the current way?”
• “How often does this happen?”
• “If this problem magically disappeared, what would change for you?”

Avoid:

• “Would you use an app that does X?”
• “Do you like my idea?”
• “On a scale of 1 to 10, how cool is this concept?”

Those questions give you compliments, not data.

Red flags and green flags from interviews

Red flag	What it probably means
“That is interesting, yeah, maybe.”	They are being polite. Low urgency, low pain.
They struggle to remember the last time it was a problem.	Problem is not frequent or not serious.
“I guess that would be nice to have.”	You are in “nice to have” territory, which is dangerous.
They already hacked together their own solution (spreadsheets, group chats, scripts).	This is a good sign. They care enough to patch the problem.
They say “Can you build this faster? When can I try it?”	Very strong signal. They want it, not just think it is interesting.

If your interviews sound like vague “yeah that would be cool” chats, you do not have a business idea. You have a dinner topic.

Step 3: Create a fake “front door” with free tools

At some point, you need to move from words to behavior. The clean way to do this without spending money is to build an entry point that looks a bit real, even if nothing is fully built yet.

Think of it as a “front door” to your idea.

Quick free tools you can use

• Google Forms for sign-ups, waitlists, or simple “request access” pages
• Typeform free tier for nicer-looking surveys
• Canva free designs for simple one-page graphics
• Notion page as a landing page with sections
• Linktree or similar for a simple link hub
• Instagram page or Substack sign-up for content-led ideas

You do not need a full website. You need a place where someone can:

• Read a clear statement of the problem
• See what you are claiming to solve
• Enter an email or submit a form

How to write a zero-budget landing page

Use this template structure on a Notion page or simple form description:

Headline:

A short sentence describing the outcome, not the tool.

Example: “Stop missing club events you actually care about.”

Subheading:

Who it is for, and the main problem.

Example: “For students who are sick of RSVPing to everything and forgetting what they actually wanted to attend.”

Body, 3 short bullets:

• What it does in simple language
• When they would use it
• Why it is better than what they use now

Example:

• See all club events you care about in one calendar
• Get one reminder the day before, not 20 spam emails
• No new app, just connects to the tools you already use

Call to action:

“Add me to the early access list” with an email box.

That is enough to test if anyone cares. You do not need perfect branding.

What you are measuring here

You are not aiming for thousands of sign-ups. You are measuring:

• Do people reach this page and leave immediately?
• Does anyone submit their email?
• Do club officers or friends react when you share it?

This is not fame. This is a small traffic, small conversion test.

If 20 real target users visit your “front door” and zero sign up, that is strong negative feedback. Listen to it.

Step 4: Ask for real commitment, not just interest

Here is the uncomfortable part. Interest is cheap. Commitment has a small cost. That is where validation lives.

You can ask for three types of free commitment:

• Time
• Contact details
• Reputation

Time: “Can we schedule a call or session?”

If someone says your idea sounds useful, immediately see if they are willing to invest time.

Simple tests:

• “Can we do a 15-minute call and I will walk you through a simple demo on Zoom?”
• “Would you let me shadow you for a class or one work session to see how you handle this problem now?”

If they always “get busy” after saying yes, the interest is probably weak.

Contact details: “Can I notify you when this is ready?”

The classic early access test:

• Collect emails with a short promise of what they will get and when
• Offer a clear update: “I will send you the first version in 3 weeks”

Better than just emails: ask short questions with the email:

• “What is the most annoying part of [problem] for you?”
• “How do you currently handle it?”

People who answer long paragraphs care a lot more than people who just type their email.

Reputation: “Will you share this with one friend?”

This is powerful because people do not like to recommend junk to friends.

Tests:

• “If this looks useful, would you mind forwarding this to one person who struggles with the same problem?”
• “Would you be open to posting this waiting list link in your group chat or Discord?”

If a club president shares your link in the official channel, even before your product exists, that is a big validation signal.

When someone risks looking slightly silly by supporting your idea, and they still do it, you have moved beyond hypothetical interest.

Step 5: Use “manual mode” instead of building product

A professor once said something that stuck with me: “If you are not slightly embarrassed by how manual your first version is, you are probably overbuilding.”

On a zero budget, you can still provide the service by hand before writing a single line of code.

What “manual mode” looks like

Think of it as you pretending the product exists, but doing the work behind the scenes.

Example ideas and manual versions:

Idea	Manual version (free)
App that curates events for your interests	Ask 10 students for their interests, then each Sunday send them a personalized email with events you found.
Study group matching platform	Use Google Forms to collect course + schedule, then personally form groups and put them in WhatsApp chats.
Service for cheaper textbooks	Act as a “matchmaker” in a simple spreadsheet: collect who sells and who buys, connect them by email.
Campus meal prep planning	Create shared Google Docs for weekly menus and send shopping lists by email on Fridays.

You are testing: will anyone actually use this if I do the work by hand?

How to frame “manual mode” to early users

Do not pretend you are a big company. Just be transparent:

“Right now this is a very early prototype. I am basically your personal assistant for [problem] for the next 2 weeks. You tell me what you need, I will handle the details. In exchange, I need honest feedback.”

Students are very forgiving if you present it as a scrappy experiment.

Signals to watch during manual mode

Strong positive signs:

• People reply fast and keep engaging
• They ask you “Can you also help with X?” related to the same problem
• They complain when you are slow, which means they rely on you

Weak or negative signs:

• They do not open your emails or messages
• They miss meetings or never use what you send
• They say “this is a great idea” but stop responding

Manual mode is harsh but fair. If people will not use the free, personal version, they will not use the fancy automated one either.

Step 6: Use your campus as a built-in test market

If you are on a campus, you are sitting inside a small, dense test environment with short feedback loops. It is almost unfair not to use it.

Free channels you are probably ignoring

• Course mailing lists (ask the professor for permission first)
• Student union newsletters
• Faculty or major-specific groups on WhatsApp / Telegram / Discord
• Bulletin boards (yes, physical paper still works)
• Club meetings where you can make a 2 minute announcement
• Office hours with professors who care about entrepreneurship or applied projects

Message to a professor, for example:

“Hi Professor [Name], I am working on a small project about how [students in your course] manage [problem]. I wondered if I could share a 1-minute form with the class or take 2 minutes at the start or end of a lecture to mention it. The goal is to learn, not to sell anything.”

Many will say yes, because it feels like supporting student projects, not marketing.

Micro-experiments you can run in one week

• Put a QR code on a printed poster linking to your waitlist or survey; count scans.
• Ask one club president to send your link plus a short blurb in their newsletter; track sign-ups.
• Stand near the cafeteria and ask 10 people from your target group 3 short questions.
• Run two different wordings of your idea on two separate stories or posts; see which one gets more replies.

These are small, cheap (actually free) ways to learn which framing and which audience react more.

Step 7: Be honest with the numbers, even if they hurt

This is the part where many of us start lying to ourselves. “The post did not get sign-ups because Instagram was weird that day.” “People are just busy.” That might be true, but it might also be that the idea is weak.

You need a simple scoreboard.

A simple validation log

Open a spreadsheet (Google Sheets is fine) and track:

Experiment	People reached	People who engaged	Type of commitment	Notes
Problem interviews	25 DMs sent	12 said yes	Time (calls)	Strong complaints from 5, mild from 7
Waitlist page in course group chat	80 students in chat	9 sign-ups	Email + simple question	Most sign-ups from people in 3rd and 4th year
Manual service pilot	10 invited	4 active users after 2 weeks	Ongoing use	2 users send long feedback messages

You do not need fancy analytics. Just a track record of “reached” vs “responded.”

When to keep going, when to pivot, when to quit

Some rough guidelines:

• If you spoke to fewer than 10 real potential users, you simply do not know enough.
• If you spoke to 20+ and almost nobody has a strong complaint, the problem might be too soft.
• If you had 50+ people see your waitlist and fewer than 3 signed up, the current idea or framing is very weak.
• If a tiny group (like 5 out of 20) are extremely excited, you may have a niche segment to focus on.

Killing an idea early is not failure. It is tuition you did not have to pay with cash.

The worst outcome is not “this idea did not validate.” The worst outcome is building for months on top of imaginary demand.

Step 8: Common traps students fall into (and how to avoid them)

I am going to be a bit strict here, because I made most of these mistakes.

Trap 1: Overvaluing compliments

Symptom: You tell people about your idea and they say “That is so smart, you should totally build it!” You feel great. Then nobody answers your follow-up message.

Fix:

• Do not accept compliments as evidence.
• After someone says “this is cool”, immediately ask for a small commitment: call, email sign-up, introduction to a friend.

If compliments do not translate into action, you learned something: the idea is not yet strong enough.

Trap 2: Asking leading questions

Symptom: You ask, “Do you get frustrated when your assignments are unorganized?” Most people say yes. You feel validated. But they are not thinking about your solution, just responding to a loaded question.

Fix:

• Ask them to describe actual behavior, not emotions about your suggested problem.
• Examples: “Describe your last week of assignments. How did you keep track?”

You want their story, not agreement.

Trap 3: Confusing “student” with “customer”

Symptom: You think “All students are my target audience.” They are not. The average student might not care at all.

Fix:

• Define your narrow group: “1st year CS students who commute”, “International grad students in labs”, “Club presidents who run events weekly”.
• Design tests for that narrow group, not for everyone.

If a very specific small group really cares, you have something real.

Trap 4: Hiding behind “stealth mode”

Symptom: You are scared to share the idea because you think someone will steal it, so you never get feedback. Secret projects feel safe, but they are invisible.

Fix:

• Share the problem openly, keep the tech detail private if you want.
• Nobody will steal a problem. People will just tell you if it actually exists for them.

Your main risk is not idea theft. Your main risk is building something nobody wants.

Step 9: Example validation scripts you can copy

Sometimes the hardest part is the first message or conversation. Here are some simple scripts you can adapt.

Script: DM to potential user

“Hi [Name], random question. I am working on a small project about how [group] handle [problem]. I noticed you are [in that group / involved with X]. Could I ask you a few quick questions about how you deal with this? I am not selling anything, just trying to understand if this is actually a real problem.”

Script: At the end of an interview

“Thanks, this really helps. Based on what you said, I am thinking of testing a super rough version where I [describe manual mode idea]. If I set that up for 1 or 2 weeks, would you want to try it? Totally fine to say no.”

If they say yes, that is commitment. If they say no, ask why. That “why” is gold.

Script: Short pitch to a club or class

“Hi, I am [Name], I am working on a tiny project for students who are tired of [problem]. Right now I am not launching an app, I am just testing if this is worth building. If [1 sentence description of their situation], there is a 20-second form here [QR code or link]. I need about 15 people for an early test, and I will share results with anyone interested.”

You are not pretending to be bigger than you are. You are honest about the experiment.

Step 10: Turning early validation into your next move

Once you have some real signals, what should you do next without money?

If the signals are weak

If you have tried:

• 10+ interviews
• A front-door page or form with at least 20 real visitors
• One or two manual mode tests

and the pattern is low engagement, low excitement, and people drifting away, then:

• Either the problem is too soft
• Or your target group is wrong

What you can do:

• Pick a different segment with stronger urgency
• Or move on to a different idea and reuse your validation skills

Letting go is not defeat. It saves your future time, energy, and money.

If the signals are strong

Strong usually looks like:

• People keep replying without you chasing them
• They introduce you to others who “need this”
• They complain when your manual service is slow

Then your next steps, still mostly free:

• Collect all feedback in one document or Notion page.
• Write a clear “problem spec”: who, when, what, why it hurts.
• Sketch out the simplest real version that covers just the core behavior.
• Ask 3 to 5 of your strongest early supporters to be “design partners” who see every version.

If you reach that point, and you truly have users waiting, then you can justify spending either time learning to build or a bit of money later. You earned the right to invest.

Validation without money is not about being cheap. It is about being honest with yourself early, so you invest cash only where reality has already voted “yes.”