This policy describes the standard framework under which Stravix Technologies engagements are scoped, delivered and accepted. Individual engagements may be governed by a signed service agreement, which takes precedence where terms differ.
1. Engagement formation
An engagement is formed when you accept a proposal in writing or through the client portal approval function, or when you complete purchase of a published fixed-price package.
The accepted proposal defines scope, deliverables, timeline, payment schedule, assumptions and exclusions. Anything not stated in the proposal is outside scope.
2. Delivery methodology
Custom engagements are delivered in two-week increments. At the end of each increment you receive working software or a defined deliverable, together with a progress summary published to your client portal.
This structure exists so that scope, direction and quality are verifiable continuously rather than at the end of the engagement.
3. Acceptance
Deliverables are submitted for acceptance against the acceptance criteria stated in the proposal. You have ten business days to accept or to provide a written statement of deficiency identifying where the deliverable does not meet the stated criteria.
Where no response is received within ten business days, the deliverable is deemed accepted. Deficiencies within scope are remedied at no additional cost.
4. Change control
Requests outside the approved scope are documented as change orders with an estimate of cost and timeline impact. Work proceeds only on written approval. Change orders are invoiced according to the same payment terms as the parent engagement.
5. Client dependencies
- A nominated decision-maker with authority to approve deliverables
- Response to review requests within five business days
- Provision of content, data, credentials and third-party access as scheduled
- Coordination of any third-party vendors within your control
- Availability of nominated users for acceptance testing and training
6. Confidentiality and data handling
Client information is treated as confidential and accessed on a least-privilege basis. Detailed terms are set out in our Confidentiality Policy and in any mutual non-disclosure agreement executed before discovery.
7. Warranty period
Delivered software carries a defect remedy period of thirty days from acceptance unless a longer period is stated in the engagement. Defects are faults in delivered functionality against the approved scope; they do not include new requirements or changes in third-party dependencies.
8. Transition and handover
On completion you receive source code and repository access, infrastructure definitions, technical and operational documentation, recorded training sessions and a written transfer of intellectual property, subject to final payment.
Questions about this policy?
Contact Stravix Technologies LLC at hello@stravixtechnologies.com or call +1 (862) 260-4180. We respond to policy enquiries within five business days.
Contact us