News for hackers. Stuff that matters.
Re:Rate our pivot: A Python cloud spreadsheet by notahacker on Wednesday March 09, 2011 @06:23PM (#2307137)
Charging based on compute time makes no sense to me. Not only does it force your customer to guesstimate their required compute time (a function of code they haven't yet written and servers they don't administer), but it also implies that your service offers little more value than the commodity infrastructure underpinning it.

I'm far more likely to have advance knowledge of the number of inputs and outputs I'm expecting and to pay more for features. My gut feeling is that the real value in what you've developed is that business types with little programming knowledge can use a spreadsheet based on data automatically imported from elsewhere. They'll be the sort of people very happy to pay more for widgets that simplify using the relevant libraries (your screen-scraping example is excellent) and very uncertain about how many minutes I need (unless I'm doing something very simple on the free plan). If you need to charge more for intensive processes it might make more sense to have it as an abstract bolt-on like Heroku's dynos that can be added on top of the monthly fee.

Unrelated aside: for some reason I have to sign in to view one of your examples: /user/tutorial/sheet/1024

Re:Rate our pivot: A Python cloud spreadsheet by gpjt on Wednesday March 09, 2011 @08:12PM (#2307476)
Interesting, thanks for that. Our model for the compute-time-plus-markup was the plethora of companies that make money doing a similar model with storage -- Dropbox being the shining example. But you raise a good point that those are inherently more predictable for the users. You know that you need N Gb of storage because that's what's on your hard drive, whereas knowing how many seconds a calculation will take is much less knowable.

Of course, if we were to take the more-technical route suggested by others on this page (ie. moved from being a "super-powerful programmable spreadsheet" to being "easy cloud supercomputing [with a shiny spreadsheetlike interface]") then perhaps our current pricing model would make sense.

On the other hand, if we stick to the spreadsheet model, you could well be right.

Hmm. Food for thought. Thanks for the pointer, anyway, and in particular for the reference to Heroku's dynos -- always good to know how people have successfully solved similar problems!

Oh, and thanks for the heads-up re: the sheet that needed a sign-in, I've fixed that, and 1025 as well (it seemed to have the same problem).