3 ms·
> This became a full-time job for a handful of our most senior engineers, and resulted in a six month project before we were ready to put it through our QA test
by Osiris 7y ago
> This became a full-time job for a handful of our most senior engineers, and resulted in a six month project before we were ready to put it through our QA testing.
So let's say that you pay your senior engineers $150k, 6 months is $75k per engineer, say 3-5 engineers, that's $225-375k. Plus QA time, etc.
It might have cost the company $500k just to implement a program that would reduce their revenue by letting people by in at a lower price.
I'm not saying this is the case here, but I often see companies I've worked for not do this kind of math, the opportunity cost of implementing a feature or product.
- atYevP 7y agoYev here -> while the numbers aren't entirely correct in our case the equation is correct. We do account for engineering time and opportunity cost of other projects that aren't getting worked on (though we tend to stack projects so while one team works on, billing, another will work on UI, when billing team is done they'll move on to the next project, etc..). One of the side-benefits for us in this case was building out the Extensions program meant we had to build a more robust crediting system, which is code we might be able to re-use later!