Software built for your process
We start from how your business actually runs, not from a template that has to be bent into shape afterwards.
About Codes Atlas System
A software development company based in Kolkata, building systems for businesses that have outgrown the tools holding their operations together.
What we do
We build custom software, websites, web and mobile applications, ERP platforms and cloud infrastructure. Most of our work starts the same way: a business has a process that is costing more time than it should, and the tools it runs on have stopped being adequate.
We map how the work is actually done — the approvals, the exceptions, the spreadsheet somebody maintains by hand — and then propose the smallest thing that would meaningfully improve it. Sometimes that is a substantial system. Sometimes it is one screen.
How we work
You talk to the people writing the software, not an account manager relaying messages. Requirements get written down and corrected before development starts, because a misunderstanding caught in a document costs minutes and the same misunderstanding caught in code costs days.
Work is delivered in short cycles with working software to look at throughout, rather than a single reveal at the end. Every stage produces something you can review and act on.
What you own
Source code, repositories, hosting accounts and domains are yours, registered in your name. Nothing is held back to keep you dependent on us for maintenance, and the code is documented well enough that another developer could take it over without archaeology.
What we will not do
We will not tell you a custom build is necessary when a packaged product would serve you better. We will not quote a timeline before understanding the scope. And we will not publish invented testimonials, client counts or awards — you will not find any on this site, because none has been independently verified.
The way a project moves
Eight stages from first conversation to ongoing support. Each one has an output you can look at, which is what stops a project drifting quietly off course.
Stage 01
Discovery
How the work is done today, and where it breaks.
Stage 02
Business understanding
What the business actually needs to change.
Stage 03
Planning
Scope, priorities and a written build order.
Stage 04
UI/UX
Screens and flows agreed before code.
Stage 05
Development
Short cycles with working software throughout.
Stage 06
Testing
Functional, device, access control and data integrity.
Stage 07
Deployment
Release, migration, certificates and monitoring.
Stage 08
Support
Fixes and refinements once real users arrive.
Principles
How we operate
Statements about working practice — not rankings, awards or superlatives.
You own everything
Source code, repositories, hosting accounts and domains stay in your name. There is no lock-in and nothing held back.
Architecture that can grow
Data models and services are designed for the load you expect in three years, not just the load on launch day.
Direct access to developers
You talk to the people building the system. Questions get answered by someone who knows the code.
Security taken seriously
Access control, input validation, encrypted transport and sensible data retention are part of the build, not a later hardening exercise.
Maintainable code
Readable structure, meaningful naming and written documentation, so another developer can pick the project up without archaeology.
Support after launch
Most systems need adjusting once real users arrive. We stay available for that rather than disappearing at handover.
Straight answers on scope
If a feature is not worth building yet, we say so and explain why, even when it makes the project smaller.
Engagement
Ways to work together
Four arrangements covering most situations. We will suggest which fits.
Model A
Fixed scope, fixed price
The scope is written down in detail before work starts, and the price is fixed against it. Changes are quoted separately as they come up.
Best for: Well-understood projects — a website, a defined module, a rebuild.
Model B
Monthly retained team
An agreed number of developer days each month, directed by your priorities. Scope can move without renegotiating a contract.
Best for: Products that will keep evolving after the first release.
Model C
Phased delivery
The system is split into phases that each ship something usable. Every phase is quoted before it begins.
Best for: Large ERP, SaaS and platform builds where the full scope is big.
Model D
Support and maintenance
Ongoing care for a system that already exists — ours or someone else’s — covering fixes, updates and small enhancements.
Best for: Live systems that need a reliable pair of hands.
Where we are
Find us
Tell us what you are trying to build
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.