[{"data":1,"prerenderedAt":486},["ShallowReactive",2],{"insight-nearshore-offshore-onshore-cost":3,"insights-cards":375},{"id":4,"title":5,"body":6,"category":357,"date":358,"description":359,"extension":360,"meta":361,"navigation":362,"path":363,"readingTime":364,"relatedArticles":365,"relatedAssessment":369,"relatedServices":370,"seo":372,"stem":373,"__hash__":374},"insights\u002Finsights\u002Fnearshore-offshore-onshore-cost.md","Cheap Hours, Expensive Projects: Pricing US, Nearshore and Offshore Teams Honestly",{"type":7,"value":8,"toc":337},"minimark",[9,13,18,21,44,47,51,54,59,62,65,68,71,74,77,81,86,89,92,96,99,103,106,110,113,117,120,124,127,227,230,234,237,243,249,255,258,262,265,268,271,275,278,317,320,324,327,330,334],[10,11,12],"p",{},"Comparing engineering teams by hourly rate is like comparing cars by the price of a gallon of fuel: the number is real, and it leaves out how far you get on it. A project's cost is the rate multiplied by the hours, and team location has a much larger effect on the hours than most comparisons admit. No delivery model is best for all work. Each one fits a different kind of work, and you can tell which is which before you sign.",[14,15,17],"h2",{"id":16},"terms-first","Terms first",[10,19,20],{},"The labels are used loosely, so here is how this article uses them for a company based in the United States.",[22,23,24,32,38],"ul",{},[25,26,27,31],"li",{},[28,29,30],"strong",{},"Onshore:"," the team works in the US, in or near your time zones.",[25,33,34,37],{},[28,35,36],{},"Nearshore:"," the team works in a nearby country with similar working hours. For US companies this usually means Latin America or Canada.",[25,39,40,43],{},[28,41,42],{},"Offshore:"," the team works many time zones away, commonly in Eastern Europe, South Asia or Southeast Asia.",[10,45,46],{},"A caution before going further: anyone who tells you one of these is always the right answer is describing what they sell. Offshore delivery is the best choice for some work, and this article will say where.",[14,48,50],{"id":49},"the-equation-behind-the-invoice","The equation behind the invoice",[10,52,53],{},"Write the cost of a piece of work like this:",[10,55,56],{},[28,57,58],{},"Total cost = rate x (building hours + rework hours + coordination hours) + the cost of delay",[10,60,61],{},"The rate is the only term that appears in a proposal. The rest decide the outcome.",[10,63,64],{},"Here is an illustration with invented round numbers, chosen only to show the mechanics. These are not market rates.",[10,66,67],{},"Suppose Team A charges 100 per hour and Team B charges 50. The work needs 1,000 hours of building. Team A, working the same hours as your product owner, redoes 10 percent of its output and spends 10 percent on coordination: 1,200 hours, total 120,000. Team B, with two shared hours per day and requirements that are still changing, redoes 40 percent and spends 25 percent on coordination and documentation: 1,650 hours, total 82,500.",[10,69,70],{},"Team B is still cheaper on paper. Now add the last term. Team B's version took four months longer because each question cost a day. If the system was meant to remove a manual process or open a sales channel, four months of that benefit is gone, and it never appears on the invoice.",[10,72,73],{},"Change the scenario to work with a complete, stable specification. Team B's rework drops to 12 percent and coordination to 12 percent: 1,240 hours, total 62,000, with no meaningful delay. Here the lower rate is a real saving.",[10,75,76],{},"The lesson from the arithmetic is that the rate matters most when the other terms are small, and they are small only for certain kinds of work.",[14,78,80],{"id":79},"what-actually-moves-the-hours","What actually moves the hours",[82,83,85],"h3",{"id":84},"shared-working-hours","Shared working hours",[10,87,88],{},"The time difference matters less than the number of hours per day when both sides are at their desks. With two shared hours, a question asked in your afternoon gets its answer the next morning, and a follow-up takes another day.",[10,90,91],{},"For stable, well-specified work, questions are rare and this costs almost nothing. When the team is still learning what to build while building it, questions come up hourly. Each one forces a choice between waiting and guessing. Waiting costs calendar time. Guessing is faster, and a share of the guesses will be wrong.",[82,93,95],{"id":94},"rework","Rework",[10,97,98],{},"Rework is output that functions correctly and solves the wrong problem, so it has to be done again. It is the largest hidden cost in distributed delivery and almost nobody tracks it. If a vendor cannot tell you roughly what share of delivered work comes back for changes, they are not measuring it.",[82,100,102],{"id":101},"the-documentation-burden","The documentation burden",[10,104,105],{},"When you cannot ask, you have to write. Some of that is good discipline. Written specifications, recorded decisions and clear acceptance criteria help any team. Beyond a certain point, though, you are running a documentation project next to the software project, and your most senior people spend their days writing instructions instead of making decisions.",[82,107,109],{"id":108},"turnover","Turnover",[10,111,112],{},"When an engineer leaves, a replacement needs weeks to become productive, wherever they sit. The damage is greater when knowledge is concentrated in a few people and little of it is written down. Ask about it directly, because average tenure on your kind of engagement varies a great deal between firms, in every region.",[82,114,116],{"id":115},"coordination","Coordination",[10,118,119],{},"Every additional location adds scheduled meetings, summaries, handoffs and one more place where a decision can sit waiting. Language and communication style count as well. A team that says \"yes\" to mean \"I heard you\" instead of \"I agree and it will be done\" will cause misunderstandings that surface as rework.",[14,121,123],{"id":122},"matching-the-model-to-the-work","Matching the model to the work",[10,125,126],{},"The useful question is not which model is better. It is which model fits the work in front of you.",[128,129,130,146],"table",{},[131,132,133],"thead",{},[134,135,136,140,143],"tr",{},[137,138,139],"th",{},"Kind of work",[137,141,142],{},"Good fit",[137,144,145],{},"Reason",[147,148,149,161,172,183,194,205,216],"tbody",{},[134,150,151,155,158],{},[152,153,154],"td",{},"Fully specified work with settled requirements",[152,156,157],{},"Offshore",[152,159,160],{},"Few questions arise, so limited overlap costs little and the rate advantage holds",[134,162,163,166,169],{},[152,164,165],{},"High volume of repetitive, similar tasks (test automation, data conversion, many similar screens or reports)",[152,167,168],{},"Offshore or nearshore",[152,170,171],{},"The effort of writing a precise specification is spread over many units",[134,173,174,177,180],{},[152,175,176],{},"Discovery, architecture and decisions with business stakeholders",[152,178,179],{},"Onshore, or nearshore with a full shared day",[152,181,182],{},"Questions are constant and need answers within the hour",[134,184,185,188,191],{},[152,186,187],{},"Systems holding regulated data under US rules",[152,189,190],{},"Often onshore, depending on contracts",[152,192,193],{},"Legal and contractual limits decide before cost does",[134,195,196,199,202],{},[152,197,198],{},"Production support and incident response",[152,200,201],{},"Whoever is awake during your business hours",[152,203,204],{},"During an outage, response time is the only metric",[134,206,207,210,213],{},[152,208,209],{},"A small team with moving requirements",[152,211,212],{},"Onshore or nearshore",[152,214,215],{},"Coordination cost would consume the rate difference",[134,217,218,221,224],{},[152,219,220],{},"Round-the-clock coverage",[152,222,223],{},"A deliberate mix",[152,225,226],{},"Multiple time zones become an asset when handoffs are designed",[10,228,229],{},"Most mid-sized companies have work in several of these rows. The expensive mistake is to pick one model for everything, usually on rate, and then find that the discovery work suffered or that simple volume work was overpaid.",[14,231,233],{"id":232},"when-the-law-or-the-contract-decides-for-you","When the law or the contract decides for you",[10,235,236],{},"For some work, location is a constraint to be checked before any cost comparison.",[10,238,239,242],{},[28,240,241],{},"Health data."," Under HIPAA, a vendor that handles protected health information for a covered entity is a business associate, and a subcontractor that handles that information for the vendor is a business associate as well. Each link in the chain needs a written agreement. This means an offshore team with access to production health data is workable only if it is explicit: the entities are named, the agreements are signed, and access is controlled and logged in a way that would hold up in an audit. If a team can read patient records while being absent from every one of those agreements, you have a compliance problem that an auditor will eventually find.",[10,244,245,248],{},[28,246,247],{},"Contractual residency clauses."," Many customer contracts, and many government and financial programs, state where data may be stored and from where it may be accessed. Some of them rule out foreign access entirely. Read your own customer contracts before you compare vendors, not after you have chosen one.",[10,250,251,254],{},[28,252,253],{},"A practical workaround."," Teams outside the US can often work productively without touching regulated data, using synthetic or de-identified datasets in development and leaving production access to a small onshore group. This has to be designed in from the start.",[10,256,257],{},"This section is general information, not legal advice. Have counsel confirm what applies to your data and contracts.",[14,259,261],{"id":260},"the-arrangement-that-fails-most-often","The arrangement that fails most often",[10,263,264],{},"The worst results I have seen do not come from offshore delivery as such. They come from a split: architecture is decided by one group in one country, the code is written by another group somewhere else, and neither group owns the result in production.",[10,266,267],{},"The architects are not present when their decisions meet reality. The developers implement designs they did not choose and cannot easily question. When the system fails at night, the people who understand why it was built that way are asleep, and the people who are awake do not have the authority to change it.",[10,269,270],{},"The fix is a rule about ownership more than about geography: the people who make the architectural decisions should also be the people who get paged when those decisions go wrong. A blended team works well when it is one team with shared ownership, shared channels and a shared rotation.",[14,272,274],{"id":273},"six-questions-that-make-vendors-comparable","Six questions that make vendors comparable",[10,276,277],{},"Put the same questions to every candidate, whatever their location. Precise answers tell you more than the rate card.",[279,280,281,287,293,299,305,311],"ol",{},[25,282,283,286],{},[28,284,285],{},"Which hours of the day will your team and ours both be working?"," Ask for clock times in your time zone. \"We are flexible\" is not an answer.",[25,288,289,292],{},[28,290,291],{},"When a developer has a question about a requirement, who answers it and how quickly?"," The reply should identify the person responsible and commit to a turnaround you can believe.",[25,294,295,298],{},[28,296,297],{},"How long do engineers typically stay on an engagement like this one?"," If the answer is vague, treat that as the answer.",[25,300,301,304],{},[28,302,303],{},"Who makes the architecture decisions, and do they write code on this project?"," If the designers and the builders are different groups, budget for the translation between them.",[25,306,307,310],{},[28,308,309],{},"Production fails at 2 a.m. our time. Who is called, and are they awake?"," This tells you whether support is a real capability or a contract clause.",[25,312,313,316],{},[28,314,315],{},"Who will be able to access our production data, from which countries, under which agreements?"," For regulated work this is the first question, not the last.",[10,318,319],{},"Specific answers to all six can only come from a vendor with real practice in this way of working. Give that more weight than a moderate difference in rate.",[14,321,323],{"id":322},"a-quick-way-to-run-your-own-comparison","A quick way to run your own comparison",[10,325,326],{},"For each proposal, write down four numbers next to the rate: shared hours per day, the expected rework share for this type of work, the weekly hours your own staff will spend on coordination and documentation, and the months to first usable release. Then recompute the total with those included. The ranking often changes.",[10,328,329],{},"Location also does nothing to the underlying size of the project. That is set by the systems to integrate, the data to migrate and the compliance regime in scope, and it applies to every team equally.",[14,331,333],{"id":332},"which-parts-of-your-work-need-to-sit-close-to-you","Which parts of your work need to sit close to you?",[10,335,336],{},"Tell Trivo what you are trying to staff. We will say plainly which parts need same-day answers from a team in your time zone and which can sit elsewhere, even if the honest conclusion is that another model fits better than ours.",{"title":338,"searchDepth":339,"depth":339,"links":340},"",2,[341,342,343,351,352,353,354,355,356],{"id":16,"depth":339,"text":17},{"id":49,"depth":339,"text":50},{"id":79,"depth":339,"text":80,"children":344},[345,347,348,349,350],{"id":84,"depth":346,"text":85},3,{"id":94,"depth":346,"text":95},{"id":101,"depth":346,"text":102},{"id":108,"depth":346,"text":109},{"id":115,"depth":346,"text":116},{"id":122,"depth":339,"text":123},{"id":232,"depth":339,"text":233},{"id":260,"depth":339,"text":261},{"id":273,"depth":339,"text":274},{"id":322,"depth":339,"text":323},{"id":332,"depth":339,"text":333},"Strategy","2026-10-12","The hourly rate tells you little about what a project will cost. How overlap, rework, turnover and compliance change the math for each delivery model.","md",{},true,"\u002Finsights\u002Fnearshore-offshore-onshore-cost",9,[366,367,368],"custom-software-cost-framework","evaluating-engineering-depth","hipaa-business-associate-agreement","operational-efficiency",[371],"custom-software",{"title":5,"description":359},"insights\u002Fnearshore-offshore-onshore-cost","da1S9wepLTSbzeAJEIw7kzLAxCN_1qLy_JmAjk9Ys_Q",[376,382,389,394,399,404,412,417,422,427,433,440,445,451,457,463,469,471,476,481],{"path":377,"title":378,"description":379,"category":357,"readingTime":364,"relatedServices":380,"date":358},"\u002Finsights\u002Fbuild-vs-buy","The License Fee Is the Small Number: A Working Guide to Build or Buy","Buying software is usually right, until the product sits on top of how you make money. How to sort capabilities, price the hidden costs and decide.",[371,381],"modernization",{"path":383,"title":384,"description":385,"category":386,"readingTime":364,"relatedServices":387,"date":358},"\u002Finsights\u002Fcloudflare-observability","The Cloudflare Signals You Need Wired Up Before Something Breaks","Cloudflare records plenty by default. Whether a person hears about a problem in time depends on choices made in a quiet week, not mid-outage.","Cloudflare",[388,381],"cloudflare",{"path":390,"title":391,"description":392,"category":386,"readingTime":364,"relatedServices":393,"date":358},"\u002Finsights\u002Fcloudflare-performance-tuning","After the Static Assets: Where Cloudflare Performance Is Actually Won","Default caching handles images, CSS and JavaScript. The larger gains sit in HTML, API responses, cache keys and origin trips that nobody tuned.",[388,371],{"path":395,"title":396,"description":397,"category":386,"readingTime":364,"relatedServices":398,"date":358},"\u002Finsights\u002Fcloudflare-waf-and-ddos","Managed Rules Know the Internet. Custom Rules Have to Know Your Application.","Cloudflare's managed WAF and DDoS rules stop generic attacks. Logins, APIs, bots and false positives still need rules written from your own traffic.",[388,371],{"path":400,"title":401,"description":402,"category":386,"readingTime":364,"relatedServices":403,"date":358},"\u002Finsights\u002Fcloudflare-zero-trust-and-integrity","Who Got In Versus What Is Running: Two Integrity Problems One Control Cannot Solve","Zero Trust verifies who reaches a system. Client-side script monitoring verifies what runs in the browser. They fail differently and need separate owners.",[388,381],{"path":405,"title":406,"description":407,"category":408,"readingTime":409,"relatedServices":410,"date":358},"\u002Finsights\u002Fcrm-adoption-and-training","Your CRM Passed Every Test and Nobody Uses It: A Diagnostic for Stalled Adoption","Low CRM adoption is rarely a training gap. How to tell whether the cause is screen friction, missing payback or management habits, and what to fix first.","CRM",8,[411],"crm",{"path":413,"title":414,"description":415,"category":408,"readingTime":409,"relatedServices":416,"date":358},"\u002Finsights\u002Fcrm-implementation-timeline","The Honest Calendar of a CRM Implementation: Five Phases and Where the Weeks Go","Provisioning a CRM takes a day. Making it the place your team sells from takes months. A phase-by-phase calendar, with the parts quotes tend to leave out.",[411,371],{"path":418,"title":419,"description":420,"category":408,"readingTime":364,"relatedServices":421,"date":358},"\u002Finsights\u002Fcrm-migration-checklist","CRM Migration Checklist: The Records Arrive, the Selling Process Gets Left Behind","A CRM migration is a process migration with a data load attached. What a plain export loses, how to choose a cutover, and a checklist for each stage.",[411,381],{"path":423,"title":424,"description":425,"category":408,"readingTime":409,"relatedServices":426,"date":358},"\u002Finsights\u002Fcustom-crm-vs-off-the-shelf","Should You Build Your Own CRM? Run the Build-or-Buy Test on Your Sales Process","Most of a CRM is a commodity you should buy. The question is whether the way you sell fits the platform's model, and what it costs when it does not.",[411,371],{"path":428,"title":429,"description":430,"category":357,"readingTime":431,"relatedServices":432,"date":358},"\u002Finsights\u002Fcustom-software-cost-framework","Estimate Before the Estimate: Sizing a Custom Software Budget on Your Own","You can't know the price before a quote, but you can know what drives it. Six cost drivers, a self-check worksheet and how to read a proposal.",10,[371],{"path":434,"title":435,"description":436,"category":437,"readingTime":364,"relatedServices":438,"date":358},"\u002Finsights\u002Fetl-vs-elt","Transform before or after loading? A practical ETL versus ELT decision for mid-sized teams","ETL or ELT is a question of where transformation runs and who pays for it. A practical way for a mid-sized team to choose, with the costs most plans miss.","Data",[371,439],"ai-automation",{"path":441,"title":442,"description":443,"category":357,"readingTime":431,"relatedServices":444,"date":358},"\u002Finsights\u002Fevaluating-engineering-depth","Ask About the Outage: How to Vet a Software Vendor's Real Engineering Ability","Portfolios and logos look the same from every vendor. The interview questions, artifacts and deal-breakers that show who has really run software in production.",[371,381],{"path":446,"title":447,"description":448,"category":449,"readingTime":431,"relatedServices":450,"date":358},"\u002Finsights\u002Fhipaa-business-associate-agreement","A BAA Is a Contract, Not a Badge: What Your Software Vendor Is Really Signing Up For","What a HIPAA Business Associate Agreement commits a software vendor to, what it leaves unproven, and what to ask and build before PHI reaches the system.","Compliance",[371,439],{"path":452,"title":453,"description":454,"category":449,"readingTime":455,"relatedServices":456,"date":358},"\u002Finsights\u002Fhipaa-technical-safeguards-checklist","Reading 45 CFR 164.312 Like a Design Document: HIPAA Technical Safeguards for Engineers","The five HIPAA technical safeguard standards mapped to concrete engineering decisions: identity, logging, integrity, authentication and encryption.",11,[371,381,388],{"path":458,"title":459,"description":460,"category":461,"readingTime":364,"relatedServices":462,"date":358},"\u002Finsights\u002Flegacy-erp-anticorruption-layer","The ERP stays as it is: building on a decades-old system through an anti-corruption layer","How to build new software on an old ERP without modifying it, using an anti-corruption layer: what goes inside, how to handle writes, when to skip it.","Modernization",[381,371],{"path":464,"title":465,"description":466,"category":467,"readingTime":431,"relatedServices":468,"date":358},"\u002Finsights\u002Fllm-in-production-confidence-thresholds","An LLM that proposes and a system that decides: thresholds, review and audit for production AI","Running an LLM in production without giving it autonomy: measured confidence, thresholds set by business cost, human review that works, an audit trail.","AI",[439,371],{"path":363,"title":5,"description":359,"category":357,"readingTime":364,"relatedServices":470,"date":358},[371],{"path":472,"title":473,"description":474,"category":467,"readingTime":364,"relatedServices":475,"date":358},"\u002Finsights\u002Frpa-vs-api-integration","Bots on the screen or calls to the API: where RPA earns its place and where it becomes debt","RPA and API integration solve the same problem at different layers. How to choose, what screen automation really costs, and how to run it safely if you must.",[439,371],{"path":477,"title":478,"description":479,"category":461,"readingTime":364,"relatedServices":480,"date":358},"\u002Finsights\u002Fstrangler-fig-modernization","Replace the legacy system in slices: a working guide to the strangler fig pattern","How to retire a legacy system piece by piece while the business keeps running: the facade, the first slice, parallel runs, and when the pattern fails.",[381,371],{"path":482,"title":483,"description":484,"category":357,"readingTime":431,"relatedServices":485,"date":358},"\u002Finsights\u002Ftwo-week-discovery-deliverables","Paying for a Plan, Not a Pitch: What Two Weeks of Discovery Owes You","A paid discovery should leave you with documents another team could build from. The five deliverables, the work behind them and the limits to expect.",[371,381],1792618973203]