Posted on 03-19-2013
I wrote about the web to API service Import.io earlier today, and before I close the Evernote for this story, I wanted to highlight something else I thought they did interesting, on their pricing page.
I thought they provide a very honest peak into how they are pricing their services. First off, they admit that they are a young company, which is cool, but they also lay out some pretty interesting points around their business philosophy::
- We are a free service. We will always provide a free-to-use tool
- We will introduce premium features. Some of these you may have to pay for
- We will always provide you with a tool to export your connectors
- We will let you know if we are going to change anything that may impact your usage of import.io
- We are currently in Developer Preview. Some things might not work as expected
- Free accounts may be volume-limited as we move from Developer Preview to production
- We will never spam you or share your details with any third parties
All of these points are something I feel ALL startups should commit to as part of their services to their users. One thing I'd also like to see from startups, is some mention of their exit strategy. What is the end goal? I think this is a relevant question for all startups, as is also good one for Import.io after the Google acquisition and shut-down of a similar service called Needlebase, back in 2012.
My goal isn't to pick on Import.io, but along with the other items they outline, I think all API startups should be openly discussing everything listed above.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Someone Please Build My Open, Interactive, Portable, And Visual API Documentation Toolkit
- Dwolla Using Slate For An Evolved API Documentation Experience
- Crazy Mess Of URLs Across 400 Of The APIs In My Stack
- Reworking My API 101 Content: Consuming APIs
- I Need Help To Make Sure The Dept. of Agriculture Leads With APIs In Their Parks and Recreation RFP
- What Is The Biggest Challenge For Fraud Detection API SiftScience?
- Reworking My API 101 Content: Providing APIs
- What I Spent Ada Lovelace Day Working On
- An Outside-In Approach To Jumpstarting An API Effort At The University of Oklahoma
- Exposing Dictionaries From My API Collections