3 ms·

I am glad to see an example of a better-built API which has pricing terms attached. For someone working in a corporate setting who needs a great off-the-shelf A

I am glad to see an example of a better-built API which has pricing terms attached. For someone working in a corporate setting who needs a great off-the-shelf API to get an integration working ASAP, it seems to be just at the threshold of needing a purchase order to get it. For 'goksan, I'm curious what kind of research you did on the customer base for this, and how you thought through pricing? It feels attractive to me, but curious if there's more rigor involved there.

goksan 4y ago
Hey, thanks for commenting. The API still a subset of the Airtable API for the moment to avoid requiring rewrites of existing integrations. I do plan to expand the API in the future to enable novel features. Most of my research is in talking to other engineers using Airtable, admittedly none used Airtable as widely as we did at my last job. I want to deliver the best possible experience for Airtable API integrations, and I believe pricing in the speculated range is necessary to sustain that focus. It's something I'm still thinking about. Moving out of Airtable and replicating all of it's goodies is a tricky and expensive task, I'd like to help customers avoid that where possible, or delay it at the very least.