The one-page launch checklist for student projects
· buildtolaunch
You have a project that works and you want to share it. This is a one-page checklist a student can finish in an evening: what to check before you post, what to do on launch day, and what to do the week after. It is part of the student launch playbook.
Short answer
Before launching, make sure five things are true: your link works on a phone, you can describe the project in one sentence, a new visitor knows the first action to take, people can send you feedback, and the project has its own name and look. On launch day, message ten people personally. Afterwards, count visitors, users and returners.
The one-page checklist (copy this)
Paste it into your notes app and tick it off.
BEFORE YOU LAUNCH
[ ] Public link opens on my phone, on mobile data, while logged out
[ ] I tested it on a second device or browser
[ ] One-line pitch: "A [thing] for [who] that [does what]"
[ ] A visitor can do the first action in 30 seconds
[ ] No placeholder text, broken buttons or default template branding
[ ] A way to reach me: form, Zalo/Messenger link or email on the page
[ ] A name, a title and a screenshot I am not embarrassed by
[ ] Analytics switched on (visitors and first action)
[ ] List of 10 people who have the problem, with their names written down
LAUNCH DAY
[ ] Send the link personally to the 10 people, one question each
[ ] Post once in a student group where I am already a member
[ ] Post on a friendly launch board with the screenshot and the pitch
[ ] Reply to every comment and message within a day
AFTER LAUNCH (DAYS 2 TO 7)
[ ] Talk to 3 users and ask where they got stuck
[ ] Fix the single biggest problem and tell the people who reported it
[ ] Post a short update with before and after
[ ] Count visitors, users and people who came back
[ ] Write one decision for next week: improve, change audience, or stop
The rest of this page explains each line, so you know why it is there.
Before you launch
A public link that works on a phone
Most students will open your link on a phone, often inside another app such as Messenger or Zalo. Test it exactly like that: send the link to yourself, open it on mobile data, and use a logged-out browser so you see what a stranger sees. If the page needs a login you did not mean to require, fix that first.
A second device or browser
Something that works on your laptop can break on an older phone or a different browser. Ask one friend to open it and tell you what they see. This takes five minutes and prevents the most embarrassing launch-day bug.
A one-line pitch
Fill in: "A [thing] for [who] that [does what]." Example: "A flashcard maker for exam students that turns lecture notes into cards in one click." If you cannot write the sentence, your users will not be able to repeat it. For help, read Write your one-line pitch.
A first action a visitor can do in 30 seconds
Decide what a new visitor should do first: paste a text, upload a photo, press a button. Remove everything that stands between them and that action. If the first screen asks for five things before showing any value, people will leave.
No leftovers
Search your own app for "Lorem ipsum", default template images, broken links and buttons that do nothing. These small things make a project look unfinished, and they make visitors doubt the rest.
A way to reach you
Add a short form, a Zalo or Messenger link, or an email address where visitors can see it. If people cannot reach you, you cannot learn from them.
A name, a title and a screenshot
Choose a real name, write a clear page title and take one clean screenshot. You will reuse the screenshot in every post. A simple landing page helps too: see Làm landing page và danh sách chờ miễn phí (Vietnamese).
Analytics
Switch on a free tool before you post, not after. As checked on 18 Nov 2026, Cloudflare Web Analytics describes itself as free and privacy-first and says it does not use cookies to collect usage metrics. Microsoft Clarity describes itself as free forever, with heatmaps and session recordings that show where people get stuck. Check each tool's terms yourself before relying on it.
Ten named people
Write down ten real names of people who have the problem: classmates, club members, friends of friends. If you cannot name ten, your audience is probably too vague. Narrow it, for example from "students" to "first-year students preparing for their end-of-term exams".
Launch day
Message ten people personally
A personal message works better than a public post when nobody knows you yet. Keep it short:
Hi [name], I built a small [tool] for [who] who [problem]. Could you try it for two minutes and tell me the first thing that confused you? Link: [link]
Post once, in one group
Choose a group where you are already a member and read its rules first. Say what you built, who it is for and what feedback you want. For advice on how to avoid being flagged as spam, read Đăng sản phẩm lên group Facebook sinh viên mà không bị coi là spam (Vietnamese). Templates are in Mẫu bài launch sản phẩm (Vietnamese).
Post on a friendly board
A practice board lets strangers who build things try your project. On buildtolaunch, that is the Launch League. If you are comparing places to post, see launch sites that are still free in 2026.
Reply fast
Reply to every comment and message within a day. A launch is a conversation, not an announcement.
The week after
- Talk to three users. Ask what they tried to do and where they got stuck, and write down their exact words. Use 5 câu hỏi phỏng vấn người dùng sau khi launch (Vietnamese) as a guide.
- Fix one thing. Choose the problem that blocked the most people. Tell those who reported it.
- Post an update. A before and after screenshot with two lines of explanation is enough.
- Count three numbers. Visitors, users who did the first action, and people who came back within a week.
- Decide. Improve, change the audience, or move on. If nobody came, read I launched and nobody came.
Checklist for a launch on buildtolaunch
buildtolaunch is a free community for university students of any major, with no coding needed to start. Once the checklist is done, you can post your project to the weekly Launch League board, which resets every Monday. Before that, you can learn from 70+ free courses, and build in a Space with an AI teammate. If you have questions about how to start, sign up.
FAQ
What is the minimum I need before launching a side project?
A public link that works on a phone, a one-line pitch, one clear first action, and a way for people to send feedback. A finished product is not required. If a stranger can open it and understand it in under a minute, you can launch.
How long does the checklist take?
About an evening for most small projects. Testing the link and writing the pitch take under an hour. The longest part is usually naming ten real people who have the problem, which is worth the time.
Do I need a landing page before launching?
Not always. If your project is already a working web app with a clear first screen, that screen can act as the landing page. A separate page helps when you are collecting a waiting list before the product is ready.
Should I set up analytics before or after launch?
Before. You cannot measure the first day if the tool was not running. Free options such as Cloudflare Web Analytics and Microsoft Clarity are enough for a first project.
Is it okay to launch with bugs?
Small bugs are normal. Bugs that stop a new visitor from doing the first action are not, so fix those first. Tell early users the project is a first version, and thank them when they report problems.
What if I do not have ten people to message?
Start with five and ask each one to name one more person who has the same problem. Join a student group related to the problem and spend a few days answering questions before you post your project.
Read the full guide
For the full path from a working link to your first real users, see the student launch playbook.