Hiring an App Development Company in Kolkata: 8 Checks
Hiring a Mobile App Development Company in Kolkata: 8 Things to Check Before You Pay a Deposit
App projects go wrong differently from website projects, and more expensively.
A bad website is embarrassing and replaceable. A bad app is a rejected store submission, a users’ list of one-star reviews, a codebase nobody else will touch, and — the one that catches people out — an app store account you do not control, holding a product you paid for.
Kolkata has capable app developers. It also has firms that will quote you a very attractive number and hand you a problem. These eight checks separate them, and all of them happen before money changes hands.
1. Who owns the code — and where does it live?
The first question, and the one that determines whether you have bought an asset or rented one.
Ask: will the source code be in a repository owned by us, from day one, with our developers having access throughout? Not delivered at the end — from the start.
Why it matters: code delivered as a zip file at the end of a project, if it arrives at all, is how businesses discover that what they own is unmaintainable by anyone else. A shared repository from day one means you can bring in another developer at any point, which is both a protection and, frankly, a way of keeping everyone honest.
Red flag: any reluctance, any suggestion that the code is proprietary to their framework, any version of “we’ll hand it over at the end.”
2. Whose name is on the app store accounts?
Specific to apps, routinely overlooked, and painful to fix later.
Your app should be published under your Apple Developer account and your Google Play Console account, both registered to your business. If it is published under the agency’s account, they control your listing, your reviews, your updates and your ability to leave.
Ask: we will register the developer accounts in our company name and add you as a developer — is that acceptable?
If it is not, you have learned something important.
3. What exactly is being built, screen by screen?
Most app disputes are scope disputes, and most scope disputes trace back to a proposal that described features rather than screens.
“User management” can mean a login page or a full role-based permissions system with invitations, audit logs and account recovery. The gap between those interpretations is months.
Ask for: a screen-by-screen list, or wireframes, before signing. Including the unglamorous ones — errors, empty states, loading, offline, onboarding, password reset. Those screens are half the work and they are the ones missing from cheap quotes.
A good sign: an agency that pushes back and reduces your scope before quoting. It usually means they intend to actually build it.
4. Which platforms, and built how?
Native, cross-platform or web — a technical decision with real cost consequences, and one that should be justified rather than defaulted to.
Ask: what are you proposing and why, and what are the trade-offs for our specific case?
A firm that answers “we build everything in X” is telling you they have one skill, not that X is right for you. We go through the actual trade-offs in native versus PWA versus cross-platform.
5. What is the design process — and who does it?
The most common structural weakness in Kolkata app quotes.
Many firms are development shops with a designer, and design is a short phase producing screens for developers to build. That works for internal tools. For anything a customer chooses to use, it is how you end up with an app that has every feature and no users.
Ask: who is doing the product design, how long is it allocated, and can we see product work rather than a portfolio of interfaces?
Rough benchmark: design should be 20–30% of the budget on a consumer-facing or business-critical app. If design is 8% of the quote, you are buying an implementation of your own assumptions.
6. How will it be tested, and on what?
Apps break on device and OS combinations you do not own. Android in India is enormously fragmented — a huge range of manufacturers, screen sizes, Android versions and memory constraints.
Ask: which devices will you test on, how do you handle older Android versions, and what happens when a bug is found after launch?
Also ask about network conditions. An app tested only on office wifi will behave badly on a patchy connection, and that is how most of your users will experience it.
Establish the warranty period. Bugs found within a defined window after launch should be fixed free. Get the window and the definition of “bug” in writing, because the boundary between a bug and a change request is where post-launch relationships sour.
7. What does year one actually cost?
The build price is not the cost of the app.
Get written numbers for: ongoing maintenance (budget 15–25% of build cost annually), backend and hosting costs at your expected usage, third-party services such as SMS, OTP, push and payments, app store fees ($99/year Apple, $25 one-time Google), and the day rate for changes after launch.
The one people forget: iOS and Android ship major versions every year. An app that is not maintained will break on its own within about eighteen months, regardless of whether anyone touched it.
We laid out the full cost picture in what it costs to design and build an app in 2026.
8. What happens if we want to leave?
Ask it directly. The answer, and the reaction to the question, tell you most of what you need to know.
A good answer: you have the code, the accounts and the documentation throughout, so leaving is inconvenient rather than catastrophic.
A bad answer: anything that reveals you cannot leave without losing something.
You are not being adversarial by asking. You are checking whether the relationship is held together by mutual interest or by lock-in.
What a fair Kolkata price looks like
Kolkata rates sit at the lower end of the Indian market, which is genuinely an advantage — but it also means the gap between a serious quote and an unserious one is wide.
As a rough guide: a simple app with one user type and a straightforward backend starts around ₹4–8 lakh. Something with payments, multiple user types and real integrations runs ₹12 lakh and up. Anything transactional and business-critical — like the ticketing platform we built for CRSPL, handling thousands of transactions daily across multiple locations — is a different bracket again.
If a quote for a substantial app comes in at ₹1.5 lakh, it is not a bargain. Something on this list of eight is missing from it, and the most likely candidates are design, testing and the screens nobody remembered to specify.
The shortest version
Own the code. Own the accounts. Get the screens listed before you sign. Check that design is properly funded. Establish the warranty. Know year one’s costs.
Six sentences, and they prevent nearly every expensive outcome in app development.
Frequently asked questions
How much does app development cost in Kolkata? Roughly ₹4–8 lakh for a simple app, ₹12 lakh and up for one with payments, multiple user types and integrations, and considerably more for business-critical transactional platforms. Kolkata rates sit at the lower end of the Indian market.
Who should own the Apple and Google developer accounts? You should, registered in your business’s name, with the development agency added as a developer. An app published under an agency’s account leaves you without control of your own listing, reviews and updates.
How long does it take to build an app? Four to eight weeks for a genuine MVP, ten to twenty weeks for a medium-complexity app, and longer for enterprise builds. Unclear scope causes more delay than development speed does.
What should be included in an app development contract? Screen-by-screen scope, platform and technology choice, code ownership and repository access, app store account ownership, testing devices, warranty period, maintenance terms and post-launch rates.
Should I choose a Kolkata firm or one from a larger city? Kolkata has capable teams at competitive rates. Judge on relevant portfolio, design capability and the eight checks above rather than on location — app development is not a proximity business.
What are the ongoing costs after launch? Budget 15–25% of the build cost annually for maintenance, plus backend hosting, third-party services and app store fees. Unmaintained apps break within roughly eighteen months as operating systems update.
About to sign with an app developer? Send us the proposal. We’ll tell you what’s missing from it, whether or not you work with us. Book a call →
