As someone who's built his own infrastructure, I'll respond. 1. 30m requests/month is about 11.5 requests/second. My service can do 300 search requests/second

As someone who's built his own infrastructure, I'll respond. 1. 30m requests/month is about 11.5 requests/second. My service can do 300 search requests/second sustained off of one machine. That's with a pretty minimal setup. Data is backed up to S3. Multi-homing isn't a big priority for me, but I could easily do it for not much effort/cost. 2. If you're whitelisted, Twitter actually gives out 14.4 million calls a month for free. If not, it's 111,600 calls per month. So, I'm not sure where you're getting your numbers here. 3. I've spent a lot of time building my service and API, but AFAICT you're not providing an API I could vend directly to client applications I don't own myself. Ditto on the premium content, which I can almost guarantee you don't have the rights to give re-vending access for. (As in, I can't build a weather API service on it and charge money. Same for business info.) 4. How many of those POIs are license-free? Also, half a terabyte of point data would be a lot, if you were actually indexing that much. I'd wager $1 you're counting non-point data in that number, such as addresses and the like. That said, this is probably your strongest point, 5. That's cool. It took me awhile to write my mapping engine, and I haven't started on my AR view yet. Honestly, your biggest problem seems to be that you don't describe your service very well. If I were you, I'd be pitching this as a good way to build up a service without the knowledge required to build a geo API in house, negotiating with geodata vendors directly (who can be extremely standoffish and unreasonable), and monitoring/scaling/etc the geodata side of things. Also, the things I'd like to see, so that I don't have to build them myself, would be: 1. Worldwide address geocoding with no usage restrictions. AFAICT, this service does not exist. 2. Worldwide address canonicalization. If I'm missing a postal code, province, etc, or if a phone number is in a weird format, I'd love a service that would clean that up for me. 3. Address unification among services. I'd love to be able to tie together the primary ids of a given address among the various services: Yelp, foursquare, Gowalla, OpenStreetMap, etc.