Hiring a Software Company in Kolkata – What to Look For

Technical depth matters more than buzzwords

You don’t need a team that shouts about the latest framework in every slide. What matters is whether the engineers can solve the problem you have today and adapt when the problem evolves. Look for concrete evidence of competence: a portfolio that shows similar domain work, open‑source contributions, or a clear description of the tech stack they use.

When you compare two firms, ask them to break down a typical feature into design, development, and testing hours. That gives you a sense of how they think about effort and risk.

The diagram above shows the usual proportion of effort. If a vendor claims 70 % of time is spent on UI design, you should question whether they are under‑estimating development complexity.

Communication habits you can live with

You’ll be on conference calls, Slack threads, and occasional in‑person visits. The key is not the tool but the cadence and clarity. A firm that sends a daily stand‑up summary at 6 pm IST when you’re in Mumbai will feel like a time‑zone nightmare.

• Response time: Expect a reply within a few hours for normal queries, not days.
• Language: English fluency should be strong enough for technical discussion without constant clarification.
• Documentation: Look for a habit of writing brief tickets or user stories rather than relying on memory.

If a company uses a ticketing system you can view, ask for a sample sprint board. That tells you whether they treat work as a shared artifact or a private spreadsheet.

Pricing transparency vs hidden costs

Most Kolkata firms quote a lump sum or an hourly rate. Both have traps. A fixed price can hide scope creep; an hourly rate can balloon if the team is inefficient.

A practical approach is a hybrid: a fixed price for the MVP, then an hourly rate for post‑launch enhancements. Ask the vendor to list any extra charges—cloud usage, third‑party licenses, or weekend work—up front.

Cultural fit and business understanding

Your product will likely involve Indian tax rules, GST compliance, or low‑end Android device constraints. A partner that has built for similar markets will already know the pitfalls—like handling intermittent connectivity on 2G networks.

Ask them:

1. Have you delivered a product that runs on Android 6.0 or lower?
2. How do you test for patchy internet connections?
3. What experience do you have with GST invoicing APIs?

If they can point to a real project (even anonymously) that faced those issues, you’ve saved yourself weeks of re‑work.

Process maturity you can rely on

A mature vendor follows a repeatable process: discovery, design, build, test, launch, support. They should be able to show you a short version of that pipeline.

When you ask for a timeline, watch for "we’ll start development next week" without a preceding discovery phase. Skipping that step usually means hidden re‑work later.

Security and data protection

Even if you’re building a simple catalogue app, data protection rules apply. The vendor should:

• Use HTTPS everywhere.
• Store passwords with a strong hash (bcrypt, Argon2).
• Offer a clear data‑retention policy.

If they cannot name the encryption library they use, that’s a red flag.

Support model after launch

Most businesses think the contract ends at launch. In reality, you’ll need bug fixes, performance tuning, and occasional feature tweaks. Clarify:

• Support window: 9 am–6 pm IST, 24/7 on‑call, or limited hours?
• Response SLA: Critical bugs fixed within 4 hours?
• Pricing: Fixed support fee or per‑incident billing?

A vendor that bundles a modest support package for the first three months shows confidence in the stability of their code.

The annoying detail: hidden third‑party costs

It’s easy to overlook the price of a payment gateway SDK, a map API, or a push‑notification service. Those licenses can add up to several thousand rupees per month. Ask the vendor to list every external service they plan to integrate and the associated cost.

Decision matrix you can copy

Below is an illustrative matrix you can fill in for each candidate. Assign a score from 0 (poor) to 5 (excellent) for each row, then total the column.

The highest total points to the vendor that best matches your priorities. Remember, the scores are subjective; use them as a conversation starter rather than a final verdict.

On‑shore vs off‑shore trade‑off

Kolkata sits in the same time zone as most Indian businesses, which can be a plus if you already have a local team. Compared with a distant offshore hub, you get:

• Faster feedback loops (same working day).
• Easier legal compliance (GST, Indian labor law).
• Potentially higher hourly rates.

If budget is the overriding constraint, you may accept the time‑zone lag. If speed to market matters more, the on‑shore advantage often outweighs the cost difference.

Final checklist before you sign

• Verify portfolio relevance (industry, device range, compliance).
• Request a short prototype or code sample for a core feature.
• Get a written breakdown of effort by phase and a clear pricing sheet.
• Confirm response SLA and support window.
• Ask for a list of all third‑party services and their fees.
• Ensure they follow a documented development process.
• Check security practices (HTTPS, encryption, data policy).
• Evaluate cultural fit through a brief discovery call.

If the answers satisfy you, you’re ready to move forward.

We at Nexgino follow the same disciplined approach when we partner with clients, keeping the focus on transparent process and realistic budgeting.