Operating model
How we work together.
Here is how we agree the scope, work with your team and vendors, and hand over the finished work.
Process
From the first inquiry to handoff.
Tell me what you need
Send a short project inquiry with the systems involved, what needs to change, and any timing or budget constraints you already know.
Agree the right scope
I respond with clarifying questions and a direct view on whether the problem needs a live discussion, written assessment, implementation project, ongoing advice, or no engagement yet.
Larger work is scoped separately
A Technology Health Check, Infrastructure Roadmap and Implementation project, or Fractional Technology Advisory engagement has its own scope, deliverable, boundary, and price before kickoff.
Access is limited and intentional
I request only what is necessary for the agreed work. Shared access, named ownership, and revocable permissions are preferred to loose credentials.
Keep the work you commissioned
Health Checks produce reports and debriefs. Implementation produces roadmaps, working systems, documentation, handoff, and verification. Fractional advisory produces the agreed governance record. You keep the operating artifacts.
Procurement details
The questions buyers usually ask before a kickoff.
NDA and confidentiality
I sign NDAs when needed. Client systems, pricing, credentials, and vendor history are treated as operationally sensitive by default.
Access and permissions
The preferred model is least-privilege access, shared admin visibility where possible, and revocable permissions tied to the actual workstream.
Reporting cadence
Technology Health Checks end with a written report and debrief. Implementation uses agreed milestones and verification. Fractional advisory uses the governance cadence defined in scope. The Decision Session includes no written output.
Vendor coordination
I regularly work with accountants, agencies, SaaS vendors, and internal operators so the client is not stuck translating between six partially informed parties.
Language and coordination
I coordinate with Japan-side teams, vendors, and mixed operating contexts. Required working languages, translation, and document production are confirmed explicitly in scope rather than assumed.
Ownership after delivery
Clients keep the system decisions, documents, and operating logic. Ongoing help is available, but the work is not designed to trap you in dependency.
FAQ
Common engagement questions.
Do you sign NDAs?
Yes. For many clients that is standard. If access to internal systems, vendor pricing, or customer data is involved, confidentiality is treated as part of the normal engagement setup.
How do you handle passwords and admin access?
The preferred setup is shared access through proper permission layers, not loose credentials in email. I ask for the minimum access needed, and revocable access is always better than opaque handoffs.
Can you work with Japan-side teams and vendors?
Yes. Engagements can include global and Japan-specific tools, local vendors, and mixed operating contexts. Required working languages and any translation needs are confirmed explicitly during scoping.
Who owns the deliverables and documentation?
The client does. Reports, maps, operating notes, and handoff documents are part of what you are buying. The point is to make the business easier to understand and more durable, not more dependent.
More about the work
Need proof or a Japan-specific fit check?
If you are still deciding whether the work is credible or whether it fits a foreign-owned SME operating in Japan, start with these.