The right scope depends on whether you need to present an offer clearly, sell online, focus attention on a single service, or structure a more complex process.
When uncertainty is material, the first step may be an audit or paid discovery with a concrete outcome.
What Vollory projects have in common
Exact deliverables depend on the SOW, but the working standard remains consistent.
Task before solution
We understand the business goal, audience and main scenarios before starting from a ready-made layout.
Written scope
Pages, templates, features, content, integrations, assumptions and exclusions are recorded before implementation.
Individual UX/UI
Structure and interface are tailored to the business rather than sold as a ready-made template.
Two consolidated design revision rounds
Each round is one agreed feedback set from the designated decision owner.
New-scope control
A new page, feature, integration or direction after approval is handled through a Change Request.
QA and acceptance
We test the agreed pages, forms, navigation, responsive behavior, browsers, CMS and integrations.
Client accounts and handoff
Domain, hosting and key services remain under client control where practical; access and recurring costs are documented.
30 days for confirmed defects
For 30 calendar days after actual launch or written handoff, we correct reproducible issues that do not match the approved SOW or design.
What shapes scope and final pricing
The service name is a starting point. Final assessment follows the expected outcome, dependencies and risk.
Number of pages, sections and unique templates
Features, forms, CMS and relevant states
Readiness of copy, imagery, branding and product data
Number of languages and localization method
Integrations, external systems and required accounts
Migration of content, products, data and URLs
Timing, material readiness and decision speed
Uncertainty, technical risk and legal dependencies
Costs of external tools, licences, fees and subscriptions
The short brief does not calculate a price automatically. After manual review, Vollory may provide a preliminary assessment, ask 1–3 questions or suggest discovery.
Frequently asked questions
Why are prices shown “from”?
Projects with the same service name vary in pages, templates, features, languages, integrations and content readiness. A “from” price shows the lower starting point for a selected project with controlled scope. Exact pricing follows manual review and scope definition.
How long does a project take?
Timing depends on scope, content readiness, decision speed, access, integrations and risk. We set a realistic schedule after reviewing the inquiry and clarifying the project. Choosing a service does not confirm a launch date.
What if the copy or materials are not ready?
We can begin by identifying gaps and responsibilities. Copywriting, translation, photography, branding and data cleanup are not included automatically, but can be added as separate scope. Gaps may affect price and timing.
How do staged payments work?
Payment is divided into stages described in the individual proposal and SOW. Exact percentages, amounts and gates depend on the project. Work begins after the first payment, and launch or handoff follows the relevant final payment condition.
How many design revision rounds are included?
The standard process includes two consolidated design revision rounds. Each round is one agreed feedback set from the designated decision owner. New scope after approval is assessed separately through a Change Request.
Can the website have several languages?
Yes. Additional languages increase scope because they require content localization, layout review, metadata and QA. A standard additional language version does not automatically make the project Custom; complex localization logic may require individual assessment.
What do launch and handoff include?
Scope depends on the project, but includes readiness confirmation, agreed accounts and access, instructions, materials or exports defined in the SOW, recurring-cost information and an issue-reporting route. Key-service accounts remain under client control where practical.
What happens after launch?
For 30 calendar days from actual launch or written handoff, we correct confirmed reproducible issues that do not match the approved SOW or design. New features, content or design changes, third-party outages and unauthorized changes are separate scope.
Next step
Not sure which service is right?
Choose “I’m not sure — I need a recommendation” in the brief and describe the task without technical language. If you only have one question, write directly.