Issue #27: Hello HeyEcho! šŸ‘‹

The Minimum Video-able Product

Last week I left you with a teaser, so Iā€™ll share more about HeyEcho today. šŸ„ 

Table of Contents

What is HeyEcho?

I introduced the idea already two weeks ago. The two biggest issues of using AI to generate content are:

  • not sound like AI-written,

  • sound like it has been written by ourselves by incorporating our own personal voice.

Solving the second one means solving also the first one (unless you write like a robot šŸ˜…), but I see them as two steps to be solved separately.

I discussed this topic also on Reddit in the last weeks and it was very interesting to read all the usersā€™ contributions on the topic. You can check it out here where I asked in all these subreddits ā€œHow much time do you spend on writing content? Do you use AI? What about maintaining the "brand/personal voice"?ā€:

Thatā€™s the reason for the name ā€œHeyEchoā€. The platform aims to be the echo of the ā€œselfā€ as in being able to replicate the usersā€™ voice during content generation. This is also reflected in the choice of the TLD .xyz that complements the concept of extending the user's voice and presence in a limitless, all-encompassing wayā€”reaching from "A to Z and beyondā€.

I also wanted to reflect this in the logo where the central circle represents the ā€œselfā€ and the arcs represent the echo as waves form spreading in the water when you throw a stone.

HeyEcho logo

This would be the core value, but it doesnā€™t mean it would be the only value proposition. Generating a blog post is the starting point, but Iā€™d like to pair it with a distribution on steroids. Thatā€™s where the experience of EchoWords to repurpose on X and HaveYouHeard to integrate with Reddit would be a great fit. Iā€™m still framing it in my mind, but I see it as some sort of CMS with an integrated AI-powered content generation reflecting the voice of the user/company, and integrations for publishing and repurposing on different platforms.

But for now, Iā€™m focussing on the core value as the starting point. The rest will come depending on what customers will experience.

Itā€™s still in alpha but hereā€™s what it looks like so far:

From a product perspective, itā€™s a very simple chatbox to gather the blueprint of what has to be written, followed by some steps to generate the content. The current output is still very AI-ish, but this week I focussed mostly on the UX rather than on the text quality itself. In my experience showing transparently to the user what the AI is doing under the hood generates trust, but that took some time to implement properly.

There are just a few steps implemented right now:

  • requirements gathering,

  • SERP research,

  • content drafting.

I still need to add humanization, add images, etc. Once I feel confident that this very single feature of building a blog with this interface produces a good-quality output, Iā€™ll be ready to start onboarding, but this should not stop me from marketing early on.

Next steps

From a marketing perspective, Iā€™ll start adding a ā€œSubscribeā€ button on the landing and generate some hype. This will allow me to build an email list I can use once itā€™s ready to be used by real users. Iā€™ll be more consistent with publishing updates on my social media and on Reddit to drive some traffic on the landing. Iā€™ll also reach out to the users who got involved in the discussions I mentioned above on Reddit.

From a product perspective, Iā€™m now all-in focused on making the content sound like written by a human. I expect this to take some time, but Iā€™m very confident. Next week Iā€™ll share more about the outcome of the approach I have in mind.

Conclusion

As always, time to push even harder! šŸ’Ŗ šŸ˜‚

I hope you enjoyed this update!

If youā€™re interested in following my journey, make sure to subscribe or follow me on X/Twitter and LinkedIn! 

Appendix

Personal branding

X

X Premium analytics

Beehiiv newsletter

Beehiiv Analytics

Reply

or to participate.