Look past the portfolio for technical depth
A polished portfolio shows design sense, not engineering discipline. Ask to see how a shortlisted company handles code review, testing and deployment on a past project — the answer tells you more about long-term reliability than any case study.
Local presence matters less than process maturity. A Kolkata-based team that documents requirements clearly and ships in predictable increments will outperform a larger, less disciplined vendor regardless of location.
Clarify the pricing model up front
Fixed-price engagements work well for tightly scoped projects with a stable spec. Time-and-materials suits work that will evolve as you learn from users. Mismatching the model to the project is one of the most common sources of budget disputes.
Ask what happens after launch
Post-launch support terms — response times, bug-fix SLAs, and whether ongoing work is billed separately — should be agreed before the contract is signed, not negotiated after the first production incident.
Frequently asked questions
Should I choose a local Kolkata company or a remote team?
Location matters mainly for time zone alignment and occasional in-person meetings. A local Kolkata company can be easier to coordinate with early on, but process maturity and communication quality matter more than proximity for long-term outcomes.
How long does a typical custom software project take?
A well-scoped MVP typically takes 8-14 weeks from kickoff to first release, depending on integration complexity. Larger, multi-module systems are usually delivered in phased releases rather than a single big-bang launch.