We're in the exact same bucket at geocod.io[1]. I definitely agree with the sentiment that there is less flexibility with pricing on an API-based SaaS. We've a

We're in the exact same bucket at geocod.io[1]. I definitely agree with the sentiment that there is less flexibility with pricing on an API-based SaaS. We've also decided to go with the usage-based model, on the contrary it however also makes it easy to make a simple a transparent pricing model. We still have a UI-based piece with a spreadsheet upload tool, but under the hood it's more or less just a GUI on top of our API. When building out a new SaaS, I think it should be clear from the beginning whether it lends itself to an API-first approach, especially as a part of target audience research. In our case our primary target audience is developers, and the secondary is data analysts that prefer the GUI-based approach for one-off batches. [1] http://geocod.io http://geocod.io