Answer how-to questions in other products' forums

This tactic means finding people in another product's forum who are stuck on a how-to question, answering it in full, and only then naming your own product. At Zapier, Wade spent hours a day in other SaaS products' forums looking for people asking about integrations, and early customers came from that work. Each link sent only about 10 to 20 visitors.

How it works

The mechanism is simple. You show up where someone already has the exact problem your product solves, and you help before you sell.

1. Pick forums where your buyer asks for help. For Zapier, these were the forums of other SaaS products, where users asked about or complained about missing integrations.
2. Search for the problem every day. Wade did this for hours a day. At the time, Zapier was a side project and the founders still had day jobs.
3. Answer the question completely first. Wade explained how the person could reach the APIs and build the integration on their own.
4. Mention your product last, as the shorter route. Only after the help did he say he was building Zapier, which made those steps easier.
5. Repeat across many threads. One answer brings little. The value comes from volume and from reaching people at the moment of need.

The traffic per answer is small. A third-party newsletter write-up on Zapier reports each forum link brought roughly 10 to 20 visitors. The forum threads were where people were asking or complaining about integrations. The problem in those threads, connecting apps, is still the core of the product: Zapier's about page describes a platform that moves data across more than 9,000 apps. The full story is on the Zapier case page.

This sits inside a wider set of community tactics. The community-led growth playbook covers the operating model, and the Reddit marketing playbook covers what gets removed on one of the strictest platforms.

What it takes

Our estimate: about 20 hours of work, and about 21 days before you can read a signal. The hours go into picking five to ten forums, writing saved searches for your problem keywords, and writing your first 20 to 30 full answers by hand. Good answers take time because they must solve the problem without your product. The signal takes about three weeks because each answer sends a trickle, so you need enough answers live and enough visitors through signup before the counts mean anything.

What to measure

Visitors per answer link tells you which forums and question types pull readers. Tag every link so you can compare. A good reading is a few forums that clearly beat the rest. A bad reading is flat, thin traffic everywhere.

Signups from forum links versus other channels shows whether those visitors convert. Compare over the same weeks so seasonality does not fool you.

Founder hours per signup is the cost line. This tactic is cheap in money and expensive in time. If the hours per signup are worse than your other channels and are not improving, stop.

Activation of forum-sourced signups checks the main promise: people who arrive with a specific problem should reach value faster. See the activation entry for how to define it. If they activate no better than other signups, the targeting is off.

Removed or flagged answers is your early warning. Any steady rate means you are reading the forum rules wrong.

When it backfires

• Pitching first. Zapier's order was help, then mention. Reverse it and moderators may delete the post, and the host community remembers your name for the wrong reason.
• Too little thread volume. Each link sends a small number of visitors. If your problem comes up only a few times a month, the totals never add up.
• It depends on one person. Wade's version took hours a day. Once the founder stops, so does the channel, and handing it to a junior hire can lower answer quality.
• Answering questions you do not solve. Dropping your link into loosely related threads reads as spam and draws visitors who will not activate.
• Rules change. A forum can restrict links from new accounts or ban promotion outright. The tactics that stopped working teardown shows how platform rules end tactics like this.

Run it as an experiment

Hypothesis. Full answers to problem-specific questions in five target forums will produce signups that activate at a higher rate than our average signup, at an acceptable cost in founder hours.

Comparison. We recommend a fixed four-week window. A true split is hard because you cannot randomize who reads a forum. Compare forum-sourced signups against all other signups that started in the same four weeks.

What to log. For each answer: forum, thread URL, question type, minutes spent, date posted, tagged link, visitors, signups, activations, and whether it was removed.

Decision rule. We suggest you keep going if forum signups activate at or above your average and hours per signup fall over the window. Cut forums with removals or near-zero visitors after two weeks. Track it in the growth experiment backlog template, and use the growth experiment guide for the write-up.

How strong the evidence is

The grade is practitioner report. The numbers come from a third-party newsletter, not from Zapier itself. Zapier's own page only describes the product today. The sources do not show how many answers were posted, how many visitors became customers, or what any other channel produced at the same time. The claim that early customers came from this work is the newsletter's framing. The later figure of 600K users within three years is not attributed to forum answers, and many other things happened in that period.