Locations
Software Development Company in Kolkata
Atisolve builds custom software, mobile applications and web platforms for businesses in Kolkata. We work remotely on Indian business hours, so you deal directly with the developers on your project rather than through a layer of account management.
This page sets out what we build, how a remote engagement runs, and what to establish about any development partner before committing budget. Contact details are at the bottom.
Replacing Systems That Have Been Working for Twenty Years
Kolkata has a higher concentration of long-established businesses than almost anywhere else in India — trading houses, tea and jute, engineering firms, distributors and professional practices that have been operating for decades. Many are on their second or third generation of management. That produces a software problem with a very particular shape.
The system in place usually works. It may be an old FoxPro or VB application, a heavily customised package, or an arrangement of spreadsheets and registers refined over twenty years. It encodes an enormous amount of institutional knowledge — pricing rules, credit terms per customer, exceptions that exist for reasons nobody has written down. It is also slow to change, dependent on someone approaching retirement, and running on something no longer supported.
The mistake we see repeatedly is treating this as a greenfield build. A new system designed from a requirements document will capture the process people describe, not the process they actually follow, and the difference between the two is where twenty years of accumulated exceptions live. It launches, it does not handle the cases nobody mentioned, and people quietly go back to the old way.
The alternative is slower and works better: read the existing system before designing the new one. The old code is documentation, however unpleasant it is to read. Every strange condition in it exists because something happened once. We would rather spend two weeks understanding why a discount rule has three exceptions than discover the reason from an angry customer after go-live.
What We Build
Legacy Modernisation
Replacing systems that still work but have become slow to change and risky to depend on — generally in stages, so the business keeps running while the new system takes over area by area.
Order and Inventory Systems
Purchases, stock across godowns, dispatch, returns and reconciliation for trading and distribution businesses running several product lines.
Custom Business Software
Internal systems built around how the firm actually operates — approvals, credit control, scheduling, documentation and reporting that reflects reality rather than the org chart.
Customer and Dealer Portals
Platforms where customers, dealers or agents place orders, check status and pull statements themselves instead of telephoning your staff.
System Integration
Connecting Tally or your ERP to operations, marketplaces, payment gateways and logistics partners so a figure is entered once and agrees everywhere.
Mobile Applications
Android and iOS apps with the backend they depend on, built as one system — field sales, delivery tracking and customer apps.
We also provide SEO, generative engine optimisation, digital marketing, UI/UX design and ongoing maintenance.
How a Remote Engagement Actually Works
Read What Exists
For a replacement project we start by reading the current system and talking to the people who operate it daily — not only the managers. The exceptions that matter are usually known to a clerk rather than to a director.
Scope and Estimate
A written breakdown of what gets built, sequenced and priced, with assumptions and exclusions stated. Where we are uncertain we say so and explain what would settle it.
Build in Increments
Working software every two weeks, starting with the area causing most pain. Real use reshapes requirements far more reliably than a specification review.
Run in Parallel
For replacements we usually run old and new alongside each other for a period and compare outputs. It is duplicated effort for a few weeks and it is the cheapest insurance available against discovering a missing rule after the old system is switched off.
Migrate and Launch
Deployment, data migration and training. Decades of accumulated records are routinely the hardest part of these projects and we plan for it explicitly rather than meeting it at the end.
Support
A maintenance retainer or a documented handover to your own team, without the handover being priced to discourage it.
Communication and Working Hours
A shared WhatsApp, Slack or Teams channel with the developers on it rather than a ticket queue, and written weekly summaries whether the news is good or not. Same time zone, so nothing waits overnight for an answer.
Industries We Work With in Kolkata
Trading and Distribution
Established houses running multiple product lines, credit terms that vary by customer, and stock across several godowns.
Engineering and Manufacturing
Production planning, job costing and dispatch for firms in and around the industrial belts, usually integrating with accounting already in place.
Tea, Jute and Commodities
Lot tracking, grading, auction records and buyer documentation for trades where the paperwork is as important as the goods.
Professional Services
Legal, accounting and consulting practices needing matter tracking, document management and billing that reflects work actually done.
Healthcare
Hospitals, clinics and diagnostic chains joining up patient records, appointments, billing and report delivery across locations.
Education
Institutions handling admissions, attendance, assessment and fee collection across systems that were never designed to interoperate.
Keeping a Team Is Harder Than Building the System
Kolkata produces a great many capable engineers and loses a large share of them to Bengaluru, Hyderabad and Pune. For a business here that means hiring an in-house developer is achievable, but keeping the specific person who understands your system is considerably harder, and the risk concentrates exactly where you least want it.
We build with that in mind: conventional framework patterns rather than clever abstractions, documentation written for whoever arrives next rather than for us, and more than one person familiar with the codebase. Every firm claims this, so the way to test it is to ask mid-project for a walkthrough of some part of the system by someone who did not write it.
When the Second Generation Takes Over
A large share of the software projects we see in Kolkata start for the same reason: someone younger has taken a serious role in a family business and cannot accept that nobody can answer a straightforward question without a two-day search through registers. That is a good reason to build something. It also carries a predictable difficulty.
The people who have run the operation for twenty years are not obstructive, but they are rightly sceptical. They have seen the current arrangement survive things a new system has not been tested against, and they know which of its apparent inefficiencies are actually deliberate. A project framed as replacing their judgement with a computer will be resisted, quietly and effectively, no matter how good the software is.
What works better is treating them as the source rather than the obstacle. The exceptions they carry in their heads are the specification. We would rather spend the extra days interviewing the person who has done the job since before the software existed than build from a clean requirements document and discover what it omitted after go-live.
What to Check Before Hiring Any Development Partner
- Will they read the existing system? A partner who recommends a full rewrite before reading your current code is choosing the easier path for themselves, not the cheaper one for you.
- Who owns the code? You, in the contract, with no conditions attached to continued payment.
- Whose account is it hosted in? Yours, under your billing, or changing supplier means rebuilding.
- Who will actually write it? Meet them, and ask what happens if that person leaves mid-project.
- What is documented? Enough that a different developer could take over without a guided tour.
- What does support cost afterwards? Establish it before you depend on the system.
When We Are Not the Right Choice
If you need thirty developers next quarter, a larger services firm is better structured for it. If you need someone physically present daily, hire locally. And if your existing system is sound and merely undocumented, we will tell you that after the assessment rather than sell you a replacement you do not need.
Pricing and Engagement Models
- Fixed scope, fixed price. For settled requirements — a defined deliverable at an agreed price, changes quoted separately.
- Retained team. Agreed days per month against a backlog you prioritise, for continuous work.
- Phased. Fixed-price assessment and first phase, then a real decision point. Nearly all our replacement projects start this way, because the assessment usually changes the scope.
We quote per project rather than publishing rates. Estimates state their assumptions and exclusions so a comparison against another quote compares like with like.
Getting Started
Start with a conversation. Call +91 91082 92463 or email atisolve@gmail.com. You can also see the full range of services, read how we work, or browse our writing on building software.
Frequently Asked Questions
Do you have an office in Kolkata?
No. We are a remote-first team serving clients across India and prefer to state that plainly rather than imply a local presence. We work Indian business hours and travel where a meeting genuinely needs to be in person. If a partner with a local office is a firm requirement, we are not the right fit.
Our system is very old. Can it be replaced without stopping work?
Usually, and it should be. We replace in stages rather than in one switchover — one area at a time, with old and new running in parallel and their outputs compared before the old one is retired. It takes longer and costs a little more than a single cutover, and it is the difference between a difficult month and a catastrophic one.
Nobody remembers why parts of our system work the way they do. Is that a problem?
It is normal, and it is the main reason we read the old code rather than working only from interviews. Every odd condition in a twenty-year-old system was put there because something happened. We would rather spend two weeks working out why a rule has three exceptions than find out from a customer after go-live.
How much does custom software development cost in Kolkata?
Too variable for a meaningful single figure, and replacement projects vary more than most because the answer depends on what the old system turns out to contain. That is exactly why we start with a paid assessment — it converts a guess into an estimate you can rely on.
Who owns the code you write?
You do, in full, written into the contract — source, deployment configuration and documentation. Wherever possible we deploy into your own cloud account so the infrastructure is yours as well.
Our older staff are not comfortable with new systems. Will they use it?
This decides whether the project succeeds and it is a design problem, not a training one. Systems fail when the new way takes longer than the old way for the person doing the work. We keep screens close to the existing workflow where that is sensible, support Bengali or Hindi where it helps, and test with the people who will actually use it rather than with the most capable person in the office.
Can you work alongside our existing IT person?
Yes, and it is often the best arrangement — they hold the institutional knowledge and we bring capacity and current practice. We agree the boundary and the review process at the start, because ambiguity about who owns which part causes more trouble than any technical disagreement.
What if we want to bring development in-house later?
That is a legitimate goal and we plan for it when you say so. In practice it means documentation aimed at an incoming team, avoiding unusual technology choices, and a handover period where your developers work on the system with us still available rather than being handed a repository and wished well.
Do you sign NDAs?
Yes, routinely and usually before the first detailed conversation. If your customer terms or pricing are sensitive, raise it at the outset.
How do we begin?
Call +91 91082 92463 or email atisolve@gmail.com describing the problem. We will propose a discovery conversation, free and without obligation, and for replacement projects a short paid assessment before any larger commitment.
Have a vision? Let’s bring it to life.
Whether it’s an app, website, or platform—your idea deserves expert execution. Let us help you build it from the ground up with clarity, care, and speed.
