— Offshore Development
Offshore Development from Kyoto, Japan
Japanese PM × Vietnam Team. We bridge Japanese clients and Vietnamese engineering teams with quality-focused PMs based in Kyoto.
Looking for the Japanese version? 日本語ページはこちら →
A real bridge between Japanese clients and Vietnamese engineers
Netsujo is a Kyoto-based engineering studio. For four years we have run cross-border product builds with senior partner teams in Vietnam — not as a staffing agency, but as the bilingual PM layer that makes offshore delivery feel close to a domestic Japanese team.
Whether you are a Japanese client looking to scale beyond Tokyo engineering supply, or an international client who wants quality-first delivery on a Japan-grade SLA, we run the same playbook: a Japanese PM owns the relationship, the spec, and the quality bar.
What you get
Four guarantees that define every Netsujo offshore engagement.
Japanese PM oversight
Bilingual PMs based in Kyoto translate intent — not just words. We write specs the way Japanese stakeholders expect them, then re-frame the same scope for engineers who think in English and Vietnamese.
"Language is the easy part. Intent is the hard part."
Senior Vietnamese engineers
Long-term partner teams in Hanoi and Ho Chi Minh City, vetted for production experience in React Native, Next.js, Solidity, and Cosmos SDK. No body-shopping, no rotating juniors.
"You meet the people who will actually write the code."
Cost optimization without compromise
Vietnam engineering rates land at roughly 20–40% of comparable Tokyo rates. We invest the savings back into review cycles, automated tests, and onsite visits — so quality stays at Japanese-domestic level.
"Cheaper headcount, not cheaper outcomes."
NDA and IP protection
Mutual NDAs in English and Japanese, IP assignment clauses written for cross-border contracts, and source-code escrow on request. Repositories live in your GitHub organization — never ours.
"Your code stays yours, from commit zero."
How we actually run an offshore team
Lessons distilled from four years of running cross-border builds — Kyoto to Hanoi, Tokyo to Ho Chi Minh City.
Onsite trust building
Our PMs travel to Hanoi and Ho Chi Minh City on a regular cadence. Sharing a meal with the team changes the texture of every remote standup that follows — and we have seen this pay back many times over.
"Trust starts in the same room. Then it scales over Zoom."
Code review across borders
We seed a code-review culture deliberately. Early on, Vietnamese engineers can find review comments intimidating; with patient, specific feedback they shift to proposing improvements themselves within weeks.
"Growth needs psychological safety — that part is universal."
Direct questions, plain English
The Vietnamese teams we work with are not shy about saying "I do not understand." When a Japanese spec gets vague, they push back immediately. We treat that directness as the strongest QA tool we have.
"Honest questions catch bugs earlier than any test suite."
Specs that survive translation
The real bottleneck is rarely language — it is the spec. Our PMs write requirements with the technical context baked in, so the same document reads correctly in Tokyo, Kyoto, and Hanoi.
"Remove the comprehension gap, not just the language gap."
Culture as a quality lever
Nine out of ten offshore failures we see come down to how the work is briefed. "Just build this" is never enough. Once the why is shared, comprehension — and quality — jump dramatically.
"Share the why, and the quality follows."
Incremental improvement over perfection
Our Vietnamese partners taught us that chasing perfection on day one breaks teams. Five points of improvement every sprint compounds into a higher ceiling than any one-shot quality push.
"Five points a sprint, every sprint, forever."
Team structure
A typical Netsujo offshore squad. We adjust the shape to fit the engagement, but every team includes a Kyoto-based PM as the single point of accountability.
Kyoto, Japan
Bilingual PM
Owns scope, schedule, and quality. Writes specs in both languages, runs sprint reviews, and is the only contact you need.
Hanoi / Ho Chi Minh City
Senior engineers
Typically 2–6 engineers per squad. Mid-to-senior level, working in Next.js, React Native, Solidity, Go, and Rust. English-fluent on the technical side.
Cross-team
QA & DevOps
Test engineering and CI/CD shared across squads. Every PR runs through linting, unit tests, and end-to-end checks before review.
Engagement & pricing
Indicative ranges for a Kyoto PM plus a Vietnam engineering squad. Final pricing depends on scope, stack, and team size. USD figures use approximate JPY 150 = USD 1.
2 weeks
Discovery sprint
JPY 600,000
~USD 4,000
Scope clarification, architecture sketch, and offshore staffing plan. Deliverable: written spec ready for build.
8–12 weeks
MVP build
JPY 4–8M
~USD 27,000–53,000
Cross-border squad with a Kyoto PM and 2–4 senior Vietnamese engineers. Weekly demos, automated CI, code review on every PR.
Quarterly
Long-term squad
JPY 2–4M / month
~USD 13,000–27,000 / mo
Dedicated team retained quarterly. Includes PM oversight, sprint planning, QA, and onsite visits twice per year.
Selected work
Cross-border projects delivered with a Kyoto PM and a Vietnam squad.
Real-world asset tokenization platform
End-to-end Web3 build for a Japanese real-estate operator: smart contracts, investor dashboard, and KYC workflow. Japanese PM in Kyoto, contract and frontend engineering in Vietnam.
Solidity · Next.js · Subgraph · Wagmi
Read the caseHR TechMobile app for a national HR-tech operator
React Native application delivered for one of Japan’s largest HR platforms. We owned spec translation, sprint reviews, and release engineering across a distributed team.
React Native · Expo · TypeScript · GraphQL
Read the caseNFT / SBTNFT and Soulbound Token issuance
Issuance platform and minting flow for a brand campaign. Smart contract design and audit prep led from Kyoto; contract implementation and frontend built in Vietnam.
Solidity · ERC-721 · ERC-5114 · Next.js
Read the caseFAQ
Japan and Vietnam are only two hours apart, so we share a working day. Our Kyoto PM joins the morning standup with the Vietnam team and a separate sync with the client. Specs, decisions, and review comments are written in English and Japanese; the PM is the single point of accountability.
Yes, when the engagement is built for it. We invest in written specs, mandatory code review, and automated tests. Most of our long-term clients report defect rates indistinguishable from their in-house teams.
Yes. We sign a mutual NDA in English or Japanese before sharing anything technical. We also handle IP assignment, escrow, and repository ownership in our standard contract.
You do. Repositories are created inside your GitHub organization (or AWS CodeCommit, GitLab, etc.). Our engineers are invited as collaborators and removed at the end of the engagement.
Frontend: Next.js, React, React Native, Expo. Backend: Node.js, NestJS, Go, Rust. Web3: Solidity, Cosmos SDK, Symbol, Subgraph, Foundry, Hardhat. Infra: AWS, Vercel, Cloudflare, GitHub Actions.
Most clients begin with the two-week Discovery sprint. It is the cheapest way to test how we write specs, how the Vietnam team works, and whether our cadence matches yours.
From Kyoto, World-Class.
Bridging fields, building futures. Tell us about your project — we will reply within one Japanese business day with a Kyoto-based PM as your first point of contact.