How engagements work
How we work together.
Every engagement follows the same five steps, from a short note to a handover you keep. Scope and price are agreed in writing before any work starts.
From the first note to handover
- 01
Tell me what needs to change
- You send
- A short note on the systems involved, what is not working, who it affects, and any deadline or budget you already know.
- I do
- I read it and reply within 48 hours with questions or a suggestion.
- You get
- A direct answer on whether I can help, and where to start.
- 02
Pick the smallest useful stage
- You send
- Answers to my questions, and anything that shows the current setup.
- I do
- Recommend one stage: a Decision Session, Diagnostics, a Digital Baseline project, Ongoing Stewardship, or no engagement yet.
- You get
- A clear recommendation, with the reason for it.
- 03
Agree scope and price in writing
- You send
- Confirmation of what is in and out of scope.
- I do
- Write down the deliverable, the boundaries, the working languages and the price, plus tax, before any work starts.
- You get
- A fixed scope you can approve internally.
- 04
Grant only the access the work needs
- You send
- Named, revocable access through proper admin roles, never passwords by email.
- I do
- Work with your staff, accountant, agencies and vendors so you are not translating between them.
- You get
- Progress you can see, with milestones for project work.
- 05
Keep everything you paid for
- You send
- Time for a debrief or handover session.
- I do
- Hand over the report, the working systems, the documentation and the logins, then remove my own access unless you retain me.
- You get
- A business that runs without depending on me.
What each stage leaves you with
Prices, formats and who makes the changes are compared on the Services rate card.
- Decision SessionA 45-minute live discussion. No written follow-up.
- DiagnosticsA written report and a debrief.
- Digital BaselineA working foundation, documented and handed over.
- Ongoing StewardshipMonthly administration of the stack, with priorities set together.
- Operational ExpansionNew tools, workflows and people brought onto the foundation.
Terms of the work
The questions buyers usually ask before a kickoff, answered up front.
- §1
Confidentiality
I sign NDAs when needed. Client systems, pricing, credentials and vendor history are treated as confidential by default.
- §2
Access and permissions
Least-privilege access, shared admin visibility where possible, and permissions that can be revoked when the work ends.
- §3
Reporting
Diagnostics end with a written report and debrief. Project work uses agreed milestones and a final check. Ongoing Stewardship follows the cadence set in scope.
- §4
Vendors and partners
I work directly with accountants, agencies, SaaS vendors and internal staff, so one person holds the whole picture.
- §5
Language
Working languages, translation and document formats are agreed in scope rather than assumed.
- §6
Emergency action
If I reasonably believe your systems face an active or imminent security threat, I may make low-risk, reversible protective changes without waiting for approval: enabling authentication, rotating credentials, applying security updates, adjusting email-authentication or DNS records, or suspending compromised accounts. I tell you within 24 hours what changed and why, and reverse any change on request unless that would reopen the threat. This never covers deleting your data or changing how your services work.
- §7
Ownership
You own the deliverables, the documentation, the accounts and the decisions. Ongoing help is available, but nothing is built to lock you in.
Common 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.