Questions we get before you sign.

Fixed. We write down the scope, agree it with you, and price that — so the number you approve is the number you pay. We only bill hourly for open-ended support work after launch, and only when you ask for it. If a requirement is genuinely too vague to price, we will say so and propose a short paid scoping phase rather than invent a figure.

A paragraph about the problem is enough to start. From there we ask the handful of questions that actually move the price — how many people will use it, which platforms it has to run on, what it needs to connect to, and when you need it live. Most quotes go out within one working day of that conversation.

Three milestones on most projects: 40% to start, 30% when the build reaches a version you can test with real data, and 30% on handover before it goes live. Larger projects get split into more milestones so neither side is ever far ahead of the other. We invoice in rupees, with GST added where it applies.

Thirty days. After that we re-check it, mainly because third-party pricing moves on its own — hosting, developer accounts, API plans. The scope itself does not expire, so if you come back in three months with the same requirement the number usually barely changes.

Small things — copy edits, a field on an existing form, a colour — we absorb without a conversation. Anything that adds a screen, an integration or a new rule gets written up as a change note with its own price and its own effect on the launch date, and we do not start it until you approve that note in writing. There are no surprise line items at the end of a project.

Around ₹40,000. Below that, the cost of scoping, designing and handing something over properly is larger than the work itself, and you are better served by a template you can run yourself. We would rather tell you that than take the job and do a thin version of it.

A marketing site is usually two to three weeks. A mobile app or a custom CRM runs four to eight, depending on how much has to connect to systems you already use. We commit to a launch date in the quote, and every project has a weekly build on a live link, so you are never guessing where it stands.

Usually within the hour on WhatsApp during working hours, and within one working day at the outside. We are a small studio in Ludhiana, not a call centre — the person who answers your first message is one of the people who would build the thing.

Content, access and decisions. Text, logos, images and product data for the screens; logins for anything we have to connect to; and one named person who can approve a design without assembling a committee. Projects that slip almost always slip on feedback, not on code.

From the first week. You get clickable screens before we build anything real, then a staging link that updates weekly. You test it on your own phone and your own laptop, with your own data — we do not run projects on screenshots and status reports.

It happens and we do not penalise you for it. The launch date does move by roughly the length of the pause, because the team gets scheduled onto other work in the meantime and we cannot always pull it straight back. We flag that the moment it starts costing you a date, not at the end.

Often, yes. We can build one piece — an app on top of your existing API, a CRM beside a site someone else maintains — and we are happy to follow another team's conventions and submit to their code review. The one thing we ask for is a clear owner of each system, so a bug never sits between two vendors for a week.

Websites on Next.js and React, mobile apps on React Native so one codebase reaches both stores, back-ends on Node with PostgreSQL. TV apps use the same React foundation, extended for tvOS, Android TV and LG webOS. These are deliberately boring, well-documented choices — you should be able to hire any competent developer in India to work on your code long after we are gone.

Only where it is genuinely the right answer — a brochure site your own team will edit every week, for instance. We do not build custom software on no-code platforms, because the day you need something the platform did not anticipate, you are stuck and the migration is expensive. If an off-the-shelf tool solves your problem for less than we would charge, we will tell you to buy it.

You do, in full, from the moment the final invoice is paid — source code, design files and database schema, delivered as a Git repository in your own account. We keep no licence, no lock and no kill switch. We do reuse our own internal libraries across projects, and those reach you under an open licence you can keep using and modifying forever.

Yours. Hosting, the domain, the Apple and Google developer accounts and the Google Business Profile are set up under your company and your billing, and you give us admin access so we can work. Where we set something up under our own account to move faster, it is transferred to you before launch and listed in the handover document.

A business website is roughly ₹500 to ₹1,500 a month. A CRM or an app with a database behind it is usually ₹2,000 to ₹6,000. A domain is about ₹1,000 a year, an Apple developer account is $99 a year and a Google Play account is a one-time $25. None of that money is ours — you pay the providers directly at their price, and we never mark it up.

A repository you own, deployment instructions that work on a clean machine, every environment variable documented, admin logins for each account, and a walkthrough session recorded for whoever joins your team later. Our test is simple: if a new developer can only get the project running because we explained it in a meeting, the handover is not finished.

Anything that does not behave the way the agreed scope says it should — broken flows, errors under normal use, layouts that fall apart on a device we committed to supporting. You report it, we fix it, at no charge and with no limit on how many. The clock starts the day the work goes live, not the day the contract was signed.

New features, design changes you decided on after launch, content updates, and breakages caused by someone else editing the code or changing a third-party service. Those get quoted as normal work. We spell this out because support means very different things to different vendors, and the disagreement always arrives in month two.

Yes, on a monthly retainer. A website with updates, backups and small changes starts around ₹6,000 a month. An app or a CRM that people use daily is usually ₹15,000 to ₹30,000, depending on how fast you need us to respond. Ad-hoc work outside a retainer is ₹1,200 an hour, always with an estimate before we start.

No. Plenty of clients take the handover, run it themselves and call us twice a year. Nothing in the software is tied to us, so it does not stop working when a retainer does. What you give up is a guaranteed response time — without one, you join the queue behind projects that are actively running.

You already have what you need to do it. The code, the accounts and the documentation went to you at handover, not on request. Tell us and we will give the new team a written summary of the architecture and answer their questions for two weeks at no cost. We would rather you left cleanly than stayed because leaving was painful.

It is a fair thing to ask, and our answer is structural rather than reassuring. Everything sits in your accounts, on standard tooling, in a stack any competent Indian development team can pick up. If we were unreachable tomorrow you would lose a good working relationship, not your software. We will not pretend a small studio provides round-the-clock on-call cover, and if your business genuinely needs that, we will tell you before you sign.