Legal · Terms
Terms.
The terms for using this site, and the shape every project takes before any code is written.
Last updated · 30 September 2026
Who you are dealing with
This site belongs to James Graham, trading as AutomatedPanda, a one-person studio, not a registered company. When you engage me, you are engaging me personally, and the work is done by me rather than passed to anyone else.
Using this site
Read it, share it, quote it, link to it. What you may not do is copy it wholesale to pass off as your own, scrape it to train a model, or try to break into the parts that are not public.
The writing, the design and the code of this site are mine. The case studies describe real work, and the clients they describe keep whatever rights they hold in their own businesses.
What the site does not promise
The notes are an account of how particular problems were solved, not advice for your situation, and applying them to a system I have not seen is your call. The case studies describe results in specific circumstances; yours will differ.
Prices on the services page are starting points, not quotes. Nothing on this site is an offer capable of acceptance. A project is agreed in writing, described in the next clause.
Enquiries
Sending the enquiry form commits you to nothing. It produces a brief, emails it to me, and I reply, usually within a working day. It is not a contract and not a quote.
What you write is stored, so please keep genuinely confidential detail for a call. I will sign an NDA before we get into specifics if you would like one. How that information is handled.
How a project usually works
These are the terms a project normally runs on, in short. The clauses that follow set them out in full. Anything different is agreed in writing first, and whatever we sign for your project governs it, not this page.
- A fixed price against a written scope, agreed before any code.
- A deposit to start, then staged against what has been delivered, not against dates.
- You decide what it needs to do. I decide how it's built.
- We agree up front whether you're buying a bespoke build, licensing a platform, or a mix of the two.
- Bespoke deliverables transfer on full payment, completed handover and any written assignment the law needs. What I retain stays mine, licensed to you for the agreed use.
- Resale, white-labelling or use by your own customers is agreed separately, before it starts.
- New features, or changes to something already agreed, are quoted before I start. A genuine bug, where it doesn't work the way we agreed, I fix at no charge during the project and for 14 days after handover.
Scope, changes and bugs
A quote covers the scope we agree at the start. New features, added requirements, and changes to something already agreed and delivered are new work: quoted separately, or billed at my hourly rate, and agreed before I begin rather than after.
A genuine bug is different. Where something does not work the way we agreed it would, I fix it at no charge while the project is running, and for the period after handover set out in clause 9. Wanting it to work differently once it already works as agreed is a change, not a bug. That distinction is the one most worth being clear about early, and it is why scope goes in writing.
Reasonable collaboration during an active project is part of the job and included: talking things through, reviewing what is being built, and the calls that go with it. Standing calls, advice and availability outside a specific project, or well beyond what the project itself needs, are covered by a support arrangement rather than being open ended.
Who owns what
Custom development
Where a project is agreed as a bespoke build that you will own, the specifically agreed deliverables transfer to you once the project has been paid for in full, handover is complete, and any required written IP assignment has been signed. What transfers, and what does not, is identified in the project agreement.
My existing software and reusable components
The software, frameworks, libraries, tools, templates and reusable components I bring to a project remain mine. That includes improvements I make to those components while working on your project.
You receive the rights needed to use those components as part of your agreed deliverables, without acquiring ownership of the underlying code. Those rights are defined in your project agreement.
Licensed platforms
Some projects involve building, adapting or extending a platform that I own and license rather than sell outright. In those cases, ownership of the underlying software and of the agreed platform developments remains with me.
You receive a licence to use the platform for the purposes, businesses, users and period agreed in writing. Paying for development, new features, configuration or infrastructure does not by itself transfer ownership of the platform.
Resale and commercial use
A licence to use software within your own business does not automatically include the right to resell it, sublicense it, white-label it, or offer it as a product or service to third parties.
If you want to make the software available commercially, we agree those rights separately in writing before that activity begins. That may include a setup fee for each new customer, an ongoing licensing fee, or another agreed commercial arrangement.
Licensing fees and support
Where software is provided under a recurring licence, the fee, billing period, permitted use, renewal terms and cancellation arrangements are agreed in writing.
Licensing fees cover the rights specified in that agreement. They do not automatically include new development, customer onboarding, maintenance, hosting or ongoing support. Those services are priced separately unless expressly included.
A recurring licence remains valid for the period and under the conditions agreed in writing. Non-payment may result in suspension or termination, subject to the notice periods and the other terms of that agreement, including its provisions for outstanding payments and access to customer data.
Ownership buyouts
If you want to acquire ownership of software you currently license, we can discuss a separate buyout. The price, the scope of rights and the transfer arrangements have to be mutually agreed in writing. No ownership transfer takes place automatically.
Third-party software and your data
Open-source libraries and third-party components remain subject to their own licences. I cannot transfer rights I do not own.
Your business data, your customer information, your branding and your materials remain yours. My owning software does not give me ownership of your business information, or permission to reuse confidential material outside the agreed project.
Payment
I usually take a deposit to start and the balance on handover, with larger projects staged against what has been delivered rather than against dates. Retainers and recurring licences are invoiced on a set date each period.
Where a project involves licensed software, setup fees, recurring licensing fees, development fees and support charges are separate unless the project agreement explicitly combines them. Each fee covers the work or the rights described in that agreement. Paying for development or infrastructure does not automatically include software ownership, resale rights or ongoing support.
Final code and access are released once payment clears. If an invoice is more than 7 days overdue, I may pause work until it is settled. Where applicable, I reserve the right to claim statutory interest and recovery costs on overdue business payments.
If a project is stopped part way, the work completed up to that point is payable.
After handover
For 14 days after handover I fix genuine defects at no charge. After that, maintenance, updates and any hosting are a separate support arrangement.
Hosting is yours to run unless we agree otherwise. For bespoke projects, I provide the agreed documentation and access your team or another developer needs to maintain the delivered software. For licensed platforms, documentation, access and permitted modifications are defined by the licence agreement.
Where a project uses software or platform components that remain under my ownership, handover does not transfer those underlying rights. Continued use, permitted modifications, third-party access and commercial distribution all stay subject to the agreed licence. Documentation and access are provided according to the type of project and the rights purchased.
Anything that matters goes in writing
Before work starts, the quote or project agreement identifies the scope, the fees, the ownership arrangement and any licensing terms that apply. Where these website terms form part of that agreement, I will provide or link to the applicable version and ask you to confirm you accept it.
Scope, fees and changes to either are agreed in writing before they take effect. A message confirming an agreement is normally enough for routine project decisions, but some arrangements, copyright assignments among them, need signed written documentation.
Updates to this page do not retrospectively change an existing agreement unless we both agree to the change.
This cuts both ways on purpose. It means I cannot be held to something I did not agree to, and it means you can hold me to what I did. Verbal understandings are easy to remember differently six months later, so I put the things that matter in writing and I will ask you to do the same.
Confidentiality and your data
What you tell me about your business, and anything I am given access to in order to build something, I keep confidential and use only for your project. That holds whether or not we have signed an NDA, and it carries on after the project ends. I am glad to sign yours if you would rather have it in your own terms.
Projects here routinely involve real data, including personal data about your customers and your staff. I handle it only as far as the work requires, keep it in systems that are access controlled, and return or delete it on request once the work is done. Where I am handling personal data on your behalf you remain responsible for it under UK data protection law, and I will sign the written terms that law requires. How this site handles your information is a separate matter, covered in the privacy policy.
What I won’t do
Consistently, and regardless of what is being offered:
- Sell you a platform when a smaller fix solves it.
- Start building before the scope is written down.
- Leave you with a bespoke build only I can run.
- Lock your data inside a platform you licence.
- Take work I'm not the right person for.
Liability
Nothing here limits liability for death or personal injury caused by negligence, for fraud, or for anything else the law does not allow to be limited.
Beyond that, and for the site itself: it is provided as it is. I keep it accurate and available, but I do not guarantee it is either, and I am not liable for losses arising from relying on it. Liability for a project is set by that project’s own contract, not by this page.
Law
These terms are governed by the law of England and Wales, and its courts have jurisdiction over any dispute about them.
Questions
If a clause here is unclear or looks wrong for what we are discussing, say so before we start rather than after. hello@automatedpanda.com. Scope disagreements are much cheaper to resolve in advance.