Project Delivery Policy

Effective Date: August 5, 2026

Introduction

This Project Delivery Policy explains how Chatwise LLC, operating under the ChatWise brand ("ChatWise," "we," "us," or "our"), plans, develops, reviews, and delivers custom software, business applications, integrations, and related digital services.

Because every project is developed according to the customer's specific needs, the exact scope, delivery schedule, features, technical requirements, payment terms, and acceptance process will be confirmed in the applicable proposal, service agreement, statement of work, invoice, order confirmation, or other written project documentation.

This Policy forms part of our Terms of Service. If project-specific written terms directly conflict with this Policy, the project-specific terms will apply to that particular project.

Nature of Delivery

ChatWise provides digital services and custom software. No physical goods are shipped unless expressly agreed in writing as part of a particular project.

Project deliverables may include software files, source code, compiled applications, web applications, account access, system configurations, databases, documentation, installation services, integrations, reports, or other digital materials described in the accepted project scope.

Delivery may take place through email, secure file transfer, repository access, installation on the customer's device or network, deployment to an agreed environment, remote access, account credentials, or another electronic method appropriate for the project.

Initial Consultation

The delivery process normally begins with a discussion of the customer's idea, business needs, desired functionality, technical environment, and expected outcome.

Information provided during an initial consultation is used to evaluate the project and prepare an estimate or proposal. An initial discussion does not create a binding obligation to begin work unless the customer accepts the applicable project terms and completes any required initial payment.

Any preliminary recommendation, price indication, or delivery estimate provided before the scope is confirmed is informational and may be revised after a more detailed review.

Project Proposal and Scope

Before development begins, ChatWise may provide a written proposal, estimate, invoice, service agreement, statement of work, or similar project document.

The project documentation may describe the agreed features, modules, technical requirements, integrations, deliverables, estimated schedule, price, payment stages, revision period, and support terms.

The customer is responsible for reviewing the project documentation carefully before acceptance. Payment of an invoice, written approval, electronic confirmation, or another clear form of acceptance may confirm the customer's agreement to the project scope.

Only the functions, services, and deliverables expressly included in the accepted project documentation are included in the agreed price.

Project Start

A project will be scheduled to begin after the customer accepts the applicable project terms, completes any required payment, and provides the information and access reasonably necessary for development.

ChatWise may delay the start date until required materials have been received. These materials may include descriptions of business processes, content, branding assets, technical information, data samples, account access, system credentials, integration documentation, or other project-related information.

The development schedule may be adjusted if the customer changes the requirements before work begins.

Development Process

ChatWise develops software according to the agreed scope and may divide the work into stages, modules, versions, or milestones.

During development, ChatWise may provide progress updates, demonstrations, screenshots, test versions, or working builds so that the customer can review the project and provide feedback.

The form and frequency of progress reviews depend on the nature, size, and complexity of the project. Small projects may require fewer review stages, while complex systems may involve several development and approval stages.

A preview, prototype, demonstration, or early working version may be incomplete and should not be treated as the final deliverable unless ChatWise confirms otherwise in writing.

Estimated Delivery Times

Any delivery periods shown on the ChatWise website are general estimates based on typical project sizes and are not unconditional guarantees.

A smaller project may have an estimated delivery period of several business days, while a larger or more complex project may require a longer period or a separately agreed schedule.

References to an initial or working version being available within a particular timeframe apply only where the project scope, technical conditions, customer cooperation, and required information make that timeframe reasonably achievable.

The final delivery schedule will be determined by the accepted project documentation and may depend on the number of features, technical complexity, integrations, requested changes, testing requirements, customer response times, and availability of third-party services.

Customer Cooperation

Timely project delivery requires the customer to provide accurate information, necessary materials, access credentials, decisions, feedback, approvals, and other cooperation requested by ChatWise.

The customer should respond to project questions and review requests within a reasonable timeframe.

If the customer provides incomplete or inaccurate information, delays feedback, changes previously approved requirements, or does not provide necessary access, the delivery schedule may be extended.

ChatWise will not be responsible for delays caused by missing customer input, unavailable customer systems, incorrect technical information, delayed approvals, or other circumstances under the customer's control.

Changes to the Project Scope

The customer may request changes during development. ChatWise will review each request and determine whether it is included in the original scope.

