Software built around the way your business actually works.

Custom work starts at ₹75,000, and most projects land between ₹1.5 lakh and ₹4 lakh depending on how much the system has to do and how many places it has to talk to. Full business systems are scoped individually after a call. Everything is milestone-based and priced in writing before we start.

A website tells people about your business. Software does the work: it holds records, takes bookings, tracks stock, chases payments and tells your team what needs doing. Plenty of businesses need one and are sold the other.

Usually a fast mobile site does the job for less money, and an installable web app covers most of the rest — home screen icon, offline use, notifications and the camera all work without a store listing. A native app earns its place when it needs the device itself: Bluetooth or NFC hardware, running in the background, or a listing customers will go looking for. Our app development page has a tool that walks through your own case and says which of the three it is.

Both. An annual maintenance contract with us covers releases, patching, backups that get tested, monitoring and someone to call — and we take it on for software somebody else wrote, not only our own. It is priced monthly or yearly once we have seen what it has to cover, because a response time promised without a defined scope is not worth much. We will look at what you have before quoting; occasionally the honest answer is that it needs replacing rather than maintaining.

That is usually where the return is. Common ones: an enquiry that reaches the right person and gets a reply without anyone remembering, admissions that run from form to payment to confirmation, appointment reminders, and orders that update stock and issue an invoice.

Yes, through the official WhatsApp Business API from Meta. That distinction matters — unofficial automation tools get business numbers banned, which is a risk we will not take with your main line of contact.

Where it earns its place, and that has its own page now — our AI automation page covers retrieval over your own documents, semantic search, extraction, multi-step and multi-agent pipelines and how they are scored, with a tool that tests whether your case is worth it at all. The short version: we will not add a chatbot because it is fashionable, and if a rule serves you better than a model we will tell you, because a rule is cheaper and never wrong.

Yes — single sign-on against the identity provider you already run, so there is no second password to issue, and revoking someone's account revokes their access here too. Underneath it, access is by role rather than per person: a branch manager sees their branch, and what each role can see and change is written down and agreed with you rather than decided by whoever built the screen. Every change of consequence is logged with who made it and when, which is the part your auditor asks for and the part that is expensive to add later.

Wherever your policy requires, and it is a question to settle in the first call rather than after the build. Default is your own cloud account or a server you control, in the region you name — data staying in India is a common requirement here and a straightforward one to meet. Personal data is handled to the DPDP Act, 2023, we tell you in writing what is processed and where before you agree to anything, and if you have a security questionnaire or a review process we fill it in rather than asking to skip it.

That is a large part of this work. The usual shape is to read from the old system while the new one runs alongside it, move one area at a time, and keep both correct until the last one is across — rather than a weekend cutover that either works or ruins a month. We start by finding out what the old system can actually be read from: an API, the database directly, or an export. Where the records are messy, and they usually are, cleaning them is scoped as its own piece of work with its own price, because pretending that is free is how migrations overrun.

Yes, all of it, and the right to have it changed by your own team or any developer you appoint, for as long as you like. Your data and your accounts are yours. What the licence holds back is passing it on — reselling it, publishing it, or letting another developer keep part of it for someone else. Outright ownership is available where a business needs it and is quoted separately, so ask before you commission rather than after.

That is the normal path, not a failure. We build the first version to do one job properly rather than guessing at everything you might need, then extend it once real use has shown what actually matters.