Pick your launch channel by who pays

You have a product and a launch date. The channel that matters is the one that turns a signup into a payment.

For a small team, the early users are a manual problem. You need to know who is buying, where they came from, and whether the channel is worth more of your time.

Pick the channel that pays before launch day

Pick the channel where your buyer already complains about the problem you solve. For a product aimed at remote teams, the people who will pay are likely already in places where they talk about remote work, async tools, and small-team operations. Choose a channel where those buyers can be reached directly, and treat the others as experiments. Done looks like a chosen channel and a reason tied to buyer intent, not a list of places you could post.

Driftnote was an asynchronous standup tool for remote teams made by a two-person team. The Driftnote team launched on Product Hunt on a Tuesday, posted a Show HN that same morning, and posted to r/SaaS and r/remotework during the next three days. That sequence shows what a small team can actually do: a main launch, a cross-post, and targeted community posts.

Do not wait for a perfect channel. Write the post that answers the complaint instead of announcing a feature. A channel full of people who want to be early but have no budget is a sign-up channel, not a revenue channel.

Tag the source in the database, not the browser

Tag the signup source at the moment the account is created. You are done when a source field in your user table survives email, referrals, and delayed purchases. When a person clicks a launch link, leaves, and pays later, the source should still point to the channel that brought them in.

The mistake is trusting the referrer. A referrer can be blank, overwritten, or lost when the user returns through a different path. The Driftnote launch used UTM-tagged links and Plausible Analytics, a web analytics tool, for traffic tracking, and it stored signup source in the database instead of relying only on the referrer. Make the tag boring. A simple value like the channel name is enough. You do not need a tracking system that requires a data engineer. You need a field that lets you answer the question: where did the paying user come from?

Score signups against paid conversion after the launch window

Score each channel with a simple scorecard. Do not reward a channel for volume alone. A channel that sends a flood of curious signups and no payments is a leak, not a win.

• Signups from the channel
• Signup-to-paid percentage
• Paid revenue share
• Source tag in the database

The result is a table you can read quickly, with the paying channel obvious.

In the January 2026 Driftnote launch, Hacker News delivered 61% of total signups. Reddit delivered 9% of signups and 22% of paid revenue in that launch. During the 30-day Driftnote launch, Hacker News had the strongest hourly signup rate but the weakest paid conversion, Reddit had the smallest overall signup count but the strongest paid conversion, and Product Hunt fell between the two while its traffic lasted the longest.

Read the spread before you read the total. A channel can produce signups without producing revenue. A paid plan is the test. Protect the channel that produces paying users.

Keep the buyer channel and cut the attention channel

Keep the channel that converts signups into paid users. Put more effort where paid revenue share is strongest, and stop pretending the other channels are working just because they produced signups.

Cut the channel that only produces attention. Put that time into manual outreach, community answers, or direct conversations with the people who already use the product. Skip the tactics that need scale to work. Write to the users who already paid, ask what they need next, and use their answers to shape the next launch post.