Category: Teams & delivery
-
Why your offshore team keeps changing people
Turnover on an offshore team is rarely malice. It is structural — and structures can be inspected before you sign. What to check.
-
Offshore, nearshore or onshore: comparing what a team actually costs
Hourly rate is the one number that reliably fails to predict what a team costs over three years. A more honest comparison frame.
-
The questions to ask an offshore development company before you sign
Eighteen questions that are awkward to answer if the underlying practice is not real — on people, work, exits and commercials.
-
How to change development vendors without stopping the roadmap
The repositories transfer in an afternoon. The context does not. A transition plan for teams replacing an existing development vendor.
-
From two engineers to twenty: scaling a startup org with a hybrid team
How Series A–C teams scale with a small in-house core plus a dedicated team — one culture, owned surfaces, and cheap insourcing later.
-
The first 90 days with a dedicated team: a playbook
A month-by-month playbook for the first 90 days with a dedicated team — what should happen, what to observe, and what to ask if you can’t.
-
Why Nepal — not India, not Eastern Europe, not Latin America
Nepal is missing from every outsourcing list. What that omission means for seniority and retention — and the trade-offs we concede honestly.
-
12 red flags to catch before you sign with an offshore team
Twelve pre-signature warning signs — pitch-team swaps, blended rates, vendor-held repos, exit penalties — and why they are incentive problems.
-
IP protection when outsourcing development: repos, contracts and jurisdictions
Structure beats clauses: why your repos and your cloud protect IP better than contract language — plus what the contract still has to do.
-
Time zones as a feature: follow-the-sun development for US teams
Kathmandu’s workday fits inside a US night. Hand off at your evening, review merged work before standup — if the delivery system is built for it.