Quantide0
Legal

How we work together.

What we quote, what you pay, who owns the result, what we promise and what we do not — in plain language, under South African law.

The short version

Nothing starts until the scope is written down and you have accepted a quote. The quote covers the build described in it and nothing else.

You see a working version before you pay the balance. Once the build is paid up in full, the work we made for you is yours — the code, the content and the accounts.

If the scope changes, we requote that change before doing it. Nobody gets a surprise invoice.

Effective 25 August 2026. The sections below are the detail behind this summary.

1

These terms

These terms apply to this website and to any work Quantide(“we”, “us”) quotes or carries out for you. By accepting a quote from us, you accept these terms.

Where a signed proposal, statement of work or written quote says something different to these terms, that document wins for the project it covers.

2

What we do

We build applications, business websites, automations, custom AI tools and digital workflows to a defined brief. We are based in Durban, KwaZulu-Natal, and work with businesses across South Africa.

We do not take on brand identity or logo design, and we do not resell off-the-shelf products under your name.

3

Quotes, scope and acceptance

Before any work begins we agree the scope in writing: what the software has to do, who uses it, what it connects to and what is explicitly not included. That scope is the basis of the quote.

  • A quote is valid for 30 days from the date we issue it, unless it says otherwise.
  • Prices published on this site are FROM prices for build size. They are not an all-in figure for your project, and your quote may differ once the scope is known.
  • Work starts once you accept the quote in writing and the deposit reflects in our account.
  • Anything not written into the accepted scope is out of scope until we quote it.
4

Fees and payment

  • Builds are priced by scope. The published bands are a guide to build size, not a menu.
  • A deposit is payable before work starts. The balance is payable on approval of the working build, before final handover.
  • You get to use a working version before you commit the balance. That is the point of the preview — it is there so you can see what you are paying for.
  • All amounts are in South African Rand and, unless the quote says otherwise, exclude VAT.
  • Invoices are payable on the terms stated on the invoice. We may pause work on an overdue account after giving you written notice.
  • Third-party costs — licences, subscriptions, app store fees, paid APIs — are yours and are quoted separately or billed at cost.
5

Changes to scope

Briefs change, and that is normal. When a request falls outside the agreed scope we tell you before doing it, and we quote the change separately. You decide whether to proceed. We will not do out-of-scope work and invoice you for it afterwards.

A round of revisions is included as set out in your quote. Further rounds, or a change of direction after approval, are quoted as a change.

6

What we need from you

Most delays on a software project come from waiting for the client, so it is worth being explicit. We need:

  • One person with authority to make decisions and sign things off.
  • Content, assets, credentials and access to any system we have to integrate with.
  • Feedback and approvals within a reasonable time of us asking.
  • Confirmation that you have the right to use anything you give us — content, images, data or code.

You remain responsible for the accuracy and legality of the material you supply, and for the content you publish once the build is yours.

7

Timelines

We give an estimated schedule with each quote and we work to it. Timelines assume the access, content and approvals in section 6 arrive when asked for; where they do not, the schedule moves accordingly.

Estimated dates are estimates. We do not guarantee a delivery date, and we are not liable for a delay caused by something outside our reasonable control — including a third-party platform, an app store review, or a client-side dependency.

8

Third-party services and licences

Most builds rely on third-party services — hosting, payment gateways, messaging platforms, model providers, app stores. Those services are governed by their own terms and pricing, which we do not control and cannot vary.

If a third party changes its terms, its pricing or its API, or withdraws a service, we will tell you and quote the work needed to adapt. That work is a change under section 5.

9

Ownership of the work

On receipt of full payment for a build, the deliverables we created specifically for you — the source code, the configuration and the content we produced for you — become yours, along with the accounts set up in your name. It is your software to run, change, or take to someone else.

Two things stay with us. First, anything we owned before the project, and our general tools, libraries, methods and know-how: you get a perpetual licence to use those as part of your build, but they remain ours to reuse. Second, third-party and open-source components stay under their own licences.

Until the build is paid in full, everything we have produced remains our property. We may show the finished work in our portfolio unless you ask us in writing not to.

10

Hosting, domains and running costs

A build almost always has running costs after handover — hosting, domains, licences, usage-based services. Those costs are yours, and they are billed by the providers directly unless we have agreed otherwise in writing.

We do not publish a standard monthly figure for hosting, support or maintenance, because every build runs on a different stack and a generic number would be misleading. Where you want us to keep something running after handover, we scope and quote that separately for your specific build.

11

Confidentiality

Each of us will keep the other’s confidential information confidential, use it only for the project, and not disclose it without permission. This does not apply to information that is already public, that you or we already lawfully held, or that we are required by law to disclose.

12

Personal information

We process personal information in line with the Protection of Personal Information Act, 2013 (POPIA). How we handle information collected through this website is set out in our Privacy Policy.

Where we process personal information inside a system we build or run for you, you are the responsible party and we act as an operator on your written instructions. You are responsible for having a lawful basis for that processing and for your own POPIA obligations to your users.

13

What we warrant, and what we do not

We warrant that we will perform the work with reasonable skill and care, and that the build will materially do what the agreed scope says it will do. If a defect in our work is reported within 30 days of handover, we will fix it at no charge.

That warranty does not cover:

  • Changes made by you or anyone else after handover.
  • Faults caused by a third-party service, platform or device.
  • New requirements, or behaviour that was never in the agreed scope.
  • Content, data or instructions you supplied.

We do not warrant that software will be uninterrupted or error-free, and we make no promise about any business outcome — revenue, growth, ranking, efficiency or hours saved. Beyond what is stated here and what the law requires, all other warranties are excluded to the extent the law allows.

14

Limitation of liability

To the fullest extent permitted by law, neither party is liable to the other for indirect or consequential loss, loss of profit, loss of revenue, loss of business, or loss or corruption of data.

Our total liability arising out of a project is limited to the fees you have actually paid us for that project.

Nothing in these terms limits liability for death or personal injury caused by negligence, for fraud, or for anything else that cannot lawfully be limited — including your rights under the Consumer Protection Act where it applies to you.

15

Ending a project

Either of us may end a project on written notice if the other commits a material breach and does not fix it within 14 days of being told about it.

You may also stop a project at any time. If you do, you pay for the work completed and for any third-party costs we have already committed on your behalf. Deposits cover work already scheduled and started, and are not refundable once work has begun.

Sections 9 (ownership), 11 (confidentiality), 13, 14 and 17 survive the end of a project.

16

Your consumer rights

Where the Consumer Protection Act, 2008 applies to you, nothing in these terms limits the rights it gives you. Where the Electronic Communications and Transactions Act, 2002 applies, our details for the purposes of section 43 are set out in section 19 and on our contact page.

Bespoke software built to your specification is made to order. Where a statutory cooling-off right applies to a transaction, it does not extend to work already produced to your brief.

17

Governing law and disputes

These terms are governed by the law of the Republic of South Africa, and the South African courts have jurisdiction.

If something goes wrong, tell us first. Most disputes are a misunderstanding about scope and are settled in a conversation. If we cannot resolve it between us, either of us may refer it to mediation before starting legal proceedings.

18

Changes to these terms

We may update these terms from time to time. The version published on this page when you accept a quote is the version that applies to that project.

19

Contact us

For anything to do with these terms, a quote or a project, email admin@quantide.co.za or call 072 759 9160.

Last updated 25 August 2026. Quantide — Based in Durban, working with businesses across South Africa.