Frequently asked questions

It depends on scope, and we would rather give you a real number than a cheap one. A business website typically falls in the tens of thousands of rupees; operational software with inventory or billing usually runs into the low lakhs; an AI automation project depends heavily on how clean your inputs are. The pricing page shows indicative ranges, and a short discovery conversation produces a figure specific to your requirement.

A focused website is two to four weeks from approved content. A single automation is two to five weeks. Operational software has a first working module in six to ten weeks, with further phases after that. The most common cause of delay is not development — it is waiting for content, data or decisions from the client side, so we structure that collection up front.

Yes, and a good share of our work is single-module projects for small businesses. Starting with one narrow, high-value piece — billing with stock, or WhatsApp enquiry handling — and expanding later works considerably better than attempting a complete system first.

You do. Source code, database and documentation are yours, and everything runs on infrastructure in your own accounts with billing in your name. If you stop working with us, we will brief an incoming developer. Nothing is locked to us.

Often, yes — and we will say so. Buy when your need is standard: accounting, payroll, email. Build when the process is specific to your business and no product fits without heavy compromise. We assess this during discovery and have recommended buying over building where that was genuinely cheaper for the client.

Sometimes. AI is genuinely good at answering questions from your documents, reading unstructured paperwork and handling the mechanical parts of a defined workflow. It is not a general answer to disorganised operations, and automating an undefined process only produces errors faster. We measure accuracy on your real data before you commit, and we will tell you when a database and a form would serve you better than a model.

You choose. We offer a monthly support arrangement covering fixes, dependency and security updates and a quota of small changes. Alternatively we hand over with documentation, tests and a walkthrough so your own team or another developer can maintain it.

Yes, as an optional monthly arrangement. It matters more than people expect: dependencies need security updates, APIs change their terms, and small process changes accumulate. Software left entirely untouched for a year tends to need expensive attention in the second year.

Yes, before any detailed discussion of your process or product if you prefer. We treat client information as confidential by default regardless of whether an agreement is in place.

Yes. Website, automation and AI projects are delivered remotely across India as standard, using video discovery, a reviewable staging environment and recorded training. For large operational projects where the process genuinely needs to be observed, an on-site visit can be arranged.

Text, service entries and contact details live in clearly commented configuration and content files, so a non-developer can make routine edits with brief guidance. If you would rather not touch code at all, we can connect a content management system or handle updates for you under a small monthly retainer.

We scope a first phase narrow enough to be delivered and used — the smallest version that replaces the current manual process. You see working software early, decide what phase two should be based on real usage, and retain the option to stop. Fixed scope per phase, not an open-ended build.

That risk cannot be reduced to zero, which is why the design matters. The assistant is constrained to answer only from retrieved passages of your own content, is instructed to decline when it finds nothing relevant, and can show the source behind an answer. We also test it against a list of awkward questions before launch and review logs afterwards.

Business verification with Meta usually takes a few days to two weeks depending on how quickly your documents are accepted. Template approval is normally within a day. We prepare the submission to minimise rejections, but the timeline is Meta's, not ours.

If your processes are standard, a product like ERPNext, Zoho or Odoo will be cheaper and faster, and we will recommend it. Custom development makes sense where your manufacturing or distribution process is genuinely unusual, where a product would need heavy customisation anyway, or where you have already been through a failed implementation of a rigid product.

For static sites and lightweight APIs, Cloudflare is extremely cost-effective and often free at small-business volumes. For general applications, DigitalOcean is simpler and cheaper than AWS and sufficient for most needs. AWS or Azure make sense at larger scale, where you need specific managed services, or where a client mandates them.

It can be migrated to the API, but then it cannot be used in the regular WhatsApp app any more. Many businesses put a new number on the API and keep the existing one for personal conversations already in progress. We will explain the trade-off before changing anything.

The design is built around that risk: answers come only from retrieved passages of your own content, sources are shown so customers and agents can verify, uncertain cases escalate rather than guess, and we test against a list of awkward questions before launch. We also review logs in the first weeks and correct specific answers directly.

Usually yes. Slab rates, customer categories, quantity breaks, material-based calculation, freight rules and approval limits are all expressible as rules. The real test is whether the logic can be written down — where part of it genuinely cannot, we automate the rest and leave that element to a reviewer.

For billing, stock and receivables, yes. For statutory accounting, audit and GST filing, we recommend keeping Tally and syncing to it, because your accountant and auditor already work there and replacing that creates risk without benefit.