8

Ask HN: How did you establish and maintain relationships with your first users?

 2 years ago
source link: https://news.ycombinator.com/item?id=27959475
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Ask HN: How did you establish and maintain relationships with your first users? Ask HN: How did you establish and maintain relationships with your first users? 41 points by dwrodri 4 hours ago | hide | past | favorite | 14 comments I'm currently working on a side project and will be searching for early users / alpha testers in the near future. Our target demographic is established, but we want to keep an open mind as we iterate on the product. Anyone have any "dos" or "don't"s that you can share? Also, sharing a brief description of the product/service itself would be really helpful as well.

For context, I am working in the computer vision space.

A community Discord has worked well while building Print Nanny, which monitors 3D printers using computer vision. https://www.print-nanny.com/

I love that people share their latest projects, chat about experiments. 3D printing is such a creative hobby and I'm constantly amazed with the ingenuity I see. Really helps me stay motivated through the night/weekend grind.

A few stats about my beta program:

* Roughly 2,200 applications for the private Beta program

* 200 beta invitations sent

* 100 actually used the product

* 180 hanging out in Discord

* 6 months of nights/weekends development

* 10 paid Beta spots offered, sold out in 2 days

I do support over email or Discord.

I think event-based analytics like Posthog are more valuable than a chat bubble integration, if you have to choose 1 to implement. People often tell you more with their actions than with words.

(Edited list formatting)

I'm building a public discussion site (https://sqwok.im). So far I've learned a few things:

1) Most people will happily give you feedback. Some of it will be good, some of it you won't agree with, but keep an open mind, and always thank them.

2) I go out of my way to tell new users that I appreciate their taking the time to check out the site.

3) If you get the opportunity, engage with your early users and talk on a human level. Many times that simple act of connecting and having a conversation with another person will spark an increased interest in the success of the project and you'll find that people will reach out to you when _they_ have an idea or suggestion.

4) List your email and/or a phone number if applicable, and likewise if you're having a good conversation with someone, ask if they'd be ok with you emailing them with some follow up questions. I've had a few people whom I got to know a fair bit and have exchanged multiple emails.

5) Lastly, I've made one specific mistake that I'm learning from, which is to _not_ neglect your early users. That is, when people start to show interest in your product, make sure to show up each and every day to interact with them and keep the interest up. I've had a few periods where I went into a development k-hole for weeks on end and wasn't as active on the site, which led to a decrease in overall activity.

Good Luck!

Assuming your users are also users of Slack, I highly recommend creating shared channels; that way, they can reach out to you in your slack, without leaving their own. Email is great, but there is something about IM that feels way better.

Also, if you are offering your product/service for free initially, I would say, "it's free, but in exchange you gotta give us 20 minutes on a call every week/every other week". This ends up being super valuable.

Dos:

1. Buy a tollfree phone number and list it your website. Some people like to talk to a support agent rather than email.

2. An official email makes the business appear legitimate. Have an [email protected].

Don'ts:

1. I didn't have good experience with website chat widgets as I found them confusing to configure and that generated numerous low quality interactions.

2. Since the volume of emails is low initially, better to avoid email automation as that can take up a chunk of time to set up. Start with manual emails and once you know which email copy evokes a response, you can think about automating them.

s.gif
This makes a lot of sense: Ideally, we'd want a small (<20) amount of "future power users" as our focus group, since we imagine these users would provide us with the most most powerful growth via word-of-mouth if we work extra hard to make that initial focus group happy.
If your users sincerely have a pain point and think you can solve it, they will usually be happy to give you lots of input and feedback. This requires two things- intending to solve a real problem that users care about and being credible. You can increase the second aspect by communicating with and listening to your core and ideal customers, and getting to know not only if the problem matters, but what they care about in the context of that problem. There's a maxim that the value of your product is what your customers think it's worth. Learning from them why they care will increase your chances of building strong early relationships.

Mechanically, regular communication that offers value via email, plus actual conversations that are informational not sales-y.

From being the person doing this at both B2B and B2C companies in early stage.

I did a public chat. It was a pain to code and a bigger pain to moderate. But it worked extremely well. A side effect is we never got bad ratings because anyone could just make an anonymous account and rant and complain where we'd see it. We ended up with two WhatsApp groups that lasted longer than the app itself.

I tried doing a Discord server for it recently but it doesn't have the anonymity effect.

s.gif
your product was a public chat? how did you market it/what was your plan for it?
Reaching out to them manually on Twitter. DMs are surprisingly effective.
Get to know them. Some might be wackos but just limit your time, not your conversations.

You want to be open to radical departures from the current implementation. You may think you know everything but before you have customers you actually know nothing

It may seem simple, but list an email address on the website and invite people to use it. Whether or not you have a DIY free trial or signup, you’ll want to make it easy for interested parties to contact you with questions before starting to use your project.
I just have free apps, so I didn't do much. There's an email they can contact me at. I have recieved a few requests for enhancements through that.

I also run a honey business. I tell people to follow our facebook page so they get an alert when we have a harvest since quantity can be limited. I'm also working on a website with an email list.

s.gif
My product is a web B2C SaaS that will be initially targeted at hobbyists/beginner/intermediate programmers, so I think getting them to believe in the product will either require a killer demo or a free tier they can play with which provides them with value.

Do people really just start showing up if the service has a free tier? I'd assume you did some basic marketing.

s.gif
The free apps I have are not very popular. I did try some basic marketing, but it wasn't that successful.

I would guess the best marketing you can do for a developer tool is to create tutorials around whatever problem you tool solves. I know I tend to stumble across stuff when googling "how do I do...".

s.gif Applications are open for YC Winter 2022
Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search:

About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK