Start with the website URL and what you want to improve
The short brief will capture the redesign context. You can also write directly through your preferred channel — no completed audit or specification is required.
Redesign
We determine what is worth preserving, what needs organizing and where the redesign affects not only appearance but also content, structure, functionality, technology or migration.
Pricing model
Individual assessment
Pricing depends on the current platform, access, the content and URLs to preserve, integrations, migration and technical risk.
You do not need a completed audit. Share the current website URL and describe what is not working or no longer matches the business.
A redesign is the right direction when the issue goes beyond a single fix and affects how the website explains the offer, guides users or works technically.
The offer is fragmented, navigation makes information hard to find, or the current hierarchy no longer reflects what the business sells.
The site performs poorly on mobile, forms or key flows are inconvenient, and the visual layer no longer builds the right level of trust.
The CMS, codebase, access, integrations or maintenance model make safe updates and further development difficult.
Scope depends on the current-site diagnosis, but the outcome should be a coherent, usable rebuild rather than only a new visual layer.
A clear decision on what to preserve, rebuild, migrate or remove.
An organized structure and content priorities aligned with the current business.
Individual responsive UX/UI for the agreed pages, templates and states.
Implementation, migration and redirects only within the scope recorded in the SOW.
QA, acceptance, launch or handoff, plus organized information about accounts and recurring costs.
Before pricing, the current platform or codebase, access, pages and content to preserve, URLs and redirects, integrations, migration scope, required features and acceptance criteria must be established. Redesign has no single public package or maximum page count.
When uncertainty is material, the first paid outcome may be an audit or discovery rather than a full delivery estimate.
A full technical audit, SEO strategy, guaranteed ranking preservation, bulk migration, repair of undocumented legacy code, recovery of missing access, licence purchases, copywriting, translation, legal content, new integrations and work in an unsupported environment require separate scope or review.
Required items can be added after feasibility, external costs and schedule impact are reviewed.
The number and variety of pages, templates and content, and the state of the current structure.
The platform or codebase, documentation quality, access and technical constraints.
Content and URLs to preserve, redirects, SEO risk and migration scope.
Forms, integrations, data, external accounts and required features.
Material readiness, expected timing, acceptance criteria and the level of unknowns.
We review goals, content, user experience, technology, access and the main risks.
We decide what remains, what needs redesigning and what is safer to replace.
We record pages, content, URLs, redirects, integrations, responsibilities, risks and acceptance criteria.
We design the agreed experience and implement the approved scope with controlled changes.
We test the agreed flows, responsive behavior, forms, migration and redirects, then launch or hand over the project.
Often yes, but content quality, structure, technology and the purpose of each URL must be assessed first. Preservation or redirection of specific URLs is recorded in scope; SEO results are not guaranteed automatically.
You can share the public URL and describe what is available. Missing platform, hosting or account access may increase uncertainty, delay the start or require a separate audit.
Yes. Changes to content, structure, URLs, technology and performance can affect visibility. Risks, redirects and responsibility for SEO strategy must therefore be defined before delivery; Vollory does not guarantee rankings.
When the platform, codebase, migration, integrations, data or preservation scope are too unclear for safe delivery pricing. That stage has its own agreed outcome, such as an audit, requirements, a migration plan or a further estimate range.
The short brief will capture the redesign context. You can also write directly through your preferred channel — no completed audit or specification is required.