How to Find Your First 500 Users for a Student SaaS (Without Buying a List)

Students are not in any B2B database. Here is the playbook for finding your first 500 of them — where they actually gather, how to build the list, what to send, and which numbers tell you the idea is validated.

Every founder building for students runs into the same wall in week one. You have a product that genuinely helps somebody cram for an exam, and no idea how to put it in front of five hundred people who have an exam next week.

The instinct is to buy a list. That instinct is wrong here, and not for the usual reasons. It is wrong because the list does not exist. Apollo, ZoomInfo, Clay and every other contact database is built on the same raw material: company domains, job titles, LinkedIn profiles with employers attached. A second-year medical student has none of those. They are not a "Director of Operations at Acme Corp". They are a person with a YouTube history, a subreddit, a Discord server, and a group chat.

So the job is different. You are not filtering a database — you are finding a scattered audience across the places they actually gather, and building the list yourself. This is the playbook for doing that, ending with the numbers that tell you whether the thing is working.

Why student audiences break the standard prospecting stack

It is worth being precise about the failure, because it determines the whole approach.

B2B contact databases are assembled by crawling company websites, scraping LinkedIn, and buying data from vendors who do the same. Every record is anchored to an employer. The query language reflects it: industry, headcount, revenue band, seniority, tech stack. Every one of those filters is meaningless for a nineteen-year-old studying organic chemistry.

The consequences show up fast:

Search filters return nothing usable. "Students" is not a job title, and the handful of records where it appears are usually PhD candidates with a university email and a research page.
Coverage is close to zero. The people you want have never appeared in a sales database, because no sales team has ever wanted to sell to them.
The one thing you can filter on — university email domains — is a trap. Those addresses are frequently locked down, forwarded, or abandoned the moment term ends.

You will burn a month and a subscription fee discovering this. Skip that month.

Where students actually are

Students concentrate in public, searchable places. Not all of them, and not evenly, but enough of them to build a real list. In rough order of how well they convert for study tools:

Reddit. The single densest source. Subject subreddits (r/premed, r/EngineeringStudents, r/lawschool, r/MCAT, r/6thForm), university subreddits, and exam-specific communities that spike hard in the weeks before a session. People post under a persistent handle, describe their exact problem in detail, and many link a personal site, a Notion page, or a contact address in their profile.

YouTube comments and community tabs. Lecture recordings, exam walkthroughs and revision channels attract exactly the audience a study tool wants, at exactly the moment they are struggling. The comment sections are a live feed of specific complaints — "I had to rewatch this three times to get the derivation" is a product brief.

Discord. Course servers, exam-prep servers, university servers. Harder to scrape, easier to join. Treat this as a manual channel, not a list-building one.

X and TikTok. StudyTok and academic X skew toward the students who already buy tools — the ones with a Notion template collection and a colour-coded calendar. High intent, smaller volume.

Product Hunt and indie communities. Not students themselves, but the people who write about student tools and the founders whose audiences overlap yours.

Course pages, society pages and campus listings. These are the ones people forget. University society directories, student union pages, tutoring listings and course handbooks publish contact addresses openly, and they rank in Google.

The pattern across all of these: the contact details are published, they are public, and they are not in any database — which means finding them is a search problem, not a purchasing problem.

The playbook

1. Write the audience down as a sentence, not a filter set

Before touching any tool, write who you are looking for in plain language, specific enough that someone else could recognise one.

Not "students". Instead: "second and third-year engineering students in the UK and US who watch lecture recordings and complain about note-taking."

That sentence contains everything you need — the subject, the year, the geography, and crucially the behaviour. Behaviour is what makes a prospect findable. "Complains about note-taking" is a phrase that appears in text you can search for. "Student" is not.

2. Turn the sentence into search queries

This is the step most founders skip, and it is where the leverage is. Every place students gather is indexed, and every indexed place can be queried precisely.

The building blocks:

site:reddit.com/r/EngineeringStudents "lecture notes" "@gmail.com"
site:reddit.com "studying for" "MCAT" contact
site:youtube.com "revision" "second year" comment
site:linkedin.com/in "student" "mechanical engineering" "class of 2028"

