Finding a person who needs your product is only half the job. The reply decides whether you help them and earn some trust, or annoy them and the community they are part of. This framework is simple on purpose.
1. Answer first
Start with a direct, specific answer to the question that was asked. If there is a free or built-in way to solve it, say so. If another product is a better fit, say that too. A reply that would be useful even if your product did not exist is the kind communities welcome.
2. Mention your product at most once, and only if it helps
If your product genuinely solves the problem, mention it once, explain what it does in one sentence, and link to it if the community's rules allow links. Do not repeat the pitch, add a list of features, or ask for a sign-up.
3. Disclose your affiliation, every time
A short, plain statement such as "Disclosure: I built this" is enough. Many communities expect it, some require it, and readers trust a disclosed recommendation more than a disguised one. Never pose as a neutral user.
4. Respect the community's rules
Each subreddit, forum and Q&A site has its own rules about self-promotion, links and account age. Read them before posting. If a community does not allow product mentions, either help without one or do not reply.
5. Post yourself, and stay for the follow-up
Post from your own account and answer follow-up questions. A conversation is worth more than a one-off link. If someone is not interested, leave it there.
A short example
Someone asks how to get alerts when a scheduled job silently stops running.
The usual pattern is a "dead man's switch": the job pings a URL when it finishes, and something alerts you if the ping does not arrive on time. You can build a simple version with a small script and any uptime checker. I built a hosted version of this, linked here, in case you do not want to run it yourself. Disclosure: it is my product.
The example is illustrative. It answers the question with a general pattern first, mentions the product once, and discloses the affiliation.
How Distrarc applies this
Reply drafts prepared by Distrarc follow the same rules: answer the person's actual question first, mention the product at most once and only when it helps, and include a plain disclosure. Drafts are suggestions. You review and edit them, and you post them yourself; Distrarc never posts for you.
Related: channel guides for platform-specific etiquette, and perceived value and buyer effort for why this approach tends to work. To see drafts for your own product, start with a free first report or compare plans.