ie are the efficiency gains of having something that's exactly tailored to you enough to create a competitive advantage.
It's back to the old idea - of software eating the world.
So for example in the UK - there is a relatively new 'energy' company called Octopus - it's grown and grown and finally overtaken the old established players.
In reality it's not an energy company - it's a software company - that used it's expertise in software to overtake it's energy supplier competitors - it was able to provide innovative products in the market because it controlled it's own software - rather than 'big vendor says no'.
I think it's telling that the founder originally left school at 16 to write computer games, before coming back to do a degree etc.
ie the question is - for any particular industry what's the benefit of custom software. Does a bakery having it's own give it enough of an advantage?
ie not sure issues with the smart meters themselves is the fault of Octopus - as the meter standards are set centrally so they can still work if you switch supplier?
Back to another old adage,
"people who are really serious about software should make their own hardware"
Mind you, I couldn't help noticing that the meters themselves are owned by a leasing company... (there is a plate on each one explaining this).
Not sure it is. Unless the Saas company is ripping you off (sure it can happen - but hopefully competition in the market would manage that over time ), then it won't be that much different from your own maintenance costs.
I always think if that's the business case for custom software ( a few quid license cost savings ) then you probably shouldn't be doing it as there is almost always a better ROI case for transformation through custom software.
So back to the bakery case. Is the benefit savings on license costs, or the fact that you can give much better estimates to customers, better de-risk supply chain issues, hire less people to operate, and improve morale via reducing busy work?
All these sort of things have to be more valuable than a few quid on licensing.
Many workflows are about B2B transactions. PO -> Sales Order -> Invoicing workflows. ASNs, etc.
So a lot of workflows are not driven by companies but by the standard operating framework of B2B
> Does a bakery having it's own give it enough of an advantage? 50 bakeries of the same franchise may benefit from it. But it does not need to be SAP or Dynamics365 or something along this line to work. People been doing business with text-mode AS360's for ages, and nobody complained. Coca Cola was using AS-something for the warehousing in 2004, while it was already discontinued for years.
ERPs and CRMs were highly configurable long before SaaS.