Project model
Novix is set up for defined projects. We scope the work, deliver against that scope, document what was done, and hand over clearly when the project is complete.
Engagement Terms
How engagements work.
This page is a practical summary of how Novix typically structures project work. It is not a substitute for a signed proposal, statement of work, or master agreement.
Scope and change
Project proposals are based on the scope known at the time of planning. If requirements, dependencies, or delivery conditions change materially, scope, timeline, and commercials may need to be adjusted.
Client responsibilities
Clients normally provide timely access, decision-makers, relevant technical context, and internal coordination required to keep a project moving. Delays outside Novix control can affect timing and sequencing.
Confidentiality and materials
Project information is treated confidentially. Deliverables, documentation, and implementation assets are defined in the relevant engagement documents and handed over according to the agreed scope.
No managed-service promise
Unless explicitly agreed in writing, Novix is not providing an ongoing support retainer, helpdesk function, or open-ended managed service. Our default model is project delivery, then handover.
Priority of signed agreements
If there is ever a difference between this page and a signed client agreement, the signed agreement wins. This page exists to explain the operating model before that stage.
Commercial questions
If you want the current commercial or engagement terms for a proposed project, email hello@novixhq.com and we will share the right documents during scoping.