A website contract usually turns up once you’re already excited to get moving, which is exactly the wrong moment to read it properly.
Before you sign, ask who owns the finished website. Some contracts hand you the code, the content, and the design outright once the final invoice clears. Others keep the developer as the only one who can access or move it, even after you’ve paid in full.
Ask what’s included, too. “A modern website with a few pages” means something different to every developer who reads it. A proper contract lists the pages, the functionality, and how many rounds of changes are covered at the agreed price. Anything outside that list should come with its own cost and timeline, not get folded in quietly later.
Then there’s support. “Ongoing support included” is one of the most common phrases in a website contract, and one of the least defined. Included for how long? Covering what? What happens once that period ends?
None of these questions need legal training to ask. They need a willingness to read the contract properly and raise what it doesn’t say, not just what it does. A developer who answers clearly, without hesitation, is showing you how the rest of the relationship is likely to go.
For more on getting your website working harder for your business, visit https://kupu.co.uk