You hired a "web developer." A few weeks into the project, you notice something: you've never actually spoken to the person writing your code. Every question goes to an account manager. Every fix takes three, four, sometimes six days to come back. And when an answer finally arrives, it doesn't quite address what you asked — because by the time your question reached the person who could actually answer it, it had already passed through one or two other people first.
This setup is more common than most small business owners realize, and it's almost never disclosed upfront. You think you're hiring a developer. What you're often actually hiring is a relay: a local point of contact who finds someone else — a freelancer, or a dev shop, frequently overseas — to actually build and maintain your site. The local person keeps the relationship and the invoice. The person doing the technical work is someone you'll probably never talk to directly.
Why This Model Exists (And Why It's Not Automatically a Scam)
Subcontracting isn't inherently dishonest. Most small agencies aren't staffed to do every specialty in-house, and pairing sales/account management with a technical partner is a completely normal business structure — I've written before about how this plays out with monthly marketing retainers specifically, including the ownership and security problems it can create. This post is about a narrower, more immediate issue: what happens to your communication — your speed, your clarity, your ability to just ask a question and get a real answer — when a relay sits between you and the person actually doing the work.
That gap is what most owners feel first, long before they ever think to check who owns their domain.
Why You're Actually Waiting Days for an Answer
The delay isn't random, and it isn't personal. It's structural. When your account manager has to relay a question to a subcontractor — especially one working across a large time-zone gap — a question that would take five minutes to resolve in a direct conversation can take days to come back around.
Here's what that actually looks like in practice: a clarifying question that gets answered in about five minutes when the person asking and the person building are on a call together can take roughly two days to resolve when it has to cross a 10–12 hour time-zone gap with no working-hours overlap — and that's before it's even passed through a middleman relaying it in both directions. Industry data compiled by Gitnux puts time-zone differences behind delays in around 60% of offshore development projects, with an average schedule impact of about 31%.
It's not just the clock, either. In surveys of organizations running offshore development work, communication difficulties are named the single biggest challenge by 61% of respondents, ahead of cost, quality, or technical skill — with differences in working style and business culture flagged by another 51%, according to a Market.us report on the offshore software development market.
It's Not About Where the Developer Is
To be clear about what this post is and isn't saying: there's nothing wrong with a developer working overseas, and plenty of excellent developers do. The problem isn't geography or skill — it's the number of people a message has to pass through before it reaches someone who can actually act on it, and whether you were ever told that chain exists. A direct relationship with an overseas developer who answers you personally beats an undisclosed relay to a local-sounding "team" every time.
What research on software project failure consistently shows is that unclear requirements are one of the top predictors of a project going sideways — and every extra hop a request takes through another person relaying it is another chance for it to get less precise, not more.
The Markup Nobody Shows You
Here's the part that surprises people most: the relay usually isn't cheaper. It's often priced like a fully local, fully staffed team, even though the actual technical work is being paid for at a fraction of that rate.
A quality U.S.-based developer or small studio typically bills somewhere in the $100–$200/hour range. Agencies that quietly offshore the technical work often still bill clients $60–$100/hour — while paying the actual developer doing the work in the neighborhood of $18–$40/hour in parts of Asia or $25–$50/hour in Eastern Europe. That's not a small spread.
This is standard practice in the white-label agency world, and it's openly taught as a pricing strategy: industry guides for agencies commonly recommend marking up subcontracted or white-label web work by 30–60%, with many agencies landing in a 60–80% markup range, and some premium-positioned shops pushing 100% or more on smaller projects. A frequently cited starting rule is simple — bill the client 50% more than the subcontractor is actually paid.
None of that markup is inherently wrong on its own — sales, project management, and coordination cost real money and take real time. The issue is that the client is often paying close to full boutique-agency pricing for what amounts to a coordination service, without ever being told that's what they're buying, or getting the direct access that price would normally include.
The Cost Isn't Just Slower — It's Also Riskier
A relay doesn't just slow you down. It adds real risk that a direct relationship doesn't carry.
- Rework eats the savings. Roughly 27% of outsourced code typically requires rework, per industry data compiled by Gitnux — and when it does, someone has to absorb that extra time. It's rarely the agency's margin.
- The relationship itself has decent odds of falling apart. Dun & Bradstreet's Barometer of Global Outsourcing research found that 20–25% of outsourcing relationships fail within two years, and roughly half fail within five. When the agency and its subcontractor part ways, the client is usually the last to find out — because there was never a direct relationship to preserve in the first place.
- Cost-cutting on the subcontractor isn't always in your interest. Aggressive 25–40% budget reductions in offshore engagements are linked to elevated failure rates in industry analysis of offshore software deals. The cheapest subcontractor available isn't always chosen to benefit you — sometimes it's chosen to protect the agency's margin.
Put together, that's the real cost of the relay model: not just a slower answer to your email, but less accountability if something goes wrong, and less visibility into whether the people building your site are even still on the project six months from now.
What Direct Access Actually Buys You
Working directly with the person building your site isn't just a nicer experience — it changes the mechanics of the project. Comparisons of freelance/direct-hire development versus agency-relay setups consistently point to the same advantages: communication that doesn't have to pass through an intermediary, faster iteration because there's no internal handoff process to wait on, and a level of personal accountability that's hard to fake when your name is directly on the work.
That's the model I run at Forged. I'm Kevin, and I write every line of every client site myself — no bench of subcontractors, no offshore hand-off, no account manager standing between you and the code. When you email or call, you're talking to me: the person who actually opens the project and fixes it, not someone relaying your message to whoever's turn it is. It's also part of why I can keep client sites running lean with no unnecessary monthly overhead — there's no second company's margin baked into your invoice.
Questions Worth Asking Before You Sign Anything
If you're evaluating a developer or agency right now, these are worth asking directly — and worth being suspicious of a vague answer to:
- Will I have direct email or phone access to the person actually writing the code? Not "you can always reach us" — specifically the person doing the technical work.
- What's your typical response time, in writing? A real number, not "quickly" or "same day, usually."
- If I report a bug at 9am, who sees it first — you, or someone you have to forward it to? This tells you how many hops exist between you and a fix.
- Where is the person doing the technical work physically located, and what hours do they keep relative to mine? There's no wrong answer here — the point is whether they'll actually tell you.
- What happens to my support if that arrangement ends? If they can't answer this clearly, they probably haven't thought about it either.
My Take
I'm not arguing that every agency is hiding something, or that offshore developers are a red flag — plenty of talented people build great software across every time zone there is. What I am arguing is that the chain of people between you and your code is something you're entitled to know about before you sign a contract, not something you're supposed to discover three weeks in when a simple fix takes a week to come back.
If you're already working with someone and answers are taking days, you're not being unreasonable for wanting to know why. Ask who actually touches your code. Ask how many people a request passes through before it gets answered. If the answer makes you uncomfortable, that discomfort is data — not something to talk yourself out of. (For what it's worth, if you ask me that question, I'm the one answering it — not checking with anyone first.)
Want to talk to the person who'd actually be building your site, before you sign anything? Reach out and let's have that conversation directly — no account manager required.