“I understand it” is not “I built it”
Seminars end at comprehension. But a workflow only changes when someone has actually built the thing that replaces it — with their own hands, on their own data.
We embed with the team, not the org chart
Which number has to move, for whose decision, by when. We settle that first — then build it with the two-to-five person team that actually owns the problem. Company size is not the point. A division inside a global firm and a company of five are the same unit to us. After three months what remains is not a slide deck; it is an agent that has already finished its work before Monday morning.
Weekly analysis effort
15hrs 5min
99.4%of the weekly roll-up removed
Every client sorted into four quadrants, automatically
Open the one closest to your work — all six are live and clickable.
The problem
Seminars end at comprehension. But a workflow only changes when someone has actually built the thing that replaces it — with their own hands, on their own data.
Every company’s real work is held together by undocumented judgement calls. A generic template cannot encode the exception that your team handles every Thursday.
A tool built entirely by a vendor is a tool nobody inside can extend. Six months later it is quietly abandoned — and the budget is gone.
So we work the other way around: your people build it, we sit next to them until it runs.
Why us
Software has a role called the Forward Deployed Engineer — a strong engineer who embeds inside the client’s workflow and rebuilds it from within, so that one person’s judgement leverages the whole organisation. What AI adoption is actually short of is the business-side equivalent.
Carried the number
Sales leadership at a Western tech company, with the revenue and the loss on the same sheet. So we do not close a report with “we removed some hours.” We push it to which number moved, and by how much.
Close to the data
Careers built next to the analytics and the digital stack. The hard part of automation is not generating an answer — it is knowing when the answer is not good enough to act on. That judgement only comes from having had to act on it.
Across industries
Business lead roles across several industries rather than a single vertical. It means that on an unfamiliar workflow we already have a hypothesis about where the waste collects — usually at the handoffs nobody owns.
So our work does not stop at swapping a tool in. We rebuild the workflow from the marketing and business layer, and then reconnect the hours freed and the accuracy gained to the investment decision they were supposed to serve. That last connection is the part that usually goes missing.
How we work
We sit in on the actual task — the one people call “a knack” or “something only they can do” — and translate it into steps an AI can hold.
Not a lecture. Your person drives the keyboard; we sit beside them. The goal of week one is a single small thing that visibly runs.
This is where we differ from training. Every week we hunt the reason it broke, and fix it. Demos survive one day; this survives Mondays.
We finish when your team can add the next agent without us. Templates, prompt libraries and the decision log stay with you.
Selected work
Client names are withheld under confidentiality. Everything below was actually built and delivered. Figures under “scale of the saving” are the projections agreed with the client when the work was scoped, not audited results. Prices live in one place only — see “how we work together” below.
Descriptions only go so far. These six actually run — open whichever is closest to your work.
Overseas subsidiary · Consumer electronics · Marketing
Payback 5–10 months, then the saving repeats every year
Social media services company · approx. 50 employees
Payback The assembly work stopped recurring — every month, from then on
Professional association · accounting & tax
BtoB manufacturer · Communications & marketing
Fee ¥1,000,000 — three weeks, three sessions, nothing after
New business development · nine concurrent projects
Fee ¥1,000,000 — three weeks, three sessions, nothing after
Investment
One-shot · fixed price
¥1M Flat. No monthly commitment, no retainer attached.
Ask about the one-shot buildIf it turns out that a build is not the honest answer for you, we say so in the first session and stop there.
Everything below is for teams who want the second, third and tenth one built by their own people.
Entry
¥100k – ¥300k
Half a day to a full day. We look at the actual work and come back with a specific answer on what AI changes — and what it does not. Deliberately not free.
Core
¥3M – ¥6Mover 3–6 months
We work alongside your two-to-five person team, on your real data, until they run without us — then stay long enough for it to hold.
Weekly at the start, monthly once they are running. The density is meant to fall — that drop is the result we are aiming for.
Build
¥3M – ¥8M
PoC through production. When building it for you is the honest answer, we build it — and hand over the parts your team should own.
Embedding
¥200k – ¥500k / month
After hand-over, the phase most projects skip. We keep what was built in daily use as the work changes around it: monthly review, a channel for “is this worth doing?”, and what actually changed in the tooling this month.
Pricing works backwards from the hours that disappear. On a recent project the design removed roughly 700 hours of manual work over two years — on the order of $35,000.
We do not discount. If the budget doesn’t fit, we cut scope and say so plainly — a discounted engagement is one we cannot staff properly, and you would feel it by week three.
Fit
Saying this up front saves both of us a month.
Team
Founder & CEO
Hitotsubashi UniversitySonyDeNAHakuhodo
For now, the founder is the producer on every engagement. That is a function of how many we can run at once, and it is not a promise we can keep indefinitely.
A career spent on the side of the table where the number has to move: carrying a revenue line, reading the data underneath it, and growing the business on what the data said. That is why these sessions are not training. We start from the business question — which number, whose decision, by when — and the agent only comes up after that.
LinkedIn →The bench
Not a fixed org chart. We pick the background the engagement actually needs. Company names are withheld under confidentiality, but the following sit within a phone call.
Implementation lead
Designs the templates and prompt libraries clients keep after hand-over. Runs the hands-on half of every session — the part where the thing has to actually run.
Infrastructure & review
Sets up the working environment before session one, keeps the “public data only” boundary enforced, and reviews each program from outside the delivery team.
We deliberately keep the permanent headcount low and compose the team per engagement, so the experience in the room matches the problem in the room rather than whoever happened to be free.
Field notes
We publish what worked, what didn’t and the numbers behind it on note (in Japanese). Details are generalised to protect clients.
FAQ
It is the normal case, not the exception. Our overseas program was delivered end-to-end on public data only, with no access to internal systems, official accounts or company data. We design the boundary with your security team before session one.
Our participants are marketers, accountants and business leads — not engineers. The sessions are built for people who work in natural language. If your team can write a clear brief, they can build an agent.
Yes — that is our home ground. We have run a full multi-week program across a time zone in Japanese and English, for a Japanese-affiliated team overseas with local non-Japanese members participating.
The first session ends with something running. Whether it is worth keeping is a question for week three — and we will tell you honestly if the answer is no.
None by default. We pick per engagement and tell you the running cost before you commit. If the honest answer is a ¥3,000/month tool instead of a build, we say so.
Get in touch
No deck, no pitch. We will tell you within the call whether this is something we should work on together — including when the answer is no.
Try it · synthetic data
Six samples — switch between them
Every company name, figure and note in this dashboard is synthetic. It is the shape of what we build, not a client’s data.