3
6 Comments

I got tired of paying more every time my email list grew, so I'm building QeakFlow

After months of research, talking to small business owners, and reading countless discussions here and on Reddit, I finally launched the first landing page for QeakFlow.

The idea came from one recurring frustration:

Why does every email marketing platform become more expensive just because your subscriber list grows?

Many small businesses don't need a CRM, AI features, landing page builders, or dozens of integrations. They just want a simple way to send newsletters at a predictable price.

That's what I'm building:

• Flat monthly pricing
• Bring your own SMTP (keep control of your sender reputation)
• Simple campaign management
• GDPR-friendly
• Built for small businesses, not enterprise teams

The product is still in development, and I'm currently looking for beta users to help shape it.

If this sounds like something you'd use, I'd love to hear your thoughts.

👉 https://qeakflow.com

on July 20, 2026
  1. 1

    Going this narrow is the right call. I sell to the same segment (trades and home services, in Canada) and everything you wrote matches: they don't compare features, they compare 'does this earn me one more job than it costs per month.' The buying trigger is almost never a feature list — it's one specific painful miss they can name. If that holds for German tradespeople too, your best landing copy is probably a story, not a benefits grid. And +1 on ecommerce being a different species — a plumber and a Shopify store share nothing about how they use their inbox.

  2. 1

    The pricing frustration is real. Paying more just because the list grew feels like a tax on doing the thing that matters.

    BYO SMTP is an interesting wedge too. Control and predictable cost together is clearer than “yet another simpler Mailchimp.”

    Main risk I’d watch: “simple email tool” is a crowded shelf. The sharper the buyer (“local businesses who only send monthly newsletters and hate per-subscriber pricing”), the easier this sells.

    I built Make it RAIN for creators monetizing products, so I’m biased toward clear ICP early. Flat pricing alone may not be enough without a specific “this is for you” sentence.

    If I were beta testing, I’d want to know the exact flat price and what breaks when someone hits 10k subscribers.

  3. 1

    This really resonates, I'm building in a totally different category but from the exact same "why am I paying for 40 features to use one" frustration. One thing to watch with flat pricing though: the single huge sender whose volume blows past your flat price while your revenue stays flat, that one case can quietly eat your margin, so a soft cap or a second tier keeps the "predictable price" promise without the downside. Bring-your-own-SMTP is a smart move too, it pushes deliverability cost and sender reputation onto the user, which is exactly how you stay cheap. Who do you picture as the main switcher, someone leaving Mailchimp on price, or someone who never wanted a full suite to begin with?

  4. 1

    The predictable-price idea is easy to understand, but “small businesses” can mean very different email habits. Are you looking for your first beta users from one specific group — newsletters, local businesses, or ecommerce stores — or are you deliberately keeping it broad to learn where the frustration is strongest?

    1. 1

      Deliberately narrow.
      The first group I'm focusing on is local service businesses
      in Germany - tradespeople, real estate agents, small consultancies.
      They share a specific pattern: a warm list of 200–2,000 customers,
      wanting to send a monthly newsletter, and either left Mailchimp
      because it got expensive or never started because the setup
      felt overwhelming.
      They don't need automation workflows or ecommerce integrations.
      They need to send an email and see who opened it.
      The reason I'm not keeping it broad is exactly what you're pointing at -
      "small business" frustration varies too much by use case
      to learn anything useful from it. A local plumber and a Shopify store
      have completely different email habits and completely different
      reasons to be unhappy with their current tool.
      Ecommerce is explicitly out of scope for now -
      the integrations those stores need take months to build well
      and aren't the problem I'm solving.
      Starting narrow also makes the first conversations easier.
      I know what to ask, I know what the friction looks like,
      and I know when feedback is signal versus noise.
      Are you working in one of those segments?

  5. 1

    I like that you're challenging the pricing model instead of assuming the feature set is the problem.

    I'll be interested to see what beta users consistently describe as the reason they switch. That tends to reveal whether the product is really about predictable pricing, sender control, simplicity, or something else entirely.

Trending on Indie Hackers
I built a web-based vector editor from scratch and integrated an AI Agent. Need just ONE beta tester! User Avatar 65 comments I built an AI that turns an idea into a live business in under 10 minutes. Here’s what 1,000 launches taught me User Avatar 31 comments Building Noodle, a keyboard-first REST client for the terminal User Avatar 23 comments "Looks Good to Me" Is Quietly Killing Your Feedback Loop User Avatar 22 comments Launched 580 landing pages in 1 week. Solo. No team. User Avatar 18 comments What Building a Local Dumpster Rental Business Taught Me About Customer Intent User Avatar 7 comments