/
13 min readThe 45-Minute Time Zone: What a Kathmandu Team Looks Like From New York
Nepal's clocks sit 45 minutes off the hour and at least 9 hours 45 minutes ahead of New York, so a full Kathmandu working day fits between the end of your day and the start of the next. The article works through the clock math for the four main US time zones, one night hour by hour, the holidays to plan around and the numbers behind Nepal's growing tech sector.
13 min readWho Owns the Code? IP, NDAs, and Contracts for Offshore Software Work
Paying an offshore team is not enough to make you the owner of the code it writes. In the US, the UK and Australia, the usual route is a written, signed assignment, and Nepal's rule in favor of whoever paid does not clearly settle the case of a foreign client. This explains how ownership passes from engineer to vendor to you, what an NDA covers, and seven clauses to check before you sign.
15 min readNepal vs India for Software Teams: What the Pitch Gets Right
Founders hear that Nepal is cheaper than India, keeps engineers longer and speaks better English. We test each claim against public data. English scores favor Nepal, the time zones are level, and the cost and retention claims have no public data behind them. What to check before choosing, and when India is the better choice.
14 min readHow to Vet an Offshore Development Partner: 12 Questions That Get Honest Answers
A sales call rewards rehearsed answers. These twelve questions ask an offshore development partner for named people, written artifacts and the rules for when things get decided, so the answer has to come from how the team actually works. Three of them are uncomfortable on purpose, and the honest answer to those will not sound reassuring.
7 min readOverlap Hours Are the Real Currency of Offshore Work
Buyers compare offshore vendors by hourly rate. What actually predicts delivery speed is overlap hours — the real-time window both teams are online together.
Newsletter
New writing, when there is something worth sending
Occasional notes on architecture and delivery practice — the same things we write about here, sent when a piece is published. Roughly once a month, never more.