Skip to content
7 min read

Website Development Contract: What to Check Before You Sign

A website development contract gets read carefully once, usually when something has gone wrong and the terms can no longer be changed. This is a step-by-step guide to the clauses you need, what to verify before signing, and the wording that most often leads to disputes with a studio.

Website development contract: subject and the technical spec

The phrase 'website development' in the subject line means nothing. A working contract refers to an appendix with a technical specification listing pages, features and integrations: a lead form, a Telegram bot, a CRM, online payments, three interface languages (Uzbek, Russian, English). Without that appendix, arguing about unfinished work is pointless, because legally the contractor delivered 'a website'.

The spec must be signed by both parties and attached to the contract, not left in a chat history. Telegram messages are useful evidence in everyday terms, but a contract appendix carries far more weight. If there is no spec yet, write 'drafting the specification' into the contract as a separate line with its own deadline and price.

Also check that the subject defines what the result includes: design, layout, programming, content entry, basic SEO setup, analytics, and hosting deployment. Anything not named, the contractor may reasonably treat as outside the price.

Rights to the result, source code and access

State it plainly: exclusive rights to design mockups and source code pass to the client after full payment. Without this clause you formally get the right to use the site, but not to change it with another team.

Access is a separate matter: domain, hosting, admin panel, code repository, analytics and webmaster accounts. Record that all of them are registered to the client and handed over when the acceptance certificate is signed. This is not distrust but hygiene: studios close, teams change, and the site stays your asset.

Account for third-party components. Fonts, plugins, paid themes and stock photos carry their own licences, and a studio cannot transfer more rights than it holds. Ask for a list of such components and clarify who pays for the licences and who renews them.

Deadlines, revisions and what happens if they slip

Tie deadlines to stages with a mutual obligation rather than to calendar dates: design is delivered N working days after the structure is approved and the client supplies materials. This is fair to both sides, because delays on the client's side are the most common cause of a missed schedule. Typical stages are structure and spec, design, layout and programming, content and testing, launch.

Spell out what happens on a delay: a penalty, a right to terminate, and how the advance is returned. A penalty is usually set as a percentage of the stage price per day of delay, with a cap so the figure stays realistic. Even if you never use the clause, having it imposes discipline.

Revisions are the most contentious clause. Fix the number of rounds per stage (usually two or three for design) and state that changes after a stage is approved are paid separately. Define what counts as a revision and what is a new task: changing a button colour is a revision, while adding a page that was not in the spec is a new task with its own estimate.

Payment and acceptance procedure

Splitting payment into stages protects both parties: an advance to start, a payment after design approval, and the balance on delivery. Full prepayment is risky for the client and full post-payment is risky for the studio, so a sensible split is a sign of a reasonable contractor. Clarify whether VAT is included and in which currency the amount is calculated: soums, or dollars at the rate on the payment date.

Describe the acceptance procedure: the review period, the format of comments, and what happens if the client stays silent. A clause saying 'work is accepted if no comments are sent within N days' is fair, but make sure N is long enough to really test the site, not just open the home page. Check forms, the mobile version, every language, load speed, emails and lead notifications.

Sign the acceptance certificate only after testing against the spec and after all access has been handed over. A signed certificate usually closes claims about visible defects, so do not rush it.

Warranty, support and confidentiality

A warranty period is the time during which the studio fixes errors made during development for free, usually a few months after acceptance. Define what counts as a warranty case: a bug in a feature from the spec qualifies, while a new feature or a failure caused by your own changes to the code does not.

Post-launch support is a separate service. State what the monthly fee covers: updates, backups, monitoring, hours for small changes, and the response time to a request. If the contract has no support clause, help after the warranty ends will be priced from scratch.

If you give the studio customer databases, commercial terms or internal documents, add a confidentiality clause and a clause on storing visitors' personal data. Also settle in writing whether the studio may show the project in its portfolio.

FAQ

Do I need a written contract for a small project? Yes. The smaller the project, the easier it is to fit the contract into two or three pages with a spec appendix, but without it you have no proof of scope, deadlines or rights.

Who should own the domain? The client. The domain is registered to your company or to you personally, and the studio gets only temporary access for setup.

Can I get the source code before full payment? Usually not: code is handed over after the final payment. That is why the handover procedure and the moment rights transfer should be written into the contract in advance.

What if the studio misses a deadline? First record the breach in writing and propose a new date. If the contract has a penalty and a right to terminate, use them; if not, you will have to negotiate, which is why these clauses are needed up front.

What makes up the price of a website? The number of pages, design complexity, features and integrations, the number of languages and the volume of content. In the contract the amount should be split by stages rather than shown as a single line.

Checklist before you sign

Before signing, run through the list: a spec appendix exists; stages and deadlines are named; revisions are limited; rights to code and mockups pass after payment; the domain and hosting are registered to you; the acceptance procedure is described; warranty and support are specified; details and responsible persons are listed. If any item is missing, ask for it to be added before you sign.

At 4 Digital, turnkey website creation starts from 1 399 000 soums, and we record the scope, stages, deadlines and access handover in a contract with a spec appendix. If you already have a draft contract from any contractor, compare it with this list before signing.

Need a website or ads? Let’s discuss your project.

Turnkey Website Development + CRM · от 2 399000 сум

We reply within 15 minutes during business hours. No spam.