Most of our clients are in Canada and the USA, about half a day behind us in Mathura. We've seen offshore development work brilliantly, and we've heard plenty of stories where it went badly before people found us.

The difference is almost never luck. It's the questions asked before signing. If you're planning to hire a development team in India, these are the twelve questions we'd ask in your shoes, including of us.

Business meeting at a cafe table with laptops
A reference call with a past client tells you more than any portfolio.Photo: Helena Lopes / StockSnap · CC0

Questions about the people

1. Who will actually work on my project?

Ask for names, roles and how much of their time is allocated to you. Some agencies win work with senior people on the sales call, then hand the project to someone you've never met. You should know who is designing, who is writing the code and who manages the project.

2. Can I see live work and talk to a past client?

Screenshots are easy to borrow. Live websites and apps you can click through are much harder to fake. Ask for two or three projects similar to yours, and a short reference call with one of those clients. Ask that client what went wrong and how the team handled it.

3. What happens if a team member leaves?

People change jobs everywhere. A professional team documents its work, uses version control properly and can introduce a replacement without your project stalling. Ask how they handled it last time.

Questions about scope and process

4. What exactly is in the written scope, and what isn't?

Get pages, features, integrations, number of design concepts, revision rounds and timeline in writing before you pay. Ask for an explicit "out of scope" list. Vague scope is the root of most disputes.

5. How do you handle changes?

Requirements change; that's normal. A good team explains how changes are estimated, approved and billed before they're built, so there are no surprises on the invoice.

6. Will I see progress before the end?

You should get a private preview link early and see work as it develops, not a big reveal on launch day. Seeing progress is the single best protection against misunderstandings.

Questions about communication

7. How and when will we communicate?

Agree on tools (email, Slack, WhatsApp or video calls), how often you'll get updates, and a regular meeting time that suits both time zones. With a large time difference, short daily written updates matter more than instant replies.

Your locationTime difference with IndiaWhat usually works
US East Coast / TorontoAbout 9½–10½ hours behindCall in your morning; written updates overnight
US West Coast / VancouverAbout 12½–13½ hours behindCall in your late afternoon or early morning
Australia (Sydney / Melbourne)4½–5½ hours aheadLive calls in your afternoon
UK4½–5½ hours behindCalls in your morning

8. Who is my single point of contact?

One accountable person on their side, and one on yours, prevents mixed messages and lost decisions.

Two people shaking hands across a desk
Ownership, payments and support terms belong in the contract, not in a chat thread.Photo: Kristin Hardwick / StockSnap · CC0

Questions about ownership and money

9. Who owns the code, designs and accounts?

Your domain, hosting, app store accounts, analytics and cloud services should be registered in your name. The source code should live in your repository from day one, and the contract should assign IP to you on payment. Be wary of anyone who wants to keep any of these.

10. How are payments structured?

Payments tied to milestones, such as design approved, build complete and launch, are normal and fair to both sides. Paying 100% upfront for a large project isn't. Ask what happens to the payment schedule if a milestone slips.

Questions about after launch

11. What support do you provide after launch?

Websites and apps need updates, security patches and bug fixes. Ask who fixes problems, how fast, how requests are made and what ongoing maintenance costs. A warranty period for bugs in delivered work is a good sign.

12. If we part ways, how does handover work?

Ask how you'd receive the code, credentials and documentation. A good team has a clear answer because they've thought about it, and because they're confident you won't want to leave.

Red flags to walk away from

  • A firm price before anyone has asked about your business
  • No named people, or a different contact every time
  • Reluctance to share a preview link or give you repository access
  • Domains or accounts registered in the agency's name
  • Pressure to pay everything upfront
  • "Yes" to every request, with no trade-offs explained

A simple scoring sheet for comparing teams

After you've spoken to two or three teams, score each one from 1 to 5:

CriterionTeam ATeam BTeam C
Relevant live work
Quality of their questions about your business
Clarity of the written scope
Named people and continuity
Communication plan and time-zone fit
Ownership and contract terms
Support after launch
Reference call
Total

Price matters, but compare it only between teams that score well on everything else.

Your first two weeks with a new team

  • Day 1–2: kick-off call, access to tools and repository, agreed communication rhythm.
  • Day 3–5: the team shares a written plan or first designs; you give feedback quickly.
  • Week 2: first working piece on the staging site; you review and confirm the process works.

If communication is already difficult in the first two weeks, it rarely gets easier. Raise concerns early and directly.

Frequently asked questions

Is it safe to hire a development team in India?

Yes, with the right partner and contract. Choose a team based on live work and references, keep code and accounts in your name, pay against milestones, and make sure IP is assigned to you.

How do I check an Indian development company is legitimate?

Look for a registered company, a real address, live client work you can verify, and a reference you can speak to. Start with a small, well-defined first phase before committing to a large project.

Should I hire a freelancer or an agency in India?

Freelancers suit small, one-off tasks. For projects that need design, development, testing and ongoing support, or where continuity matters, an agency or a dedicated team is usually safer.

We're happy to answer every one of these on a call, at a time that suits your time zone. Read how we approach outsourcing to India, hire dedicated developers, or get in touch.

Have a question about your own project? Ask us directly. We reply to every message.