Service delivery policy.

How work is delivered

The delivery method is agreed in the project agreement. Depending on the project it may include:

• Private Git repository. Work delivered into a private repository, either your own or one created for the project and transferred to you on completion.
• Source code. Complete, tested source code for the agreed deliverables.
• Staging environment. A staging deployment for review before production, where the project includes one.
• Deployment to client-approved hosting. Production deployment to hosting you have approved, such as Vercel or AWS.
• Project files. Where a repository is not appropriate, files are provided through a private, access-controlled download.
• Documentation. Setup, configuration and technical documentation covering how the delivered system works. API documentation where the project includes an API.
• Secure credential handover. Any credentials created for the project are transferred through a secure channel agreed with you. Credentials are never sent in plain email and are never committed to a repository.
• Handover call. A walkthrough where the project warrants one, so your team can operate what has been delivered.

Delivery timing

Delivery times shown with a published package apply to the scope of that package. The delivery period starts once the project brief, content, assets and any required access have been supplied and the first invoice has cleared. Where a project is blocked waiting on information or access from you, the delivery period is extended by the length of that delay.

For scoped projects outside a published package, the timeline is estimated in the proposal and agreed in the project agreement. Fahymas LLC does not commit to a delivery date before a scope has been defined and agreed.

Review and acceptance

Completed work is made available for your review. The project agreement sets out the review period, what constitutes acceptance, and how issues raised during review are handled. Defects in delivered work that fall within the agreed scope are corrected as part of the engagement.

Revisions listed with a package apply to the deliverables of that package, within the scope described.

After delivery

Once work is delivered and accepted, you are responsible for hosting, third-party service accounts and ongoing operation, unless a separate maintenance agreement is in place. Maintenance, improvements and further development are arranged separately.

Ownership

Intellectual property and ownership of deliverables transfer on the basis set out in the project agreement, on payment of the fees for those deliverables.

Contact

Fahymas LLC — contact@fahymas.com — +1 (859) 210-9982