Bring the real problem
Start with the outcome, not the software shopping list.
The useful first message is simple: what needs to happen, who owns the consequence, what currently gets in the way, and what failure costs. NULLWORKS can work outward from there.
System / workflow problem
Describe the current process, desired outcome, actors, evidence, authority, exceptions, and known failure conditions. Screenshots, documents, recordings, and ugly real-world details are more useful than polished diagrams.
Partnership / research
For institutional, technical, research, or Japan-related conversations, describe the system or question worth exploring. A useful relationship does not need to begin as a sales engagement.