| We use so many SaaS I'm not sure it's worth resisting anymore. Microsoft 365.
Can't exit because: it's our SSO provider, also it's cost competitive with all the other email providers and you can't self-hosted email because sender reputation is too important in business. Job tracking system.
Can't exit because: it integrates with our cloud accounting software and getting that to link up with anything self-hosted is virtually impossible. Freshdesk.
Can't exit because: we could get off the ticketing system, but the knowledge base is hosted here as well, and that's publicly accessible. Miro.
Can't exit because: needs to be cloud hosted to share boards with customers, probably not worth hosting it considering costs involved and feature gaps with open source version. This probably costs us like $2-3,000/yr per employee, sure, but wages are like 50x that these days. On the business continuity side of things using a bunch of SaaS does make me nervous, but if you have to have to rely on APIs connecting everything and throwing SSO around the place, can you really escape being held hostage to it all? I think what it would take to escape SaaS is to go back to paper filing, and I think that would be more expensive than the money saved by the cross-integration of SaaS, for example manually copying bank lines from statements from several banks would take a good part of a day. Manually distributing copies of documents around the office would mean we get less work done. Manually backing-up everything probably costs more in external hard drives and time than it saves in SaaS fees. I write this while holding back tears (:/) that things have come to it. |
It is not uncommon to self-host everything except the outgoing sending. So you can mostly bring it all home without tackling sender reputation.
> Freshdesk. Can't exit because: we could get off the ticketing system, but the knowledge base is hosted here as well, and that's publicly accessible.
This can be done. The knowledge base sounds like some of the easier things to migrate tbh.
Why the need to go to paper filing? Airgapped servers are a middle ground.
But I guess your deeper issue is one of organizational culture norms, not of technical limitations or challenges...
Which I hope can be encouraging. It's all doable if you (plural) actually want it.
One path is to start with setting up contingency systems. Continously sync all mail to your own infra so you can access mailboxes even if o365 is unavailable. Mirror the knowledge base. Forward ticket mails to a duplicate archive (obviously potential caveats around PII and security here).