Honestly, I'd scrap everything up to $29/mth and change the pricing basis from MB and number of queries (people who use spreadsheets have no real understanding of this) to number of spreadsheets.
I remember working for Deutsche Bank 15yrs ago when one Excel spreadsheet could make them millions of £/day — don't be afraid to charge a decent amount! People who care about data, have spreadsheets, and need some interoperability will not baulk at $29, $50 or even $200/mth. And if they're giving you a decent income, they'll trust that you'll be around for longer.
Would you expect a bank (or accountant, or FMCG company) to trust a critical part of their process to a free or £12/mth service? Hell, no.
But perhaps part of the problem is that you've build a cool thing but don't know exactly who your customers should be. When you figure that out you'll be able to write more compelling copy and price it appropriately.
The only problem is that I'm almost sure that DB were making millions not thanks to the excel data per se but thanks to all the logic that was running inside/behind that Excel.
In this case, you can't "APIfy" it with a tool like this.
N.B. I'm not bashing sheetlabs, just saying that sometimes the most important part is not the numbers in the cell but how you create them
I remember working for Deutsche Bank 15yrs ago when one Excel spreadsheet could make them millions of £/day — don't be afraid to charge a decent amount! People who care about data, have spreadsheets, and need some interoperability will not baulk at $29, $50 or even $200/mth. And if they're giving you a decent income, they'll trust that you'll be around for longer.
Would you expect a bank (or accountant, or FMCG company) to trust a critical part of their process to a free or £12/mth service? Hell, no.
But perhaps part of the problem is that you've build a cool thing but don't know exactly who your customers should be. When you figure that out you'll be able to write more compelling copy and price it appropriately.