Yes. Most engagements begin from "I don't know what the real problem is." The first consultation is free; we then agree on the scope and I quote from there.
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. In the first consultation we identify 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 mapping how the work actually runs 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. You can start with only the scope you need, far smaller than a typical 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.