Launch day is next week. The product works on sample data, the announcement draft is open, and the distribution plan says “Product Hunt, Reddit, LinkedIn, SEO.” That is not four channels. It is four unanswered questions about access.
Start with doors you can actually open
A channel is usable only when you can name the people or context, explain why your presence belongs there, and carry the follow-up yourself. “Reddit” is a venue. “A community where operators already compare missing-document workflows, with a rule that permits vendor participation in a named thread” is a possible route.
Build the map from access you have today. Existing relationships may offer a relevant introduction. A community may allow a useful teardown. A partner may be willing to inspect a workflow that affects their clients. Public business information may support carefully targeted outreach, subject to the rules and laws that apply. Product-led questions may eventually justify search content. None of those routes is automatically first.
| Route | Access evidence | Permission check | What the test can reveal |
|---|---|---|---|
| Introductions | A named person can judge the workflow or make a relevant introduction. | The request does not imply endorsement and gives them an easy decline. | Whether the problem wording is recognisable to the intended role. |
| Community contribution | A specific discussion already contains the job your product addresses. | The platform and community rules permit the proposed contribution. | Whether the example attracts concrete workflow questions. |
| Direct outreach | A public business trigger creates a defensible reason for contact. | Identity, targeting, suppression and applicable legal requirements are checked. | Whether the role and trigger are specific enough to merit a reply. |
| Partner review | A service provider already sees the workflow in legitimate client work. | No client information is requested or shared without authority. | Where the product would create value, risk or extra support work. |
| Search page | A recurring, privacy-safe product question has been documented. | The answer can be published without exposing a person or private account. | Whether the question deserves a supported public answer—not whether traffic will arrive. |
The rule check comes before the copy
Platform access is conditional. Product Hunt’s official launch guidance, observed on 2026-07-28, says makers may submit their own products and do not need a third-party hunter. It also says to ask people to visit or comment, not to upvote. Those are Product Hunt rules, not a promise that a listing will be noticed.
Reddit’s official spam policy, also observed on 2026-07-28, prohibits repeated or unsolicited mass engagement and tells users to check each community’s rules. A subreddit can still reject a post that appears acceptable under the site-wide policy. Read the current local rules before the test; do not make throwaway accounts, simulate independent interest, mass-message members, or repost the same pitch across communities.
Choose one route with a decision card
Skip the weighted scoring model. It creates decimal confidence from weak inputs. Use a short card and force a choice:
- Reachable context: name the source of access, not the platform logo.
- Eligible person: define the role and the observable trigger that makes the problem relevant.
- Permitted action: state what you may do and which rule you checked.
- Useful object: choose something inspectable—a sample input/output, a workflow sketch, or a narrow product walkthrough.
- Observable signal: decide what would teach you something: a correction, a specific question, a workflow description, or a clear non-fit reason.
- Stop condition: name the event that ends or changes the test.
A launch record with no success story attached
Illustrative scenario, not a real launch or customer result. A founder has a product that turns emailed contractor updates into a draft weekly report. The founder knows a project coordinator who can critique the workflow and has access to a construction-operations community with a designated vendor thread.
Chosen route: the permitted community thread.
Object: a fictional update email beside the draft report it produces.
Question: “Which part of this draft would still require manual checking before it could enter your weekly process?”
Boundary: no claim about saved time, fewer errors, or customer use.
Stop or revise: stop if the thread rules do not permit the post; revise the segment if eligible readers say the report belongs to another role; revise the object if responses discuss presentation but not the workflow.
There is deliberately no contact count, reply target, or expected sale in this example. Those values need a real operating capacity, an observation window, and an authorised log.
Run the pre-mortem before launch day
Imagine the test produced nothing you can interpret. Which failure happened?
Route failures
- The people present do not own the job.
- The community does not permit the contribution.
- The public trigger does not justify contact.
- The founder cannot research and answer carefully.
Message and product failures
- The example hides the actual input or handoff.
- The claim asks for more trust than the proof supports.
- The product addresses a different moment in the workflow.
- Polite interest produces no specific question or correction.
Do not “solve” either list with more accounts, automated messages, or a broader blast. First determine whether the route, object, audience, or product assumption failed.
A route is either ready or it is not
An empty launch calendar can feel like a marketing emergency. Treat it as a routing problem instead. One legitimate door and one inspectable object can support a decision; a stack of scheduled announcements cannot.
Keep a factual launch log: rule checked and date; eligible segment; access source; object shown; questions, corrections and objections received; opt-outs or removals; founder time required; and the resulting stop, revise, or continue decision. These are observations, not a benchmark.
Choose the single route for which you can name access, permission, object, signal and stop condition. If one of those fields is blank, do not launch through that route yet.