Earlier quoted context omitted.
> IT systems are not a full time job for a startup. They're not even a part time job. They're an every-once-in-a-while type job. All you need is one engineer that can also run a single small internal server. Just one. Soon enough he or she will have to maintain your mail server, CRM, file server, bug tracker, CI service, backup services etc. and woops, your developer is now a sysadmin.
From experience: That level of maintenance only grows to sysadmin proportions at a scale where you can hire a sysadmin. These systems largely run themselves, indefinitely.
How we’re spending $55,930.08 a year on SaaS products
31–40 of 63 posts
Re: How we’re spending $55,930.08 a year on SaaS products
#32While interesting - there's often a free or opensource alternative for these "generic" SaaS services. You'd probably be spending just as much on this list if you used no SaaS products and hired an engineer to either maintain the open source versions or add similar custom functionality to your product/CMS/dashboard/somewhere. If you hired the engineer, you'd probably get the exact functionality you needed too.
We have engineers and we already spend a lot more on them than we do on SaaS. But we want them focused on building Muck Rack into an awesome PR tool for our customers, not internal tools unless they're specific to our product. Even so I don't think there's any engineer we could hire for $60k salary (or any salary for that matter) who could effectively maintain all of the functionality we get from these products, but…
Re: How we’re spending $55,930.08 a year on SaaS products
#33It's significant this is a SaaS company using these services. Some of the services have a cost based on team size, while others have a cost based on user base (and usage volume). Services whose cost is f(team size): CircleCI, Trello, Github Services whose cost is f(user base): MixPanel, Moz, Shopify I mention this distinction because the f(team size) services generally offer solid value to any team, being useful and…
And this is precisely why many large enterprises build things in house rather than license commercial tools. It's a lot more palatable to buy 3-5 full time developers to build and support and internal helpdesk than license ServiceNow, etc, for tens of thousands of users.
Building something in-house probably doesn't usually result in a better product up front (and definitely not for less up-front expenditure), but it can reduce some risks and be less constraining to future moves if you own the app.
Re: How we’re spending $55,930.08 a year on SaaS products
#34I'm more certain every day that there is a place in the market for a company offering "subscription management" service. Manage all SaaS for a business (or personal as well!), keeping costs low and utilization high. Provide one central billing endpoint. I would definitely use a service like that, both personally and professionally. The number of subscriptions I have is growing, and it's frustrating to keep up with al…
Re: How we’re spending $55,930.08 a year on SaaS products
#35While interesting - there's often a free or opensource alternative for these "generic" SaaS services. You'd probably be spending just as much on this list if you used no SaaS products and hired an engineer to either maintain the open source versions or add similar custom functionality to your product/CMS/dashboard/somewhere. If you hired the engineer, you'd probably get the exact functionality you needed too.
ahh what!!!! did you see the amount of services provided?? could you please support your statement with some logic
Re: How we’re spending $55,930.08 a year on SaaS products
#36Earlier quoted context omitted.
Paying someone to micromanage the services to get cost savings would cost at least $60,000 a year and make the company lose focus. There's no way digging into the details of the Mailchimp spend structure, for instance, is worth the time.
> There's no way digging into the details of the Mailchimp spend structure, for instance, is worth the time. Actually that's one point where you are not correct. For a good email campaign, it's imperative that you manage your list. You need to be looking at stats from the previous campaigns and making changes for future campaigns. If you have a lot of low-engaged/no-engaged emails, you need to try to re-engage them a…
Re: How we’re spending $55,930.08 a year on SaaS products
#37Earlier quoted context omitted.
$60k/year is 1/3 to 1/2 a developer/sysadmin. If maintaining in-house systems based on open source equivalents of all of those packages would take more than 1/2 a headcount, then they are making the right choice. And even if they could do it all in-house, that's a developer who's not working on the stuff that makes their product distinctive. Running your own email sending / file sharing / customer support tracking /…
yes that's the tradeoff/investment, where people differ of opinion and I (very technical person, not management/paper pusher), find it more important to have in-house capabilities (even at higher cost) then to simply rely on a third party vendor. Plus that you are not making any third party aware of anything, as you don't need them. And might save you a lot of hassle in the middle of the night and you need vendor sup…
Re: How we’re spending $55,930.08 a year on SaaS products
#38Re: How we’re spending $55,930.08 a year on SaaS products
#39It's significant this is a SaaS company using these services. Some of the services have a cost based on team size, while others have a cost based on user base (and usage volume). Services whose cost is f(team size): CircleCI, Trello, Github Services whose cost is f(user base): MixPanel, Moz, Shopify I mention this distinction because the f(team size) services generally offer solid value to any team, being useful and…
And this is precisely why many large enterprises build things in house rather than license commercial tools. It's a lot more palatable to buy 3-5 full time developers to build and support and internal helpdesk than license ServiceNow, etc, for tens of thousands of users.
There's always a build vs. buy decision and sometimes you should build, but this is why even huge companies use Salesforce over maintaining an internal CRM.
Re: How we’re spending $55,930.08 a year on SaaS products
#40I'm more certain every day that there is a place in the market for a company offering "subscription management" service. Manage all SaaS for a business (or personal as well!), keeping costs low and utilization high. Provide one central billing endpoint. I would definitely use a service like that, both personally and professionally. The number of subscriptions I have is growing, and it's frustrating to keep up with al…