A request may be treated as additional work if it adds new functions, modules, integrations, designs, platforms, user roles, reporting requirements, automation, data migration, or other work not included in the accepted project documentation.

Additional work may require a revised price, additional payment, or an extended delivery schedule.

ChatWise is not required to begin work outside the original scope until the customer approves the revised terms.

Third-Party Dependencies

Some projects may depend on third-party services, including hosting platforms, operating systems, databases, application programming interfaces, payment providers, communication tools, external software, plugins, libraries, or integrations.

Third-party services are controlled by their respective providers. Their availability, approval processes, technical changes, pricing, service interruptions, and response times may affect project delivery.

ChatWise will make reasonable efforts to account for known third-party requirements but cannot guarantee the continued availability, compatibility, or performance of services outside its control.

Delays caused by third-party providers may require changes to the delivery schedule.

Testing and Review

Before final delivery, ChatWise may test the software to determine whether the agreed functionality operates as intended under the relevant test conditions.

The customer is responsible for reviewing the test version or delivered software in its intended environment and reporting any material errors, missing agreed features, or other concerns.

Customer testing should include the main workflows, data entry, reports, exports, user access, integrations, and other functions relevant to the agreed project.

The customer should not use test data or early versions for critical business operations unless ChatWise confirms that the software is ready for such use.

Customer Feedback

Feedback should be clear, specific, and related to the agreed project scope.

Where possible, the customer should provide screenshots, examples, error messages, affected records, or steps that reproduce a reported issue.

General dissatisfaction without sufficient technical or functional detail may make it difficult to investigate or correct an issue.

Feedback that introduces new requirements may be treated as a change of scope rather than a correction.

Corrections and Revisions

The applicable proposal or service package may include a limited period for corrections or agreed modifications after delivery.

The duration and scope of any included revision period will be stated in the project documentation. Website package descriptions may provide general examples, but the terms confirmed for the specific project will control.

Included corrections generally apply to errors or missing functionality that materially differ from the agreed scope.

New features, major changes, redesigns, expanded integrations, changes caused by third-party platforms, and work requested after the included revision period may require additional payment.

Project Approval

A project may be considered approved when the customer confirms approval in writing, signs an acceptance document, authorizes deployment, begins using the software in normal business operations, or otherwise clearly accepts the delivered work.

Where a review period has been specified, the project may also be treated as accepted if the customer does not report a material issue within that period.

Approval does not prevent the customer from reporting a hidden technical defect that could not reasonably have been discovered during ordinary testing.

Requests submitted after approval will be handled according to the applicable revision, support, maintenance, or additional development terms.

Final Delivery

Final delivery occurs when ChatWise makes the agreed deliverables available through the approved delivery method.

Depending on the project, delivery may include installation, access credentials, application files, deployment, repository access, source code, documentation, or a demonstration of the completed system.

ChatWise may withhold final delivery, production deployment, source code transfer, account transfer, or administrative access until all amounts due for the relevant project have been paid.

Delivery of items not included in the agreed scope is not required.

Source Code and Ownership Transfer

Ownership and usage rights relating to source code, custom components, and other project deliverables will be governed by the Terms of Service and the applicable project documentation.

Where ownership of custom code is agreed to transfer to the customer, that transfer will occur only after full payment of all amounts due for the relevant work.

ChatWise retains ownership of its pre-existing tools, frameworks, templates, reusable components, technical methods, development knowledge, and materials created independently of the customer's project.

Third-party and open-source components remain subject to their respective licenses.

Local Installation and Customer Systems

Where software is installed on the customer's own computer, server, or network, the customer is responsible for providing a suitable technical environment.

This may include compatible hardware, supported operating systems, network access, storage capacity, user permissions, security controls, and backup procedures.

ChatWise is not responsible for delivery delays or performance issues caused by unsupported equipment, restricted access, customer network conditions, malware, hardware failure, or changes made by the customer or another provider.

Any additional work required to address an unsuitable or changed technical environment may be charged separately.

Web Application Deployment

Where the project includes a browser-based application, deployment conditions will depend on the agreed hosting arrangement, domain access, server configuration, security requirements, and third-party services.

Hosting, domain registration, server maintenance, certificates, backups, monitoring, and ongoing infrastructure services are included only where expressly stated in the project documentation.

If the customer controls the hosting environment, the customer must provide the necessary access and maintain the applicable hosting account in good standing.

