Eddine’s decision criteria. Examples are hypothetical and do not represent client results.
| Area | Ask for it in writing | How to check |
|---|---|---|
| Content | Page map, languages and content ownership. | Inventory and review of a representative page. |
| Design and development | Templates, mobile states and functional requirements. | Demonstration with agreed tasks and viewport sizes. |
| Integrations | Connected systems, permissions and responsibilities. | End-to-end test without unnecessary real data. |
| SEO and accessibility | Technical deliverables and service boundaries. | HTML, metadata, links, keyboard and mobile review. |
| Handover and continuity | Accounts, documentation, support and recurring costs. | Owner access and acceptance record. |
Start with a customer task
Define what a visitor should do: understand the offer, request a proposal or buy. Identify who handles that request and where it is recorded. Hypothetical example: opening an email application and recording an enquiry in a CRM have different scopes, even if both are called a contact form.
Make deliverables comparable
List pages, languages, content to retain and missing materials. Distinguish design, writing, development, catalogue entry and migration. If a proposal includes SEO, ask whether it covers technical structure or also research, content and monitoring. Technical compliance does not guarantee rankings.
Agree acceptance criteria
Describe concrete tests: keyboard navigation, reading without JavaScript, using a phone and completing the enquiry journey in a test environment. WCAG provides criteria for evaluating accessibility; an automated score alone does not establish full conformance. Agree who reviews the work and how issues are handled.
Separate dependencies and exclusions
Identify required access, legal review, translations and image permissions. Clarify who contracts hosting, domains and external services and who owns the accounts. Agree that changes are estimated before execution and dependencies are distinguished from completed features.
Compare life after launch
Ask what support includes, how the website is documented, who can update it and how it is maintained. Separate one-off costs from renewals and ongoing services. This makes comparison possible without assuming the cheapest or most expensive proposal is the right fit.
Before you decide
- Define the goal and main user journey.
- Inventory pages, languages and content.
- Specify integrations and exclusions.
- Write tests and acceptance criteria.
- Clarify ownership, support and renewals.