You can also watch a lot of developers “spend thousands in a vain attempt to save hundreds” just by putting a usage-based price tag on something.
(It doesn’t even have to be denominated in money; we’ll golf any available metric.)
(It doesn’t even have to be denominated in money; we’ll golf any available metric.)
I remember vividly a conversation with @tqbf when I was at his office regarding optimizations I could make to Redis to prevent me from having to go up to a 1 GB VPS.
“How much does it cost extra?”
“$10 a month.”
“Then why are we having this conversation?”
“How much does it cost extra?”
“$10 a month.”
“Then why are we having this conversation?”
In addition to being reflexive nosetweaking, I’ll point out that this is a reason to avoid usage-based pricing for developer-oriented tools and, instead, orient pricing around proxies for sophistication.
Not only is it better for you, it will be better for your customers, as relatively few developers say “Oh we’re actually *not* sophisticated. I would like my account downgraded to Total Noob, please.” and so this won’t incentivize unproductive reinventing of wheels optimization.
“What’s a proxy for sophistication?”
Features like SAML which strongly suggest there is a materially sized business using the software with standardized guidelines for vendor management administered by professionals, as opposed to one dev trying things out.
Features like SAML which strongly suggest there is a materially sized business using the software with standardized guidelines for vendor management administered by professionals, as opposed to one dev trying things out.
