About

Auditors who stay with the evidence, not the jargon

Software Hub Audit Co. grew out of repeated requests from regional firms that needed application findings written in language directors and application owners could share without a translator for “control frameworks.”

Audit practitioner reviewing notes during a client workshop

Origin

Rooted in Miyagi practice

Our office address sits in 昭三町, 宮城県. Much of our early work came from manufacturers and distributors around Sendai that ran critical applications with thin internal audit coverage. Those first engagements taught us to respect change freezes around Golden Week and fiscal year-end, and to schedule evidence requests around the people who actually close the books.

We remain a specialist practice focused on the audit of applications. We do not sell software, monitoring retainers, or product licences.

Quiet office workspace used for writing audit findings

People

Who you will meet

Portrait of lead auditor Kenji Morita

Kenji Morita

Lead auditor. Former internal audit manager for a Tohoku industrial group. Owns scope letters and findings workshops.

Portrait of senior reviewer Aya Fujimoto

Aya Fujimoto

Senior reviewer. Specialises in access sampling and change evidence. Drafts remediation roadmaps with named owners.

Portrait of engagement coordinator Hiroshi Tanabe

Hiroshi Tanabe

Engagement coordinator. Schedules interviews, tracks evidence requests, and keeps external review calendars honest.

Working approach

Plain findings, named owners

We write observations so an application owner can see the evidence reference, the risk in operational terms, and a credible fix window. Severity ratings exist to prioritise — they are not a substitute for narrative.

Values we hold: independence from vendors whose products we review, respect for confidential commercial data, and refusal to inflate findings to justify longer engagements.

See how an engagement runs
Findings workshop with application owners