1. Application and contracting parties
These consulting terms apply only where expressly incorporated into a separately accepted written agreement. Viewing this page or submitting a contact request does not create a paid engagement.
The agreement identifies the actual contracting customer, authorized representatives, applicable statement of work (SOW), and document precedence. An expressly agreed contract controls over these public terms.
2. Services and scope
3QInnova provides only the services and deliverables described in the applicable SOW. These may include architecture, software and API development, cloud and AI engineering, telecommunications and contact-center integrations, or advisory work. The SOW identifies exclusions, milestones, dependencies and acceptance criteria.
Production operations, monitoring, managed hosting, formal compliance certification and continuous support require express scope.
3. Independent consulting and subcontracting
3QInnova acts as an independent contractor. Where another consulting firm engages 3QInnova for an end-customer project, the agreement identifies the contracting party, authorized approvers and any specifically accepted end-customer obligations. Neither party may bind the other without express authority.
Payment responsibility, confidentiality, access and the ownership chain must be defined for that engagement.
4. Customer cooperation and access
The customer supplies accurate requirements, timely decisions, authorized access, necessary licenses and designated contacts. The SOW allocates backup, rollback, security and production-change responsibilities. Dependency delays and their schedule or cost effects are reviewed through the agreed project process.
5. Changes and operational approvals
Material changes to scope, schedule, acceptance criteria or fees require approval through the agreed written change process. Identify the people authorized to approve changes and spending. Cloud deployment, paid usage, phone ordering, number porting and public releases follow the permissions and limits agreed for the project.
6. Fees and expenses
The SOW specifies hourly, fixed-price or retainer fees, billing increments, currency, approved expenses, taxes and invoicing. It also identifies who pays cloud, carrier, model and licensing charges. An estimate is a fixed spending cap only where the agreement expressly says so.
Payment periods, deposits, invoice disputes, late charges, unused-retainer refunds and any suspension rights must be agreed in writing. These terms set no default amounts or payment period.
7. Delivery and acceptance
The SOW defines measurable acceptance criteria and a process for reporting material nonconformities, correction and retesting. Source delivery, successful builds, deployment, provider testing and business acceptance may be separate milestones. New requirements and changes are distinguished from defects.
Review deadlines and any deemed-acceptance mechanism require express agreement.
8. Professional standard and correction
3QInnova will perform agreed services with reasonable professional care and skill. Any deliverable warranty, correction period and re-performance or other remedy must be defined in the agreement.
No particular savings, business outcome, carrier approval, regulatory approval or security result is promised solely by a website description or demonstration.
9. Customer materials and custom deliverables
Customer-provided materials remain with their owner. 3QInnova receives only the rights needed to perform the engagement. The SOW expressly identifies whether each custom deliverable is assigned or licensed, when rights vest and which source code and documentation will be delivered. Third-party rights must be respected.
10. Reusable technology and open source
3QInnova retains its pre-existing and independently developed tools, libraries, templates and general methods. Reuse must not disclose customer confidential information or customer-owned work. The agreement specifies the rights the customer needs to use retained technology embedded in its deliverables.
Relevant third-party and open-source components and their license conditions should be identified. Client-funded proprietary work is not automatically reusable merely because it resembles a common pattern.
11. Confidentiality and publicity
The agreement defines mutual confidentiality, permitted uses, need-to-know access, exceptions, required disclosures and return or deletion. Customer names, logos, case studies and customer-specific demonstrations require written permission. Confidentiality duration, backup exceptions and any approved subcontractors are agreed for the engagement.
12. Privacy and security
Project-specific arrangements identify the data, systems, processing roles and approved providers involved. Agree any necessary data-processing schedule, safeguards, credential handling, incident procedures, retention and deletion before access. Regulated workloads require expressly scoped responsibilities and controls.
These public terms make no blanket compliance certification or universal incident-notification commitment.
13. Cloud and telecom dependencies
Identify ownership of accounts, domains, numbers and registrations, responsibility for recurring usage charges, support escalation and post-handoff operation. Provider outages, quotas, platform changes, ports and carrier decisions may affect delivery. Those dependencies do not excuse 3QInnova from its own agreed responsibilities.
Availability commitments, service credits, emergency work and migration assistance require express agreement.
14. AI-enabled work
Agree approved AI tools, permitted data inputs, training restrictions, retention and human review. Evaluation criteria and relevant limitations should match the intended use. Introducing a provider that changes confidentiality, privacy, residency or licensing exposure requires the applicable approval.
15. 3QInnova lab and demonstrations
3QInnova may maintain its own lab and demonstration environments. Unless an SOW expressly states otherwise, those environments remain 3QInnova resources. They do not represent a customer deployment, customer endorsement or customer acceptance.
Use synthetic data or specifically authorized customer data. Any connection to customer systems, transfer of lab assets, environment charges or teardown responsibilities must be agreed.
16. Support and handoff
Support hours, time zone, request channels, priorities, response targets and maintenance are defined only where purchased. A response target does not by itself guarantee resolution. The SOW specifies repositories, documentation, approved credential transfer, training and transition assistance. Delivery does not imply indefinite maintenance.
17. Liability indemnity and insurance
Liability caps, damage exclusions, exceptions, insurance requirements and any third-party indemnities require express agreement and legal review. Indemnities should define covered claims, notice, defense control and settlement procedures. These terms do not establish a damages cap, waive non-waivable rights or impose an unlimited general indemnity.
18. Termination and transition
The agreement defines termination rights, notice and cure periods, payment for completed work and approved commitments, and unused-retainer treatment. It also addresses delivery of paid-for work, data export, access removal and transition services.
These public terms authorize no hidden deactivation of production systems for a payment dispute.
19. General provisions and notices
Governing law, venue, dispute resolution, force majeure, assignment, subcontracting, electronic acceptance, insurance and any restrictive covenants remain for counsel and the parties to agree. Existing signed agreements and their stated precedence remain controlling.
Contact will@3qinnova.com to discuss a proposed engagement.