Two ways of looking at the same thing
Anyone buying an automation has one of two mindsets in their head, and almost always without noticing it
The first is the project mindset. You start, you work, you deliver, you say goodbye. It's how you redo the bathroom at home: the builder leaves and the bathroom sits there working for twenty years with nobody having to come back
The second is the service mindset. The thing gets built, but then somebody keeps looking after it, because the world around it moves and on its own it doesn't move with it
Why the project mindset is comfortable, and sometimes right too
The project mindset has an advantage worth taking seriously. You know where it ends, you pay, you're done, and you're left with no commitment renewing itself every month
For some things it works perfectly well. A small, settled automation that runs on a file produced the same way every time and touches nobody else's program can stand on its own for years without anyone looking at it. There, paying somebody to look after it is paying for nothing
Almost nothing stands still
The trouble with the project mindset shows up when the automation leans on something you don't decide
Programs update and a window moves. Web portals redo their look and shift the download button. A supplier redesigns the invoice template and that number is no longer where it was. And then there's the one nobody counts on, you, changing an internal rule because a customer changed, or the law did
None of these is a mishap, it's the ordinary background noise of a company at work. An automation left on its own doesn't absorb it, it breaks, or worse, it carries on running and doing the wrong thing
What happens to an automation nobody looks after
A well-built automation, when it no longer recognizes what it's looking at, stops instead of guessing, and that's the right behavior
But stopping means somebody has to get it going again. If that somebody isn't there, the first few times the person in the office redoes the work by hand and grumbles, after a month she redoes it without grumbling, and after three months nobody remembers there was ever a system doing it
At that point everything you spent is thrown away, and not because the work was done badly, but because it was sold as something that ends when it wasn't
The shape that matches the thing
Muffin Suite works with a monthly fee agreed before the work starts, and inside it sit development, use, support, fixes and maintenance, while the term and the conditions are set in the contract for each project
The reason isn't commercial. The fee is the shape that matches the thing: if something has to be looked after over time, it gets paid for over time, and whoever looks after it has a reason to make it last instead of delivering it and disappearing
There's a practical effect too, and it counts more than all the rest. You don't put down a large sum at the start betting that it works, so the risk of that bet isn't all yours, and the subscription page sets out what it covers
How to decide
The question to ask isn't which arrangement costs less on paper. There's only one: does this automation lean on something that can change without asking my permission
If the answer is no, meaning it reads a file of yours, writes into a place of yours, and no outsider touches anything, then a one-off job is enough and costs you less
If the answer is yes, and in practice it almost always is, because portals and business software change whenever they feel like it, then a one-off job is a job that decays slowly. The real question becomes who keeps it standing, because that cost exists either way. The only choice is whether you pay it to a supplier or pay it in your own people's hours, as they go back to doing the work by hand