A clear basis for the work.
How we approach enquiries, pricing, scope, reviews and support. Your written proposal sets out the specific arrangements for your project.
1. Enquiries and project agreements
Submitting an enquiry or selecting a package starts a conversation. It does not place a paid order or confirm a project booking. Before work starts, we agree the proposal, scope, commercial terms and any required payment arrangements in writing.
The accepted proposal defines the engagement. If it specifies a different arrangement from this general overview, that written project arrangement takes precedence.
2. Website prices and package boundaries
- Launch: ₹14,999. A one-time development price for the agreed website scope.
- Growth: ₹29,999. A one-time development price for the agreed website scope.
- Custom Build: ₹49,999–₹99,00,000. Quoted against an individual scope, from a focused build to larger phased work.
The Custom Build upper figure is ₹99,00,000, or ₹99 lakh. The range covers different project sizes; it is not a single fixed-price offer for any combination of features. The proposal defines the pages, functionality and integrations included.
Mobile apps, standalone software and AI integration receive tailored proposals. See the website packages page for the published inclusions.
3. Agreed scope
The proposal defines the pages, templates, functionality, content responsibilities, supported environments and acceptance criteria. Items outside that scope are estimated separately.
4. Design revisions
Launch includes 2 consolidated design feedback rounds; Growth includes 3. Custom Build rounds are agreed per project. Each round covers one collated set of feedback within the agreed brief. New requirements or a fresh design direction require a scope update.
5. Post-launch bug support
The included window begins on the agreed production launch date: 14 calendar days for Launch, 30 for Growth and 60 for Custom Build. It covers reproducible defects in our delivered work against the written acceptance scope.
6. Changes and ongoing care
New features, content updates, redesigns and ongoing maintenance are separate work. Third-party outages or service changes, and problems introduced by later external code changes, are outside the included bug-support scope.
7. External costs and taxes
Domain, hosting, paid tools, licences and provider fees are separate unless the proposal expressly includes them. Applicable taxes and expected external costs are identified in the proposal.
8. Milestones and payments
Delivery stages, target dates, payment milestones, review responsibilities and handover are agreed in writing before work starts. No universal delivery time applies to every project.
9. Content, access and client inputs
The project proposal identifies the content, brand assets, approvals and access needed from each party. You should have the right to use material you supply for the project. Content readiness, feedback and external dependencies can affect the target schedule.
Changes to requirements, deliverables or timing are recorded as an agreed scope update, including any effect on cost and milestones.
10. Ownership, licences and handover
Ownership, source files, account access, documentation and handover conditions are defined in the written proposal. Third-party software, fonts, imagery and services remain subject to their applicable licences or provider terms.
Any ongoing maintenance, hosting management or future development is agreed separately unless expressly included in the proposal.
11. Concept work shown on the website
Work labelled “Concept study” is an illustrative design exploration. It demonstrates a possible interface or product journey. It is not presented as a completed client engagement, launched product or measured business result.
12. Questions and privacy
To clarify a package or discuss the terms for your project, email codekaarya@gmail.com or send a project enquiry.
Our privacy notice explains how the website handles enquiry information and uploaded briefs.
