# A developer’s checklist for launching a side project

You’ve deployed your side project. Authentication works, the main feature is usable, and the landing page is live.

Now you need to put it in front of people who might use it.

I’m at this stage with llaunch, a product launch platform I’m building. It also includes Directories, a paid database of places to launch and promote products.

While preparing my own distribution, I’ve been putting together a repeatable process for choosing channels, preparing submissions, and recording what happens.

Here’s the checklist I’m using.

## 1\. Check the journey from a stranger’s perspective

Before sharing your URL, walk through the experience without relying on what you already know about the project.

Start in a logged-out session and check:

- Can someone understand the main use case from the landing page?
- Can they see an example, preview, or demo?
- Is it clear what is free and what requires payment?
- Does the primary action work?
- If they get stuck, can they find a way to contact you?

Then try one complete journey: landing page → signup → first useful action.

For a paid product, check the purchase flow as well.

The goal is to catch issues that would prevent someone from evaluating the project after you’ve earned their attention.

## 2\. Write down who needs it and when

Use a sentence with a person, a task, and a situation:

> This project helps \[person\] do \[task\] when \[situation\].

For example:

> This tool helps developers notice failed background jobs when they’re running a small app without a dedicated operations team.

That description gives you something specific to look for: discussions about scheduled tasks, deployment reliability, and maintaining small applications.

For my directory database, I’m looking for founders who have a working product and are deciding where to promote it.

Keep this sentence next to your channel shortlist. Use it when deciding whether a platform’s audience is relevant.

## 3\. Choose a format for each channel

A product listing, a tutorial, and a community discussion require different material.

Imagine you’re launching the background-job monitoring tool from the example above.

### Product listing

Explain what it monitors, how alerts work, what setup requires, and how much it costs.

Include a demo or screenshots that help someone understand the workflow.

### Technical article

Walk through a problem readers can solve.

For example: detecting a missed scheduled job, deciding when to send an alert, and avoiding duplicate notifications.

Include enough detail for readers to apply the ideas themselves.

### Community discussion

Share a specific problem or implementation decision and invite relevant feedback.

For example:

> How long do you wait before treating a scheduled job as missed? I’m working on alert thresholds and would like to understand how others handle jobs with variable runtimes.

Ask a question you actually need answered, and explain your connection to the project.

### Answer to an existing question

Address the person’s setup and constraints first.

Mention your project if it helps answer the question, with a clear disclosure that you built it. The answer should still be useful if they never open your link.

## 4\. Read the requirements before preparing a submission

For every candidate platform, record:

- Accepted project types
- Rules on product promotion
- Account requirements
- Submission price
- Review process or queue
- Required images, text, badges, or backlinks

Save the source URL and the date you checked it.

This avoids preparing a launch for a platform that doesn’t accept your project or requires something you haven’t budgeted for.

It also makes “free” more useful as a planning label. A submission might cost no money while still requiring a badge, an editorial review, or time spent participating in a community.

## 5\. Prepare a small launch kit

Keep the core product information in one document:

- Product name and URL
- One-sentence description
- Short description
- Intended user and use case
- Current pricing
- Demo or preview URL
- Logo and product images
- Contact details

Use this as the factual source for each submission. Adapt the final text to the platform.

For an article, lead with what the reader can learn. For a product page, make the workflow and offer easy to understand.

Check that descriptions and pricing remain consistent across both.

## 6\. Start with a batch you can follow up on

I’ve selected five platforms for my first round.

That gives me enough room to prepare each publication and respond afterward. I can also make changes between submissions if early feedback exposes an unclear explanation.

For each platform, I want to know:

1. Why is this audience relevant?
2. What am I publishing?
3. What do I hope to learn?
4. When will I review the result?

A useful outcome might be a purchase, a signup, or a conversation that reveals why someone wouldn’t use the product.

Write down which outcome matters for the experiment before publishing.

## 7\. Keep a lightweight distribution log

A spreadsheet or Markdown table is enough to start:

| Field | What to record |
| --- | --- |
| Channel | Platform or community |
| Publication URL | Direct link to the post or listing |
| Date | When it went live |
| Format | Listing, article, discussion, or answer |
| Time spent | Preparation and follow-up |
| Visits | Website traffic you can attribute |
| Conversions | Relevant signups or purchases |
| Feedback | Questions, objections, and suggestions |
| Next action | Repeat, revise, investigate, or stop |

Where the platform permits it, use a distinct campaign URL:

```plaintext
https://example.com/?utm_source=hashnode&utm_medium=article&utm_campaign=first_launch
```

Verify that your analytics captures the parameters.

A tagged visit doesn’t automatically give you purchase attribution. Depending on your setup, you may need to preserve the source through signup or checkout.

Keep the limits of your measurement visible when comparing results.

## 8\. Review the questions as well as the numbers

After each publication, look at what people needed you to explain.

Repeated questions can point to changes worth making:

- “Who is this for?” may mean the audience is unclear.
- “Can I try it?” may mean you need a better preview.
- “How is this different?” may mean the existing workflow needs more explanation.
- “Does it support my setup?” may reveal a missing compatibility detail.

Record the actual question before interpreting it. One comment is a lead to investigate; several similar comments give you more reason to act.

## How I’m using this checklist

I’m applying this process to [llaunch Directories](https://llaunch.dev/directories), my database of places to launch and promote products.

Disclosure: I’m the maker. Access costs $19 once for lifetime access, including future updates. The page includes free examples.

I’m using it to build my own shortlist, then checking each platform’s requirements and preparing material for its audience.

I don’t have conversion results from this campaign yet. My first goal is to complete the initial batch and collect enough evidence to choose the next one.

If you’re preparing to share a side project, you can use the checklist above with a shortlist of your own.

What did you discover after putting your last project in front of people outside your usual circle?
