Questions before you start.

Me, directly. I handle the design, the code and the deployment, so the person you talk to is the person who builds it.

Yes. Each service stands alone. Most projects combine two or three of them, and the scope builder on the Services page lets you tick the parts you need and send me the result.

You send a short description, we agree scope on a call, and I send a written quote. The quote lists what is included, the timeline and the payment schedule. Nothing is charged before you have read and accepted it.

You do, once it is paid for. It lives in your repository and on your own accounts, with no platform fee and no lock-in.

Usually. Send me the repository or the design files and I will tell you what I can take on and what I would change first.

Possibly. If it sits next to what I have shipped, such as another kind of web app or integration, I will quote it. If it does not, I will say so rather than learn on your budget. The Work page lists what I have shipped and what I have not.

Smaller builds have a fixed scope, so they have a fixed price. Larger ones, such as a Standard or Premium API or a web and Android product, depend on what is inside them, so the listed price is where they start. A short call settles the scope, and the written quote confirms the final price before anything is charged.

Half to start and half on acceptance for jobs up to about ₹1,00,000, and three milestones above that. For the listed AI builds, the balance is due after the test passes. MVPs are billed 40% at start, 30% at a mid-build demo and 30% on acceptance. The schedule is written into your quote.

No GST is charged. Invoices carry my PAN, and TDS is deducted by you where it applies.

Your own hosting, domain, database, AI model and messaging usage, billed to your accounts by those providers. I estimate them before we start.

No. Checkout creates a project brief with your prices. We confirm scope on a short call first; you pay half to start and the rest after it passes its test.

It only answers when it can point to a line in your own content; otherwise it hands the question to your team. Misses on the test set are fixed before launch. Wrong answers you report later are fixed within 3 working days during the support period.

No. The suggested questions replay answers recorded in real test runs. Typed questions are matched by keyword against a small offline sample of captured passages and quoted back. A real build uses a language model on your own pages.

Monitoring, content refresh, a monthly re-run of the test and cost checks. They are not a bug-fixing hotline: the Watch plan is capped at about 4 hours a month. Model, hosting and messaging costs pass through at cost on your own accounts.

Model and WhatsApp usage is billed to your own accounts by those providers. For a support desk that is usually a few paise per question at current prices. I estimate it before we start.