Finally! 🚀 

HeyEcho is publicly available! No invitation is required anymore!

I haven’t announced it yet anywhere, so you're among the first to know about this. 😄 

Congrats! 🤣 

Table of Contents

• Dogfooding helps

• I never tested login with username and password

• Why the hero image is always very similar?

• Moving HeyEcho out from Framer as well

Dogfooding helps

In the last two weeks, I started generating blog posts for NextCommit, and I’m going to tell you a secret. 🤫 

In order to copy the raw content and paste it I accessed the database. 😅 

That’s because copying it from the editor was a mess…

So, I shipped a button to copy the raw content. TBH other users told me this, and yeah, I felt their pain.

But no more! ✨ 

However, the copied content is still not optimal. The hero image is currently shared as a b64-encoded image, so the copied content is VERY long. In the future, I’ll move these to object storage to make them available through a simple link pointing to a CDN.

I never tested login with username and password

This week I had the first beta user join using email and password (not using Google). Guess what? It was bugged. 😂 

When listing the blog posts, I show who the “author” (or the person who generated the blog and/or edited the output) is. This consists of extracting the name from the user profile associated with Clerk. However, in the case of non-Google, these are not available, so HeyEcho was just breaking.

I just patched it to prevent it from breaking, but I will provide a way to add that information in the future.

Why the hero image is always very similar?

It’s been a few weeks already that I’ve been wondering why the hero image was always very similar and 90% of the time showing the very same damn cloud… This week I had the time to check it out.

It turned out that I thought I was passing the content of the blog post to the prompt, but in reality, I was always passing an empty string. 😅 

What did I learn from this? That a cloud is the visual that DALLE thinks is the most appropriate for a generic SaaS. 😂 

Moving HeyEcho out from Framer as well

Last week I mentioned how my SaaS template is now offering a way to have a landing and a corresponding blog.

This week I also migrated HeyEcho! The new landing is a bit fancier, has its own blog, and ofc it now has a pricing section.

Check it out!

I still need to generate articles for the blog, but everything is ready! 🚀

This also means another 20€/month saved by dismissing Framer.

HeyEcho pricing plans

The pricing is very simple:

• a free plan with 1 blog post per month,

• 3 different plans with an increasing number of blog posts quota per month,

• a cost per blog post that decreases with quota.

The current price tags are what I call “Pioneer pricing”. In the future, I will increase them to “Launch pricing”, and then to “Standard pricing”. The price is grandfathered, this means that someone joining now would maintain the “Pioneer pricing”. 🤝

Ofc this is the initial idea and the execution will depend on how things will evolve.

Conclusion

I’m excited for the upcoming weeks! Now that the product is publicly available I will try to focus more on customer acquisition and content marketing. 🤞

Let’s close the first deal! 🔥

I hope you enjoyed this update!

If you’re interested in following my journey, make sure to subscribe or follow me on Bluesky, X, and LinkedIn!