|
|
|
|
|
|
by patio11
5125 days ago
|
|
|
Apropos of nothing: if one is making decisions based on estimates of probable conversion rates, my ballpark for "web page visitor -> makes at least one API request" would be closer to 1/100th of 2% than to 2%. You're probably better off going for an intermediate conversion (cough get their email cough) and then selling them into using the API over time, since this is a thing that the best prospects won't exactly do on a lark. (I am unsure of whether I like the make-a-play-in-the-browser-utility suggestion from the perspective of the business. I have never work directly on that question for a client, so I don't have even anecdata for y'all on this, but the developer in me says "That's a great idea! That way I don't have to do any work to kick the tires." and the marketer in me says "If we sold 'tire kicking' that would be wonderful now wouldn't it") |
|
|
Firstly- its a great way to engage with users where you might not offer exactly what they want (do you print canvases, how about xyz). We get most of our feature ideas from our users wanting something that we don't yet offer.
I also try and schedule in a Skype call with all of our users to understand exactly what they want from us, and how we can help them (I think this also convinces them that there's a real person there they can do business with).
Once we've got their emails, we probably convert about 20% into 'making API calls'. However, I'm expecting that to increase over time (lots of people sign up, but are just working out how they're going to build their app, rather than actually doing it).
It's also worth following up non-active users after 1,3 and 6 months. You can often get useful info that you'd otherwise miss 'we decided not to use you because x,y,z; we canned the project but are keen to use you in the future etc)