RetireRangers: our first weeks running Flyzio, documented

The problem

RetireRangers is a retirement planning tool for German ETF investors. We had the product. We had a handful of users from direct outreach. But organic growth was zero.

We knew our audience lived on Reddit — r/Finanzen, r/ETFs, r/personalfinance. People posted questions there daily: which ETF broker to pick, how to set up a Sparplan, whether to bother with a Freistellungsauftrag. These were exactly the conversations where our tool added value.

The problem was finding them. Manually, you'd check subreddits a few times a week and hope to catch the right thread before it scrolled off. We missed more than we caught.

The setup (20 minutes)

We installed Flyzio and configured three things:

• Subreddits: Finanzen, ETFs, personalfinance, Vermögensaufbau
• Keywords: ETF, Freistellungsauftrag, Depot, Sparplan, Altersvorsorge, Rentenlücke
• Hot keywords: "welches Tool", "gibt es eine App", "Empfehlung" — phrases where someone is actively looking for something

Voice was set to "founder". One-line product description: "RetireRangers helps German ETF investors plan retirement — we calculate your Rentenlücke and build a personalised Sparplan."

Day 1–3: watching the queue fill

The first scan ran immediately. 47 threads surfaced. Most were low-scoring general discussion. Eight had hot keywords. Three were recent enough (under 3 hours old) and specific enough to be worth replying to.

I read all three threads. Flyzio had generated draft replies for each. The drafts were genuinely good starting points — they acknowledged the specific question, gave a useful answer, and mentioned RetireRangers naturally at the end. But I rewrote each one to add something only I could know: a specific number from our data, a nuance about German tax law that a generic answer would miss.

That editing step takes 10–15 minutes per reply. It's worth it. The reply doesn't read like a marketing comment. It reads like a person who knows the subject happened to mention they built a tool for this exact thing.

The replies we posted

What the log actually shows

We'd rather show you the mechanism than a hero number. Over the first weeks the activity log recorded threads scanned across our target subreddits, a handful of hand-reviewed replies posted (we cap ourselves at ~3/week, following the safe posting schedule), and the engagement each earned — score, upvotes and reply counts tracked for 7 days after posting.

That's the honest picture: a small number of genuinely relevant comments, at an acquisition cost of essentially zero, in a channel where the audience is actively asking for recommendations. The live case study page shows the current numbers, fed by the real log rather than a polished claim — including the weeks it's slow.

What we learned

• ✅ Hot keywords are everything. Threads where someone asks "does a tool exist for X" perform noticeably better than general discussion.
• ✅ Edit the draft. A generated reply is a starting point, not a final answer. Add one specific fact only you know.
• ✅ Fresh threads only. Replying to threads over 6 hours old wastes your daily reply budget.
• ✅ Niche subs convert better. r/Finanzen outperformed r/personalfinance for our German-focused product by a wide margin.
• ❌ Don't post daily. We posted 3 replies week 1 and 3 replies week 2. Week 3 we pushed 5. Week 3 we got a warning from Reddit. Back to 3/week max.