Yes. Most engagements begin from "I don't know what the real problem is." The initial operations diagnosis (¥30,000) helps map your workflow and structure the issues.
We first identify the repeated decisions and tasks in your workflow. Embedding AI (ChatGPT, Claude, etc.) into report generation, data classification, inquiry handling and so on cuts manual work sharply. The diagnosis proposes concrete places to apply it.
It depends. I may decline build-only work that ignores operation and real usage. To avoid "built and abandoned," I often propose a diagnosis first.
I handle design, build and operation alone — no spec drift from a game of telephone. Eight years on the restaurant floor lets me prevent "rolled out but unused" at the design stage. Starting at ¥30,000, you can begin far smaller than a multi-million-yen SIer quote.
Yes. I care less about size than about whether we can think and improve together.
Yes. If the structure and background are unclear, I start by mapping and analyzing it. Depending on the situation I may propose a redesign.
As a rule, for projects I designed or built — because I value making operational judgments with a full grasp of the design intent.
System development is per project. Operational support is a monthly contract, continued or ended as the situation calls for.
Minor adjustments, sometimes yes. Routine or high-volume task work is out of scope.