PIPELINEGuide
Web design: contract, ownership, and exit
Who owns the data, access credentials, and outputs in the end? The answer to this question says more about a provider than any reference list — and belongs before the signature, not after.
Before commissioning web design, it must be clarified in writing: data and access belong to the client, in what format and timeframe they will be handed over upon termination, what a later change costs, and that documentation is a line item in the quote and not a verbal promise.
01 — Contract
What needs to be clarified in writing
- Ownership of data and access. They belong to the client. If a provider won't clearly confirm this, that's the most important information from the conversation.
- Handover upon termination. In what format, within what timeframe, at what cost.
- No minimum term without consideration. Lock-in is justifiable if something is delivered in return — otherwise not.
- What a later change costs. The total cost isn't determined by the project price, but by the hourly rate in year three.
- Documentation as a deliverable. Not as a promise, but as a line item in the proposal.
02 — Questions
Questions you should ask
- What happens if the project becomes more expensive than estimated — who bears that?
- Who owns data, access, and, if developed, the source code?
- What does operation cost in the second and third year?
- What does the documentation we receive at the end look like?
- How would you measure whether the project was successful?
- Is there a case in which you would advise us against this?
03 — Warning signs
When to be skeptical
- Guaranteed results. Anyone promising top Google ranking or a specific revenue increase is selling something they can't deliver.
- No pushback. A provider who thinks every project is a good idea has either not listened or is only selling.
- Time pressure. Limited-time discounts on project prices are a sales tool, not an offer.
- Unclear ownership. Anyone who won't clearly say who owns data and access doesn't have your interests at heart.
- No contact with technical expertise. If only sales sits in the first meeting, that's where misunderstandings arise.
04 — Questions
Frequently asked questions
What about accessibility in design?
We check contrast, font sizes, focus presentation, and click areas against WCAG 2.1 AA. That's significantly cheaper in design than later in implementation.
Who owns the files?
You do. You get the source files and the documentation. If you work with someone else later, they can continue with them.
Do we get several drafts?
Two to three directions on one page type. Ten variations help no one — they just shift the decision to the client instead of making it.
How many revision rounds are included?
Two rounds per draft are standard and usually sufficient, because the directional decision is made after the first presentation. Additional rounds are possible but noticeably extend the timeline.
Do we even need custom design?
Not necessarily. If you need a site with five pages and no brand ambitions, a well-adapted standard system is the more sensible choice. Custom design pays off when you need to stand out from competitors or manage many pages.
What if we don't like any of the directions?
Then we go back to the discovery phase — usually that means something important about the business hasn't been understood yet. It rarely happens, but better to start fresh than to force a design.
Will this look good on mobile too?
We design the narrow view first, because that's where the majority of visitors arrive. The wide view is the easier case, not the other way around.
05 — Next
Related pages
- Web design — Overview
- Web design — introduction
- Web design — ongoing operation
- Web Design — Duration
- Web design — Checklist
- Web design — Funding
- Web design — doing it yourself
- Web design — practical examples
- Have a website created
- Landing page
- Website relaunch
- All guides
Web design by region
Next step
Let's talk briefly about whether this makes sense for you.
A twenty-minute conversation is usually enough to clarify whether a project makes sense. If not, we'll say so — that's cheaper for both sides than an offer nobody needs.