Nearshore 9 min
Outsourcing Web Design to Bosnia: What You Need to Know
The 11 questions every buyer should ask any nearshore agency before signing — and what the answers reveal.
Summary
Nearshore web development means outsourcing to a team in a geographically proximate country with timezone overlap — for UK and DACH clients, typically Eastern Europe (Poland, Czech Republic, Bosnia, Serbia, Croatia). Offshore means outsourcing to a team in a geographically distant location, typically India, the Philippines, or Ukraine. The headline rate difference is real: offshore teams often quote $15–40/hr versus nearshore rates of €55–90/hr. The total cost difference is much smaller — and in complex or long-duration projects, the nearshore option is frequently less expensive in total when rework, communication overhead, management time, and failure rates are factored in.
Headline rates tell you nothing. The real comparison is the total cost of engagement — and that number looks very different from the invoice.
A note on bias: I am the founder of a nearshore web agency. I have an obvious interest in the conclusion of this analysis. I will try to give you the actual numbers anyway — because clients who choose us for the wrong reasons end up disappointed, and clients who choose us with accurate expectations become long-term partners.
The Definitions — What Nearshore and Offshore Actually Mean
The terminology in outsourcing is used loosely. For this comparison:
Nearshore: A vendor located in a country within 1–3 time zones of the client, typically sharing cultural alignment and European working conventions. For UK and DACH clients: Poland, Bosnia, Serbia, Croatia, Czech Republic, Romania, Bulgaria. Rates: €45–90/hr for senior-level work at established agencies.
Offshore: A vendor located in a country 4+ time zones from the client, with significant cultural distance and limited working-day overlap. For UK and DACH clients: India, Pakistan, the Philippines, Bangladesh, Vietnam. Rates: $15–40/hr for comparable seniority levels at reputable agencies; $5–15/hr at lower-tier marketplace vendors.
Onshore: A vendor located in the client's own country. UK agency: £85–200/hr. DACH agency: €100–180/hr.
The rate arbitrage between onshore and nearshore (30–45%) and between onshore and offshore (60–80%) is real. The question is whether that rate arbitrage translates into equivalent cost savings at the project level — and the answer, consistently, is no.
The Headline Rate Comparison
The numbers most people look at when comparing nearshore and offshore:
| Level | Onshore (UK) | Nearshore (Eastern EU) | Offshore (India/Philippines) |
|---|---|---|---|
| Senior developer / designer | £100–180/hr | €60–90/hr | $25–45/hr |
| Mid-level developer / designer | £75–120/hr | €40–65/hr | $15–30/hr |
| Junior developer | £50–85/hr | €25–40/hr | $8–20/hr |
| Project manager | £80–140/hr | €45–70/hr | $20–40/hr |
On headline rates alone, offshore appears to offer 60–80% savings versus onshore, and nearshore offers 30–45% savings. A 500-hour web application project quoted at £100/hr onshore (£50,000) would cost approximately €45,000 nearshore or $20,000 offshore. This comparison is meaningless without accounting for effective hours and the additional management, communication, and rework costs the client bears.
The Total Cost of Engagement
Total Cost Formula
Total Cost =(Quoted hours × hourly rate)
+ Communication overhead
+ Rework hours
+ Management time
+ Failure premium
Each of these variables behaves differently across nearshore and offshore engagements.
Effective hours and rework rate
The offshore development projects we have inherited as rescue jobs share a consistent pattern: the delivered codebase requires significant rework before it can be extended or maintained. Not because offshore developers are incompetent — many are highly skilled — but because brief interpretation without strategic challenge produces technically correct work that solves the wrong problem, and communication latency means misunderstandings propagate across multiple development cycles before they are caught.
Industry data from Deloitte, McKinsey, and Standish Group outsourcing research consistently shows that offshore IT projects have rework rates 1.5–2.5× higher than equivalent onshore or nearshore projects. For a web project, approximately 20–40% of total offshore development hours are spent correcting work done incorrectly the first time.
Adjusting the 500-hour example for a 30% rework rate: the effective offshore cost becomes $20,000 ÷ 0.70 = $28,500 in real output terms. With management time and communication overhead, the fully loaded cost is typically $32,000–$38,000 for a project quoted at $20,000.
Communication overhead
A nearshore engagement with full working-day timezone overlap (CET to CET) has communication overhead of approximately 5–8% of project hours. A well-managed offshore engagement with an 8–10 hour timezone gap has communication overhead of 12–20%, because every communication event is asynchronous and misunderstandings accumulate before they are corrected.
For a 500-hour project:
- Nearshore communication overhead: ~35 hours at €70/hr ≈ €2,450 client-side time cost
- Offshore communication overhead: ~80 hours at client internal rate — even at £60/hr for an internal stakeholder, this is £4,800 in management time that does not appear on the vendor invoice
Failure premium
Offshore project failure rates are significantly higher than nearshore. A 2023 Standish Group study found that only 29% of IT projects delivered with offshore teams were classified as "successful" (on time, on budget, with stated requirements met). The partial failure rate was 50%. The failure rate (abandoned or requiring complete restart) was 21%.
A project that fails and requires a restart costs not just the restart price — it costs the original vendor payment, the delay to market (opportunity cost), and the management time invested in the failed engagement. For a £30,000 website project with a 12-month revenue expectation, every month of delay has a calculable cost.
The Six Hidden Costs of Offshore
01 — Discovery deficit
The discovery gap
Offshore teams operating on thin margins do not invest time in discovery — the strategic questioning phase that challenges the brief and surfaces problems before they become committed development. A discovery session that catches a structural brief problem might cost 10 hours at €70/hr (€700). The same problem caught in development week 8 costs 40–80 hours of rework.
02 — Specification vacuum
The brief-to-spec gap
Offshore development operates from detailed functional specifications — documents that describe every state, every edge case, and every interaction before a line of code is written. Most UK and US clients do not have functional specifications for their web projects. The gap between brief and specification is filled, in offshore engagements, by assumptions. Assumptions that are wrong produce code that must be rewritten. In nearshore engagements with cultural proximity and communication fluency, the specification gap is bridged through conversation.
03 — English proficiency tax
Communication friction at every level
English proficiency at the developer level is high in top-tier offshore markets. At the project management and account management level — the people the client communicates with daily — quality is more variable. A client who sends a clearly written brief and receives a response that requires interpretation and follow-up questions is paying a time cost in every communication cycle. This cost is invisible in the vendor quote. It is very visible in the client's calendar.
04 — Timezone productivity lag
The 18-hour bug cycle
A bug discovered by a UK client at 3 PM on a Monday is reported to an Indian team at 8:30 PM IST — after their business day ends. It is addressed the following morning IST — approximately 5:30 AM UK time. The client sees the fix at approximately 9 AM UK time on Tuesday. That is an 18-hour lag on a same-day urgency item. For an e-commerce site processing £10,000/day with a checkout failure, that lag has a calculable revenue cost of approximately £7,500. Nearshore teams in CET overlap with UK working hours almost completely — same-day resolution is routine, not exceptional.
05 — Codebase handover problem
The inheritance cost
At the end of an offshore engagement, the client receives a codebase. Whether that codebase is maintainable — documented, structured for extension, using conventions a new developer can understand — varies significantly. Offshore codebases delivered at lower rate points frequently use opaque custom approaches, minimal inline documentation, and dependency choices that make long-term maintenance difficult. Inheriting an undocumented, unconventionally structured codebase from an offshore vendor is one of the most common triggers for a website rebuild — a cost that appears nowhere in the original offshore project budget.
06 — Quality assurance gap
The QA delta
Structured QA — cross-browser testing, accessibility audit, Core Web Vitals benchmarking, structured data validation, form testing — requires dedicated time that lower-cost offshore engagements do not budget for. Delivering a website that passes basic function testing is a different deliverable from delivering a website that passes WCAG 2.1 AA, scores 95+ on Lighthouse, and has all schema validated. The QA work that nearshore agencies build into their process is often simply absent in offshore deliverables — producing a site that works but does not perform.
The Quality Differential — What the Data Shows
In our own analysis of websites inherited from offshore vendors for remediation, the WCAG 2.1 AA failure rate was 91% — with an average of 14 failures per site, versus an industry average of 6 for domestically built sites.
The pattern is not random. The most common offshore-inherited failures are:
- Missing or meaningless alt text on all product and portfolio images
- Colour contrast failures throughout — the entire colour scheme chosen without WCAG testing
- No skip navigation link — a 20-minute implementation omitted entirely
- Custom UI components with no ARIA roles — menus, modals, and accordions built without screen reader compatibility
- No visible focus indicators —
outline: nonein the CSS base styles, never re-implemented
These are not complex failures. They are baseline requirements that structured QA processes catch in 30 minutes. They are absent because the offshore engagement did not include structured QA.
When Offshore Makes Sense Despite the Risks
Offshore development produces good outcomes in specific conditions:
- Well-specified projects. If you have a complete functional specification — a document that describes every user story, every state, every edge case, and every integration requirement — offshore teams with strong development skills can execute it competently. The specification removes the communication gap. Most businesses do not have functional specifications for their web projects.
- Commodity work. Data entry, content migration, routine maintenance, testing against a defined test plan — tasks where the definition of "done" is unambiguous and verifiable. These are tasks where the hourly rate arbitrage delivers genuine savings without the risk premium.
- Experienced in-house management. A business with an internal technical project manager who understands software development, has experience managing offshore teams, and can quality-assure the output independently can significantly reduce the failure risks described above.
- Non-critical timelines. Projects without hard external deadlines, where a 3-month delay is inconvenient but not commercially damaging, can absorb offshore delivery variability more easily.
When Nearshore Is the Structurally Correct Choice
- Complex projects without functional specifications. Most web projects. The brief-to-specification gap is bridged by communication — and communication works best with timezone overlap and cultural proximity.
- Projects where post-launch accountability matters. A 90-day SLA with a nearshore agency in a compatible timezone is a meaningful contract term. With an offshore vendor who operates with an 8-hour lag and significant cultural distance, it is a weaker commitment in practice.
- Projects where design quality is a commercial differentiator. B2B professional services websites, law firms, private healthcare practices — sites where the quality of visual design directly affects conversion. Eastern European design talent, partly because of its proximity to Western European design markets and the DACH-influenced precision standards, consistently produces higher-quality visual work at equivalent rates.
- Projects for regulated industries. ADA compliance, HIPAA-aware architecture, GDPR compliance, SRA advertising standards — these require not just technical implementation but understanding of the regulatory context. A nearshore team with active experience in Western markets has accumulated this context through client work.
The Decision Framework — 5 Factors
Score each factor from 1 (strongly favours offshore) to 5 (strongly favours nearshore):
| Factor | Score 1 — Offshore | Score 5 — Nearshore |
|---|---|---|
| Specification completeness | Complete functional spec exists | Brief only; spec to be developed collaboratively |
| Communication sensitivity | Commodity / clearly defined task | Complex / evolving / requires strategic input |
| Timeline tolerance | Delay acceptable | Hard external deadline |
| Internal management capacity | Experienced technical PM in-house | Non-technical founder or team |
| Post-launch accountability | Low — single project engagement | High — ongoing relationship required |
5–10
Offshore is a viable option with appropriate risk management.
11–17
Either could work; nearshore reduces risk at a cost premium you should evaluate.
18–25
Nearshore is the structurally correct choice. The cost premium is lower than the risk premium of offshore.
Most mid-market business website projects score 15–22 on this framework. The "obvious" choice of offshore for its cost advantage is not supported by the economics when the full cost model is applied.
The Hawd Design Position in This Landscape
We are a nearshore agency. Our rates are €65–85/hr — approximately 35–45% below comparable UK and US agency rates, and approximately 2–3× above typical offshore rates. We charge what we charge because the work we deliver requires senior professionals operating to a structured, documented process with post-launch accountability built in.
If you have a complete functional specification, an experienced internal technical project manager, and a non-time-sensitive delivery timeline — an offshore team might serve your project well and save you meaningful money. We would rather tell you that than take a project we are not the right fit for.
If you have a brief and a commercial objective, need a partner who challenges the brief before executing it, and need a website that performs to professional standards without a rebuild in 18 months — we are the right choice.
Ready to compare costs for your project?
Send us a brief description — we'll respond with a detailed cost comparison and our honest assessment of whether nearshore is the right fit for your specific project.