Terms and conditions

These terms govern services provided by Thinqmesh Technologies. They are written to be read rather than skimmed, and the section on delivery timelines is the one that matters most.

1. What "four weeks" means

Our marketing states that we deliver a first working version in four weeks. In these terms a first working version (sometimes called a minimum viable product, or MVP) means the scope defined in writing under clause 1.1. This section defines that claim precisely. Where anything elsewhere on this site is less specific, this section governs.

1.1 Four weeks applies to a defined first working version

The four-week period covers delivery of a minimum viable product against a scope agreed in writing before work begins. It is not a commitment to deliver every feature of a finished enterprise system in four weeks.

The written scope is agreed at the end of the working session and forms part of the engagement. Nothing outside it is included.

1.2 The four weeks begins when conditions are met

The period starts on the later of: the scope being signed, the initial payment being received, and our receiving the access, data and named decision-maker required to proceed.

1.3 What is included

• Adaptation of an existing Thinqmesh system, or building a first working version where no such system exists, to the agreed scope
• Your branding, structure, roles and business rules as specified in that scope
• Migration of data that your existing system can export in a standard format
• Deployment to a domain you control
• A working system you can put real work through at the end of the period

1.4 What is not included

• Features not named in the agreed scope
• Content creation — course material, copy, product data or similar
• Ongoing support, hosting or maintenance beyond the engagement, unless separately agreed
• Third-party licences, subscriptions or fees
• Statutory, regulatory or accounting filings of any kind
• Training programmes beyond a handover session, unless separately agreed
• Hardware of any description

1.5 When four weeks does not apply

The four-week timeline does not apply, and a longer timeline will be quoted in writing before work begins, where the engagement involves any of:

• Enterprise-scale deployments, or multi-system architecture programmes
• Regulated environments carrying audit, certification or compliance obligations
• Migration from systems that cannot export their data in a standard format
• Integration with systems lacking a documented, accessible interface
• Scope that we assess as materially exceeding a first working version

We will tell you this in the first conversation. If we do not believe your requirement fits four weeks, we say so before you commit, not afterwards.

1.6 What can extend the period

The four weeks assumes the conditions in clause 1.2 continue to be met. It may extend where: scope changes after signature; decisions or approvals are delayed on your side; required access, data or third-party cooperation is not available; or data quality problems are discovered that require remediation beyond a standard migration.

Where the period extends for any of these reasons, we will tell you promptly, in writing, with a revised date.

1.7 Nature of the commitment

The four-week period is a good-faith delivery schedule based on the conditions above. It is not a guarantee, and it does not create a liability for consequential loss arising from a delay. Any remedy for late delivery is limited as set out in clause 5.

2. Working sessions

A working session is a demonstration and scoping conversation. It carries no cost and no obligation on either side. Systems shown are Thinqmesh's own, presented through Upfyn Desktop; we do not provide access credentials or URLs to them.

Where a service is described on this site as "built to order", no running system exists for it and any interface shown is a design concept, labelled as such.

3. Fees and payment

Fees, payment schedule and currency are set out in the written scope. Prices shown as "on request" on this site are indicative of nothing until quoted in writing. Published starting prices, where shown, cover the standard adaptation described in clause 1.3 and exclude anything in clause 1.4.

4. Intellectual property

On full payment, you own your data, your configuration and any bespoke work produced for you. Thinqmesh retains ownership of its underlying platforms, systems and reusable components, and licenses them to you for use as part of the delivered system.

5. Liability

Our total liability under an engagement is limited to the fees paid for that engagement. We are not liable for indirect or consequential loss, loss of profit, or loss of data where you have not maintained your own backups. Nothing here excludes liability that cannot lawfully be excluded.

6. Confidentiality

Each party keeps the other's non-public information confidential. We will not disclose your data, and we will not name you as a client without your written permission.

7. Termination

Either party may end an engagement in writing. You pay for work completed to that point; we hand over what has been produced.

8. Governing law

These terms are governed by the laws of India, and the courts of India have exclusive jurisdiction.

9. Changes

We may update these terms. The version in force for an engagement is the one published when its scope was signed. The date at the top of this page shows when it last changed.

10. Contact

Questions about these terms: anit@thinqmesh.com