Ask HN: Build vs. buy? Or: How many logins are too much?
I have built a custom web app for their business which handles the "core" of what they do. They often need new functionality to help employees do a better job, and every time this comes up I'm torn between building & buying. Some examples of functionality they've requested:
* Job dispatching (built into the web app)
* Time tracking for employees (bought 3rd-party software)
* Team communication (bought)
* Invoicing (built into the web app, due to custom processes)
* Managing a warehouse of supplies (bought)
I'm now faced with a new problem: Keeping track of expensive equipment that must change hands between employees.
None of our existing software handles this, so I'm stuck on build vs. buy.
On one hand: Employees already manage 4 logins for various services, so I'm hesitant to add another.
On the other hand: I'd like to avoid adding complexity to our existing software if it isn't necessary.
I work alone, so I'm reaching out to HN to see if there are any good resources, experiences, evaluation frameworks, etc. for making this decision for small businesses. Evaluating which is "better" feels like a shot in the dark. Thank you!