Goal and project route
Clarify whether the need is a new website, targeted improvement or ongoing care.
Five controlled stages
What happens from first contact to ongoing care.
Written scope and dependencies
Confirm pages, functions, client-supplied content, exclusions, price, VAT treatment, timing, feedback and ownership.
A working responsive version
Review a real page and provide bundled feedback through the agreed decision-maker and number of rounds.
Acceptance before launch
Check content, links, forms, mobile behaviour, metadata, domains, privacy and any project-specific acceptance points.
Support within the selected package
Hosting, technical maintenance and agreed changes continue after launch; larger additions are scoped separately.
How remote collaboration works across countries.
- English is the working language for the international project
- Meeting times and every deadline are confirmed with the relevant time zone
- The proposal records the primary communication route and update checkpoints
- One authorised client decision-maker bundles feedback within the agreed rounds
- Important scope, price and acceptance decisions are confirmed in writing
The first contact can be handled asynchronously through the project brief, email or WhatsApp. If a live meeting is useful, the time, time zone and conferencing route are agreed before it is scheduled; no particular client software is assumed in advance.
During the active build, progress is shown at the agreed review checkpoints. A dependency that affects scope, price or timing is raised for a decision rather than being silently absorbed or postponed.
At handover, domain control, website access, content ownership, hosting, support and the exit route follow the written proposal. After launch, hosting, technical care and agreed updates continue under the selected plan.
What VURM needs from the client.
- A clear business offer and primary website goal
- Approved logo, images and content or an agreed copywriting scope
- Access to domains, existing hosting and relevant accounts when required
- One authorised decision-maker who bundles feedback
- Permission to use every supplied image, logo, quote and customer claim
The target build period for a standard VURM website is 14 days, starting only when the required content, accounts and decisions are available. A shop, integration, migration or delayed feedback can change the feasible date.
An intake or first discussion creates no order. The project starts only after written agreement and the payment route stated in the proposal.
Frequently asked questions
What to confirm before deciding.
How many feedback rounds are included?
The number of rounds is stated in the project-specific proposal. Feedback is bundled by one authorised decision-maker so scope and timing remain controllable.
How are remote meetings and updates handled?
English is the working language. Meeting time, time zone, communication route and update checkpoints are agreed before the build. Important decisions are confirmed in writing.
What if content or access arrives late?
The timeline is reassessed. VURM does not silently guarantee the original date when a required dependency is missing.
What is checked before launch?
The agreed acceptance gate can include content, links, forms, responsive behaviour, accessibility controls, metadata, sitemap, domains, privacy and project-specific functions.