FeedHive

FeedHive has just launched!
It's now live, and open for everyone to sign up.

Simple go to:
https://feedhive.io

We also just launched on Product Hunt:
https://www.producthunt.com/posts/feedhive

This has been an amazing ride so far!
I hope you'll all get to enjoy using FeedHive.

Today I rolled out a paid plan on FeedHive.
This means that some of the current users got downgraded to a free plan.

Within the first couple of hours, 3 users decided to upgrade FeedHive to the paid plan.

This feeling is absolutely amazing!
Especially given that FeedHive has not officially launched yet.

The launch date is set to February 6th, 2021 - that is exactly one week from now.

Needless to say - this is a super promising start!

I made a public announcement on Twitter with a small presentation/promo video.

The interest really surprised me.
This tweet took off and spread around Twitter fast.

It quickly got +1000 likes and a lot of comments.

• Anyone having tried to announce paid products on Twitter knows that it's extremely hard to get traction on it.

I was super excited to see the reaction to this.

See the tweet here:

After a few more weeks of developing - this time with great help and feedback from the first early adopters - it was time to let a few more users in.

I announced the product in my monthly newsletter and letting around 800 people know about FeedHive.

100 more people quickly signed up, and a few stuck around to use the product.

After developing on FeedHive for a few weeks, I decided to get the first early adopters on board.

After having spent most of the year on Twitter, I've been lucky to have built a strong network on the platform.

So I reached out to a few people, and they started using FeedHive right away.

At this point, the product was super limited.
You could do two things:
Write a tweet and schedule it.
See your tweets in an overview.

But the support from the early adopters was amazing.
It became very clear to me that people really needed this product.

This was where it all started.

I needed something to manage my Twitter workflow.
Twitter's UI was horrible for scheduling. Thus it didn't allow for scheduling threads.

The alternatives out there were either super pricy, really clunky, insufficient for my needs - or a good mix of all.

For a while, I had been using my own custom setup for scheduling, which included a handful of cloud functions and a CLI tool.
Tweets were written in YML files.

Starting a new product that is already covered by plenty on the market already is always scary.

But I decided to go for it anyway.