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
- How Do We Continue Moving Green Button Data And APIs Forward?
- Beyond Public APIs In Government: Internal Access to Resources
- Can You Show Me The ROI On All Of This API Stuff Before We Commit
- In The Future APIs Will Be Default For All Cities
- No Public APIs Are Not Going Away Just Cause A Few BigCos Fumble At It
- Internal API Search Engine For Everyone At Your Company (Not Just Developers)
- If You Need Assistance With Your Healthcare API Strategy I Have The Person
- Explaining APIs To Senior Leadership: Access To Company Resources Without The IT Hassle
- A Conversation With @ijroth, @dorkitude, @antonyfalco, and @medjawii In The Next Generation API Stack Panel @APIStrat
- API Evangelist Thoughts On The Right To An API Key And Algorithmic Organizing
- Explaining APIs To Your Senior Leadership
- An API Evangelism Strategy To Map The Global Family Tree
- Thank You For Your API Evangelist Blog(s)
- Video From The Hypermedia Panel At API-Craft In Detroit Last Month
- Please Open Source Your API Before Shutting It Down
- Explaining My Work Around APIs In Higher Education To Institutions
- You Can Have An API Just By Choosing Products And Services That Have APIs
- Using Excel As An API Datasource And An API Client For The Masses
- Brewing Up Something Awesome With The Jive Software API
- Relationship Between APIs And Containers
- Real-time and Visualizations Will Be Key in Financial API Deployments
- Notification Focused Startups Within Leading API Ecosystems
- APIs That Do One Thing And Do It Well Like ZipLocate
- Which API Do I Need?
- The Expanding API Conference Landscape