Picture a 300-person insurer that needs 4 more backend engineers for 12 months. A US agency quotes $105 an hour, a Mexico-based firm quotes $60 and an India-based vendor quotes $45. The CFO sees a 57 percent gap between the first and the last quote and asks the CTO what the work will really cost. The CTO knows the hourly rate leaves out management time, rework, turnover and legal terms, but can’t say how much those add or where they differ. This scenario is invented for illustration and doesn’t describe a real company or vendor.
This post compares onshore, nearshore and offshore staff augmentation on total cost and risk. It draws on Bureau of Labor Statistics wage data, a law firm’s summary of a Department of Justice data rule and a CPA firm’s note on paying overseas contractors. It also draws on 4 vendor and agency articles from Full Scale, Kanerika, Edana and Stealth Agents. All 4 sell something, and I flag their unsourced claims and contradictions where they appear. All cost models here are invented and recomputed in code. Confirm every rate in a written quote, and ask counsel and your tax advisor to review the contract.
TL;DR
- Compare total cost, not the hourly rate. In my invented 4-engineer, 12-month model, raw labor of $806,400 onshore, $460,800 in Mexico, $537,600 in Poland and $345,600 in India becomes $846,720, $516,096, $618,240 and $432,000 after invented hidden-cost loads. India’s saving falls from 57 percent to 49 percent, and the loads would need to top 145 percent to erase it. Vendor claims of 50 to 70 percent savings have no sources.
- Time zones decide how the work flows. On a standard 9-to-5 day, Bogota overlaps 8 hours with US Eastern time in December, Warsaw 2, and India and Manila none. Vendor claims about the cost of that gap, such as managers spending up to 30 percent of their time syncing, are unsourced. Decide which tasks need live overlap before you pick a region.
- Risk isn’t uniform by country. A law firm summary of the Department of Justice data rule names China, Cuba, Iran, North Korea, Russia and Venezuela, and sets civil penalties up to $377,700 or twice the transaction value. A CPA firm says overseas contractors complete Form W-8BEN or W-8BEN-E. Confirm both with counsel.
Defining onshore, nearshore and offshore
The vendor pages I read don’t define the 3 terms the same way, and Full Scale and Kanerika group countries by region rather than by hours. I use working definitions of my own: onshore means the engineers work in the client’s country, nearshore means a zone within about 3 hours of the client, and offshore means 6 or more hours away. That distinction matters when you compare models such as IT staff augmentation because location changes overlap, legal review and management effort as well as price. The table shows what that means for the working day, using the time zone database and an assumed 9-to-5 local schedule for the engineer and for US Eastern.
| Location | Offset from US Eastern in December | Overlap in December | Overlap in July |
| Bogota, Colombia | 0 hours | 8 hours | 7 hours |
| Mexico City, Mexico | 1 hour behind | 7 hours | 6 hours |
| Sao Paulo, Brazil | 2 hours ahead | 6 hours | 7 hours |
| Warsaw, Poland | 6 hours ahead | 2 hours | 2 hours |
| Bucharest, Romania | 7 hours ahead | 1 hour | 1 hour |
| India (Kolkata) | 10.5 hours ahead | 0 hours | 0 hours |
| Manila, Philippines | 13 hours ahead | 0 hours | 0 hours |
The offsets change in July because US Eastern moves to daylight time while Colombia, Mexico, Brazil, India and the Philippines don’t, which is why Bogota and Mexico City lose an hour of overlap and Sao Paulo gains an hour. Stealth Agents’ page says India and the Philippines share a 12 to 13 hour offset from US Eastern, which fits Manila but not India, where the gap is 9.5 to 10.5 hours. Compute overlap for your own city pair instead of trusting a vendor’s summary.
Why the hourly rate misleads
An hourly rate is a single input to cost, and it’s the figure vendors choose to emphasize. Full Scale, a staff augmentation vendor, says its regional ranges are built from salary data plus a 30 to 50 percent markup rather than from invoices, and it concedes that “nobody has clean visibility into every agency’s invoice.” The same article gives senior developers at $5,000 to $7,000 a month without naming a region, which works out to $31.25 to $43.75 an hour at 160 hours a month. Those numbers may be a Full Scale price list, not a market.
The rate also hides what you buy with it. The worker’s take-home pay, the staffing agency markup, employer taxes and benefits, recruiting and account management costs and margin are all inside a single number, and the split changes retention. Full Scale argues that low rates often mean underpaid developers who leave sooner, which is plausible but unquantified. When you compare quotes, ask each vendor for the worker’s pay rate, the markup and the minimum term in writing, and ask what happens to the rate if the worker leaves mid-project.
Compare like with like before you compare totals. A quote built on a 40-hour week with no holidays differs from a quote built on 1,920 billable hours, and Kanerika’s monthly figures assume 160 hours per engineer. Ask each vendor how many billable hours a month it assumes, who pays during holidays and sick time and whether overtime is billed at a higher rate. A 5 percent difference in billable hours moves the invented India total of $432,000 by $21,600, which is larger than most rate differences between vendors.
Rates by region: what the vendors publish
Full Scale. The article lists agency bill rates per hour: Mexico $45 to $75, Brazil $50 to $80, Romania $40 to $60, Ukraine $40 to $65, Poland $55 to $90, the Philippines $30 to $50, Vietnam $30 to $50 and India $30 to $55. For the US it lists $80 to $150, but that’s described as a loaded in-house cost rather than an agency rate. These figures can be compared with the types of roles covered by software engineering staffing, but they still aren’t observed market-wide invoice data. It says “about 90 percent” of developers live outside the US, attributing it to GitHub and SlashData figures I couldn’t verify, and it reports 93 percent retention for itself, which is self-reported.
Kanerika. This vendor’s article gives blended hourly rates by seniority. India runs $18 to $28 for juniors, $28 to $45 for mid-level and $45 to $70 for seniors. Southeast Asia runs $15 to $25, $22 to $38 and $35 to $60. Eastern Europe runs $28 to $40, $40 to $60 and $60 to $90. Latin America runs $30 to $45, $45 to $65 and $60 to $85. It suggests a 15 to 25 percent buffer on raw labor and a 20 to 40 percent premium for specialties, both unsourced.
Where they disagree with themselves. Pairing Full Scale’s take-home pay with its bill rates implies markups from 30 percent to 100 percent, wider than the 30 to 50 percent it states. Brazil’s $25 to $45 take-home against a $50 to $80 bill rate is the widest gap, because a 50 percent markup on $45 is $67.50. Kanerika says Eastern Europe and Latin America cost 30 to 90 percent more than India in 1 place and 30 to 60 and 40 to 70 percent in another. Treat both lists as vendor price anchors, not market data.
Hidden costs that belong in the model
- Coordination and management time. Edana, a Swiss digital agency, says project managers can spend up to 30 percent of their time synchronizing time zones, and Stealth Agents cites an unnamed 2025 study for 12 to 15 hours a week of management time. Neither figure has a source I could check. The direction is plausible, because every handoff across a 10-hour gap takes longer, but the size will depend on your team, your tools and how much you document. Track your own hours during a pilot.
- Rework and quality. Edana claims inconsistent standards and test gaps can double or triple QA time, and Kanerika lists thin code review that surfaces later as bugs and technical debt. Both are unsourced and both vendors promote a competing model, so I’d use them as a checklist rather than a forecast. Ask each vendor for its definition of done, its test coverage targets and the share of work returned for fixes in its last 3 engagements.
- Turnover and ramp-up. Edana says an offshore developer may be replaced every 6 to 9 weeks, with no source, and Stealth Agents lists offshore turnover of 25 to 35 percent a year and a 60 to 90 day ramp-up, also unsourced. Whatever the real figure, each replacement costs onboarding time that you probably pay for. Ask for the vendor’s replacement terms, whether you pay for the handover period and how long the replacement guarantee lasts.
- Legal, tax and compliance work. Kanerika notes that cross-border IP assignment and jurisdiction terms add cost if skipped, and the tax and data rules discussed below add review time. These are mostly upfront costs, and they fall on legal and finance rather than engineering. Budget a few hours of counsel time per vendor, ask for a copy of the vendor’s standard agreement early and compare IP, confidentiality and audit terms before you compare rates.
Onshore benchmarks from public data
The Bureau of Labor Statistics software developer outlook reports May 2025 median pay of $135,980 for software developers and $104,300 for QA analysts and testers, with $134,040 for the combined group. It projects 10 percent growth for developers from 2025 to 2035. Those are employee wages, not agency bill rates, so they set a floor for what an onshore contractor must earn. Kanerika cites a BLS median of $133,080, which doesn’t match the figure on the page I read, probably because it refers to a different year.
For a planning figure, compare the federal wage data with current IT salary benchmarks before applying a staffing markup. I divided the developer median by 70.1 percent, which is the wage share implied by the 29.9 percent benefits share that Stealth Agents attributes to BLS employer-cost data. That gives about $193,980 a year, or $93.26 an hour at 2,080 hours. It mixes an all-industry benefit ratio with a developer wage, so treat it as rough. Kanerika’s $170,000 to $190,000 loaded cost and Stealth Agents’ $162,700 to $182,000 are both lower and both come with unsourced elements. My invented $105 bill rate sits about 12.6 percent above $93.26.
An invented cost model for 4 engineers
The table prices 4 engineers for 12 months at 1,920 hours each, or 7,680 hours in total. I chose the bill rates inside the published ranges: $105 onshore, $60 for Mexico, $70 for Poland and $45 for India. I also chose hidden-cost loads of 5, 12, 15 and 25 percent for coordination, rework, turnover and legal work. No source supports those loads. The last column shows the productivity each model could lose, compared with onshore, before its cost per productive hour matches onshore.
| Model | Bill rate | Raw labor | Invented load | Total | Saving vs onshore | Break-even productivity |
| Onshore | $105 | $806,400 | 5 percent | $846,720 | n/a | n/a |
| Nearshore (Mexico) | $60 | $460,800 | 12 percent | $516,096 | 39.0 percent | 61 percent |
| Offshore (Poland) | $70 | $537,600 | 15 percent | $618,240 | 27.0 percent | 73 percent |
| Offshore (India) | $45 | $345,600 | 25 percent | $432,000 | 49.0 percent | 51 percent |
Read the last column as a stress test. If an Indian team delivers only 70 percent of the output of an onshore team for the same hours, its cost per productive hour rises from $56.25 to $80.36, still about 27 percent below onshore’s $110.25. If Polish engineers deliver 70 percent, their cost per productive hour is $115, above onshore. The model doesn’t say which region is cheaper in your case. It shows which assumptions decide the answer.
Sensitivity matters more than the base case. Raising India’s load from 25 to 40 percent lifts its invented total to $483,840 and trims its saving to 42.9 percent. Raising Mexico’s load from 12 to 25 percent gives $576,000 and a savings of 32.0 percent. The ranking holds in both cases, but the gaps narrow, and the break-even productivity figures in the table rise with them. Rerun the model with your own loads before you present a savings number.
Reading the savings claims
- The “50 to 70 percent” figure. Full Scale calls it a number “everyone quotes” and gives no source. In my invented model the total saving ranges from 27 to 49 percent, and the raw labor saving ranges from 33 to 57 percent. The claim isn’t impossible, since cheaper rate cards exist, but it describes labor cost before the hidden costs. Ask any vendor who quotes a savings percentage what it’s measured against and what costs it includes.
- Stealth Agents’ range. The page headlines savings of 40 to 78 percent, while its body estimates a net 40 to 60 percent and an FAQ implies 50 to 80. Its worked example claims an 80 percent saving on a $25 hour against $65, when the arithmetic gives about 62 percent. The page also sells offshore services, mixes BLS data from different years and cites 18 sources while its header says 14. Use its BLS-derived wage figures and ignore its savings claims.
- Kanerika’s internal contradictions. Beyond the regional gaps above, Kanerika’s takeaways say the floor is $18 an hour, while its own table shows $15 for junior developers in Southeast Asia. It cites McKinsey and Oxford findings of 45 percent over budget and 56 percent less value, without a verifiable link. Those 2 figures describe large IT projects generally and don’t isolate offshore work, so don’t read them as an offshore penalty.
- The break-even test. In the invented model, the hidden-cost load on India would have to reach 145 percent of raw labor before India’s total equals onshore’s $846,720. That’s far above any figure in the vendor articles, so the real risk isn’t cost overrun. It’s the delivery risk the percentages don’t capture, such as a missed release or a product that needs more rework. Price those risks separately and decide which you can absorb.
Time zones and the working day
What the overlap means. With 8 hours of overlap, a Bogota team works almost the same day as a New York team, and standups, reviews and incident calls happen live. With 2 hours, as in Warsaw, there’s a short window for decisions, and everything else waits for the next day. With none, as in India in this model, the team needs a shifted schedule or fully asynchronous work. The table assumes a standard 9-to-5 day for the engineer, which is a simplification you should replace with the vendor’s actual hours.
What vendors claim about the gap. Edana says a technical answer can take hours or even a full day to arrive and that managers lose time syncing, with no data. It promotes hybrid delivery with onshore leadership, so its framing favors that model. I found no independent study measuring the cost of a 10-hour gap on software delivery. The logic is simple, because a question asked at 4 p.m. in New York reaches an Indian engineer at 2:30 a.m., but the size of the effect depends on how work is divided.
Mitigations to price. Teams usually shift hours, overlap on a few days a week or give the remote team ownership of work that doesn’t need live decisions. Each choice has a cost: the shifted engineer works late or early, the overlap days compress meetings, and the separated work needs good documentation. These trade-offs also affect how you structure broader information technology staffing solutions because some project roles tolerate asynchronous work better than others. Ask the vendor how its engineers actually schedule overlap, whether they’re paid for it and what happens during local holidays.
Data and legal exposure
Clark Hill, a law firm, summarizes a Department of Justice final rule that restricts certain transactions involving bulk sensitive personal data and countries of concern. The official DOJ Data Security Program compliance guide names China, including Hong Kong and Macau, Cuba, Iran, North Korea, Russia and Venezuela, and covers certain vendor, employment and investment agreements involving access to covered data. Bulk thresholds include identifiers on 100,000 US persons, health or financial data on 10,000 and biometrics on 1,000. Penalties run up to $377,700 or twice the transaction value, and up to $1,000,000 and 20 years for willful violations.
The summary gives compliance dates running from April 8 to Oct 6, which appear to refer to 2025, so the obligations may already apply. It also describes a compliance program, a security policy tied to CISA requirements and an annual independent audit kept for at least 10 years. I didn’t read the rule itself, so confirm the details with counsel. The rule names specific countries, and staff elsewhere aren’t covered by it, but other privacy, contract and sector laws may apply. If your engineers will touch customer data, ask the vendor where data sits, who can access it and which subcontractors are involved.
Ask for specifics beyond the legal summary. Have the vendor complete your security questionnaire, describe how it manages laptops and access for engineers on your account and name who can see your repositories. The CISA vendor and supplier assessment guidance provides a useful reference for physical and logical access, cybersecurity training and contractual security obligations. Ask what happens to your data and credentials when an engineer leaves, and how fast access is removed.
Risk matrix by model
The table lists the main risk areas and what each source says about them. Where no source speaks to a cell, I wrote my own assessment and marked it. This is a discussion aid rather than a score, because the weight of each risk depends on your data, your product and your team. If the engagement involves sensitive systems, involve your security team early and compare the skill requirements with those used in cybersecurity staffing before you choose a model. Ask your security and legal teams to fill in their own version before you choose a model.
| Risk area | Onshore | Nearshore | Offshore |
| Live collaboration | Full overlap | 6 to 8 hours in the table | 0 to 2 hours in the table |
| Cost | Highest in my model | 39.0 percent below onshore, invented | 27.0 to 49.0 percent below, invented |
| Data rule exposure | Low unless covered persons are involved (my assessment) | Check the vendor’s staff and subcontractors | Check the countries named in the rule |
| Tax paperwork | Standard US forms | W-8BEN or W-8BEN-E if you hire individuals or entities abroad | Same, per the CPA firm |
| Turnover | Unquantified | Unquantified | Vendor claims range from 25 to 35 percent a year, unsourced |
| IP assignment | Domestic law applies | Cross-border terms needed | Cross-border terms needed |
Tax and employment mechanics
Contractor or employee. PBMares, a CPA firm, says employing someone overseas is much more involved than engaging an independent contractor. In staff augmentation, the vendor usually employs the engineers, which puts payroll, benefits and local employment law on the vendor. If you hire individuals directly, classification depends on the facts rather than the label in the contract, and the IRS employee-versus-independent-contractor guidance looks at behavioral control, financial control and the relationship of the parties. I haven’t analyzed local employment law, so ask counsel before you contract with an individual who works under your direction and on your schedule.
Forms and withholding. The CPA article says US companies generally shouldn’t withhold tax from payments to overseas independent contractors, who report the income under their own country’s laws. The IRS’s foreign beneficial owner guidance explains the roles of Form W-8BEN for foreign individuals and Form W-8BEN-E for foreign entities. The article states the no-withholding rule without exceptions, was first published in 2023 and carries its own disclaimer, so confirm it for your case.
What I couldn’t confirm. The article doesn’t cover 1099 reporting, treaties, state tax or permanent establishment, which is the risk that a foreign activity creates a taxable presence. None of the vendor pages covered them either. If you plan to place a manager or a team abroad, or give an overseas contractor authority to sign contracts for you, ask a tax advisor about permanent establishment before you start. For a vendor-employed team that works only under your direction from its own office, the risk is lower, but confirmed.
Contract terms to negotiate
- IP assignment and jurisdiction. Kanerika flags cross-border IP assignment and jurisdiction terms as a cost when skipped. Ask for a clear assignment of work product to your company, a statement of which country’s law governs and where disputes are heard. Include the vendor’s obligation to get assignments from its own staff and subcontractors. Have counsel review the clauses for the country involved, because enforceability varies and I haven’t analyzed it here.
- Replacement and ramp-up. Full Scale notes that the hourly model carries overhead for timesheet tracking and re-onboarding, and turnover claims in other articles run high. Write down who pays for the overlap while a replacement ramps up, how fast the vendor must supply a substitute and whether you can approve the replacement. A guarantee that exists only in a sales deck doesn’t bind the vendor, so put the terms in the agreement.
- Data location, access and audit. Specify where data may be stored, who may access it, which subcontractors are allowed and how you can audit the vendor’s controls. If the rule above applies to your data, the contract should also forbid access by covered persons. Ask the vendor to name the countries where its staff and its subcontractors work, and require notice before any change. Put the notice duty in the same clause as the restriction itself.
- Rates, minimum terms and exit. Fix the hourly rate for the term, say how increases are handled and cap the minimum commitment. Stealth Agents lists offshore wage growth of 3 to 10 percent a year without a source, so ask how the vendor handles raises. Require documentation and knowledge transfer at the end, and decide in advance who keeps the code, the tools and the accounts. Add a clause that lets you reduce headcount on notice.
Where the sources conflict
The 4 vendor articles disagree with each other and with themselves, which is the main reason to build your own model. Full Scale says markup is 30 to 50 percent while its numbers imply up to 100 percent. Kanerika lists a $15 floor in its table and an $18 floor in its summary. Stealth Agents reports savings of 40 to 78 percent, 40 to 60 percent and 50 to 80 percent in different places, and offers an hourly range for developers that doesn’t reconcile with its own annual figures. Edana gives only anecdotes for its numbers.
The common thread is commercial interest. Full Scale and Kanerika sell offshore staff augmentation, Stealth Agents sells offshore assistants and Edana sells hybrid delivery with onshore management, so each article leans toward its own model. The government and professional sources, BLS, the law firm summary and the CPA firm, are more reliable on what they cover and say little about cost. When comparing IT staffing agencies, treat published savings and speed claims as questions to verify rather than proof. I found no independent survey of what companies actually pay, so the best evidence available is a written quote from each vendor.
A decision framework
Choose onshore when. The work needs constant live collaboration with product owners, touches regulated or highly sensitive data, or changes daily as the business learns. A rate of $105 against $45 looks expensive until a delay or a data problem costs more than the difference. In my model the gap is $414,720 a year for 4 engineers before risk. Weigh it against the cost of a single missed release and of the extra review that offshore work might require.
Choose nearshore when. You want most of a day of overlap at a lower rate. Bogota overlaps 8 hours in December and Mexico City 7, which supports pairing, standups and incident response. In my model Mexico saves $330,624 over onshore after loads. Nearshore also keeps legal and tax questions manageable, though you still need cross-border terms. Working with experienced tech recruitment agencies doesn’t remove those questions, so check that the vendor’s staff are where it says they’re and ask for evidence of holiday coverage.
Choose offshore when. The work is well specified, can run asynchronously and has strong tests and documentation. Back-office tooling, well-scoped features and maintenance often fit, in my view, because a delayed answer costs little. In my model India saves $460,800 in raw labor and $414,720 after loads, and it still saves about 27 percent at 70 percent productivity. Ask for a paid trial and a named technical lead, and plan for shifted hours.
Running a pilot before committing
- Pick a bounded workstream. Choose a project of 8 to 12 weeks with a clear owner, written acceptance criteria and a repository the vendor can reach. Before choosing the provider, compare the same requirements across several tech recruiting firms rather than letting each vendor define a different scope. Avoid your most sensitive data in the pilot unless the contract already covers it. Tell the vendor what you’ll measure, and agree on a small team so you can see how individuals perform.
- Measure what the model assumed. Track management hours per week, the share of work returned for rework, the number of replacements and the hours of live overlap each week. These are the inputs behind the invented loads of 5 to 25 percent, and your own numbers will replace them. Keep the log simple enough that engineers fill it in, and review it at the end of each sprint with the vendor.
- Recompute the model with real inputs. At the end of the pilot, put the measured loads and the vendor’s actual bill rate into the table and recalculate the totals and the break-even productivity. If a region’s break-even productivity is 73 percent and your team delivered 60 percent of what an onshore team would, the cheaper rate is costing you money. Share the result with finance before you sign a longer term.
- Set exit criteria and keep your options. Decide in advance what result ends the pilot, what extends it and what triggers a switch to another region or model. Keep documentation and code in your own repositories from day 1, so a change of vendor doesn’t mean a rewrite. Confirm the exit terms, the knowledge-transfer period and the final invoice with counsel before the pilot starts. Write down who owns each step of the handover.
FAQs
What’s the difference between onshore, nearshore and offshore staff augmentation?
The vendor pages I read don’t define the terms consistently. I use onshore for engineers in your own country, nearshore for a time zone within about 3 hours and offshore for 6 or more hours away. In December, Bogota overlaps 8 hours with a 9-to-5 US Eastern day, Warsaw 2 and India none. Ask each vendor where its staff sit and what hours they work. Put the answers in the contract, as well as in the proposal.
How much does offshore IT staff augmentation cost per hour?
Published ranges are vendor price anchors. Full Scale lists agency bill rates of $30 to $55 an hour for India and $55 to $90 for Poland, and Kanerika lists $28 to $45 for mid-level developers in India and $60 to $90 for senior engineers in Eastern Europe. None of them is a survey of invoices. Get a written quote with the worker’s pay rate, the markup and the minimum term.
Is offshore staff augmentation really 50 to 70 percent cheaper?
Full Scale calls it a figure “everyone quotes” and cites no source. In my invented 4-engineer model, India’s raw labor is 57 percent below onshore and its total is 49 percent below after a 25 percent load, while Poland’s total is 27 percent below. The answer depends on rates, hidden costs and productivity. Build your own model with a pilot, and replace the invented loads with measured ones. Treat anything higher as a claim to test.
How do time zones affect offshore teams?
They change which work can happen live. On a 9-to-5 schedule, Bogota overlaps 8 hours with US Eastern in December and 7 in July, Warsaw overlaps 2 and India overlaps none. Edana says answers can take hours or a full day, and that managers lose up to 30 percent of their time syncing, but those claims are unsourced. Decide which tasks need live overlap, and price shifted hours. Ask the vendor how its engineers actually schedule overlap.
What are the data and legal risks of offshore staff?
A law firm summary of a Department of Justice rule names China, Cuba, Iran, North Korea, Russia and Venezuela, restricts vendor and employment agreements involving bulk sensitive data and lists civil penalties up to $377,700 or twice the transaction value. I didn’t read the rule. Other privacy, contract and sector laws may apply elsewhere, so ask counsel to review where data sits and who can access it. Confirm the countries your vendor’s staff and subcontractors work in.
Do I need tax forms to pay overseas contractors?
A CPA firm says overseas independent contractors complete Form W-8BEN for individuals or Form W-8BEN-E for entities, and that without the forms the payer may be required to withhold. The article was first published in 2023 and doesn’t cover 1099 reporting, treaties, state tax or permanent establishment. If a vendor employs the engineers, the paperwork differs, so confirm your case with a tax advisor. Ask the vendor which arrangement applies to its engineers.
What hidden costs should I budget?
Coordination time, rework, turnover and ramp-up, and legal and tax review. Kanerika suggests a 15 to 25 percent buffer on raw labor, and my invented model uses 5 to 25 percent by region, but no source supports either set. Track management hours, returned work and replacements during a pilot, then replace the assumptions with your measured numbers before you commit to a longer term. Share the numbers with finance each month of the pilot.
How should I pilot a new region?
Run a bounded workstream of 8 to 12 weeks with a small team, written acceptance criteria and an agreed set of measures. Track management hours, rework and overlap, then recompute the cost model with real inputs, including break-even productivity. Set exit criteria before you start, keep code and documentation in your own repositories and ask counsel to review the exit and handover terms before you sign. Share the results with finance and engineering together.
