About us
A small team that would rather be trusted than impressive
Delgrade Corporation started with a few developers who liked building things and disliked how software work usually gets sold. That is still roughly the shape of it.
We are based in Kolkata, West Bengal, and we build software for other businesses: the website customers arrive on, the app they use, and the internal system that keeps the whole thing running behind the scenes.
The team is deliberately small. That means we take on fewer projects than a bigger agency would, and it means the person who scoped your project is one of the people who builds it. There is no layer of account managers relaying messages, and nothing is quietly subcontracted without telling you.
It also shapes what we say no to. If a project needs a specialism we do not have, or if the honest answer is that an off-the-shelf tool would serve you better than anything custom, we will say so. Losing that job costs us less than delivering it badly.
We do not publish client counts, project tallies or five-star testimonials. Ask us for references and we will introduce you to people we have actually worked with.
What you can hold us to
Four commitments
Scope before code
We would rather spend an unpaid hour understanding the problem than three paid weeks building the wrong thing. You get a written scope and a fixed estimate before we start.
You own everything
Source code, repositories, domains, hosting and analytics accounts are yours and stay in your name. No hostage arrangements, no licence you have to keep renewing to keep the lights on.
One person you can call
A named point of contact for the life of the project. Small team, no account-management layer between you and the people writing the code.
Plain reporting
Weekly progress in plain language, including what slipped and why. If a deadline is at risk you hear it from us early, not on the day.
How a project runs
No surprises by design
The same four stages every time, whether the project is a two-week site or a six-month system.
Conversation
A call or a meeting in Kolkata. We ask what the software has to achieve and what happens today without it. No charge, no obligation.
Scope and estimate
A written document: what we will build, what we will not, the milestones, and a fixed price or a clear rate. You approve it before anything is built.
Build in the open
Short cycles with something you can click at the end of each one. You see progress in a staging environment rather than in a status report.
Launch and support
We handle deployment, monitoring and handover documentation, then stay available for changes on an agreed support arrangement.
Tell us what you are trying to build
A first conversation costs nothing and usually clarifies the scope more than another week of internal discussion.