Terms of Service
Effective date: 16 August 2026
These terms cover the automation work Worklifted ("we", "us", "our") does for clients, the care plans under which we maintain it, and your use of this website. They do not cover our mobile applications.
We have tried to write these in plain words. Where a sentence could be read two ways, we mean the reading that is fairer to you.
1. What we do
We design, build, hand over and — where you want us to — maintain automations: workflows that carry out repeat work using tools such as n8n, together with the applications you already use. Each engagement is agreed separately in writing. Nothing on this website is an offer to contract; the scope document we send you is.
2. Getting started
Work begins with a conversation about a process you want automated. We review how the work moves through your team today, and we tell you what we would automate and what we would leave alone. If we think automating something is a bad idea, we say so before you pay us.
3. Scope and price
- We agree a fixed scope and a fixed price in writing before any build work starts. You get the exact number before you commit.
- There is no hourly meter. If the work takes us longer than we judged, that is our cost, not yours.
- The price changes only if you change the scope. Any change is agreed in writing before it is built.
- Where a care plan is part of the engagement, its monthly price is quoted in the same document, separately from the build price, so you can see both numbers before you agree to either.
- The written plan is yours to keep, whether or not you go on to have us build it.
4. The care plan
We recommend that every build we hand over runs on a monthly care plan, and most of our engagements are set up that way. The reason is not commercial: an automation is not a finished object. It depends on services that change underneath it, and something that nobody is watching fails silently until the day somebody notices the work stopped happening.
What the plan covers. We monitor the automations we built for you, we are told when one fails, and we repair it. That includes keeping up with changes made by the services your workflow depends on, and small adjustments to what we already built.
What it does not cover. New functionality, new workflows, or work outside what we originally built. Those are scoped and priced as their own piece of work under section 3. We will tell you which side of that line a request falls on before doing it, not after.
Monitoring means we receive error reports. An error report generally contains the item that failed, so a copy of that data reaches our systems. Our Privacy Policy sets out what we do with it, how long we keep it, and how to have alerts routed to you instead if you would rather they were.
Your automations still run on your own instance and your own accounts. A care plan does not move anything onto our infrastructure and does not change who owns what. The only arrangement where we host something for you is one we set out in writing in the scope document beforehand.
The plan is not compulsory. If you would rather take the build and run it yourself, we will hand it over that way and you keep everything section 7 says you keep. It means nobody is watching it for you, and a break becomes something you notice and ask us to look at. We will quote that repair when you do.
5. Payment
Invoices and payment schedule are set out in the scope document for your engagement. Unless that document says otherwise, build invoices are due within 14 days of issue, and care plan fees are billed monthly in advance. Prices exclude any taxes or transfer fees, which are your responsibility where they apply.
6. What we need from you
To build something that works on your real data, we need access to the accounts and systems involved, and a person who can answer questions and approve the scope. On a care plan, that access continues for the life of the plan, because we cannot repair what we cannot reach. You are responsible for making sure you have the right to grant that access, and for the accuracy of information you give us. Delays in access or approvals move the delivery date.
7. Handover and ownership
- Automations run on your own instance and your own accounts, unless the scope document says in advance that we are hosting it for you.
- On handover you receive the working system, written notes and a walkthrough.
- Once the build is paid for, the automations and their configuration are yours. We keep the rights to our own general know-how, methods and any reusable components we built before or outside your engagement, and we grant you a perpetual licence to use those as part of what we delivered.
- A care plan changes none of this. It is a service on top of something you already own, never a condition of owning it.
- There are no exit fees and we do not hold your data. If you stop working with us, your automations keep running and the notes stay with you.
8. The 30-day fix window
Every build includes a 30-day fix window from the date of handover, whether or not you take a care plan. If something we built stops working during that window, we fix it at no charge.
Automations break for boring reasons — a connected service changes its API, a spreadsheet column is renamed, a login policy changes. Those are covered. What is not covered is new functionality, work outside the agreed scope, or a system that stopped working because it was changed by someone else after handover.
On a care plan, nothing happens at day 30: the same repairs carry on being covered for as long as the plan runs. Without a plan, the window closes and later repairs are chargeable — we quote them before starting, so there is no invoice you did not agree to.
9. If you are not satisfied
Tell us within 30 days of handover and we return what you paid for that build. It is the same 30 days as the fix window, so there is only one date to keep track of.
Care plan fees are not part of that refund: they pay for monitoring in a month that has already been monitored. What you can do instead is leave, at any time and without penalty, under section 13.
We would rather fix it first. Most dissatisfaction traces back to something we misread in the scope, and that is usually a short conversation. But a system you did not want is not something we want to be paid for.
10. Confidentiality
We treat what we see inside your business as confidential and use it only to do the work. We do not publish your name without your permission. Builds written up on this website describe what a system does, never who it was for, and a review is attributed to a named client only where that client agreed to it.
11. Third-party services
Automations depend on services we do not control — the platforms, APIs and applications your workflow connects to. We are not responsible for those services changing their terms, their pricing, their interfaces, or going away. Where a change of that kind breaks something we built, section 8 covers the repair inside the fix window, and a care plan covers it for as long as the plan runs.
12. Liability
We do our work carefully, but no software is free of failure. Except where the law does not allow it to be limited, our total liability arising out of an engagement is limited to the fees you paid us for that engagement in the twelve months before the claim arose, and we are not liable for indirect or consequential losses such as lost profit or lost data. Nothing in these terms limits liability for fraud, or for anything else that cannot lawfully be limited.
A care plan is a commitment to monitor and repair. It is not a guarantee that an automation will never fail, and it does not make us liable for the consequences of a failure.
You are responsible for keeping your own backups of business data touched by an automation.
13. Ending an engagement
A build. Either of us can end it in writing. If you end it partway through, you pay for the work completed to that point and we hand over what exists. If we end it, we return anything you have paid for work not delivered.
A care plan. Either of us can end it with 30 days written notice. There is no minimum term, no lock-in and no exit fee. We bill to the end of the notice period and keep monitoring until it expires — you are paying for that month, so you get it.
When a plan ends, your automations keep running on your own instance, the notes stay with you, and you own everything section 7 says you own. We revoke our access, hand back or destroy the credentials you gave us, and delete the monitoring data we hold on the schedule set out in our Privacy Policy.
14. Changes to these terms
We may update these terms. The version that applies to your engagement is the one in force on the date your scope document was signed, and material changes are reflected by updating the effective date above. Where a change would affect a care plan already running, we will tell you before it takes effect, and you can end the plan under section 13 if you do not want it.
15. Governing law
These terms are governed by the laws of India, and the courts of Tamil Nadu have jurisdiction, unless your signed scope document says otherwise.