Terms and Conditions
Draft dated 4 November 2026
Template for business-to-business IT consulting, product-led agile transformation, AI strategy, software development and nearshoring. It assumes a German contractual framework and must match the actual business and contract model. Contract language must be agreed separately.
1. Scope and contracting parties
These terms are intended for contracts between [FULL LEGAL NAME, LEGAL FORM AND ADDRESS], trading as Luccito, and clients acting as businesses within the meaning of section 14 BGB. The template is not intended for consumer contracts.
Individual agreements take priority. Each project contract specifies the services, fees and duration.
2. Offers and contract formation
A website enquiry is non-binding and does not by itself create an order. A contract is formed through offer and acceptance. Scope, contact persons, commencement and fees should be documented in text form for clarity; individual agreements retain priority.
3. Scope and nature of services
Services may include product organisation and agile collaboration consulting, AI strategy and transformation support, frontend development, cloud engineering and Java development. The agreed scope is decisive.
The project contract determines whether services or a defined deliverable are owed and whether a particular result is agreed. For a defined deliverable, specify the result, acceptance criteria and dates separately. A particular commercial outcome is owed only if expressly agreed.
4. Collaboration and client cooperation
The parties appoint suitable contacts and agree on information flows and necessary decisions. The client provides information, access and documents reasonably required for the agreed work and ensures the necessary permissions.
Dependencies, backups and access to client systems must be agreed for the project. Delays and their impact are discussed promptly; additional charges do not arise merely from unilateral notification.
5. Nearshoring and other service providers
The use of developers or other providers, their roles, locations and collaboration is governed by the project contract, including expertise in Romania and Türkiye. Responsibilities, access rights and any required data protection agreements must be established before work starts.
The actual nearshoring contract model requires separate review. This template does not replace a project specification or any arrangement required for temporary agency work or recruitment.
6. Fees, invoicing and expenses
Fees, billing model, currency, applicable taxes and due dates follow the offer or project contract. Time-based billing follows the agreed records of work. Travel and incidental expenses are charged only by prior agreement.
[COMPLETE BILLING INTERVAL, PAYMENT PERIOD, TRAVEL EXPENSE RULES AND TAX TREATMENT TO MATCH THE BUSINESS MODEL]
7. Changes to scope
Requested changes are assessed jointly for effort, fees and timing. Additional work is implemented after agreement. If no change is agreed, existing arrangements continue where performance remains possible.
8. Deliverables and usage rights
The project contract determines the deliverables and usage rights granted to the client. Existing materials, tools and third-party rights must be addressed separately. Third-party software and open-source components remain subject to their applicable licences.
For AI-assisted outputs, review responsibilities, intended uses and the extent of possible usage rights must be agreed for the project.
[SPECIFY DELIVERABLES, SOURCE CODE, DOCUMENTATION, SCOPE OF RIGHTS AND WHEN RIGHTS ARE GRANTED]
9. Confidentiality
The parties keep non-public business and project information confidential and use it only to perform the contract. The obligation does not cover information already lawfully known or publicly available, or disclosure required by law. Any further protection is agreed separately.
10. Data protection and information security
The parties comply with applicable data protection law. If one party processes personal data on behalf of the other, the necessary agreement must be concluded before processing starts. Security requirements, subprocessors and international access must be addressed for the project.
The website privacy policy does not replace a project-specific data protection or confidentiality agreement.
11. Defects and liability
Statutory rules govern defects and liability unless a valid individual agreement provides otherwise. This template contains no blanket exclusion of liability or shortening of statutory claims.
Any desired liability limits, insurance references or specific warranty provisions require legal review against the actual services.
12. Duration and termination
Commencement, duration and any agreed notice periods follow the project contract. Otherwise statutory rules apply. Termination for good cause remains available. Handover, return of materials and treatment of data after termination are agreed separately.
13. Applicable law and final provisions
German law is the intended contractual framework. Mandatory legal rules remain applicable. A specific court venue is agreed only where legally permitted. Individual agreements remain decisive.
[CONFIRM CHOICE OF LAW, ANY PERMITTED COURT VENUE AND CONTRACT LANGUAGE BEFORE USE]