[dorkitude]

Good point. We're not released yet, and there are probably < 100 people who have a good enough idea of what we're doing to really dig in and give us feedback

We'll edit the blog post to add a bit more background

update:

here's the working copy:

--

We make three kinds of APIs:

  -data collection APIs
  -data analysis APIs
  -data visualization APIs

For instance, if you had a social-local-mobile shopping app for the iPhone, you'd probably want to insert a rich event into Keen every time a user does one of the following actions: opens the app, does Facebook connect, likes/comments/shares an item, adds an item to their shopping cart, and completes a checkout. You send us this data using the collection APIs (https://keen.io/static/docs/data_collection/data_collection....)

Once your app is sending us stuff, your product manager may ask you to make her a little analytics dashboard, so she can agonize over it every morning. For instance, this dashboard could have answers to questions like "How many people opened the app each day over the course of the last week?" That question (and many way more advanced ones) can be answered using one of our analysis APIs (in this case, the Series API https://keen.io/static/docs/data_analysis/series.html)

Finally, suppose a few weeks later she's tired of staring at numbers and wants to see this information graphed visually in a line graph. That can be done using our visualization APIs (not yet released).

[rgraham]

I think the what here might be less important than why for pricing. It's easy to get a sense of your platform from your website, but who is your target customer and why are they paying you? Does this save them time? Money? Make them money? Got any scenarios or customer sketches?

[kirkers]

(Disclosure: I wrote the post)

These are all great questions. Thinking long-term, the answer should be yes to all of those questions. We should save time (and therefore money) and be a vehicle for increased revenue. And, we intend to do a lot more writing about how folks are using/could use/should use our product. At the same time, in the long run, we’re all dead. So, in the present, we’re looking to work with Series-A type companies who are in the midst of early product development. We want to work alongside them to understand their analytics needs and tweak our roadmap accordingly.

Those customer sketches/white papers are extremely important to us. We’re still learning (and probably always will be). It’s my hope that we will be in a position to blog about customer experiences soon. Dominos are certainly lining up for that.

[michelleclsun]

who is your target customer and why are they paying you? Does this save them time? Money? Make them money? Got any scenarios or customer sketches?

In addition to these questions, I'd also think about how to reach a point where customer feels a high switching costs. It seems that a service like yours can be offered by many, but the important competitive advantage is that the more customers have stored data on your service, the more 'expensive' for them to switch.

What part of your service increases in value the longer someone uses it? Is it the historical data of the customer's own app, or is it the cross-sectional data of apps in other categories? As mentioned above, mixpanel is a good example, so is new relic.