MAKER GUIDE
How to promote a side project: a practical first-week plan
Start with one audience and one task your project helps them finish. Make that task easy to try, choose a channel where those people already participate, and use the response to decide what to improve next.
Prepare a useful first visit
Write a sentence that identifies a person, a task, and an outcome. For example: “A browser tool for freelance designers to turn scattered client feedback into a revision checklist.” That tells you more about where to share than “an AI productivity platform.”
Before promotion, test the first visit on a fresh browser session. Can someone understand the promise, see an example, and complete the core task? Prepare one screenshot of the result, a short demonstration, and a contact route for questions. If account creation is necessary, explain why and what happens afterward.
Choose an activation event before sharing: exporting a checklist, completing a search, or saving a first project. A signup alone may leave you unsure whether the tool helped anyone.
Choose channels by fit and readiness
| Channel | Editorial fit | What to prepare |
|---|---|---|
| Direct conversations | A narrow audience with a specific recurring problem | A useful observation and a question about their workflow |
| Show HN | Personally built, usable work with technical details to discuss | A working demo and an explanation of your decisions |
| Product Hunt | A product ready for a clear public introduction | Concise positioning, visuals, and time for questions |
| Discovery listings | A product that fits the site's scope | Accurate listing materials and a stable product URL |
These channels serve different purposes. Read the Show HN eligibility guide or the Product Hunt checklist before choosing a launch. For discovery listings, compare LaunchOnIt, PublishYourSaaS, and MeetSomething in where to submit your product. A listing is an additional route to discovery; it does not establish a dependable stream of users.
An example one-week plan
This hypothetical plan is for the client-feedback tool above. Adjust it to your audience and available time; it is not a case study.
- Monday: test the revision-checklist flow and write the audience sentence.
- Tuesday: prepare a sample using fictional client notes. Capture the output and explain one limitation.
- Wednesday: join a relevant conversation about revision work. Offer a helpful answer, then share your example where participation rules allow it.
- Thursday: collect questions. Fix the most confusing step before widening distribution.
- Friday: publish an introduction on one suitable launch channel or submit to a matching directory.
- Saturday: answer comments and ask people who tried it which step was difficult.
- Sunday: review completed checklists, acquisition sources, and repeated objections. Choose one improvement for next week.
Make promotion a learning loop
Keep a small log: channel, message, visits, completed tasks, and feedback. Separate observations from guesses: “three people asked about PDF export” is evidence; “designers prefer this channel” needs more support.
For manual conversations on X, the optional X Growth Engine profile describes a tool that observes a feed and suggests conversations or reply angles. Those relevant capabilities are paid, and the tool does not post, reply, or DM for you. Decide yourself whether a response is useful; a tool suggestion is not permission to promote.
Use the next week to resolve an observed obstacle. Repeating the same announcement everywhere teaches less than changing one confusing step and watching whether more people finish it.
Official sources
Platform facts checked on . Examples, channel choices and action plans are MeetSomething editorial suggestions. Recheck the official rules before submitting.