Two-way
Preparing a software contract with a team that knows how software is built and run prevents later disputes over acceptance, delivery, source code and data.
We handle the legal side with a team that knows how the product works, on the same plan as the product.
Under Turkish copyright law (FSEK), economic rights must be assigned in writing, listing each right separately. Instead of a general line like "all rights belong to the client", the rights of adaptation, reproduction, distribution and communication to the public should be written out with their duration and territory.
Software development is often treated as a contract for work under Turkish law, and whether the delivery conforms to the contract becomes the dispute. Turning acceptance criteria into testable items greatly reduces payment and defect disputes.
SaaS and licence agreements are often standard terms drafted by one side. Under the Turkish Code of Obligations, standard terms the other party was not clearly told about and given a chance to read are deemed unwritten, and terms unfairly against the other party in breach of good faith can be invalid.
We clarify your goal, timeline and critical risks together, in English or Turkish.
We write the legal, technical, design and operational steps into a single plan, each with an owner and a date.
Formation, contracts, product and brand work run in parallel. Work that requires a lawyer is done with independent legal professionals on BEG Hukuk.
We stay with you after launch: compliance updates, new markets, product development.
These answers are general information and are not legal advice for your specific situation.
Scope and milestones, delivery and acceptance criteria, payment schedule, change-request process, who owns the IP, source-code delivery, confidentiality, defect liability and maintenance period, limitation of liability, and termination. These clauses must match technical reality.
It depends on what the contract says. If economic rights are assigned, source-code delivery should be stated expressly; if only a licence is granted, the code can stay with the developer, and an escrow arrangement can protect the client.
Contracts with a foreign party can be written in English, and the parties can choose the governing law and dispute forum. Between Turkish companies, a Turkish text is advisable because of Law No. 805. In cross-border deals, a bilingual contract with a clause on which version prevails is a common solution.
Under Turkish law the author is the person who creates the work, and how far AI output counts as a protected work is debated. The contract should therefore say whether AI tools may be used, which data may be given to them and how rights in the output are handled.
