Proposed payment schedule
- Install planning structure: 50% at signing, 50% at go-live, subject to the written agreement.
- Operate planning structure: install as above; monthly fee in advance and thirty days notice to cancel, subject to the written agreement.
- Build planning structure: 40% at signing, 40% at mid-build acceptance, 20% at final acceptance, subject to the written agreement.
- Proposed invoice term: Net 15. Available payment methods and receiving details must be confirmed for the engagement.
Contract form
- A written services agreement and a statement of work define each engagement.
- The statement of work carries the written spec: the numbers the system is meant to move and how each is counted.
- Change orders are written, priced and signed before the work happens, or the work does not happen.
- Governing law and other legal terms require agreement in the signed documents.
Intellectual property
- The agreement identifies ownership and assignment terms for custom work.
- Existing software, reusable components and third-party tools keep the licensing terms identified in the agreement. No exclusive platform licence is represented by this page.
- List custom, licensed and third-party components before work starts, including any ongoing fees.
- Specify data ownership, export formats and offboarding responsibilities in writing.
Liability and insurance
- Liability limits and any exceptions require review and agreement in the signed documents.
- Insurance coverage has not been verified for this page. Confirm any required active policy and certificate before relying on coverage.
- Indemnity and third-party responsibilities are contract-specific; this page does not set them.
Security and data
- Security questionnaires require a review of current evidence. The security page distinguishes verified controls from open work. No turnaround is guaranteed.
- Data processing terms and the access model must be agreed for the project. Studio is currently owner-only; client roles and a client portal are not active.
- Current Studio backup is local and encrypted with Windows DPAPI. Offsite recovery and independent restore verification remain open work.
- A project may need hosting, storage, email, telephony, payment, monitoring or AI providers. List the actual vendors, regions, data use, access and change procedures in the agreement before connecting them; catalogue availability does not mean an integration is active.
- Service categories for discussion include IT and technology consulting, solutions and management. Potential NAICS references include 541512, 541511, 541611, 541613 and 541519; the appropriate classification and any vendor registration must be confirmed for the engagement.
- Vendor onboarding documents are reviewed case by case. A tax form, insurance certificate, bank instruction, diversity certification or signed questionnaire should be treated as available only after it has been provided and verified.
Support and exit
- Support must be agreed: scope, staffed hours, reporting route, response targets and out-of-hours charges belong in the written support plan. No four-hour response, client portal or 24/7 staffing is currently offered as a verified service level.
- Monitoring and alert destinations must be configured and tested for the specific systems in scope.
- Agree the duration, deliverables and any cost of offboarding assistance before signing.
- Confirm the named delivery lead, availability and any subcontractors before the engagement starts.
Review the working browser demonstrations for examples of workflow behavior. They use synthetic data and do not represent client deployments or measured client results.