Skip to content

Legal

Terms

The rules for using this site, and the commercial principles behind our work. Last updated September 2026.

Using this site

You are welcome to read, quote and link to anything published here. If you quote us at length, attribute it and link back. You may not republish whole articles as your own, and you may not use the site to distribute anything harmful.

What the content is and is not

The writing and published figures on this site are general information, not advice for your specific situation. Costs vary with scope, and any figure we publish is a starting point rather than a quote. Nothing here forms a contract until it is written into a proposal and signed.

Published pricing

We publish the Automation Audit fee because it is the only figure we can state honestly before looking at your process. Build pricing is quoted after the Audit, since scope varies too much for a general number to be useful. Published figures are current at the date above and can change. A price quoted to you in a proposal is fixed for that engagement and does not move with this page.

Engagement principles

These apply to every engagement and are repeated from the pricing and approach pages so they are all in one place:

  • Fixed scope, fixed price. Scope is agreed in writing after the Automation Audit. Overruns against agreed scope are ours to absorb. If work turns out materially bigger than scoped, we stop and re-quote before continuing rather than invoicing quietly.
  • You own the result. Code, credentials, repositories and infrastructure are in your name from the first day. On full payment, intellectual property in what we build for you is yours. Handover includes runbooks and diagrams.
  • 90 days of maintenance included. After handover, we fix breakages in what we built and adapt to upstream API changes for 90 days at no extra cost. It does not cover new features or changes you request, which are quoted separately.
  • No lock-in. Ongoing engagements can be cancelled with 30 days' notice. Everything built stays yours and keeps running.
  • Confidentiality. We treat what we see inside your operation as confidential, and we do not publish a client write-up without written approval.

Limits

We build systems that integrate with third-party services we do not control. If a vendor changes or withdraws an API, we will tell you and propose a fix, but we cannot warrant the behaviour of platforms that are not ours. Our liability for any engagement is limited to the fees paid for it, except where the law does not allow that limit.

Getting in touch

Questions about any of this go to info@flowzora.com. How we handle your data is covered in our privacy policy.