Service Expectations

1. Discovery Before Commitment

We begin by understanding the problem, intended users, current workflow, desired outcome, important constraints, integrations, data, risks, and definition of success.

Early discussions and application blueprints are exploratory unless incorporated into a signed proposal or agreement.

2. Written Scope

A project should have a written description of deliverables, assumptions, exclusions, responsibilities, schedule, price, payment terms, and acceptance process. Features not included in the approved scope may require a change request, revised timeline, or additional fee.

3. Communication

App Intelligence aims to communicate clearly about progress, decisions, blockers, risks, and material changes. Clients are expected to provide timely access, content, approvals, feedback, and decision-makers.

Project communication channels and review cadence may vary by engagement.

4. Incremental Delivery

Where practical, work is organized into visible stages or usable increments. This helps validate assumptions, identify risks earlier, and keep the client involved in important product decisions.

5. Testing and Acceptance

App Intelligence performs testing appropriate to the project and agreed scope. Testing may include functional, integration, responsive, accessibility, performance, security, or user-acceptance activities.

Clients are responsible for reviewing deliverables and reporting acceptance issues within the period stated in the applicable agreement.

6. Changes and Dependencies

Changes in requirements, client delays, unavailable third-party services, new compliance requirements, incomplete data, or unexpected technical constraints may affect cost and schedule. Material changes should be documented before related work proceeds.

7. Deployment and Operations

Deployment, hosting, domain configuration, monitoring, backups, incident response, maintenance, and support are included only when stated in the agreement. Ongoing operating costs charged by third-party providers are normally the client’s responsibility unless agreed otherwise.

8. Ownership and Handover

Source code, credentials, documentation, repositories, data, and deployment access will be handed over according to the applicable agreement and payment status. Third-party licences and reusable App Intelligence materials remain subject to their own terms.

9. Support After Launch

Warranty periods, defect correction, maintenance, enhancements, monitoring, and response commitments must be defined in writing. New features and changes requested after acceptance are normally treated as additional work.

10. Respectful Collaboration

Successful projects depend on professional, honest, and respectful communication. Either party should raise concerns early so they can be addressed before they become larger delivery risks.

11. Contact

Questions about a current or proposed engagement may be sent to appintelligence.ca@gmail.com.