1
1 Comment

I Built This Because I Was Tired of Chasing Followups Myself

You finish work.

You send a message.

Then you wait.

And somehow, the hardest part of the job becomes the follow-up, not the work itself.

Not invoices. Not just one use case.

Everything.

  • “Just checking in…”

  • “Any update on this?”

  • “Following up again…”

Same message. Different context. Same awkwardness.


The Part Nobody Talks About

Follow-ups are a hidden tax on your focus.

It’s not the writing that’s hard.

It’s the emotional overhead:

  • How soon is too soon?

  • Am I being annoying?

  • Should I sound firm or polite?

  • Did I already follow up too many times?

So you procrastinate.

Then overthink.

Then send something vague anyway.

And repeat.


I Looked for a Tool. Nothing Fit.

Everything I found assumes follow-ups are already structured:

  • CRM sequences

  • sales automation tools

  • reminder apps with static templates

But real follow-ups aren’t workflows.

They’re just:

“I’m waiting on someone.”

And none of the tools solved the real problem:

I didn’t want to manage follow-ups.

I wanted them to just happen.


So I Built It

I built autoremind.ai.

You describe the situation in plain English:

“Waiting on client approval for a project. No response for 5 days.”

And it:

  • writes the follow-ups

  • sends them automatically (Email / Slack / Teams)

  • escalates tone over time

  • stops when someone replies

No templates. No sequence builders. No CRM setup.

Just: describe → send → forget.


What It Actually Does Well

It’s not just for invoices.

It works for:

  • client approvals

  • project feedback

  • sales replies

  • job applications

  • partnerships

  • basically anything “waiting on someone”

The core idea is simple:

If no response, the system follows up so you don’t have to think about it.


The Honest Part: Zero Users So Far

Launched recently.

Right now:

  • a few signups

  • a few clicks

  • 0 active users

I’ve posted on Product Hunt, Reddit, X, LinkedIn.

No traction yet.

Either:

  • distribution is wrong

  • positioning is off

  • or the problem isn’t painful enough yet

Still figuring that out.


What I’m Trying Next

Before I kill or pivot it:

  • focus on a narrower use case (probably “unpaid + unresponsive clients” first)

  • improve onboarding so it feels instant, not setup-heavy

  • validate via direct users, not posts


Honest Question to Founders

Do you think this is:

  • a distribution problem

  • a positioning problem

  • or just not a painful enough problem to solve?

Trying to figure out which one I’m actually dealing with.


If This Sounds Familiar

If you’ve ever rewritten a follow-up message more than once before sending it…

you already know the problem.

Try it here: autoremind.ai (free plan, no credit card)

posted toAvatar for product autoremind.ai
autoremind.ai
  1. 1

    I'm the founder of autoremind and I built this because I kept losing hours every week writing the same follow-up emails over and over.

    The breaking point was chasing an overdue invoice for six weeks. Polite first message. Slightly firmer second. Awkward third. By the fourth I genuinely didn't know what tone to use anymore. I thought "there has to be a way to just describe what I need and have something handle the escalation for me."

    So I built it. You describe the situation in plain English, and autoremind handles the rest. It writes the message, sends it, and automatically turns up the pressure from professional to firm to urgent until you get a reply. Slack and email (Gmail OAuth) are both live today, with Microsoft Teams coming very soon.

    I'm a solo builder, so I'd genuinely love your feedback