Frequently Asked Questions

Nothing. The first call is 30 minutes, and its only job is to work out what you are actually trying to fix. You leave it with our honest read on whether software is the answer — sometimes it is not, and we will say so. If it is, you get a written scope, a fixed quote, and a delivery timeline before any money changes hands.

A brochure website is 2-3 weeks. A dynamic site or web app with accounts, payments, and a dashboard is 5-8 weeks. A mobile app is 8-12 weeks to both stores. Our ready-made products — BrightSchool, SmartFee, InvoAI, the parking platform — go live in 2-4 weeks because the software already exists; that time is data migration, configuration, and training.

Content and decisions, and both faster than most people expect. Logos, photos, service descriptions, and the final list of what the business does are the single most common reason a project slips. One named person on your side who can approve things without a committee is worth more to the timeline than anything we do.

You see a working build every week, on a real URL you can open on your own phone. Not screenshots, not a status percentage. If a week goes by with nothing to show, that is a problem worth raising, and we would rather you raised it.

Small changes are absorbed. Anything that changes the scope gets re-quoted for that piece only, in writing, before we build it — so the number never moves without you agreeing to it first. Because you see a build every week, most changes surface early when they are still cheap.

Yes — most of our clients are elsewhere in India. Mumbai, Navi Mumbai, and Thane get on-site meetings, training, and go-live support. Everywhere else gets the same team on call during IST hours, which for a business in India is the part that actually matters.

Fixed scope, fixed price, agreed before we start. We do not bill by the hour, because that makes our incentive the opposite of yours. If the scope changes, the change is quoted separately rather than quietly appearing on an invoice.

Typically split across milestones rather than paid up front — an advance to begin, one or more against agreed deliverables, and the balance at handover. The exact split is on the proposal before you sign, and it is negotiable for larger projects.

Yes, completely. The repository is transferred to your account at handover, and the domain, hosting, database, and payment gateway are set up under your own credentials from the start — not ours. There is no licence you have to keep renewing to keep using what you paid for.

You take the code, the credentials, and the documentation, and any competent developer can pick it up. We build on mainstream, well-documented tools specifically so that this is possible. A supplier you cannot leave is not a supplier, and we would rather not be one.

Often, yes, and we usually suggest it. Shipping one useful piece — the fee module, the enquiry flow, the invoicing — tells you far more about working with us than a proposal does, and it costs a fraction of committing to everything at once.

They are live products with existing users. InvoAI, BrightSchool ERP, SmartFee ERP, the AI Call Agent, and the parking platform are all in production today. You get configuration and data migration rather than a build, which is why they go live in weeks rather than months.

Yes. Most schools start with admissions and fees and add exams and the parent app once staff are comfortable. Phased rollouts are how adoption survives — big-bang launches are how it dies.

They are built API-first, so your existing accounting, HRMS, biometric attendance, payment gateway, or SSO connects rather than getting replaced. If something you rely on is not on our integrations list, it is usually an API call away — ask.

Yes, and it is the demo worth asking for. A canned dataset makes any software look good. Send us a sample of your real fee structure, invoice format, or call flow and we will show you the product handling it.

Configuration — fee heads, penalty rules, invoice formats, call scripts, parking rates — is built in and yours to change. Deeper changes to how a product works are possible and quoted as development. We will tell you plainly which of the two you are asking for.

Next.js and React on the web, Flutter for mobile, Node.js and PostgreSQL on the server, and AWS for hosting. Deliberately mainstream and well-documented, so any developer can pick your project up after us — including one who is not us.

In the Mumbai region by default, which is both faster for your users and simpler for anything with a data-residency requirement. On-premise or a specific cloud is fine where a policy or a client contract needs it; that is a real reason and we build for it.

Encryption in transit and at rest, role-based access down to the action, an audit log of who changed what, and automated daily backups. For enterprise deployments we add SSO and configurable retention. Ask us to walk through the specifics for your project — it is a fair question and we have an answer.

Yes, by restoring them. A backup job that has never been restored is a belief rather than a safeguard, and the time a restore takes is the number that actually matters when something goes wrong.

That is what we build for. A large share of Indian users are on mid-range Android devices and patchy mobile data, so we test there rather than on a flagship on office wifi. Where the use case demands it — attendance, parking, field apps — we build offline-first and sync when the connection returns.

You get an agreed support window with a named person to contact — not a form and an auto-reply. Handover includes written documentation, all credentials, and a live training session for the people who will use it every day.

For a website, not necessarily — though security updates and backups still have to happen, by us or by someone. For a mobile app, effectively yes: both mobile platforms change every year, and an app left alone for eighteen months starts failing store compliance.

We do, within the terms we agree up front. Being in the same timezone is the practical part of this — you are not filing a ticket into a queue that opens when your working day has already ended.

Yes, and on-site anywhere in Mumbai. Training happens in the language your team is comfortable with — Hindi, English, or Marathi. Software nobody was taught to use is software that quietly goes back to spreadsheets.

Often, yes. We audit what is there first and give you an honest read: if the stack is maintainable we improve it, and if rebuilding is genuinely cheaper than patching we will tell you that before you spend anything on either.