Shakya Consultants delivers digital services and project outputs, not physical products. This policy explains how we "deliver" completed work, what handover includes, and how revisions or replacements of deliverables are handled.
1. What we deliver
Depending on your project, deliverables may include:
- Web or mobile application source code in a Git repository;
- Deployed staging or production builds on agreed hosting;
- UI/UX design files (e.g. Figma exports);
- Automation workflows, CRM configurations, or integration setups;
- Dashboards, reports, and technical documentation;
- Recorded walkthroughs or handover sessions where agreed in scope.
2. Delivery process
Typical project flow:
- Discovery — requirements and timeline agreed in a proposal;
- Design / planning — wireframes, architecture, or sprint plan approved by you;
- Build — incremental demos on staging environments;
- Review — you test and share feedback within the agreed review window;
- Handover — code, access, and documentation transferred after milestone payment (if applicable).
Timelines depend on scope, your feedback speed, and access to required systems. Delays caused by pending approvals or missing content extend the schedule accordingly.
3. How delivery is confirmed
Delivery is considered complete when any of the following occurs:
- We share repository access, deployment links, or agreed files with you;
- You sign off on a milestone or user acceptance testing (UAT);
- You deploy the work to production without raising written defects within the review period stated in your proposal (typically 5–10 business days).
4. Revisions ("exchange" of deliverables)
In software projects, "exchange" means replacing or revising a deliverable within agreed revision rounds — not returning a physical item.
- Design phases usually include a limited number of revision rounds as stated in the proposal;
- Bug fixes for issues within agreed scope are addressed during the warranty/support period defined in your contract;
- New features, platform changes, or full redesigns after approval are treated as change requests and may be billed separately.
5. Client responsibilities after delivery
After handover, you are responsible for:
- Hosting and infrastructure costs (unless covered by a retainer);
- Backups, security, and access management on your accounts;
- App store submissions, domain renewals, and third-party subscription fees;
- Ongoing maintenance unless you have an active support or retainer agreement with us.
6. Defects
If a deliverable does not match the agreed specification, notify us in writing during the UAT period with clear steps to reproduce the issue. We will fix qualifying defects within the support terms of your engagement at no extra charge.
7. Contact
Delivery or handover questions: info@shakyaconsultants.com