Skip to main content

Terms & Conditions - Bot Development

These terms apply to custom bot development and related work ordered from LDR.

1. Project Scope and Technical Specification​

The scope of each project is defined by the technical specification, requirements, features, integrations, and other details approved by the customer in writing before development begins.

The customer is responsible for reviewing the specification carefully and confirming that it accurately describes the requested result. Requirements that are not included in the approved specification are not automatically part of the project.

If an important requirement is missing or unclear, it should be discussed and agreed upon before development begins.

2. Approval of the Specification​

Development begins after the project scope, price, and other essential conditions have been confirmed, and payment has been verified, unless another arrangement has been agreed in writing.

The approved specification is the main reference for assessing whether the delivered bot meets the agreed requirements. Customers should not rely on assumptions or informal expectations that were not included in the confirmed scope.

3. Included Work and Revisions​

The agreed project price covers implementation of the features and requirements included in the approved specification. It does not include unlimited revisions, repeated redesigns, or new functionality that was not agreed upon.

Once a feature has been implemented according to the approved technical specification, requests to change its design, behaviour, or functionality are treated as additional work and may be charged separately.

Examples of additional work include:

  • Adding new commands, menus, modules, or features.
  • Changing an approved workflow or the way a feature operates.
  • Redesigning an interface or changing an approved design based on new preferences.
  • Adding new integrations or changing the requirements for an existing integration.
  • Reworking a completed feature because the customer's preferences or plans have changed.
  • Making changes to requirements that were approved before development.

Any additional work must be agreed upon before it begins, including its price and estimated completion time.

4. Defects Versus Change Requests​

A defect is a reproducible issue where the delivered bot fails to meet an explicit requirement in the approved technical specification.

A change request is a new feature, a change of preference, a redesign, or a modification to a requirement that has already been implemented according to the approved specification.

Confirmed defects within the agreed scope will be reviewed under the Warranty & Replacement Policy. Change requests are not automatically defects and are not automatically eligible for free correction or a refund.

LDR may ask the customer for steps to reproduce a reported issue, screenshots, logs, or other relevant information before determining whether it is a defect or additional work.

5. Delivery and Acceptance​

The estimated delivery time will be agreed for each project based on its scope and complexity. Any estimate is subject to the customer providing the required information, access, materials, and approvals on time.

The customer should review the delivered bot against the approved specification and report any apparent defects with sufficient detail to reproduce them.

Requests that fall outside the approved scope will be handled as additional work. Reviewing the delivery does not entitle the customer to unlimited revisions or new features at no additional cost.

6. Payments​

Payments are processed manually. Development begins once the project details and payment have been confirmed, unless another arrangement has been agreed in writing.

If payment is delayed or cannot be identified, contact @ldr_studio and provide the relevant transaction details.

7. Escrow Orders and Fees​

Where a development order is agreed to be processed through escrow, the payment breakdown will be provided before the transaction proceeds.

  • Order price: The agreed price for the development project.
  • LDR service fee: An additional fee of 15% of the order price for orders processed through escrow.
  • Total payable to LDR: The order price plus the LDR service fee.
  • Escrow provider fee: Paid separately by the customer directly to the escrow provider. It is not included in the order price or the LDR service fee.

The escrow provider's fee and conditions are separate from LDR's fees. The escrow provider and transaction details must be agreed and confirmed before payment.

8. Customer Responsibilities​

The customer is responsible for:

  • Providing clear and accurate requirements.
  • Reviewing and approving the technical specification before development begins.
  • Supplying the access, credentials, materials, and third-party accounts agreed as necessary for the project.
  • Ensuring that supplied content and instructions may lawfully be used.
  • Testing the delivered bot and reporting reproducible issues clearly.
  • Keeping their own credentials and access secure.

Delays caused by missing information, access, materials, or approvals may affect the delivery estimate.

9. Third-Party Services and Ongoing Maintenance​

A bot may depend on third-party platforms, APIs, hosting, payment providers, or other external services. Changes, restrictions, outages, or pricing changes introduced by those providers may affect the bot.

Unless expressly included in the approved specification or separately agreed, the project price does not include ongoing hosting, maintenance, monitoring, future compatibility updates, new integrations, or changes required by third-party updates after delivery.

LDR will assess reported issues under the warranty where they relate to a confirmed failure to meet the approved specification. Changes to third-party services that require new development may be treated as additional work.

10. Handover and Use​

The agreed handover items, such as bot access, source code, deployment, documentation, or other deliverables, will be those confirmed for the project.

Unless otherwise agreed in writing, work outside the approved scope is not included in the handover or project price. Third-party software, libraries, platforms, and services remain subject to their own terms and licences.

Any special requirements concerning source code, ownership, deployment, or ongoing access should be confirmed in writing before development begins.

11. Cancellation and Refunds​

If a project is cancelled after development has started, the work already completed and any commitments made for the project may be relevant when assessing the request.

Cancellation and refund requests are reviewed individually against the agreed project conditions, the stage of completion, and any applicable rights that cannot legally be excluded. A request for new features, a redesign, or a change of mind does not automatically establish that the delivered work is defective or that a refund is due.

Nothing in these terms removes any mandatory rights or remedies available to the customer.

12. Support and Warranty Claims​

For project questions, reported defects, or additional work requests, contact @ldr_studio and include the project details.

LDR will review defect claims against the approved technical specification and the Warranty & Replacement Policy. Additional features, redesigns, and changes outside the agreed scope may be quoted separately before work begins.