Country · United States

Working with an India-based development team from the United States

Softivum is a web and software development company based in Kakinada, India. We have no US office and, so far, no documented US clients. This page is for a US business weighing an Indian team: how the hours overlap, who owns the code, and which US rules your website and lead follow-up still have to meet.

Softivum works remotely from Kakinada, India; US projects would run the same way our Indian projects do, with weekly demos and the code in your own accounts.

Get a Free 2-Minute Website Audit

Free 30 minutes · no obligation

What changes when your developers are in India?

Less than most US buyers expect, and mostly in three places: the clock, the contract and the compliance checklist. The build itself is the same work: a scoped business website or custom software project, delivered in short sprints that you review as working software rather than status reports.

What does change is that your team becomes the local expert. A developer in India will not know how your state treats text-message follow-up or which privacy notice your customers expect unless you tell them, or unless they ask. A good offshore partner asks. The sections below list the questions we raise at the start of a US project, so nothing is discovered after launch.

If you want to see how our projects run day to day, from scoping to handover, the Softivum India page describes the process the way our Indian clients experience it.

How much of the working day overlaps?

India runs on a single time zone, IST (UTC+5:30), and does not change its clocks. US Eastern Time is 10 hours 30 minutes behind IST in winter and 9 hours 30 minutes behind during daylight saving. Pacific Time is 13 hours 30 minutes behind in winter and 12 hours 30 minutes in summer.

In practice that means an East Coast morning lines up with an Indian evening. A 9:00 am ET call in summer is 6:30 pm in Kakinada. West Coast teams usually do better with an evening call on their side or an early start on ours. The useful pattern is one fixed overlap slot a few times a week, with everything else written down so work continues while you sleep. Our longer answer on whether a remote team can work in your time zone covers how to set that rhythm.

Who owns the code if an Indian company writes it?

Do not leave this to assumption. Under US copyright law, code written by an outside contractor is not automatically the client's. The US Copyright Office explains that commissioned software usually only counts as a work made for hire in limited cases backed by a signed agreement. The safe route is a written assignment of copyright to your company, plus the repositories, domain, hosting and analytics accounts held in your name from day one.

We work that way by default: you own the code and the accounts, and the source lives in a repository you control. Whoever you hire, ask to see the assignment clause before the first invoice, not at handover.

How do US clients pay an Indian team?

Invoices are issued in US dollars and paid by international bank transfer or an established cross-border payment service; both sides should agree the method and who carries the transfer fees before work starts. We invoice against milestones rather than fully upfront or fully on delivery, and any change in scope is re-quoted and agreed before it is built.

When you are comparing a US agency with an offshore team, compare like with like: the same scope, the same ownership terms and the same support period. Our guide to comparing software development quotes shows how to line proposals up so the cheapest number is not hiding a smaller job.

What is different about building for United States

Each point links to the official source it relies on. None of this is legal advice.

  • Accessibility under the ADA

    Title III of the ADA covers businesses open to the public, and the Department of Justice's position is that it applies to goods and services offered on the web. There is no DOJ regulation with a detailed technical standard for private businesses; WCAG is the usual benchmark. A separate 2024 DOJ rule sets WCAG 2.1 AA as the standard for state and local government websites and apps, with compliance dates in 2027 and 2028, and it reaches contractors that build services for those governments. Tell your developer which side of that line you are on.

    Source [1](opens in a new tab)
  • State privacy law, starting with California

    The CCPA applies to for-profit businesses that do business in California and have gross annual revenue over 25 million dollars, or buy, sell or share the personal information of 100,000 or more California residents or households, or earn half or more of their revenue from selling it. If it applies, your site needs the notices and request routes the law gives consumers, including a Do Not Sell or Share My Personal Information link if you sell or share data. Several other states have their own privacy laws, so confirm which apply with your counsel.

    Source [3](opens in a new tab)
  • Consent before automated calls and texts

    If your website feeds a lead-follow-up system that calls or texts mobile numbers using an autodialer or a prerecorded voice, the Telephone Consumer Protection Act requires the recipient's prior express consent, and it applies to callers outside the US when the recipient is in the US. Build the consent wording and a record of it into the form itself, not into a later step.

    Source [4](opens in a new tab)
  • CAN-SPAM for marketing email

    Commercial email must use honest headers and subject lines, identify itself as an ad, include a valid physical postal address, explain how to opt out, and honor opt-outs within 10 business days. The FTC is explicit that there is no exception for business-to-business email, and that hiring someone else to send it does not move the responsibility off you.

    Source [5](opens in a new tab)
  • Written IP assignment

    Commissioned code is not automatically yours under US copyright law. A signed assignment, plus repositories and accounts held in your company's name, removes the ambiguity. This matters most for software you plan to sell, raise money on, or eventually move to another developer.

    Source [6](opens in a new tab)

How a project runs with a team in India

  • Overlap hours

    IST is 9 hours 30 minutes ahead of US Eastern in summer and 10 hours 30 minutes in winter. We agree a fixed overlap slot, usually an East Coast morning or a West Coast evening, and keep everything else in writing.

  • Weekly demos

    You see working software every week, recorded if the live slot does not suit, so progress never depends on a status email.

  • Contract and ownership

    Fixed scope, written copyright assignment, and code, domain, hosting and analytics in your accounts from the first day.

  • Invoicing

    Milestone invoices in US dollars, paid by international transfer; scope changes are re-quoted before they are built.

United States: common questions

No. Softivum is based in Kakinada, India, and every documented client so far is in India. We work remotely as standard, so a US project would run the same way: scoped up front, weekly demos, and the code and accounts in your name. If that is a dealbreaker, it is better to know now.

Yes, if you set the target. There is no DOJ technical standard for private businesses, so agree on WCAG 2.1 or 2.2 AA in the contract, test with keyboard and screen readers before launch, and keep checking after content changes. Accessibility is a property of the finished site, not of where the developer sits.

Usually privacy notices under any state law that applies to you, such as the CCPA, consent for automated calls or texts under the TCPA, and CAN-SPAM for marketing email. Build consent wording and records into the form from the start, and have your counsel confirm which laws apply to your business.

Building something for United States?

Book a free 30-minute call, get a two-minute audit of your current site, or send a quick question on WhatsApp.

No call required

WhatsAppCall