Policies

These policies may be updated over time. If you started a project with me earlier, the version sent to you at the time — over WhatsApp and email, along with your project brief and invoice — is the one that applies to you.

Core Policies

Payment structure

  • A token amount to get started
  • A second payment once the build is complete
  • The final balance when the project is handed over

If you'd rather pay it all at once, that works too — especially for smaller projects like the Basic pack, where the total stays well under ₹4,000.

Payments are collected through Razorpay, so you can pay by card, UPI, netbanking, or whatever's easiest for you. An invoice is sent first, with the payment link included, and you'll get an acknowledgement on WhatsApp and email once each payment is received.

Assets

If you provide your own photos, logos, or content, I'll use those. Otherwise, I'll use free or AI-generated visuals to fill the gaps.

Bug fixes

Any bug I'm responsible for — something that isn't working the way it was built to — gets fixed for free, no time limit.

This doesn't cover issues caused by a third-party service your site depends on (for example, your hosting provider changing their free plan, or a tool you integrated changing how it works). Those are outside my control, but I'll always help you figure out the next step if it happens.

Refunds

If you're not happy with the revisions before your site launches, you can request a refund on your advance. Once the site is live, refunds aren't available.

If you go quiet mid-project

If I don't hear back from you for a week or more while your project is underway, I'll try reaching out a few times. If there's still no response, the project gets paused, and the advance already paid isn't refundable in that case.

Picking things back up later is no problem — just reach out whenever you're ready.

Response time

I typically reply within 24 hours.

Handover

Once the final payment is made, you get everything — the code, hosting/account access, and any accounts set up specifically for your project.

CMS & Blog Policies

CMS setup

If you'd like to update your own website — like adding new photos, changing text, or posting new blog entries — without needing to contact me each time, that's what CMS setup gives you.

It comes in two forms: setting up your whole site to be self-editable, or adding a blog-style section (like a blog, case studies, or recipes) to a site that otherwise stays as-is.

How pages are counted

Adding a blog or a collection (like case studies or recipes) counts as 2 pages toward your pack: one for the entries themselves, and one for the page that lists them all.

The listing page is optional — if you'd rather not have one, that's fine, and it doesn't change the price either way.

What's included

Before your project is handed over, I'll walk you through how to use it, so you're comfortable making changes on your own from day one.

Managing content

Once your site is handed over, keeping it updated — adding posts, changing text, replacing photos — is your responsibility.

Third-party CMS provider

The CMS runs on a third-party platform (chosen based on what your site needs). Most platforms offer a free tier that comfortably covers a small business site. If your usage grows beyond that free tier, or if you choose to purchase anything else the provider offers, that's between you and the provider — outside of what I can be responsible for.

Why not WordPress?

WordPress is a common choice for CMS-driven sites, but good WordPress hosting usually comes with an ongoing monthly cost. The setup I use is built to run comfortably within free hosting limits for a site your size, so there's no recurring bill just to keep your CMS working.