Running a Reddit AMA That Does Not Fall Flat

An AMA is worth doing when you can answer questions that only you can answer, and when those answers would still be interesting if your product did not exist. It is a bad idea when the honest premise is that you would like some attention. Most launch-week AMAs fail that test. So do AMAs run by a founder who cannot share a number, cannot describe a failure, and has been told to stay on message. The thread ends up sparse, and a sparse thread is worse than no thread at all.

Two other situations argue against it. If you have an unresolved support backlog or a recent outage, an open thread becomes a public queue and you will spend the hour apologising rather than teaching. If nobody in the subreddit recognises your username, an AMA asks strangers to generate questions about a stranger, which is work they have no reason to do. Both problems can be fixed with a few weeks of ordinary participation. Neither is fixed by scheduling the AMA sooner, or by writing a better title.

Message the moderators before you write anything else, normally two to three weeks ahead. Modmail should carry the premise in one sentence, the date and time window, who is answering and why they are qualified, the proof you can supply, and an explicit note that you are not there to promote. Ask which rules apply, whether they want a scheduled post or a particular flair, and how they want the affiliation disclosed. Moderators who agreed in advance tend to defend the thread later. Moderators who find out when it publishes tend to remove it.

Subreddit history gets checked, by moderators and by readers. An account created last month with no comments outside your own announcements reads as a marketing account, because it is one. Spend the weeks before the AMA doing what everyone else there does: answering questions inside your area of competence with no link attached, voting, and occasionally being corrected in public. Ten useful comments across a month is a low bar, and it changes how the first ten replies to your thread read to everyone who arrives later.

Verification is the cheapest credibility you will ever buy. Most communities accept a photo, a screenshot of an internal dashboard, a confirmation post from the company account, or a message sent from the company domain. Supply it during the modmail conversation rather than after somebody accuses you of being fake. If the premise involves a number, decide beforehand whether you will show its source, because the first person who asks will ask within ten minutes of the thread going live.

The premise is the reason somebody who has never heard of you clicks. Your product is not that reason. A working premise is a specific thing you did that members of the subreddit have also attempted: a technical problem you solved and can explain at whiteboard depth, a business number you will publish and defend, or a migration, rewrite, or pricing change you survived and can narrate honestly, including the parts that went badly and the month you lost to them.

Write the title as a claim rather than an introduction. A founder of a company saying they are a founder of a company offers nothing to extract. Moving forty million rows off a managed database over one weekend and breaking three things tells people exactly what they can get out of the next two hours. The stronger the premise, the less your product needs to appear, and the more comfortable moderators become about approving it. If you cannot state the premise without naming the product in the first clause, it is not ready.

Choose a premise you can still discuss at hour two, when the easy questions are gone and somebody asks for the part you left out. A premise built on a number is the most demanding version, because every follow-up is about method: what counted, over what window, and why that definition. Decide in advance which numbers are in scope and which are not, then say so in the post itself. Declaring a boundary is respected. Discovering one in the comments looks like a dodge.

Post when the subreddit is awake, not when your calendar is free. Check the timestamps on the last twenty threads that did well and take the same window, which is usually a weekday mid-morning in the community's dominant timezone. Avoid the day of a large release in your category, avoid holidays, and avoid anything else that will compete for the same readers. Announce the AMA in advance if the moderators allow it, so regulars can arrive with questions rather than waiting for somebody else to go first.

The first hour decides the thread. Early votes determine whether it reaches the front page of the subreddit at all, and the first two or three answers set a tone that later commenters copy. Block two uninterrupted hours, put a second person beside you to pull numbers and links, and take the hardest visible question early instead of clearing the easy ones. Answering something difficult well within the first ten minutes is the strongest available signal that the rest of the thread is worth reading.

Do not manufacture questions. Seeding a thread with friendly accounts is easier to spot than founders expect, and a community that spots it will spend the remaining hour discussing that instead of your premise. If twenty minutes pass with nothing arriving, the honest move is to add a comment expanding on the weakest part of your own premise, which gives people something concrete to argue with. Silence usually means the premise was thin, not that the community was busy.

