6
5 Comments

How often should you update early-adopters? 🗣

When building in public - how often should you let your early-adopters know about updates & product changes? What kinda thing goes down well?

Please share any successes / challenges you've had keeping folks engaged as the product evolves... 🌱 👇

on March 9, 2021
  1. 2

    With Kbee, we've been sending out updates every other week. At the stage we are at, there are at least 5 new features that get rolled out in that time frame and most of our customers are early adopters who want these updates.

    We see a pretty significant lift in usage when we send these out, including people committing and paying for a plan.

    Early adopters are invested in your success, so I feel safe in saying that they want more updates. As your product matures, you will probably slow this down naturally.

    1. 1

      Oh wow, okay, that's cool.... and that's awesome that you're shipping enough features each week to justify it.

      I guess I worry that most of what we ship each week is just small increments so I was worried that weekly would be too much.

      I also figure that we've not done that from the start... whereas, if your consistent and folks are expecting the update that probably help.

      Kbee looks cool btw. 🙌

      1. 2

        Weekly is probably too much haha, even two weeks like we are doing is a lot for most apps. It helps that there are two of us working full time on Kbee, so we ship a lot.

        I wouldn't worry about not having done it from the start. Just make sure you are consistent and provide value. It's ok to skip an update if nothing major happened.

  2. 2

    As a user I would say that a young product requires more updates, say once a month, whereas a more developed product maybe once a quarter.

    1. 2

      I agree, once a month feels like a happy medium to remind me about the product, without overloading my inbox.