Skip to content
codebrix

Staff augmentation

IT staff augmentation services: India-based engineers inside your team's process

IT staff augmentation services add engineers to the team you already have. They take tickets from your backlog, follow your code review rules and work in your GitHub, Jira and Slack, while Codebrix stays their employer. You direct the work; we handle employment, equipment and replacement. Our engineers sit in Noida, so the model runs on written handoffs rather than shared office hours.

Who directs the work
Your tech lead
Your contract is with
Codebrix Technologies, India
IP
Assigned to you in writing
Terms
Month to month, 30 days' notice

Updated · By the Codebrix team

Staff augmentation, a fixed-price project or a dedicated team

The three models differ less in who writes the code than in who carries the delivery risk.

Fixed-price projectStaff augmentationDedicated team
Who sets prioritiesWe do, against a signed scopeYour tech lead, day to dayYou set goals; our PM runs the backlog with you
Who runs the engineers' dayOur leadYour leadOur PM and tech lead
What you pay forMilestones at fixed pricesEngineer time agreed in writingA whole team's time
Scope changeA written change requestJust another ticketReprioritised at planning
Who carries delivery riskMostly usMostly youShared
Best whenThe brief is clear and you have no engineersYou have a team and a process, but too few handsYou need a product team without hiring one

Augmentation only works if someone on your side can write tickets, review pull requests and make decisions. If nobody can, a dedicated development team or a fixed-price project is the safer choice. For role-specific advice on what to test in a candidate, see our pages to hire developers.

Contractor status: who employs whom

The engineers are Codebrix's people in India. Your company signs a services agreement with Codebrix Technologies and pays our invoices in USD by Stripe or bank transfer. You do not run payroll, provide benefits or hold an employment relationship with individual engineers. Directing their tickets is normal; pay, leave, performance and conduct go through us.

Where US companies engage individuals directly, the IRS weighs behavioural control, financial control and the type of relationship to decide whether a worker is really an employee. Contracting with a company that employs the engineers keeps that line clearer, but your counsel should still review how the arrangement runs in practice.

On tax paperwork, the IRS says Form W-8BEN-E is used by foreign entities to document their status, and we supply one on request. The IRS also says the place where services are performed generally determines the source of the income, and that foreign-source income is exempt from nonresident withholding under section 1441(a). This is general information, not advice for your situation; our guide to paying foreign contractors goes further. Confirm with your accountant.

IP assignment that actually transfers ownership

Many contracts call contractor code a “work made for hire” and stop there. The Copyright Office's Circular 30 explains that a commissioned work counts as made for hire only if it falls into one of nine listed categories (such as a contribution to a collective work, a translation or a compilation) and both parties sign a written agreement saying so. Software is not named among the nine. Separately, 17 U.S.C. 204(a) says a transfer of copyright ownership is valid only if it is in writing and signed by the owner. So the contract should carry a signed assignment, not just a label. A checklist for your counsel:

  • An assignment to your company of all rights in everything delivered, signed by Codebrix.
  • Our confirmation that each engineer's work belongs to Codebrix under their own terms, so we hold the rights we are assigning.
  • Any pre-existing code or tools we bring, listed and licensed to you permanently.
  • A list of open-source packages and their licences at handover.
  • Confidentiality, plus return or deletion of your data when the engagement ends.
  • Repositories in your organisation from the first day.

Our contract checklist for US buyers covers the rest of the agreement.

Onboarding to your tools in the first week

  1. Accounts: your email or SSO identity if you issue one, GitHub or GitLab with repository-level write access, your issue tracker and Slack or Teams. Multi-factor sign-in on all of them.
  2. Local setup from your README. The engineer notes every missing step and sends the fix as a pull request to your docs.
  3. A read of the codebase, then a short written note on what they would change first and what they would leave alone.
  4. One small ticket through your whole pipeline: branch, pull request, review, CI and a deploy to staging.
  5. At the end of the week you judge the pull requests and the notes, not a status report.

We ask for access scoped to the work: no organisation admin, no production database credentials unless the role needs them, and cloud roles limited to what the tickets touch. If your security policy has device or background-check requirements, put them in the agreement and we confirm before the start date whether we can meet them.

Working hours: the honest version