Answer at the length the question deserves, which is usually 60 to 150 words: one direct sentence that answers what was actually asked, then the specifics that make it useful, then a caveat if one is honest. Opening with context and arriving at the answer in the third paragraph reads as evasion even when it is not. Specificity is the entire game. Name the tools, give the real figures, say when it happened, and mention the approach you tried first that did not work.

Say what you do not know, and say what you will not share. Admitting you do not have a number in front of you, stating the definition you use, and promising to edit the comment that evening is a good answer, provided the edit appears that evening. What you cannot do is answer a different question. Every reader can see the question you were asked, and a reply that quietly swaps it for a friendlier one costs more credibility than the uncomfortable answer ever would.

Sort hostile comments before replying. There is the customer with a genuine complaint, who deserves a specific fix and a date. There is the person who dislikes your whole category, who deserves one honest sentence and nothing further. There is the competitor, best answered factually and briefly for the benefit of everybody else reading. And there is plain bad faith, best left alone. Answer each type once. Arguing twice in the same subthread is the usual way a bad comment becomes the top comment.

Pricing complaints are the most common and the easiest to fail. The losing move is defending the price with value language. The answer that works names who the product is not for, what it costs you to serve a customer, and the trade-off you deliberately chose. Saying that it is expensive for a solo user, that the cheapest plan targets three-person teams, and that churn moved by a stated amount after the last increase tends to end the thread. Saying that it pays for itself extends it.

Do not delete, and do not edit silently. A visible edit line correcting yourself is respected; a comment that changed after somebody screenshotted it is not. If a thread turns genuinely hostile, ask the moderators for help rather than fighting it, and leave everything standing. Threads are permanent and searchable, and the record of a founder answering a rough question calmly is worth considerably more than the version where the rough question has quietly gone missing.

Come back at 24 hours and again at 72. Late arrivals often ask better questions than the live crowd because they have read everything above them, and answering them keeps the post surfacing. Edit the original post with a short summary of the three or four answers people found most useful, and correct anything you got wrong with a dated edit line. If you promised during the thread to ship, check, or publish something, return and say so when it is done, even weeks later.

The thread is now a source document. Questions you were asked repeatedly belong in your documentation, your onboarding, and your pricing page, phrased the way strangers phrased them rather than the way your team does. The answer you wrote at hour two about the migration is usually a better article than whatever sits on your content calendar. Do not republish the thread wholesale; take the questions, keep your own answers, and link the discussion as the place the material came from.

Measure it the way you measure any Reddit work, on a ladder from thread activity through assisted signups rather than one attribution number, and set the expectation before you start. A good AMA for a small company means a few hundred qualified readers, five to twenty real conversations, and a page that keeps arriving in search for a year. Tiptop's Reddit service sits in the workspace beside the live Listings, Influencers, and SEO channels, scoring threads on the same 0-100 scale.

For most small companies a formal AMA is simply the wrong size. It requires an audience that already wants to ask you things, which is the thing you were hoping the AMA would create. The formats below ask less of the community and generally return more, because each one begins with a contribution rather than a request for attention, and none of them needs moderator negotiation three weeks in advance.

A single deep post about one problem, with you in the comments answering for two days, is an AMA without the ceremony. A build-in-public thread works in subreddits that permit it, but the version that succeeds publishes numbers and decisions rather than milestones. A teardown of your own product, written by you and listing what it does badly, reliably outperforms anything you could say about what it does well, because it is the one post nobody expects a founder to write.

Comment-first work stays the highest return per hour on Reddit, and it compounds. After a few months of useful answers in threads you did not start, the AMA you could not justify this quarter becomes one that people actually show up for, with moderators who already know your name and a premise you accumulated rather than invented. Treat the AMA as something a track record eventually earns, not as the event that creates one.