Two things make these work. The site: operator confines the search to one platform's structure, and the quoted phrase pins the actual behaviour you described in step one. A query without a behavioural phrase returns the whole platform; a query with one returns the people who are currently having the problem.

Build twenty to thirty of these before you run anything. Vary the subject, the year, the exam name, and the phrasing of the complaint. Students describe the same problem in a dozen ways, and each phrasing surfaces a different set of people.

3. Run the searches and collect the contacts

Doing this by hand works and is a reasonable way to spend your first afternoon — you will learn what your audience sounds like, which is worth more than the list. Expect roughly forty to sixty contacts an hour once you have a rhythm, and expect to get bored around hour three.

At some point the manual approach stops paying. That is the point of a tool like Outsoci: you describe the audience in the same plain sentence, it writes the query set across Google Maps and nine social platforms, runs them live, follows the results to the pages behind them, and pulls the published contact addresses into one deduplicated CSV. Nothing is pre-stored and resold, which matters here specifically — a student who signed up for something last year is a different person from the student writing a panicked post today.

Whichever way you build it, insist on three things:

Deduplication. The same person appears across three subreddits and a YouTube comment. Emailing them three times is how you become a spammer.
Verification. Addresses scraped from public pages include typos, role addresses and dead accounts. Validate against the mail server before you send, or your domain reputation pays for it.
Provenance. Keep the source URL next to every address. You will want it later, both for personalising outreach and for answering anyone who asks where you got their details.

4. Reach out like a person, because students can smell a template

This audience has a finely tuned detector for corporate outreach. They have been marketed to their whole lives and they are unusually willing to tell you publicly that your email was cringe.

What works:

Reference the specific thing they said. You found them because they posted about rewatching a lecture three times. Say that. "Saw your post in r/EngineeringStudents about the thermo lectures" outperforms any subject line you could write.
Be short. Three sentences. What it is, why you thought of them, one link.
Ask for a reaction, not a sale. "Does this solve the thing you posted about?" gets replies. "Sign up for a free trial" does not.
Offer it free and mean it. Students are price-sensitive to a degree that surprises founders coming from B2B. Your first hundred users should cost them nothing.

What does not work: anything with a logo in it, anything that says "I hope this email finds you well", and anything that arrives at 9am on a Monday. Students read email at night.

5. Instrument the funnel before you send anything

You are running this to learn something, so decide in advance what would count as learning it. At minimum, track: contacts reached, replies, signups, first activation (they used the core feature once), and second use (they came back).

The gap between first activation and second use is the only number that matters early. Anyone will try a free tool once. Coming back is the signal.

A worked example: a study-notes tool

Take a real product shape. Notiq turns a YouTube lecture into structured study notes, flashcards and exam questions — paste a link, get a notebook. It sits squarely in the cluster this article is about: AI study notes, YouTube lecture notes, AI flashcard generator, turn a lecture into notes.

Working the playbook for a product like that:

The sentence. "University students who watch recorded lectures on YouTube and take notes badly or not at all — engineering, medicine and law, UK and US, first three years."

The behaviour to search for. Not "student". The phrases people actually type: "rewatching the lecture", "can't keep up with the notes", "lecture recording", "revision notes", "is there a way to summarise".

The query set. Around thirty variants across Reddit, YouTube, X and university society pages. A sample:

site:reddit.com/r/premed "lecture recordings" notes
site:reddit.com/r/EngineeringStudents "can't keep up" lecture
site:reddit.com "revision notes" "second year" contact
site:x.com "studytok" OR "study with me" notes app

The realistic yield. Thirty well-built queries across those platforms return somewhere in the hundreds of raw results. After deduplication and email validation you should expect a few hundred usable contacts — the exact number depends entirely on the niche and how narrow your behavioural phrases are.

What to expect from outreach. This is where new founders get their expectations broken, so let us be concrete. On cold outreach to a warm-ish, well-targeted audience, a 5–10% reply rate is good. Of those repliers, a fraction try it. Of those, a fraction come back a second time. Five hundred contacts producing thirty signups and eight repeat users is a normal, healthy first week — and it is enough to tell you whether the idea has legs.