Data Migration

Data migration, import, conversion, cleanup, or transfer is included only where expressly stated in the project scope.

The customer is responsible for providing data in the agreed format and confirming that it has the right to use and transfer that data.

ChatWise may not be able to import incomplete, corrupted, incompatible, or improperly structured data without additional work.

The customer should retain an independent backup of all original data before any migration or system change begins.

Training and Documentation

User training, onboarding, manuals, video instructions, or technical documentation are included only where stated in the applicable project terms.

Where training is included, it may be provided remotely, through written materials, through a demonstration, or by another agreed method.

The customer is responsible for ensuring that relevant employees or users attend the agreed training and follow the provided instructions.

Additional training requested after delivery may require a separate fee.

Delivery Delays

ChatWise will make reasonable efforts to meet the agreed delivery schedule.

A delivery date may be extended where delays result from customer changes, late feedback, missing information, unavailable access, technical complexity discovered during development, third-party service issues, security concerns, illness, emergencies, power or internet outages, or other circumstances outside ChatWise's reasonable control.

Where a material delay is expected, ChatWise will make reasonable efforts to notify the customer and provide an updated estimate.

A reasonable delivery delay does not automatically create a right to cancel the project or receive a refund.

Paused or Inactive Projects

A project may be paused if the customer does not provide the information, access, payment, approval, or feedback necessary to continue.

ChatWise may provide notice that the project has been placed on hold.

The delivery schedule will be recalculated when the customer provides the required cooperation and ChatWise confirms that development can resume.

Availability to resume work immediately cannot be guaranteed because other projects may have been scheduled during the inactive period.

Additional costs may apply where restarting the project requires renewed setup, technical review, data restoration, or reconfiguration.

Project Abandonment

Where a customer remains unresponsive for an extended period, ChatWise may consider the project inactive or abandoned after providing reasonable notice.

An abandoned project does not entitle the customer to a refund for completed work, reserved time, delivered materials, or incurred costs.

Resuming an abandoned project may require a new schedule, revised estimate, updated technical review, or additional payment.

Post-Delivery Support

Support after delivery is provided only to the extent included in the accepted project documentation or purchased under a separate support arrangement.

An included correction period does not constitute unlimited maintenance or permanent technical support.

After the included period ends, future corrections, modifications, updates, integrations, technical assistance, or compatibility work may require a new agreement or optional recurring support subscription.

Recurring support terms are governed by the Subscription and Recurring Billing Policy.

Backups and Ongoing Maintenance

Unless expressly agreed otherwise, the customer is responsible for maintaining backups of delivered software, databases, files, configuration settings, and business data.

The customer is also responsible for maintaining its hardware, network, operating system, hosting account, security controls, access credentials, and third-party services.

Software may require future updates because of changes in operating systems, browsers, security requirements, third-party services, or business needs. Such updates are not automatically included in the original delivery price.

Delivery Confirmation

ChatWise may retain records showing when files were sent, access was provided, software was installed, a repository was transferred, a system was deployed, or the customer confirmed receipt.

These records may be used to verify delivery, resolve support questions, review refund requests, or respond to payment disputes.

The customer should promptly notify ChatWise if an agreed deliverable cannot be accessed or appears to be incomplete.

Cancellation Before Delivery

If a project is cancelled before final delivery, the customer remains responsible for work completed, milestones reached, development time reserved, and costs incurred before the effective cancellation date.

Any refund eligibility will be determined under the Refund and Cancellation Policy and the applicable project-specific terms.

Cancellation does not automatically require ChatWise to deliver incomplete source code, unfinished files, internal development materials, or work for which payment has not been completed.

No Physical Shipping

ChatWise provides software development and related digital services. Standard shipping, physical delivery, and product return terms do not apply to these services.

If a specific project includes physical equipment or materials, the applicable delivery terms will be separately confirmed in writing.

Changes to This Policy

ChatWise may update this Project Delivery Policy to reflect changes in services, development practices, technology, delivery methods, or business operations.

The updated Policy will be published on the website with a revised effective date.

Changes will apply to future projects. Existing project-specific terms will continue to apply unless both parties agree otherwise or a change is required by applicable law.

Contact Information

Questions about project planning, delivery, testing, acceptance, or post-delivery support may be sent to: