Open role
Last updated: May 2026
Business Developer, JP/EN
Open relationships with Japanese companies that need custom software, APIs, AI workflows, LLM features, and fixed-scope PoCs.
JP/EN
language
Bilingual business communication with Japanese buyers and the delivery team.
B2B
market
Software, operations, product, and DX decision makers in Japan.
PoC
entry offer
Paid audits, fixed-scope PoCs, MVP sprints, and retainers.
Remote
model
Japan-facing collaboration with a senior European delivery team.
Buyer Guide
What Business Developer, JP/EN helps buyers confirm
Business Developer, JP/EN covers the operational details that matter when a Japanese company works with an overseas software partner. The practical questions are contract, invoicing, timezone, language, data handling, meeting rhythm, and handover.
For Japan B2B buyers, technical capability is only one part of trust. The engagement also needs to be explainable to procurement, security, management, and business users. Urbano DX documents those assumptions before a sprint begins.
Use this page as an internal briefing before the first conversation. NDA, SOW, billing details, data assumptions, and weekly demo rhythm can then be confirmed per engagement.
Confirm
Contracting, invoicing, timezone, language, data, and handover.
Japan-facing support
Bilingual summaries, weekly demos, and procurement-friendly documentation.
Before kickoff
NDA, SOW, data assumptions, meeting rhythm, and owners.
What you will do
You will identify, qualify, and develop opportunities with Japanese companies that have real software or AI workflow pain. The role is consultative rather than volume-based.
- Open conversations with software, operations, and DX decision makers
- Qualify use cases, budget timing, data readiness, and decision owners
- Prepare bilingual follow-ups, meeting notes, and proposal context
- Help buyers understand paid audits, PoCs, MVP sprints, and retainers
What good looks like
A good opportunity is not just a warm lead. It has a business owner, a workflow, a sample-data path, a delivery constraint, and a decision that a first sprint can unlock.
- Clear buyer problem
- Relevant budget or timing signal
- Named owner and next meeting
- Useful notes for technical scoping
- Calm follow-up in Japanese and English
Who fits
Best for someone comfortable with consultative B2B sales, Japanese business etiquette, and technical services that require careful scoping.
- Japanese business communication
- English working communication
- Interest in software, APIs, and AI workflows
- Patient qualification style
- Comfort with written follow-up
What you will not do
This is not generic lead scraping or pressure sales. The offer works when buyers trust the diagnosis and understand the scope.
- No vague DX promises
- No forced platform upsell
- No pretending every AI idea is ready
- No handoff without context
Role rhythm
1
Find fit
Identify Japan companies with software, API, AI workflow, or PoC pressure.
2
Qualify
Confirm use case, owner, timing, data readiness, risk, and decision path.
3
Frame
Prepare bilingual notes that help technical scoping start cleanly.
4
Advance
Move the buyer toward audit, PoC, sprint, or a clear no-go decision.
Buyer FAQs
Is this a sales role?
Yes, but consultative. The goal is to open qualified conversations and help buyers understand software and AI delivery scope.
Is Japanese required?
Yes. Strong Japanese and English business communication are required.
How should I apply?
Send a short introduction, relevant experience, language background, and LinkedIn or CV to [email protected].
Scope the first sprint
Bring the app, API, LLM feature, or AI workflow you want to test. We will turn it into a clear first-sprint scope.
Start a conversation