Terms of Service

The terms that govern automation and development work. Written to be read, not to be survived.

Last updated 26 August 2026. Version 1.0, first publication.

01. Agreement

These terms govern automation and development work provided by Uncle Systems, trading as unclesystems, to a client. Engaging the work means accepting these terms. Where a signed proposal says something different, the proposal wins.

02. What is offered

Design, build, deployment and documentation of automated systems. That typically means workflow automation, CRM configuration, lead response systems, data pipelines and reporting, assembled from third party platforms such as n8n, GoHighLevel, Make, Zapier, Supabase and hosted services.

Advice is given on the tools that suit the job. The client owns the accounts and subscriptions those tools require.

03. Scope and changes

Every engagement starts with a written scope: what is being built, what done looks like, and what is not included. Work outside that scope is quoted separately before it starts.

A change of direction mid build is normal and is handled the same way: a short written note of what changed, what it costs, and what it does to the timeline, agreed before the work happens.

04. Fees and payment

Build fee
Quoted per engagement, in the written proposal
Deposit
50% before work begins
Balance
On delivery, before handover of credentials
Payment terms
Net 7 days
Ongoing maintenance
Optional, quoted separately

Platform subscriptions, domain fees, API usage and any per token model costs are the client's, billed to the client's own accounts. They are not included in the build fee.

05. What the client provides

  • Access to the systems being automated, with permissions sufficient to do the work.
  • A named person who can answer questions and make decisions.
  • Accurate information about how the current process actually works, including the parts that are undocumented.
  • Timely review of what is delivered. Work waiting on client review does not count against the timeline.

06. Ownership

On full payment, the client owns the workflows, configurations, code and documentation produced specifically for them, and may modify them freely.

Retained are the generic methods, patterns and reusable components that predate or sit outside the engagement. These are never client specific and are not exclusive to any client.

07. Third party platforms

Systems built here run on platforms operated by other companies. Those platforms change their pricing, their features and their APIs without asking. A system that works on the day it is delivered can be broken later by a change nobody controls.

Responsibility covers building it correctly against the platforms as they exist at delivery. It does not extend to a platform's own outages, deprecations or price changes. Maintenance cover, where taken, is how those get handled.

08. Warranty

Delivered work will function as described in the written scope. Any defect reported within 30 days of handover that is a genuine failure to meet that scope is fixed at no charge.

That warranty does not cover changes made by the client or anyone else after handover, failures caused by a third party platform, or new requirements that were not in the original scope.

09. Limitation of liability

Liability arising from an engagement is limited to the fees paid for that engagement. Indirect losses, lost profits, lost revenue and loss of data are excluded to the extent the law allows.

Nothing here limits liability for fraud, or for anything that cannot lawfully be limited.

10. Confidentiality

Client information seen during an engagement, including business processes, customer data, credentials and pricing, is confidential. It is not disclosed and it is not used for anything other than the work.

Work may be described publicly in general terms, and only with the client's written agreement. No client name, customer data or figure appears anywhere without it.

11. Ending an engagement

Either side may end an engagement in writing. Work completed to that point is payable, the deposit is not refundable, and everything finished is handed over along with its documentation.

12. Governing law

These terms are governed by the laws of the Republic of the Philippines, and any dispute is subject to the courts of Manila City.

13. Contact

Trading as
unclesystems
Operator
Uncle Systems
Contact
the contact form
Location
Philippines, GMT+8

Credits

Template (c) 2026 BrewedOps, PolyForm Noncommercial + portfolio permission

Full license terms: LICENSE.txt