What happens if we stop working with you?

Everything keeps running. The automations live in your accounts, on your subscriptions, authenticating with your credentials, so they do not call anything of ours and removing our access changes nothing operationally. You keep the workflows themselves, the credentials which never left your vault, the plain-language documentation and recorded walkthrough handed over at go-live, the evaluation sets behind any AI component, any custom code, and your execution history. There is no proprietary runtime to be locked out of and any plan is month to month with no exit fee. Lock-in, where it exists elsewhere, takes four forms worth checking for: the workflows sitting on the firm's platform subscription rather than yours, a proprietary middleware layer the automation calls, credentials wired through the firm's identity so revoking access breaks production, and documentation offered as a paid extra. The test is simple: if you revoked their access this afternoon, what breaks? The answer should be nothing except having nobody to call.

What Happens If We Stop Working Together?

Short answer

Everything keeps running. The automations live in your accounts, on your subscriptions, authenticating with your credentials. They do not call anything of ours, so removing our access stops us working on them and changes nothing else.

You keep the documentation, the workflows themselves, and the evaluation sets behind any AI component. Pay as you go has no monthly fee to stop, and there is no exit fee. There is no proprietary runtime to be locked out of, because we did not build one.

This is a design decision, not a courtesy. A firm whose work stops when you stop paying has an incentive problem, and you would be right not to trust its advice about scope.

What you actually keep

Thing	Where it lives	Yours on exit
The automations	Your Make, n8n, Zapier or Power Automate account	Yes. They are on your subscription already
Credentials and connections	Your vault	Yes, and they never left it
Documentation	Handed over at go-live, in plain language	Yes
The recorded walkthrough	Given at handover	Yes
Evaluation sets behind an AI component	Built from your historical cases	Yes. This is the expensive part to recreate
Any custom code	In the workflow, or in your repository	Yes
Execution history	Your platform account	Yes, for whatever retention you set

There is no separate export step because nothing was ever somewhere else. The handover happens at go-live, not at exit, which is the point.

Why it is built this way

Two reasons, and the second is the honest one.

The first is that it is better engineering. An automation that depends on a third party's infrastructure has an extra failure mode and an extra bill, for no benefit to you.

The second is that it keeps us honest. If leaving is easy, we have to be worth keeping every month. A twelve-month lock-in mostly protects the firm from the consequences of doing mediocre work, and you can tell a lot about a vendor from how hard they push for one.

The one thing that is genuinely ours

Our methods, how we scope, the exception patterns we look for, the way we structure an evaluation set. You get the output of all of that. What you do not get is a license to resell us. That is the only asymmetry, and it does not affect anything you are running.

What lock-in looks like when it exists

Worth knowing, because it is usually presented as a feature. Four patterns to check for with any firm, including us.

Their platform account, not yours. The workflows sit on the vendor's subscription and you are a guest. Leaving means rebuilding. Ask whose name is on the billing.
A proprietary middleware layer. The automation calls an API the firm operates. It is presented as "our engine". When you leave, the engine stops answering.
Credentials wired through their identity. The connection authenticates as their user. Revoke it and production dies, so you cannot actually remove them without an outage.
No documentation, or documentation as a paid extra. The system works and nobody but them can explain it. This one is rarely deliberate and just as disabling.

The test that cuts through all four: if I revoked your access this afternoon, what breaks? The answer should be "nothing, but you would have nobody to call".

Who maintains it afterwards

Something will need attention eventually. A vendor changes an API, an OAuth token expires, someone renames a field. That is normal and it is covered in what happens when an automation breaks. Three realistic options:

Someone internal. Entirely viable for workflow platforms, which is why the documentation and the walkthrough exist. If you have somebody technical who wants to own it, we would rather hand it to them properly than sell you a plan you do not need.
Another firm. The work is in standard tools with standard patterns. Any competent automation firm can pick it up, which is exactly the property that makes the first option credible.
Us, pay as you go or on a plan. $175 a change with no monthly fee, or $700 or $1,800 a month per account with changes, monitoring and fixes included. It is the option we mention last on purpose.

Coming back later

Coming back within six months costs nothing: no new setup fee, and we pick it up where it was. Beyond six months we would want a short reassessment first, because a lot changes in half a year: platform versions move, APIs get deprecated, and your process will have drifted from what was documented. That reassessment is free, same as scoping.