IT, online stores and brand protection · Czechia and Slovakia
IT projects and agile development
Software projects fail over what the agreement leaves unsaid. What constitutes completed work, who accepts it, when a change becomes additional work and what you receive on handover. We structure functional specifications, milestones, acceptance criteria and change procedures to work with fixed scope and agile development under Czech and Slovak law.
- Lawyer registered with both the Czech and Slovak Bar Associations
- For customers and suppliers
- Fees agreed in advance
What we'll do for you
Complete drafting or review of an agreement for a software project, including the schedules that matter in practice: specifications, an acceptance protocol and a change form.
Select an item to see the details.
-
Specifications and scope of work
We turn the brief into a measurable outcome — what is included, what is expressly excluded, which environments and integrations are assumed and which document prevails in a conflict.
-
Milestones, acceptance and deemed acceptance
Acceptance criteria for each milestone, the testing period, who accepts the work, what constitutes a material or minor defect — and what happens if the customer fails to respond within the deadline.
-
Scope changes and agile development
A change request process addressing price and timing, or a sprint model with a budget cap — preventing ongoing refinement of requirements from becoming unpaid additional work or an endless bill.
-
Cooperation, delay and liability
Customer information, access and decisions within specified deadlines, consequences of non-provision, schedule extensions, contractual penalties and their relationship to damages.
-
Handover, operation and exit
Source code, documentation and repositories on handover, an inventory of open-source components, data security and migration, an SLA after deployment and exit assistance, including handover of work in progress on termination.
Deliverablean agreement for an IT project, including schedules: specifications, milestone timetable, acceptance and change-order protocols
We define the licence to the result and copyright in the code in the agreement and link them to payments. Detailed arrangements tailored to the business model are covered by our separate software and licence agreement service.
How it works
Does this process fit your matter? Describe it to the attorney →
- Consultationday 0
We review the nature of the project, pricing model, whether the scope is fixed or development is agile, and which side you represent. We select acceptance and change mechanisms accordingly.
- Draft agreement and schedules
We prepare the agreement with specifications, milestone timetable, acceptance criteria and a change form — or review the other party's draft and identify your risks.
- Agreement and signingat your pace
We incorporate comments, negotiate disputed points (acceptance, penalties and exit) and deliver a clean copy. On request, we remain available throughout project implementation.
Software projects rarely fall apart over statutory provisions. They fall apart over whether the work is complete — and whether what the client wants today was part of January’s brief. An agreement for an IT project therefore depends less on length than on schedules that provide answers: specifications with a measurable outcome, acceptance criteria for individual milestones and a form translating a requirements change into price and timing.
The end of the project deserves equal attention, even if nobody wants to discuss it at the outset. Source code, documentation, access, an inventory of open-source components, data migration and exit assistance determine whether you are left with a working product or merely invoices after the relationship ends. It also pays to know in advance what happens to work in progress if the project ends halfway through.
We draft or review the agreement for customers and suppliers under Czech and Slovak law. We know both legal frameworks in detail. This builds on the general contract for work; if your main concern is licensing, copyright in the code or agreements with developers and contractors, see our software and licence agreement service.
No-obligation enquiry
Ready to start?
Send us an enquiry. We reply within 24 hours with a price confirmation and next steps. The first 30-minute consultation is free and commits you to nothing.
- 1Send your enquiry via this form
- 2Within 24 h you get a price confirmation and plan
- 3We start work only after your approval
Not keen on calls or email? Message us on WhatsApp →
Prefer to book a time right away? Book a consultation →
Or email us about this matter.
What clients ask
Didn’t find your question? Ask us directly →
Can we enter into a development agreement when working agile and the scope is not known in advance?
Yes, but not by stipulating a fixed price for an undefined scope. In practice, a framework agreement with orders or sprints, a budget cap and a definition of “done” for individual deliveries works well. The agreement then acknowledges that requirements are not known at the outset and specifies how they will be agreed as work progresses and what will be paid for.
How can we verify that software is “complete”?
Only against agreed acceptance criteria — ideally test scenarios in a schedule. Without them, acceptance becomes an argument over impressions. Distinguish material defects preventing acceptance from minor defects recorded in the protocol with a deadline for correction.
What is deemed acceptance, and should I agree to it?
It is an agreement that work is considered accepted if the customer raises no objections within the agreed period or begins using the software in production. It protects suppliers from obstruction during handover but may catch customers off guard. It should be balanced through a sufficiently long testing period and an exception for material defects.
Who pays if the client changes the requirements mid-project?
The agreement's change procedure determines this. We recommend that a scope change takes effect only after its impact on price and timing is approved in writing — otherwise one side faces unpaid additional work and the other unexpected invoices. A change request form therefore belongs in the agreement's schedules.
Must we receive the source code, and what if the supplier used open source?
Handover of source code, documentation and repository access must be expressly agreed and linked to milestone payment — otherwise you may remain dependent on one supplier. The agreement should require an inventory of the open-source components used and their licences, because some impose conditions on further use of the result. The scope of the licence to the work itself is covered by our software and licence agreement service.
Legal Q&A
Common questions on this topic
-
Who owns the copyright in software created for me by a supplier?
An author's economic rights are non-transferable. A program commissioned directly from its author generally falls under the employee-work regime, and the customer exercises the rights unless the parties agree otherwise. Where a company supplies the software, however, the customer does not automatically obtain every entitlement: rights from its employees and subcontractors must be checked, and an appropriate licence or an assignment of the right to exercise economic rights must be agreed. The contract should also address source code, modifications and further licensing.
Read the answer -
Do I need a non-disclosure agreement, and what should it contain?
Trade secrets are protected directly by law, and their violation constitutes unfair competition even without an agreement. An NDA still makes sense: it precisely defines confidentiality, duration and sanctions, making proof and enforcement considerably easier. A clear definition of confidential information, the confidentiality period and a written contractual penalty are central.
Read the answer -
How long does a customer have to return goods bought online?
A consumer may withdraw from a distance contract with an online shop within 14 days without giving a reason. For goods, the period starts on receipt. Statutory exceptions include custom-made goods and unsealed goods protected for hygiene reasons. If the seller fails to provide proper withdrawal information, the period extends by up to 12 months.
Read the answer
Further reading
Agile software development: a contract designed for sprints
Sprints do not fit a conventional contract for work: scope is flexible, software is delivered incrementally and acceptance is ongoing. A framework agreement with orders, budget caps, a definition of done and rules for the backlog and repository handover provides a solution.
Read more →
Bespoke software: source code, SLAs and escrow determine your control
Paying for application development does not mean owning it. Without express terms, copyright law gives customers only narrow rights. The contract determines the rest: rights to the work, source code delivery, measurable SLAs and escrow if the supplier fails.
Read more →
The end of duty-free consignments up to EUR 150: online store rules from 1 July 2026
Council Regulation (EU) 2026/382 abolished duty relief for consignments up to EUR 150. Until 1 July 2028, IOSS imports and postal or courier consignments attract EUR 3 duty per item, changing the economics of every order for stores relying on low-cost imports.
Read more →