[akamia]

One of the problems that a lot of engineers have is failing to recognize that their time has a cost. Spending 4 extra hours of your own time setting up a mail server that will cost you $5/month to run instead of paying $10 per month for Office 365 or some other service is not really saving you money because that initial 4 hours of labor is time you could've spent doing other things for the business. It's not free time.

I find it really helps to put a dollar value on an hour of my time. In that context, if 1 hour of my time is worth $75 and I've spent 4 hours setting up this mail server, I've spent $300 on my labor in addition to the $60/year for the cost of the server. Obviously this doesn't work in all cases but it really helps me determine when it's worth it for me to spend my time doing something and when it's better to outsource it.

[inviromentalist]

Counter points-

There is no telling if it will actually save time. You could be messing with configurations, have to learn their docs, etc... Or future migration could be expensive in both time and money.

The cost savings can/do exist. Especially as things scale or last a long time.

Custom is more configurable.

People overestimate their time worth? Sure you can theoretically work for 75$/hr, but can you get overtime/additional revenue that easily?

What is your value add? If it's software, I might suggest custom is best because that's your business. If you mash a bunch of software suppliers together, you become a middle man. I'm not saying that doesn't work, but I've seen companies go back and forth on this.

[pembrook]

Another classic mistake is worrying about scaling issues and future configurability or migration when you don't even have a proven business yet.

There's a 95% chance your business won't last long enough to reach any scaling or migration issues. Tackle those problems when they start surfacing.

[akamia]

> There is no telling if it will actually save time. You could be messing with configurations, have to learn their docs, etc... Or future migration could be expensive in both time and money.

Sure. Every situation is different. This isn't meant to be universal. There absolutely are cases where rolling your own may be more efficient. However, my argument wasn't that existing solutions are no effort, just that they are often less effort than trying to do something completely custom or self managed.

Regarding future migrations, the same can be said in the opposite direction as well. You may get to a point where you need to migrate away from your custom solution to something more standard and you'll face similar time/money issues.

> Custom is more configurable.

Sometimes this is the case and sometimes it's not. Sometimes custom is very narrowly focused and as new use cases emerge requires significant rework.

> People overestimate their time worth? Sure you can theoretically work for 75$/hr, but can you get overtime/additional revenue that easily?

The number will vary for everyone. $75 may be too high for some and too low for others. If you're an attorney sacrificing billable time to do something administrative that could be outsourced, $75 may be low. The idea is to tie an actual realistic number to the value of your time.

> What is your value add? If it's software, I might suggest custom is best because that's your business. If you mash a bunch of software suppliers together, you become a middle man. I'm not saying that doesn't work, but I've seen companies go back and forth on this.

In software, I think it's important to know what your product is and to focus on your core competencies. I've seen lots of engineers decide that they need to build something from scratch that doesn't directly relate to their product. Could you build your own credit card processing system? Sure, but unless your business is credit card processing, it probably makes more sense to use something like Stripe. The same goes for lots of different aspects of your product and business.

I'm simply suggesting that you have a limited amount of time in each day and you should do what you can to get the most value out of that time. Don't ignore the value of your time and sacrifice it needlessly.

[cosmodisk]

I was discussing lack of space in our office with my boss and how difficult it'd be to add extra people should we suddenly have such a need.He replied: these are nice problems to have. Same with scalability of your software: if you get to the point where it's an issue, you just hire much smater people with some of that momey you've been making so far and they'll solve it all.

[hello_moto]

> There is no telling if it will actually save time. You could be messing with configurations, have to learn their docs, etc... Or future migration could be expensive in both time and money.

This refers to self-hosted / diy tools: you have to do them all up-front. Most SaaS don't require configs or deep-learning compare to FOSS. Self-Hosted/DIY tools also require future migration. Especially when the self-hosted/DIY tools did not capture future requirements due to limited vision.

> Custom is more configurable

Technically SaaS provides API which allows folks to stitch up a few SaaS-es to automate their workflow if needs be.