Services · Ownership
What you own when the work is done.
Once it's paid for, you own what I build for you: the code, the workflows, the prompts and the documentation, in your own accounts and repositories. You don't need a license or a subscription with me to keep it running.
At a glance
- where everything is built
- Your accounts
- the work becomes yours
- On payment
- or subscription to keep it running
- No license
- not used to train AI models
- Your data
- Your accounts
- Your repositories
- Your documentation
- No license to renew
- No subscription to keep it running
- Your data is not used to train AI models
- Documented for your team or another firm
Where it's built
Built in your accounts, from the start.
Your accounts
Everything is built in your Microsoft 365, Google Workspace, CRM or cloud account. Nothing depends on a server you can't see.
Your repositories
Source code, configuration, prompts and evals are delivered in your repositories, under your infrastructure.
Your documentation
Architecture and operating documentation, written so your team, or any future partner, can maintain and extend the system.
The agreement
The ownership terms, in plain English.
Every engagement has a signed services agreement. Where anything written here differs from it, the signed agreement governs.
What you own
Once the fees are paid, you own what I create for you: source code, workflows, prompts, configurations, integrations, documentation, reports and roadmaps. I assign my rights in them to you.
No license to keep it running
You don't need a license or a subscription with me to use, change or run any of it.
What I keep
My general knowledge, skills and methods, and any pre-existing tools I didn't create specifically for you. Where one of those tools is part of your system, you get a perpetual, royalty-free license to use it as part of that system.
Third-party software
Software and services from other vendors are covered by their own license terms, and their subscriptions are billed to you by the vendor directly.
Your data
I use your data only to do the work. I don't use it to train AI models, and I return or delete it when you ask in writing at the end of the engagement.
If you cancel
I deliver all the work completed up to the date you cancel.
When it becomes yours
From the first build to the handover.
Each system is documented so your team, or any future partner, can maintain and extend it with confidence.
- 01
Built in your accounts
From the first build, the work is done in your accounts and repositories, through access you approve.
Nothing on a server you can't see
- 02
Documented
I write the architecture and operating documentation, the runbook and the change log as part of the work.
Written for your team
- 03
Paid for
Once the fees are paid, you own the work, and I assign my rights in it to you.
All right, title and interest
- 04
Handed over
Your people are trained to run it, and my access to your systems is removed at the end.
Access removed
Your team, or another firm
Handing it to your own team, or to another firm.
The work is built to be inherited by your in-house team, who run it and extend it after I hand it over. Everything is documented so your own team or another firm can run it, and nothing depends on a server you can't see.
There's no proprietary runtime you have to keep renting, and you don't need a subscription to this firm to keep it running. If you bring in another firm later, they work from the same repositories and documentation your team has.
The handover
What every handover includes.
Clients don't rent or lease what I deliver. Code, workflows, documentation and architecture are transferred in full and run in your infrastructure.
Every system, workflow and document belongs to your organization outright, with no licenses to renew.
Every handover includes
- Source code and configuration in your repositories
- Architecture and operating documentation
- A runbook, a change log and the tests for the AI's answers
- Training for the people who run and use the system
Questions
Questions about ownership.
When do we own what you build?
Once the fees for it are paid. From then on you own all right, title and interest in it, and I assign my rights in it to you.
Do we need a license or subscription to keep using it?
No. You don't need any license or subscription with me to use, change or run it. Software from other vendors is covered by its own license, and those subscriptions are billed to you by the vendor directly.
What do you keep?
My general knowledge, skills and methods, and any pre-existing tools I didn't create specifically for you. Where one of those tools is part of your system, you get a perpetual, royalty-free license to use it as part of that system.
Is our data used to train AI models?
No. I use your data only to do the work, and I return or delete it when you ask in writing at the end of the engagement.
What if we cancel partway through?
I deliver all the work completed up to the date you cancel.
Can another firm take over the system?
Yes. Everything is documented so your own team or another firm can maintain and extend it, and nothing depends on a server you can't see.
Which terms apply to us?
The ones in your signed services agreement. Where the Terms of Service and a signed agreement conflict, the signed agreement controls.
Next step
How it's built, and help after launch.

The first step
Ask what you'd own before anything is built.
Bring your questions about code, data and licenses to a 30-minute call, and I'll answer them against what you want built.

