What I do
Buy the right level of intervention.
Start with the decision session if you still need clarity. If the stack is the real problem, the next move is the audit. Builds, retainers, category-development work, and field production only come after there is a clear reason to move.
Best fit
Owner-led or ops-led SMEs in Japan where the stack is already interfering with revenue, reporting, onboarding, or delivery.
- Global and Japan-specific tools mixed together
- Founder or operator acting as the integration layer
- Enough complexity that another workaround will cost more later
Need procurement details first?
Need proof before you pick a lane?
These are the pages buyers usually want before they commit: selected results, the engagement model, and how the work fits foreign-owned SMEs and market-entry projects operating in Japan.
Stack Audit
Use this when nobody can tell you what the stack costs, what owns what, or why simple changes keep breaking.
What you walk away with
- A full picture of tool sprawl, dead spend, and hidden dependency
- Where work stalls, gets re-entered, or relies on one person remembering everything
- What to kill, keep, or rebuild first before more money disappears
- A written plan you can hand to staff, vendors, or leadership
This is the cheapest way to stop guessing before another software purchase, hire, or migration makes the mess more expensive.
Infrastructure Build
Use this when the current setup is already slowing hiring, sales, onboarding, or delivery and patching it again would be a waste.
What changes in the rebuild
- Tool sprawl gets collapsed into a stack your team can actually operate
- Handoffs, approvals, reporting, and automations stop depending on Slack improvisation
- Sales, ops, and delivery systems get rebuilt around how the business really runs
- You keep the runbooks and ownership after the cutover
Good fit if
- You've outgrown your current setup but don't know what to replace it with
- You have a specific tool migration (e.g. moving off spreadsheets)
- Your team is growing and workflows haven't caught up
This is for teams that already know the stack cannot be saved with another workaround and need the system rebuilt properly.
Ongoing Management
Use this when the stack already matters and nobody inside the company has time to keep vendors, workflows, access, and reporting stable.
What stays off your plate
- Vendor renewals, tool drift, and cost creep stop being an afterthought
- Broken workflows and silent automation failures get caught and handled
- New tools get evaluated before they become another layer of chaos
- You get one operator who knows the stack and can work the problem fast
How it starts
All retainer clients start with a Stack Audit. This ensures the system we're managing is sound and I know the full picture before taking ongoing responsibility.
Retainers start after the audit because inherited chaos is not management. First the system gets understood, then it gets owned.
Category Development and Sales Enablement
Use this when a product, supplier network, or niche category needs to become understandable, trustworthy, and sellable before a distributor, buyer, or chef will move.
What this can include
- Market or category brief: buyer objections, demand signals, competitor context, and recommended first move
- Supplier scouting and vetting: criteria, shortlist, outreach notes, risk flags, and introduction rules
- Sales enablement: bilingual one-pagers, product notes, objection handling, tasting notes, and buyer-facing copy
- Pilot support: tasting/event structure, feedback capture, launch content, and next-step recommendation
Good fit if
- You need more than a website page: the category itself needs explaining
- The value depends on trust, provenance, sourcing standards, or chef/buyer education
- You want a fixed sprint first, or an external category advisor on retainer
This is the right lane for distribution, specialty-food, regional-product, and niche-market work where the commercial problem is making the offer legible enough to sell.
Media Production
Use this when a product, place, event, campaign, or regional project needs clear photo, video, written context, and distribution support.
What the package creates
- Photography, video, field notes, interviews, product context, and location context
- A clearer story for websites, launches, listings, investor materials, editorial packages, and social campaigns
- Editing, posting, web page support, cross-page placement, and social distribution
- Assets that make the offer easier to understand before someone commits attention, time, or capital
Good fit if
- The value depends on atmosphere, story, product quality, local context, or future use
- You need one operator thinking about media, copy, strategy, and distribution together
- The project sits at the intersection of media, commerce, hospitality, regional development, food, culture, or real estate
The two-day, two-night minimum gives the site enough time to be captured properly, with room for arrival, scouting, primary production, and return travel.