Is a managed AI workflow just a subscription in disguise?
A managed AI workflow is a subscription. The question is whether it's a subscription you can leave.
Whatever happens, you should keep three things: your data, in your own systems; the settings and rules that define how the workflow behaves; and the ability to run it somewhere else without a platform only the vendor can operate. What you don't keep is the work of moving it, and any accounts the vendor pays for.
Ask about all four before signing, not at the exit.
Why this question is being asked
A common argument in this market goes: if you keep paying the provider every month, it isn't really "done for you", it's a subscription with a different label. The related claim is that what matters more than price is what happens at the end, because a build you own keeps working whether or not you keep paying.
It's a fair challenge, and it deserves a direct answer.
The honest response: a managed workflow is a subscription. So is your CRM, your email provider, and your accounting software. Being a subscription isn't the problem. Being a subscription you can't leave is.
So here's what leaving actually looks like.
What do you keep?
Your data, in your systems, not exported from ours
Everything that goes in and comes out belongs to you (our terms of service say exactly that), and it already lives where you work:
- Records written to your CRM are in your CRM
- Articles published to your website are on your website
- Emails sent are in your sent folder
This matters more than a clause in a contract. "You own your data" is technically true even when getting it out has been made deliberately painful. The real test isn't ownership. It's whether you could leave on a Tuesday and still be running on Wednesday.
Because the results land directly in systems you already control, most of your data never needs to be exported at all.
Run history: the record of what the workflow did and when is exported for you as a spreadsheet file whenever you ask for it.
The settings, in a form someone else can read
The less obvious kind of lock-in isn't technical. It's when only the person who built the workflow knows how it works, so working that out again is the real cost of switching.
The things that hold the real decisions, meaning the instructions given to the AI, the if-this-then-that logic, which field maps to which, and the rules about what needs approval, should be readable by you.
The test: if you brought in someone else tomorrow, could they read what exists and understand what it does? That is what portable means. Not a clause in a contract.
Standard tools, not our own platform
We're not a platform company. There is no Wiodo-only system that only we can run, and no file format only our software can read.
What we build runs on established, widely used open tools. In practice that means the skills to run it aren't rare, and they aren't ours. Taking it in-house or moving to another provider means hiring for a common skill set, not for us specifically.
We'd rather compete on doing the work well than on being difficult to leave.
What don't you keep?
There are two things to plan for. Better to hear them now than when you are trying to leave.
Moving it is a project. If the workflow runs on our servers and you want it on yours, we plan and carry out the move with you. Worth discussing before it's urgent.
Some services are billed to us. Parts of a workflow may run on accounts held by Wiodo. If you took it in-house, you'd need your own accounts for those. Nothing is hidden, but nothing transfers automatically either.
Managed vs. build-and-hand-over
| Managed subscription | One-time build | |
|---|---|---|
| Upfront cost | Lower | Higher |
| Ongoing cost | Monthly fee | None to the vendor |
| Who watches it | Vendor | You |
| When a connected app changes | Vendor fixes it | You fix it |
| If you stop paying | Monitoring stops; the workflow runs until a connected app changes | Same, from day one |
| Best when | Nobody on your team has time to own it | Someone on your team can own it |
Notice the row that matters. "If you stop paying" ends in nearly the same place either way. A build that was handed over to you doesn't look after itself forever. It just has nobody watching from the first day, instead of from the day you cancel. The difference isn't whether it eventually needs attention. It's who was watching in the meantime.
That's the honest version of the "build you own keeps working" claim. It keeps working until a connected app changes. Then it stops working properly, and nothing tells you. What maintenance actually covers goes through that in detail. The managed column above is what Wiodo sells; the plans are on the pricing page.
Four questions to ask before signing
- If I cancel tomorrow, what specifically do I still have, and where does it live?
- Could another provider read the settings and understand them?
- Which accounts and services are billed to you rather than me?
- What would moving it to my own servers actually involve?
Vague answers to these questions are what to worry about, not the way you are billed.
Frequently asked questions
Do I own the workflow if you built it?
You own your data and the settings. Results land directly in systems you control. The run history is available on request; we export it for you.
Is a managed AI workflow the same as vendor lock-in?
Only if leaving is impractical. Lock-in comes from formats only one vendor can read, settings nobody wrote down, and data you can't get back, not from paying monthly. Judge the exit, not the billing.
What happens to my workflow if I stop paying?
Monitoring and maintenance stop. It runs until a connected app changes, such as a software update or a new file format, and then it starts going wrong, usually silently.
Can I move the workflow to my own infrastructure?
Yes, and it's a project rather than a download. Some services we pay for would need your own accounts.
Do you use a proprietary platform?
No. Everything runs on established open tools, so running it doesn't need skills only we have.