The three piles on the table
Every AI engagement creates three groups of assets. Naming them in the agreement prevents confusion during daily operations, account changes, and exit.
Pile one: your data. Customer records, documents, history — plus everything the system produces for you: the sent emails, the filed documents, the morning briefs. Those results are yours the moment they exist, and most of them land directly in your own systems anyway.
Pile two: your accounts. The CRM, email domain, phone number, and other customer-facing accounts should be registered to and controlled by the business.
Pile three: the machinery. The prompts, workflow definitions, integration logic, and runtime perform the work. At Ridgeway, those operated components remain part of the service.
| Asset | Who owns it | At exit |
|---|---|---|
| Customer data & documents | You | Exported to you, any day you ask, in standard formats |
| Work the system produced (emails, briefs, filings) | You | Already in your systems — nothing to hand back |
| Customer-facing accounts (CRM, email, phone) | You | Untouched — they were registered to you all along |
| The engine (prompts, workflows, runtime) | Ridgeway | Retired from your stack; you get a documented snapshot of what it did and how |
| Audit logs | Shared record | You keep a copy |
Why the operated engine remains with Ridgeway
The engine is the operated service: prompts, workflow logic, integrations, runtime controls, monitoring, and maintenance practices that Ridgeway continues to support.
A useful exit package focuses on continuity. It includes the client’s data, a current workflow inventory, source and destination details, decision rules, account dependencies, and documentation a successor can use to design or operate a replacement.
Specifically, the snapshot documents: the inventory of workflows that were running, each one’s trigger and output, the decision rules it applied, the approval gates and who held them, where every kind of record was filed, and a copy of the audit log. It’s written so a successor — your own hire, or another firm entirely — can stand up a replacement without archaeology. The test we hold it to: could someone competent pick this up on a Monday and know what the system was doing by Friday?
Apply familiar account-ownership principles
The same principle applies to websites, advertising accounts, phone systems, email, and CRM: customer-facing identities and business records should remain under the business’s control. AI systems add workflow logic and runtime components, so that additional boundary deserves the same written clarity.
Resolve ownership, access, exports, and transition support while the engagement is being designed.
Also written down: who pays the AI vendors
Ridgeway pays the agreed AI providers. Workflows run in projects separated for the engagement, with usage controls and vaulted credentials. Provider costs and responsibilities are reflected in the written service scope.
The exit terms are the trust terms. Read them first.
Questions that clarify ownership and exit
- Can I export everything today? In what format? What does it cost me to ask?
- Which accounts are registered to you rather than to me?
- If we part ways, what exactly do I have in hand the following Monday?
- Who owns the phone number my customers call?
- Is any of this in the contract, or only in this meeting?
These are ordinary procurement questions and should have direct answers in the agreement or supporting documentation.
After launch, test the export process on a reasonable schedule. Confirm that the files open in ordinary tools, identifiers retain their meaning, and the transition documentation reflects the live system.
An export is only useful if it can be understood
A folder of files is not an exit plan by itself. The handoff should identify the system of record, the fields that matter, the accounts that face customers, and the dependencies a replacement must recreate. It should also distinguish your business data from vendor-owned machinery so nobody discovers that boundary during an outage or a contract dispute.
Open the sample export before signing. Check that ordinary tools can read it, that dates and identifiers still mean something outside the vendor’s interface, and that attachments remain connected to the records they explain. Then ask who will answer a successor’s questions during transition. Ownership is strongest when both the asset and the practical route to using it are clear long before either side wants to leave.