About Intel Studio
A Tokyo practice built around the quiet work of checking compliance reporting applications.
Why we exist
Supervisory filings stand or fall on the applications that assemble them. Intel Studio was formed in Tokyo to give compliance and finance teams an independent set of eyes on those applications — before an examiner, statutory auditor, or board committee does.
We are not a software vendor and we do not sell a reporting product. Our craft is fieldwork: sitting with report owners, tracing evidence, and writing findings that a practical team can act on.
Origin
The practice began after repeated engagements where reporting packs looked orderly on the surface while override logs, late adjustments, and undocumented mapping changes sat unexamined. Clients needed someone who understood both the filing calendar and the habits people form inside a reporting application.
Working from Shinjuku keeps us close to the institutions and professional services firms that live on those calendars.
How we approach an audit
- Start from the filing the application is meant to support, not from a generic control catalogue
- Prefer sampled evidence over screenshots of policy pages
- Separate application behaviour from organisational workaround
- Write in plain language so non-technical owners can own the remediation
People
Engagements are led by practitioners with backgrounds in financial control review, compliance operations, and application assurance. We bring in language support or specialist counsel only when a client asks and the scope warrants it.
Values that show up in the work
Independence — we do not implement the systems we audit.
Proportion — findings are sized to filing risk, not theatrical severity.
Clarity — memoranda name screens, owners, and dates.
Respect for calendars — we plan around filing windows, not our convenience.