Terms.

These terms cover the use of this website and the basis on which we take on work. A signed proposal or statement of work for a specific project sits above them, so where the two disagree, the signed document wins.

Scope of these terms

Using this site means accepting these terms. The site is published for information. Nothing on it is an offer, a quote or professional advice, and the case figures shown are illustrative rather than a promise of the same result in your business.

We may change these terms. The version published here at the time you engage us is the version that applies to that engagement.

Engagements

Work starts with a scope agreed in writing: what gets built, what it connects to, what working means and what it costs. No code starts until that is signed off. If the scope needs to change mid-project, we agree the change in writing before doing it.

We ship weekly into your environment rather than demonstrating in ours, so you can see progress as it happens. Monthly packages run month to month and either side can end them with written notice. Project builds run to the scope and end at handover.

Delivery depends on your side too: access to systems, answers to questions and a named person who can make decisions. Where those are late, timelines move by the same amount.

Cloud, model and third party service costs run in your own accounts. You see and control that spend directly, and it is not billed through us or marked up.

Payment

Monthly packages are invoiced monthly in advance. Project builds are invoiced against milestones set out in the scope. Invoices are payable within fourteen days unless the scope says otherwise.

Fees exclude applicable taxes. We may pause work on overdue invoices after written notice, and we will tell you before we do rather than going quiet.

Intellectual property

What we build for you is yours. On full payment, ownership of the deliverables specific to your engagement transfers to you, including the workflows, prompts, configuration and code written for your systems.

We keep ownership of the general tools, libraries, patterns and know how we bring to the work and reuse across clients. You get a perpetual licence to use those as part of your deliverables. Your data, your content and your systems remain yours throughout.

We will not name you as a client or describe your project publicly without your written agreement.

Confidentiality

Each side keeps the other's confidential information confidential, uses it only for the engagement, and does not pass it on without permission. That covers your data, your systems, and anything about how your business works that we see while doing the job.

We do not use client data to train models and we do not reuse it across clients. Where a model provider processes your data during a build, that runs in your own accounts under your agreement with them, and we agree which providers before any work starts.

These obligations continue after the engagement ends.

Liability

We do the work with reasonable skill and care. We do not warrant that any system will be uninterrupted or error free, and automated systems make mistakes: the exception handling and human review points we build in are there because of that, not in spite of it.

Neither side is liable for indirect or consequential loss, loss of profit, or loss of data that the other could have prevented by keeping its own backups. Our total liability for any engagement is limited to the fees paid to us for that engagement.

Nothing here limits liability that cannot be limited by law, including for death or personal injury caused by negligence, or for fraud.

Questions about these terms go to contact@aiagency.so.