A flat white costs several times as much in Manhattan as it does in Johannesburg. Same drink, same skill behind the machine. Nobody looks at the Johannesburg price and assumes the coffee is worse — they understand, without being told, that they're looking at a different cost of living, not a different cup.
We sell software the same way, and people's instincts work less well. We deliver enterprise-grade systems at a fraction of the going US rate, from South Africa, and the most common quiet reaction is: what's the catch? It's a fair question, so here's the honest answer. There's no catch. There's an exchange rate.
Why the price is structural
The gap isn't a discount we're offering. It's the shape of where we are. Four things make it, and none of them is "we charge less because the work is worth less."
- The currency. We earn in rand and bill in dollars and pounds. A rate that reads as a bargain to a New York buyer is a strong professional income here. The distance between those two numbers is the exchange rate doing its work — not a markdown on the quality.
- The cost base. Salaries, premises, the whole cost of running a capable team sit against a lower cost of living. It costs less to deliver the work here, so it costs you less to buy it. The arithmetic is on the input side, not the output.
- The clock. South Africa runs an hour or two ahead of London and shares its afternoon with New York's morning. You get a working day that overlaps both — real-time conversation, not a hand-off to the far side of the planet that loses you a day on every round trip.
- The talent. The engineering pool here is deep and largely international in standard, much of it already building for clients abroad. Skill is the one thing that isn't discounted in any of this. It's the constant, not the variable.
This isn't a discount. A discount is quality you trade away for a lower price. An exchange rate is the same quality on different ground — and mistaking one for the other is the error that costs good buyers good suppliers.
The instinct that gets it wrong
The reflex that says "cheaper must mean worse" is a useful one in most of life. It protects you from the dodgy bargain. It just misfires across a currency border, because it can't tell the difference between a supplier cutting corners and a supplier standing on different ground.
We're not asking anyone to switch that instinct off. We're asking them to point it at the right target. Don't check the rate — check the output. The honest test is the one we'd apply to any supplier at any price, anywhere: can they show you a working system they built, running in the real world, and explain how it holds up when something goes wrong? A firm that passes that test in Cape Town passes it. A firm that fails it in California fails it. The postcode was never the signal.
The honest part
The same currency gap that lets a serious firm offer real value also gives cover to shops that are cheap and not much else — from the outside the rate looks similar, and a buyer who hasn't looked closely can't tell them apart. That's a real risk, and pretending otherwise would be the salesy move. The defence is boring and it's the right one: judge on shipped work and references you can actually call. Geography doesn't pass that test for you, in either direction.
So the position, plainly: we charge what we charge because of where we stand, not because of what the work is worth. The standard is the New York standard. The rate is the South Africa rate. Those two facts are allowed to sit in the same sentence, and the buyers who understand why tend to end up well ahead.
For the technical reader
The time-zone claim, precisely: South Africa is UTC+2, year-round, with no daylight saving. That puts us one hour ahead of London in its summer and two in its winter — close enough to share effectively a whole working day. Against US Eastern time we're seven hours ahead, so our afternoon is New York's morning: a standing overlap of a few hours every day for live calls, with the rest of our day landing as overnight progress before the US is back online. The "follow-the-sun" handoff that costs distributed teams a full day per iteration mostly doesn't apply.
On currency risk: we quote fixed-price in the client's currency, so the exchange-rate exposure sits with us, not the buyer. The rand is volatile, and that volatility cuts both ways — it's part of why the dollar-denominated rate looks the way it does, and it's a cost we carry rather than pass on mid-engagement. A weak local currency is no unmixed good for the people living inside it; imported tools and hardware cost more here too. We're describing an arbitrage, not a free lunch.
What doesn't cross the distance is genuine on-site presence — work that needs someone physically in your building every day. For that, distance is a real cost, and we'll say so. For software that's built and operated remotely, which is most of what we do, the distance is a few hours of clock offset and nothing more. The discriminator, as ever, is the one from the body: ask what they've shipped, and ask to watch it run.