Build in Public
Build in Public
3 min read

Where EmailToFuture started: a comment on r/futureme

How a FutureMe alternatives thread led me to share EmailToFuture — and how early users found the project.

The thread that started it

In March 2025 someone posted on r/futureme looking for alternatives after FutureMe stopped being free. The feeling was familiar: a yearly letter to yourself should not need a steep subscription.

I had already built a small free site for myself as a programmer — schedule an email years ahead, see a dashboard timeline without spoiling the content. So I replied with what I had.

What I offered

In the comment I explained the basics: schedule up to five years out, keep the surprise by not showing body content early, and keep the product free while costs stayed manageable. The link was simply emailtofuture.com.

That single reply is where most of the first wave of users discovered us. A month later I opened r/EmailToFuture and wrote the welcome post with roughly 500 signups already behind us.

Why this chapter belongs here

Build-in-public for EmailToFuture did not start with a polished launch thread. It started with answering a real question in a community that already cared about letters to the future. Everything after this — the subreddit, the feature megathread, the roadmap — grew from that discovery moment.

This archive keeps the permalink so the origin stays part of the product story, not just folklore.

Next: Welcome & founding story