Stack Audit
Use this when nobody can tell you what the stack costs, what owns what, or why simple changes keep breaking.
Best fit 8 to 50 person SMEs in Japan with tool sprawl, reporting drag, or no clear internal owner for the stack.
The problem
Most SMEs in Japan don't know what they're running.
You have Slack, Kintone, a Google Workspace, some spreadsheets, a CRM someone set up three years ago, and about six other things that were added over time without a plan. Nobody knows what's connected to what. Nobody knows what's actually being used. Nobody knows what it's costing.
The Stack Audit maps all of it. You get a clear picture of your full operational footprint: what you have, what it costs, how it fits together, and where the friction is. Most clients are surprised. A few are alarmed. All of them end up with a plan.
What's included
What gets clearer fast.
Tool inventory
Complete list of every tool, subscription, and service your business pays for or depends on. Including the ones you forgot about.
Workflow mapping
How work actually moves through your organization: not the org chart version, the real version. Where things slow down, get dropped, or require manual correction.
Cost analysis
What you're paying, broken down by tool category. Where you're paying twice for the same capability. What you're paying for that nobody uses.
Friction points
The specific places where time and money are being lost. Ranked by impact so you know what to fix first.
Written report
A clear, prioritized document you can actually act on. Findings, recommendations, and next steps. Written for operators, not engineers.
60-minute debrief call
We walk through the findings together. You ask questions. You leave knowing exactly what to do next.
How it works
Four steps. Two weeks. One clear picture.
Kickoff call
30 minutes. We establish scope, share access, and align on what a successful audit looks like for your situation.
Discovery
I map your tools, workflows, and costs. I'll ask for documentation, billing access, and a working session with whoever knows how things actually work.
Report delivery
Written audit report sent via email. Includes findings, prioritized recommendations, and a clear summary of your full stack.
Debrief call
60 minutes to walk through the report together. We cover the key findings, you ask questions, and we discuss next steps.
Good fit if
- You're paying for tools you don't fully understand or use
- Work keeps falling through the cracks between systems
- You're growing but your operational setup hasn't kept up
- Something is costing more time than it should but you can't pin down what
- You want a clear baseline before making any infrastructure decisions
Not a fit if
- You already have a clear, documented picture of your stack
- You have an internal IT team handling this already
- You're looking for software development or engineering work
Questions
Common questions about the Stack Audit.
What do I need to prepare before the audit?
A list of the tools you currently use, your billing statements or invoices for those tools, and 30 to 60 minutes with a key team member who knows how work flows day to day. That's it.
Do you work with businesses that don't have an IT team?
Yes, that's the typical client. Most SMEs in Japan don't have dedicated IT staff. The Stack Audit is designed to make sense to operations owners and managing directors, not engineers.
What happens after the audit?
You get a written report and a 60-minute debrief call. From there, you decide what to act on. Some clients implement changes themselves. Others move to an Infrastructure Build or an ongoing retainer. There's no obligation beyond the audit.
Do you work in Japanese?
Yes. I'm based in Tokyo and work with Japanese-speaking teams. Reports can be delivered in English or Japanese depending on your preference.
How is pricing determined?
Starting from $1,000. Final pricing depends on the size and complexity of the business. We confirm scope and price before any work begins. Most clients recover the cost inside 30 days.
Need procurement details first?
Need proof or procurement detail before you buy the audit?
These pages cover the outcome layer, the operating model, and the Japan-specific context behind the work.
Need a clean read before you spend more?
Start with the decision session. If the problem is structural, the next move is the full audit before another tool, migration, or hire compounds the mess.