Project Management Software for IT Companies in Kolkata

Support tickets and project builds, competing for the same people

Most IT services firms carry two kinds of work at once. There are support and maintenance contracts, where the client expects a ticket answered within an agreed time and the volume is never predictable. And there are builds, where scope and a delivery date were agreed up front and the team needs uninterrupted days to hit them.

When both run off one shared list, support always wins in the short term because it's louder, and the build quietly slips. A week later the project manager finds that two engineers spent most of their time on another client's tickets and nobody logged it against the right contract.

In ShipSprint each client gets its own project and board. A support contract can run as a continuous flow with per-column WIP limits, while a build runs in sprints. The limits make it visible when a support queue is full, so the decision to pull someone off a build is made by a person, on purpose, with both clients in view.

One intake for every client, assigned on purpose

Requests arrive by email, phone and chat, and the person who happens to read them first often ends up doing them. A triage inbox puts every new request in one place, where a lead decides which client's board it belongs on and who takes it. A change request on a fixed-scope build gets spotted as a change request, rather than being absorbed as free work.

Engineers then work from a "my day" screen rather than five client boards. When someone is waiting on server access or a reply from the client's side, the "I'm blocked" button pulls in the right person with the context attached, and the wait is on record instead of disappearing into a chat thread.

Hours that land on the right contract

On Team and up, time is logged in about five seconds, next to the task that was just finished. Because every task sits in a client's project, the hours are already attached to the right contract when the weekly timesheet is collected. A forgotten day sends a reminder to the engineer, not to their manager.

For a support contract, that tells you what the client is actually costing. For a build, it shows overrun while there is still time to raise it. And because ShipSprint has no screenshots, keystroke logging or activity tracking, the numbers are ones your engineers entered and can stand behind.

Staffing through the Puja season

Durga Puja in the autumn is the big regional festival in Kolkata, and Diwali follows soon after. Holi comes in the spring. Your support contracts don't pause for any of them, and clients in other states or countries keep their own calendars. On Team and up, approved leave and public holidays count towards capacity, so you can see in advance which client's queue is thin that week and arrange cover before tickets start waiting. If you run some Saturdays, plan around the days your team actually works.

Before a Kolkata services firm signs up

Who you're buying from. Quantuva Technologies Pvt. Ltd. builds ShipSprint in Hyderabad and bills in rupees with GST-compliant invoices. Support is by email and in-app chat.

Time zones. There's no gap: support works in IST and usually replies the same working day. The calendar to watch is your clients', and the festival weeks above.

Billing. Each seat is billed in rupees through Razorpay. Prices exclude GST, which appears on the invoice; with a valid GSTIN, input-tax credit is normally available. Check the details with your accountant.

Data protection. Client data that reaches a ticket is covered by the Digital Personal Data Protection Act, 2023, and often by the client's own contract too. Review the sub-processor list and the security overview against both before you paste client details into a card.