Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> My preference in these situations is always to start with buy, and then try to justify build

What if there are significant costs associated with that? Integration, training, friction to move to a new solution later, etc?

When things are commoditized it works OK but for anything complex and strategic, the cost of implementing a potentially bad solution can be absolutely crippling, especially if dependencies on that solution grow rapidly within the organisation.



Then those are all great justifications in the build column!




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: