Custom Software Development
Software shaped around the way your business already works, instead of a packaged product you have to reorganise around.
About us
Codes Atlas System builds custom software, websites, web and mobile applications, ERP platforms and cloud infrastructure for businesses in Kolkata and West Bengal.
Most of the businesses we work with are not looking for technology for its own sake. They have a process that has outgrown the way it is currently held together, and they want it to stop costing them time.
So we start there — with how the work is actually done, who does it and where it breaks — and only then talk about what to build. Sometimes the honest answer is that an existing product would serve you better, and we say so.
You will talk to the people writing the software. You will own the source code, the repositories and the hosting accounts. And the system will be documented well enough that another developer could pick it up without archaeology.
Six broad areas of work. Most projects draw on more than one of them, which is part of why they sit under one roof.
Custom software
Systems built around your process.
Web and apps
Sites, portals and browser applications.
Mobile
Android and iOS from one codebase.
ERP and CRM
Operations and sales on shared data.
Cloud and DevOps
Hosting, pipelines and monitoring.
Support
Maintenance for systems already running.
Services
Sixteen services covering the full range — from a first website through to a multi-module ERP rollout and the support that follows.
Software shaped around the way your business already works, instead of a packaged product you have to reorganise around.
A website is usually the first thing a prospective customer sees. It should load quickly, say something useful and be findable.
Applications that run in the browser, handle real workloads and hold up when several departments depend on them at once.
Apps built to be used daily — fast to open, sensible offline and maintainable once they are in the stores.
One system for inventory, purchasing, production, sales and accounts — built module by module so the business keeps running throughout.
Hosting designed around what your application actually needs, with the monitoring and backups that make it safe to rely on.
Our stack
Chosen per project from your requirements, your existing systems and who will maintain the result. Click a technology to see how we deliver it — every one of those pages also says where that technology is the wrong choice.
Why work with us
No claims about being the biggest or the best. Just the things that make a development relationship work.
We start from how your business actually runs, not from a template that has to be bent into shape afterwards.
Source code, repositories, hosting accounts and domains stay in your name. There is no lock-in and nothing held back.
Data models and services are designed for the load you expect in three years, not just the load on launch day.
You talk to the people building the system. Questions get answered by someone who knows the code.
Access control, input validation, encrypted transport and sensible data retention are part of the build, not a later hardening exercise.
Readable structure, meaningful naming and written documentation, so another developer can pick the project up without archaeology.
Most systems need adjusting once real users arrive. We stay available for that rather than disappearing at handover.
If a feature is not worth building yet, we say so and explain why, even when it makes the project smaller.
How we work
Seven stages, each producing something you can review. Nothing moves forward until you have seen the output of the stage before it.
The sequence every project follows. The stages are deliberately small: a checkpoint you can act on is worth more than a milestone you can only accept or reject.
Discovery
We map how the work is done today — the people, the handoffs and the spreadsheets holding it together — before proposing any software.
Planning
Scope, priorities and a build order. You get a written plan that says what ships first and what deliberately waits.
UI/UX design
Screens and flows are agreed before code is written, so changes happen in a design file rather than halfway through development.
Development
Built in short cycles against the agreed plan, with working software to look at throughout rather than one reveal at the end.
Testing
Functional, cross-browser, mobile and load-sensitive checks, plus a pass over access control and data handling.
Deployment
Release to your hosting or cloud account, with the domain, certificates, backups and monitoring configured and documented.
Maintenance
Updates, fixes and small improvements after launch, on a support arrangement that matches how critical the system is to you.
Industries
Each sector runs on a different operational shape. The industry pages map those workflows rather than restating the same list.
Systems that keep patient records accurate and accessible to the right people, without adding clerical work to clinical time.
Typical systems Clinic and hospital management · Electronic patient records · Diagnostics and laboratory
Systems that reduce administrative load so teaching staff spend their time teaching.
Typical systems Admissions · Student records · Attendance
The systems behind the storefront — catalogue, inventory, orders and the reconciliation that keeps the numbers honest.
Typical systems Catalogue management · Inventory synchronisation · Order management
Systems that hold up in the field, where connectivity is unreliable and the person using them is standing at a loading bay.
Typical systems Consignment management · Fleet management · Route planning
Systems built around a sales cycle measured in months, where the follow-up matters more than the enquiry.
Typical systems Inventory and listings · Lead management · Site visit scheduling
Systems where correctness, traceability and access control are the requirement — not features layered on afterwards.
Typical systems Loan origination · Loan management · Collections
Systems that connect what was planned, what was consumed and what was actually produced.
Typical systems Bill of materials · Production planning · Shop floor capture
Point of sale that keeps working when the internet does not, connected to stock the head office can actually see.
Typical systems Point of sale · Multi-store inventory · Purchase management
Portfolio
Demonstration concepts, clearly labelled as such. We do not publish client work without permission, and we do not invent it.
Multi-godown distribution platform
ERP
Stock, purchasing and dispatch across several warehouses on one set of records, with credit exposure visible per customer.
Clinic and diagnostics management
Web applications
Appointments, consultation records, diagnostics workflow and billing against a single patient identity.
Offline-first field service app
Mobile apps
Task lists, job updates and proof of completion that keep working without a data connection.
Case studies
Representative scenarios showing our approach from problem through to rollout — with no invented figures attached.
Distribution
A representative scenario showing how we approach a distribution business whose stock records have diverged across locations.
Field services
A representative scenario for a field team working where mobile data coverage cannot be relied on.
Enterprise
A representative scenario for a business-critical system whose original developer is no longer available.
Where we work
Fifty location pages covering the districts we serve, each written around the local economy rather than the same text with a different town name.
Technology expertise
The right technology depends on the requirement, your existing systems and who maintains it afterwards.
A technically superior choice your team cannot maintain is not superior in practice. That is why we weigh your existing skills and infrastructure alongside the purely technical merits.
It is also why every technology page on this site includes a section on when not to use that technology. If you are being told a single stack is right for everything, you are being sold to.
The most valuable advice is often that you do not need a custom build. Here is how we tell the difference.
Your process is genuinely distinctive
Packaged software fits only part of the job
Per-seat licensing scales badly for your team
Integration with existing systems is central
The process itself is a competitive advantage
Your process is close to industry standard
A mature product already covers it well
Speed to launch matters more than exact fit
You would rather not own the maintenance
The budget is better spent elsewhere
Client feedback
We have not published testimonials on this site, because none has yet been supplied for publication with the client’s name attached.
Reviews on our Google Business Profile are public, verifiable and useful to the next business deciding who to call. When we have written testimonials cleared for publication, they will appear here with the name and company attached.
FAQ
It starts with understanding your process rather than your feature list. We map how the work is done today, write a specification you can read and correct, agree the screens, then build in short cycles with working software to review throughout. Testing, deployment and a period of support follow.
You describe the problem; we ask questions about how the work is done now and where it breaks. By the end you should have a clearer idea of what is involved and roughly what it would take. There is no obligation, and if we think you would be better served by an existing product we will say so.
No. Most useful projects start from a problem rather than a specification. Writing the requirements is part of the work, and doing it together usually produces a better result than receiving a finished document.
Yes. We work with businesses in West Bengal and beyond. Most collaboration is remote, with on-site visits where a project genuinely benefits — process mapping, plant walkthroughs and training sessions in particular.
It depends on scope, and any figure quoted before understanding the scope would be a guess. We give a written quotation against a written specification, so you can see what is included and what is not. Fixed-price, retained and phased arrangements are all available.
A focused internal tool is typically a matter of weeks. A departmental system with integrations usually runs to a few months. Large multi-module platforms are delivered in phases so something useful goes live early rather than everything arriving at the end.
Describe the problem in plain language and we will tell you what it would take to solve it — the approach, the moving parts and the sensible order to build them in. No obligation either way.
Contact
Describe the problem in plain language. You will get an honest assessment of what it would take to solve it.