Straight answers

For a small business system, a realistic range is ₹75,000 to ₹4,00,000 depending on how many screens and how much business logic is involved. A single automation can start around ₹25,000. Anything quoted far below that range is usually a template with your logo on it; far above, and you are paying for someone's sales overhead.

We carry no sales team, no account-manager layer, and no office you are indirectly funding. We build narrow — only the screens you will use. We reuse a foundation already hardened across five production systems, so authentication, roles, tables, forms, exports and audit logging are not rebuilt and re-billed each time. And we deploy on managed cloud infrastructure costing hundreds of rupees a month.

Usually, yes — which is why we do not describe ourselves as cheap. Cheap software is a template, no database design, no permissions, and a developer who disappears. Economical software is a smaller scope built to a proper standard. The difference shows up in year two, when one of them still works.

Not for the agreed scope. If you ask for something outside it, we quote that separately and you decide. The written scope exists precisely so neither of us is arguing later about what was included.

A focused automation takes one to two weeks. A first working system with around eight screens typically takes four to six weeks. A multi-module business system runs eight to fourteen weeks. You get a live staging link in the first week regardless, so you can see progress rather than take our word for it.

A 30–45 minute scoping call, then roughly an hour a week to look at staging and give feedback, then a couple of hours for training at the end. The projects that go wrong are the ones where nobody on the client side looks at it until handover.

Yes. We are based in Chennai and work remotely across India — scoping, reviews and training all work over video calls and a shared staging link. Local clients get on-site visits where it genuinely helps.

That is the normal starting position, and the scoping call is designed for it. You describe how the work happens today; we turn that into a list of screens and rules. You are approving a concrete document, not a vague intention.

Yes — the repository, the database and the domain are all in your name. There is no licence preventing you from taking the project to another developer. We would rather earn the maintenance work than trap you into it.

A fair question to ask anyone small. Three things protect you: the code is in your repository from the first commit, the stack is mainstream enough that any competent developer can pick it up, and the database is standard PostgreSQL you can export at any time. Nothing about the setup depends on us continuing to exist.

No. The first weeks of real usage always surface edge cases and those fixes are included. After that you can take a monthly plan, call us per change, or run it yourself.

Often, yes — provided we can read the code and it uses a stack we can maintain. We start with a short paid review and tell you honestly what shape it is in before either of us commits to anything longer.

Yes. Everything we build is a responsive web application, and where it helps we make it installable so staff can add it to a phone home screen and open it like an app. That costs a fraction of building and maintaining two native apps.

Usually. We have built Tally XML integration, REST API connectors, Excel and CSV import pipelines, and WhatsApp notification flows. If a system has an export or an API, we can generally work with it.

In a PostgreSQL database on managed cloud infrastructure, in an account you control, with automated backups. You can export the whole thing at any time, and we will show you how.

Every screen enforces permission checks server-side, passwords are hashed, sessions are signed, all traffic is HTTPS, and dependencies are patched on a regular cadence. We will not claim a certification we do not hold — but the basics are done properly rather than skipped.