Delivery Policy
This Delivery Policy outlines how Vian Software Solutions delivers digital services, manages project timelines, transfers deliverables, and handles client acceptance of completed work. This policy applies to all digital service engagements.
Overview
Vian Software Solutions is a software development and digital services company. We do not manufacture, sell, or ship physical goods, jewelry, or tangible products. All our services are delivered electronically.
As a digital services provider, our deliverables include source code, design assets, documentation, analytics reports, and other digital materials transferred via secure electronic means. This policy explains how we manage the delivery process to ensure a smooth and transparent experience for our clients.
Digital Delivery
All project deliverables are transmitted electronically using secure methods appropriate to the type of asset being delivered:
- Source Code: Delivered via Git repository (GitHub, GitLab, or Bitbucket) with appropriate access controls. The Client will be granted access to the repository upon completion of the relevant milestone or project phase.
- Design Assets: Delivered via file sharing services, cloud storage links, or directly through project management platforms. Formats may include Figma files, Adobe XD files, Sketch files, or standard image formats as agreed.
- Documentation: Delivered in PDF, Markdown, or web-based format through documentation platforms or as part of the project repository.
- Analytics and Reports: Delivered as PDF reports, dashboard access links, or data exports in standard formats.
- Deployed Websites and Applications: Delivered via deployment to the Client's hosting environment, our staging environment, or the production URL as specified in the agreement.
All digital assets are transmitted with appropriate security measures, including encryption for sensitive materials. Clients are responsible for securing their own access credentials and maintaining backups of delivered assets.
Project Timelines
Project timelines are established during the proposal phase and documented in the statement of work or service agreement. The following principles apply:
- Timelines are estimates based on the information available at the time of proposal and are made in good faith.
- The project start date is contingent upon receipt of the signed agreement and any required initial payment.
- Timelines may be adjusted due to scope changes, client feedback delays, third-party dependencies, or unforeseen technical challenges.
- We will communicate any material changes to the timeline as soon as reasonably possible.
- Timelines are calculated in business days unless otherwise specified. Business days exclude weekends and public holidays observed in India.
Milestone Deliverables
For projects structured with milestones, the following delivery process applies:
- At the completion of each milestone, we will deliver the agreed-upon deliverables and notify the Client that the milestone is ready for review.
- The Client shall have a review period of 5 business days (or as otherwise specified in the agreement) to evaluate the deliverables and provide feedback or acceptance.
- If the Client identifies issues or required changes, we will address them within a reasonable time and resubmit for review.
- Milestone payment becomes due upon delivery of the milestone, regardless of the review period, unless otherwise agreed.
- If the Client does not respond within the review period, the milestone shall be deemed accepted.
Source Code Delivery
For software development projects, source code is delivered as follows:
- The source code is maintained in a version control repository throughout the project lifecycle.
- Upon full payment of all fees, the Client is granted full access to the repository with appropriate permissions.
- The repository will include a README file with setup and deployment instructions.
- Where feasible, we provide documentation covering the architecture, key components, and configuration details.
- The source code is delivered in a deployable state, with dependencies documented in standard configuration files (e.g., package.json, requirements.txt, Gemfile, etc.).
- Database schemas, migration scripts, and any required seed data are included where applicable.
Communication
Effective communication is essential to successful project delivery. Our communication practices are as follows:
- Primary Channels: Email, project management tools (e.g., Trello, Asana, Jira), and scheduled video calls as needed.
- Response Times: We aim to respond to messages within 24 business hours during the work week.
- Status Updates: We provide regular status updates at a frequency agreed upon with the Client, typically weekly for active projects.
- Escalation: If an issue cannot be resolved through normal channels, Clients may escalate to our project management team via email.
- Emergency Contact: For critical production issues, emergency contact information is provided to active support clients.
Acceptance
The acceptance process for project deliverables is as follows:
- Review Period: The Client has a specified review period to evaluate deliverables after delivery. The standard review period is 5 business days unless otherwise agreed.
- Acceptance Criteria: Deliverables are evaluated against the acceptance criteria defined in the statement of work or project specification.
- Defect Reporting: The Client should report any defects, bugs, or deviations from specifications during the review period with sufficient detail for reproduction.
- Remediation: We will address reported defects within a reasonable time. Minor defects do not constitute grounds for withholding acceptance or payment.
- Deemed Acceptance: If the Client does not provide feedback within the review period, the deliverables are deemed accepted.
- Partial Acceptance: The Client may accept individual milestones while later milestones are still in progress.
Delays
Project delays can occur for various reasons. Our approach to managing delays is as follows:
- Client-Caused Delays: Delays caused by late feedback, delayed approvals, or failure to provide required materials will result in a corresponding extension of the project timeline. We are not liable for delays caused by the Client.
- Our-Caused Delays: If we anticipate a delay in delivering a milestone, we will notify the Client as soon as possible with a revised delivery date.
- Third-Party Delays: Delays caused by third-party services, hosting providers, API dependencies, or other external factors are outside our reasonable control and will extend timelines accordingly.
- Force Majeure: Delays caused by force majeure events are governed by the force majeure clause in our Terms and Conditions.
- Expedited Delivery: If the Client requires expedited delivery, additional rush fees may apply. Such requests must be made in writing and agreed upon before implementation.
Contact
If you have any questions about this Delivery Policy, please contact us:
- Email: virenpandey89@gmail.com
- Phone: +91 9598443203