Terms
Clear expectations before any project starts.
These website terms explain how the information on this site should be understood. Specific client work is governed by the written scope, commercial terms and responsibilities agreed for that project.
Website information
The website describes Virezio services, example workflows, concept work and starting prices. Content is provided for general information and may change as services, platforms and pricing evolve.
Starting prices
Prices shown on the website are starting points for common project types. A final price is confirmed after the required scope, integrations, systems, data, content, delivery risk and acceptance criteria are understood.
Project scope
Before paid work begins, the project scope should identify the agreed deliverables, milestones, price, payment arrangement, acceptance criteria and important client responsibilities. Additional work outside that scope is agreed separately.
Specialist delivery partners
Depending on the project, Virezio may engage specialist contractors, developers, designers, analysts, engineers or other delivery partners. The project scope remains the reference point for deliverables and commercial responsibility. Where a project requires specific confidentiality, security, location or access restrictions, those requirements should be agreed before work begins.
Third-party platforms and infrastructure
Projects may rely on third-party services such as hosting, cloud platforms, app stores, domains, Microsoft services, databases, payment processors, email providers, APIs, analytics products or other SaaS tools. Their own terms, pricing, limits and availability may apply.
Client data and access
Where a project involves business data, credentials or production systems, the client is responsible for providing authorised access and identifying any regulatory, security, retention or confidentiality requirements that apply. Project-specific handling requirements should be recorded in the agreed scope where relevant.
Demo and concept content
Demo businesses, figures and sample workflows are illustrative unless clearly identified as real client work. Concept case studies are labelled as concepts and are not presented as completed client engagements.
Ownership and handover
Project-specific ownership, licences, source-code rights, infrastructure access and handover details are confirmed in the agreed project scope. Virezio's standard positioning is to keep client-owned domains and business accounts under the client's control and to make asset ownership clear before delivery begins.