Project Management Software for SaaS Companies in Kolkata
Salt Lake's Sector V is still better known for services delivery, and a smaller, newer line of homegrown SaaS companies has to build its own playbook alongside it.
A newer kind of company in a newer part of an old city
Kolkata's commercial identity runs deep into trading houses and long-established distribution businesses, and Sector V's IT sector, itself barely two decades old, has grown up beside that older economy rather than replacing it. Inside Sector V, a smaller line of genuinely homegrown SaaS companies sits next to the much larger services floors, without the dense local peer group a founder in a bigger product hub would take for granted: a subscription business here is often working out its own version of a roadmap without many nearby companies solving quite the same problem.
What it runs into anyway is the problem every SaaS company eventually runs into, whether or not there's anyone next door doing the same thing: engineering's sprint board, the sales team's promise from a call last week, and marketing's launch note tend to agree by accident more than by design. Three people, three honest updates, and somehow three different dates for the same feature.
A bug report suffers from the same lack of a shared record. A customer flags it, support writes it down, and by the time engineering closes it out weeks later as one more ticket, the paying account it came from, and the renewal that account was due for, has usually been lost somewhere along the way.
A playbook nobody nearby has already written
A board built for a company writing its own roadmap, not copying a services floor's.
The board tracks the repository directly. Opening a branch moves a card, merging the pull request closes it, and the resulting burndown and cycle-time charts come from that activity rather than a guess entered at standup.
Every forecast is calculated from the team's measured velocity as sprints actually close, not a hopeful figure from the planning meeting, so a slipping date surfaces weeks before a customer would ever notice it.
The triage inbox turns a bug report into an engineering task without stripping off who sent it, so weeks later, whoever closes the ticket can still see the paying account, and the renewal, it was actually about.
Engineering, HR, marketing and operations each get their own templates under one account, so a company without many local peers doing the same thing at least isn't also running three disconnected tools to do it.
Every decision sits beside the work it shaped, with page history behind it, so a spec written by one person doesn't quietly drift from what the rest of a small team ends up actually building.
No sales conversation required to see whether it fits
The Free plan holds five users and two projects at no cost, permanently, so an early Kolkata SaaS team can run its actual roadmap through the product before deciding anything, with no trial deadline forcing a call before the business is ready to make one. Once the team grows past that, splitting time between a Sector V desk and home on any given day, a card's position on the board, not a field someone forgets to update, keeps a support ticket's thread intact without adding another status meeting to the week.
Billing runs in rupees with GST-compliant invoices, from Quantuva Technologies Pvt. Ltd., a company registered in Hyderabad, so a Kolkata SaaS founder isn't managing tooling spend through someone else's currency and business hours while still building out a customer base of its own.
Questions from Kolkata SaaS teams
Yes. Invoices are in rupees, GST-compliant, and annual billing is an option. Quoted prices exclude applicable taxes.
No. It's built to sit beside GitHub, not replace it: a branch move shifts a card, a merged pull request closes it, and cycle-time and burndown figures come straight from that trail rather than someone's memory of standup.
No. Screenshots, keystroke logs and background activity tracking are all absent by design. The only record is outcomes, delivered items and self-logged hours, with scorecards that adjust for approved leave and stay visible only to the person they're about.
Up to five users and two projects stay on the Free plan forever, no cost. Moving to Team brings the price to ₹299 per user per month, or ₹2,899 yearly, for teams as large as 40. Business goes to ₹599 per user per month, or ₹6,499 yearly, bringing forecasts, scorecards and the owner command center with it. Full detail lives on the pricing page.
Related pages
See it on your own work.
A workspace your whole company will actually use is 60 seconds away. No card, no risk, nothing to install.
14-day full-access trial · sample project included · no card required