SaaS Product Development in Kolkata
Owner-run businesses and family firms replacing a site that was built once, years ago, by someone no longer reachable — and who kept the domain login.
Advorize delivers SaaS Product Development for businesses in Kolkata, India, from our team in India. Work is quoted and invoiced in INR, delivered in your city and your timezone, and built against India's requirements — DPDP consent and GST invoicing.
What Kolkata businesses are actually buying
Owner-run businesses and family firms replacing a site that was built once, years ago, by someone no longer reachable — and who kept the domain login.
That is a different brief from the one we get elsewhere, which is why this page exists separately from our main SaaS Product Development page. The work is the same discipline; the constraints around it are not.
Who else you are considering in Kolkata
A deep bench of low-cost freelancers and small shops competing almost entirely on price, which sets the anchor low and the expectations lower.
How we work across the distance
We are based in India, which puts us the same working day. Same city. Meetings happen in person when they need to, which for a first scope conversation is worth more than any amount of video call.
| What you get | How it works for Kolkata |
|---|---|
| Currency | Quoted and invoiced in INR (₹) |
| Tax on the invoice | 18% GST on the invoice; input credit available if you are registered. |
| Payment | NEFT/RTGS or UPI against a GST invoice, milestone-based. |
| Working overlap | In your city and your timezone |
Channels that have share in India
A channel mix is not portable. What we build for Kolkata is instrumented for the platforms that actually carry demand there:
- WhatsApp Business
- Meta Ads
- Google Ads
- Justdial & IndiaMART
What the law requires here
DPDP Act 2023 consent for lead forms, and GST-compliant invoicing on everything billed.
This is a build requirement rather than a disclaimer at the bottom of the page. Consent capture, data location and accessibility are decided in the first week, because retrofitting any of the three costs more than doing them once.
The problem this solves
The pattern is consistent. A long build against a full specification, a launch, and then the discovery that the feature the roadmap was organised around is not the one anyone would pay for. The engineering was competent. The sequence was wrong.
- The spec describes version three, and version one is scheduled to arrive after the runway does.
- Billing is 'phase two', so nothing in the build has been tested against a customer actually paying.
- There is no product analytics, so nobody can say which features are used and which are decoration.
- The database has no tenant boundary, and retrofitting one later is a rewrite of every query.
- The founder is the only person who has ever used it end to end.
Also in India
We run the same engagement for clients in Mumbai, Delhi NCR, Bangalore, Hyderabad, Pune, Chennai, Ahmedabad, on the same currency, tax and working-hours terms.