Our hours are 10:00 to 19:00 IST, Monday to Saturday. That day ends at 08:30 Eastern in winter (EST) and 09:30 in summer (EDT), and at 05:30 or 06:30 Pacific, before the West Coast day starts. US daylight saving time runs from the second Sunday in March to the first Sunday in November, according to NIST, while India does not change its clocks. We do not offer US-hours availability. The rhythm that works instead:

Your timeWhat happens
Your afternoonYour lead reviews pull requests, reorders tickets and answers questions in the thread
Your nightThe engineer works the queue and opens pull requests
Start of your dayA written update is waiting: done, blocked, questions, and pull requests ready for review
A fixed short call slotAgreed in the proposal, at the start of the US morning, for blockers only

This breaks down for work that needs a decision every hour, for heavy pair programming, and for US-hours on-call. Batch questions, write acceptance criteria into tickets and name one person who decides. Our time zone playbook has the detail.

Trial, replacement and notice

  • Trial: the first engagement is one paid milestone, a defined set of tickets small enough to judge in a week or two, paid only on approval.
  • Replacement: if the fit is wrong, say so at the review. We agree what changes or propose another engineer, and the outgoing engineer leaves a written handover; their reasoning is already in the pull request descriptions.
  • Notice: ongoing terms run month to month with 30 days' notice.
  • Holidays: Indian public holidays differ from US ones, so we share the year's calendar at the start.
  • Exit: you remove our accounts, rotate any shared secrets and receive the open-source list and handover notes. Nothing your product depends on stays with us.

What it costs

If you would rather buy an outcome than time, our fixed-price work has published indicative ranges: $5,500 to $22,000 for a web application and $9,000 to $33,000 for an iOS and Android app, with the fixed quote after discovery. Our page for US businesses covers payment and contracts.

Frequently asked questions

Are augmented engineers our employees?

No. They are employed by Codebrix in India, and your company contracts with Codebrix Technologies and pays our invoices. Your tech lead directs their tickets, but pay, leave, equipment and performance management stay with us. Ask your counsel to review how the arrangement works in practice, because day-to-day reality matters as well as the paperwork.

Who owns the code an augmented engineer writes?

You do. The agreement includes a signed assignment of all rights in the work to your company, because US copyright law requires transfers of ownership to be in writing and signed. The code lives in your repositories from the first commit, and any pre-existing tools we bring are listed and licensed to you permanently.

Can your engineers work US business hours?

No. Our day is 10:00 to 19:00 IST, which ends at 08:30 Eastern in winter and 09:30 in summer. We agree a fixed short call slot at the start of your morning, send a written update every day, and do the work while your team is offline. If your work needs live US-hours coverage, augmentation from India is the wrong fit.

What happens if an engineer is not a good fit?

Raise it at the milestone review or any time after. We agree what needs to change or propose a different engineer. The outgoing engineer writes a handover note, and because decisions are recorded in pull request descriptions, the next person can pick up the thread without starting again.

How soon can an engineer start?

After the call you get a written proposal within two to four days. The start date depends on having the right person free for your stack, and we put it in writing rather than promising a date on a web page. Onboarding then takes about a week: accounts, local setup, a read of the code and a first small ticket.

Do we need to withhold US tax on payments to you?

The IRS says the place where services are performed generally determines the source of the income, and that foreign-source income is exempt from nonresident withholding under section 1441(a). We provide Form W-8BEN-E on request. That is general information from IRS pages, not advice for your situation, so confirm with your accountant.

Sources

  • Dedicated team

    A dedicated development team that works only on your product

    Dedicated development team for US companies: a PM, engineers, QA and a designer working only on your product, with one backlog and a demo every week.

    Read more
  • Guide for US companies

    A software development contract checklist for US companies hiring an outside team

    A software development contract checklist for US companies: IP assignment, escrow, acceptance, warranty, liability, disputes, data terms and handover.

    Read more
  • Guide for US companies

    Working with an offshore team in India from the US: an operating playbook

    Working with an offshore team in India from the US: call slots by time zone, the overnight handoff, a daily update template, decision log and escalation.

    Read more
  • Guide for US companies

    Paying foreign contractors from the US: forms, withholding and payment rails

    Paying foreign contractors from the US: which W-8 form to collect, when withholding and Form 1099 apply, wire vs Stripe, and what a USD invoice shows.

    Read more
  • United States

    An offshore web development company in India for US businesses

    Offshore web development company in India for US businesses: USD pricing, Stripe or wire payment, IP assigned to you, and a planned ET and PT overlap.

    Read more
Estimate Call WhatsApp