Project Conditions

1. Application

These conditions apply to strategy, branding, websites, SaaS, web applications, mobile/PWA products, portals, marketplaces, CRMs, dashboards, internal systems, AI systems, automations, integrations and other VORAXDESIGN project work.

The accepted proposal defines the specific project deliverables and commercial scope.

2. Scope lock

Before production, VORAXDESIGN may define roles, workflows, features, integrations, architecture, deliverables, assumptions, exclusions and acceptance criteria.

Once scope is approved or a proposal is accepted, it becomes the baseline used for pricing, production and QA.

3. Build Ready

Quoted production windows normally begin only when a project is Build Ready.

Build Ready may require acceptance, the applicable starting payment, required assets, credentials, content, approvals, scope confirmation and resolution of material blockers.

Missing prerequisites may postpone the production start without placing VORAXDESIGN in delay.

4. Client responsibilities

The client must provide timely decisions, accurate information, lawful materials, credentials, access and consolidated feedback.

The client is responsible for reviewing project-specific business content, prices, claims, policies and operational instructions.

VORAXDESIGN may rely on instructions from representatives reasonably presented as authorised.

5. Timelines

Unless expressly guaranteed in writing, delivery windows and launch targets are good-faith estimates based on approved scope and timely client cooperation.

Client delay, additional requirements, unavailable credentials, delayed approvals, third-party incidents and events outside reasonable control may move the schedule.

A client-caused or dependency-caused schedule change does not create an automatic refund right.

6. Revision rounds

Included revision rounds are limited to the number stated in the relevant package or proposal.

A revision round means one consolidated set of reasonable changes to work already inside approved scope.

A revision round does not include redesigning the project, changing the underlying product direction or adding new functionality.

7. Change requests

Changes affecting pages, workflows, roles, integrations, architecture, data models, design direction, acceptance criteria or production effort may require a separate quotation.

VORAXDESIGN may move additions into a later phase rather than disrupting the approved production cycle.

8. Third-party dependencies

Projects may rely on APIs, hosting, domains, app stores, payment providers, AI systems, email services or other independent platforms.

VORAXDESIGN cannot guarantee third-party uptime, approval, pricing, policies or future behaviour.

Material third-party changes may require separately billable adaptation.

9. Client content and data

Unless content creation, migration or data preparation is expressly included, the client is responsible for supplying usable content and data.

Clients should retain appropriate backups before migration, import, integration or transformation.

10. Development and QA

VORAXDESIGN may use source control, staging, environment separation and human QA appropriate to the project.

Testing may cover authentication, permissions, database behaviour, integrations, errors, responsive behaviour, payment workflows where applicable, security-sensitive configuration and deployment readiness.

Testing cannot establish that complex software will never contain a defect.

11. Staging and review

Where staging is provided, the client must review the agreed scope and report reproducible defects or included revisions during the applicable review period.

For business clients, production approval or production use may constitute operational acceptance of the relevant deliverable, without removing mandatory rights.

12. Bugs and warranty

A bug is a reproducible material failure of custom work to operate according to approved scope or acceptance criteria.

Changed preferences, additional features, new workflows, third-party changes, new integrations and improvements are not bugs.

Where another period is not agreed, VORAXDESIGN may provide a 14-day post-launch bug warranty for reproducible defects in custom code delivered by VORAXDESIGN.

Mandatory consumer conformity rights remain unaffected.

13. Production launch

Launch means deployment into the agreed production environment.

VORAXDESIGN may withhold launch, source release or final handover while required payments, approvals, credentials or material security matters remain unresolved.

14. Client inactivity

If a project is materially blocked by missing client feedback, assets, approvals, access or payment, VORAXDESIGN may pause the project and reallocate capacity.

Restart timing may depend on the next available production slot and material remobilisation may be chargeable.

15. Handover and ownership

After full payment of all amounts due for the relevant project, the client receives the agreed handover materials.

Unless otherwise agreed, custom source code created specifically for the client transfers after full payment.

VORAXDESIGN retains generic methods, know-how, reusable modules, templates, internal tools and non-client-specific components. Third-party software remains subject to its own licence.

16. Hosting and ongoing support

Hosting, maintenance, care, growth and ongoing product support are separate recurring services unless expressly included.

Unused recurring service allowances do not roll over unless the applicable plan expressly states otherwise.

17. Cancellation

Cancellation does not reverse completed work, reserved production capacity, approved milestones, third-party expenditure or amounts already due.

VORAXDESIGN does not offer discretionary refunds. Detailed payment and cancellation rules are set out in the Contracting Conditions.

Mandatory legal rights remain unaffected.