A website that works not one that merely exists

No, and nobody honestly can: ranking is the search engine’s decision and depends on competition, content, user behaviour and algorithm changes. What we do commit to method is implementing what is actually ours to control: clean URL structure, correct titles and meta, structured data, sitemaps, load speed, readable content and connected analytics. Then we measure impressions and visits and show the difference against a baseline — with no promise of a position or a visit count.

A marketing site presents your business and collects enquiries; its user reads and then makes contact. A web application is a work tool: users with permissions, data entered and edited, reports, and a workflow with states and approvals. The difference is not the look but the rules: a web application needs permissions, change logs and handling of bad input, so it is scoped differently. In the assessment we tell you which of the two you actually need.

Yes, and that is a design requirement rather than a feature: an admin panel for text, images and pages, fields shaped for each section, and protection against edits that break the layout. We train whoever will own the updates and leave an illustrated guide. If you later need changes the panel cannot do — a new section or a new function — that is separate development scope with a clear estimate, not permanent dependence on us to change a line.

With four measurements rather than an impression: speed on a real device (Core Web Vitals before and after), accessibility through automated and manual checks on the key screens, technical coverage of the search-engine files and tools, and how easy the content is to update, measured by timing a real update. We present the numbers as they are — including what did not improve — because a report that only lists successes cannot support a decision.

We give no binding duration before the assessment, because it follows the number of pages and languages, the readiness of the copy and imagery, the number of functions in a web application, and the integrations. The factor that delays projects more than any other is late content and approvals on the client side, so we give each stage a published output and ask for content early. After the assessment you get a staged plan rather than a single date.

The client owns all three: the code is delivered into your repository and documented, the domain is registered in your name, and hosting and certificates sit in your account with their fees paid by you directly rather than through us. We neither hold the code hostage nor tie the site to a service of ours, and another developer can continue from the repository and documentation.

Writing the marketing copy and photographing products, domain, hosting and third-party service fees, running advertising campaigns and buying media, guaranteeing a search ranking or a visit count, legal advice on data protection, and professional translation of the copy. We say so before the contract so none of it is a surprise after launch.