Your side project is ready. The deployment works, the landing page explains what it does, and someone can finally use it.
Now you need to decide where to share it.
I’m working through this with my own project, llaunch. While building a database of launch and promotion platforms, I’ve also been choosing where to promote the database itself.
Here’s the process I’m using to turn a long list of possibilities into a manageable first campaign.
1. Describe the person you want to reach
Before choosing a platform, finish this sentence:
My project helps [person] who is trying to [task].
Be specific enough that you can recognise a relevant conversation.
For example:
My tool helps freelance developers turn client feedback into actionable GitHub issues.
That gives you several things to look for: freelance developers discussing client work, questions about managing feedback, and communities around development workflows.
For my directory database, I’m looking for founders who have a working product and are deciding where to promote it.
That description helps me judge whether a community is relevant before spending time preparing a post.
2. Give each channel a job
Different channels let you reach people in different situations. I find it useful to separate them into three groups.
Launch platforms
These give you a product page and a place to announce what you’ve built.
Prepare a clear description, useful images, pricing, and a working demo or preview. Someone should be able to understand what the product does without asking you.
Communities and discussions
These let you talk to people about the problem your project addresses.
Read existing discussions before posting. Look at what people ask, what gets useful responses, and where product sharing is allowed.
A relevant question can also help you understand what your landing page needs to explain.
Articles and tutorials
These give you room to teach something connected to your project.
For the freelance feedback tool, that might be a tutorial about turning unstructured feedback into reproducible bug reports. Include examples readers can use in their own workflow.
Your project can appear where it helps explain the process.
3. Check the submission requirements
Before adding a platform to your shortlist, check:
- Does it accept your type of project?
- Is submission free?
- Is there a queue or editorial review?
- Does it require a badge or backlink?
- Are there restrictions on new accounts or self-promotion?
- What do you need to prepare?
Save the page where you found the requirements and the date you checked it. That makes it easier to revisit a channel later.
Also read the requirements before writing the post. You don’t want to spend an afternoon preparing something that doesn’t fit the platform.
4. Start with five channels
Five is the size I’ve chosen for my first round. It’s a working limit that leaves me time to prepare each submission and respond afterward.
Here’s a hypothetical shortlist for a developer productivity tool:
| Channel | What to prepare | What you want to learn |
|---|---|---|
| A launch platform | Product page and demo | Can visitors understand the use case? |
| A developer community | Post about the problem and implementation | Does the problem resonate? |
| A technical publication | Tutorial with a reusable example | Does the topic attract relevant readers? |
| A Q&A discussion | A complete answer to an existing question | Does the tool fit a real request? |
| A founder community | Build story and request for feedback | What objections do potential buyers raise? |
Choose the specific platforms after checking their audiences and rules.
5. Adapt the material to each platform
You can reuse the research, examples, and product facts. The publication itself should fit the context.
Suppose your project monitors scheduled jobs.
A launch page could explain supported integrations, alerting behaviour, and setup time.
A technical article could walk through detecting a missed job, including retries and false alarms.
A community post could explain an implementation decision and invite feedback.
An answer could help someone diagnose why their scheduled task fails, mentioning your tool only if it is relevant.
Before publishing, ask:
Would this still help someone who never visits my website?
That’s a useful editing test for articles and replies.
6. Track what happens after publishing
Keep a small log:
- Channel:
- Publication URL:
- Date:
- Time spent:
- Website visits:
- Signups or purchases:
- Questions and objections:
- Next action:
Use a distinct UTM link for each placement where the platform permits it. For example:
https://example.com/?utm_source=devto&utm_medium=article&utm_campaign=first_launch
Check that your analytics actually records those parameters. Connecting a visit to a later purchase may require additional setup.
Record the questions people ask, too. Several visitors asking the same thing can reveal a missing explanation, an unclear feature, or an audience mismatch.
How I’m applying this to my project
I’m using this process to promote llaunch Directories, a paid database of places to launch and promote products.
Disclosure: I’m the maker. Access costs $19 once, and the page includes free examples.
I’ve selected five platforms for the first round. My next step is to publish something appropriate for each one and record the results.
I don’t have conversion results from this campaign yet. When I do, I want to compare the time spent, relevant visits, and purchases so I can decide where to continue.
Where did you share your last side project, and what happened after you posted?