If someone tells you they got five hundred signups on day one from cold outreach, they either had an audience already, got picked up by an algorithm, or is rounding a number they would rather you did not check.

What "validated" actually means at this stage

Validation is the word founders reach for when they mean "I feel better now". It deserves a harder definition, especially because the numbers involved are small enough that you can fool yourself in either direction.

A student SaaS is validated when:

Someone came back without being asked. Second use, unprompted, is worth more than a hundred signups.
Someone paid. Even once. Even four dollars. The first payment from a stranger is a different category of information from every piece of encouragement you have received so far.
Someone complained about the right thing. If your users are annoyed that the export is watermarked, you have a pricing problem, which is a good problem. If they are annoyed that the notes are wrong, you have a product problem, which is the real one.
The channel repeats. You found thirty users through a query set. Running a fresh variant of that query set finds thirty more. That is a channel. One lucky post is not.

What validation is not: signups, waitlist emails, upvotes, or people telling you it is a great idea. All four are free to give.

Be equally honest about the timescale. A study tool has a brutal seasonal shape — demand triples in the four weeks before exams and collapses over the summer. A great week in May and a dead week in July say almost nothing about the business. Two consecutive exam seasons say a lot.

Staying on the right side of the line

Scraping public data and cold-emailing individuals are two different activities with two different sets of rules, and student audiences are more likely than most to be covered by the strict ones.

Collection. Contact details published openly on a public page are generally defensible to collect. That does not extend to scraping content behind a login, evading rate limits, or ignoring a platform's terms.

Sending. This is where the actual obligations sit. Under GDPR, an email address belonging to an identifiable person is personal data whether or not it was public — and many of your prospects will be in the EU or UK. In practice: have a lawful basis, say clearly who you are and where you got their details, and honour deletion requests immediately and completely. Under CAN-SPAM in the US, include a real physical address and a working unsubscribe.

Minors. Take this one seriously. If your audience includes sixth-form, A-level or high-school students, some of them are under 18 and a chunk of the data protection regime changes. Either exclude those segments deliberately in your targeting, or get advice before you send.

None of this is a reason not to do outreach. It is a reason to do it in a way that does not become a problem in month six.

Five mistakes that cost founders their first month

Buying a database first. You will pay for coverage of an audience that is not in it. Search, do not purchase.
Targeting "students" instead of a behaviour. The filter that works is what they said, not what they are.
Sending before validating the addresses. A 20% bounce rate on your first campaign damages a sending domain you will need for the next two years.
Optimising the email before the list. A great email to the wrong five hundred people loses to a mediocre email to the right fifty.
Declaring victory on signups. Signups are the cheapest number in your dashboard. Watch the second use.

Frequently asked questions

How long does it take to build a list of 500 student contacts? By hand, roughly ten to twelve hours spread over a few days. With the search and extraction automated, the work moves to writing the query set — that is an afternoon, and the run itself is minutes.

Is it better to post in communities than to email? Usually, yes, and you should do both. Posting scales worse but converts far better, because the context is already there. Use outreach to find who to talk to; use the community to talk to them.

What if my audience is one specific university? Then your job is easier and your queries get more specific: society pages, course listings, the university subreddit, and the student union directory. Geography is one of the few filters that genuinely works for this audience.

Do university email addresses work for outreach? Inconsistently. Many are aggressively filtered, and students often ignore them entirely outside term time. Where you can find a personal address on a public profile, prefer it.

The uncomfortable truth about the first five hundred users is that there is no clever shortcut, and every founder who appears to have found one had something you did not — an existing audience, a lucky algorithm, or a looser relationship with their own numbers than they let on.

What there is instead is a method: describe the behaviour, turn it into queries, run them where the audience actually is, verify what comes back, and write like a person. Do that twice and you have a channel rather than an anecdote.

If the list-building half is the part slowing you down, that is what Outsoci does — one sentence in, a deduplicated and validated CSV out, across ten platforms, searched at the moment you ask rather than pulled from a database somebody else already emailed.