How the work is approached
Industrial teams usually already have a system of record and a way of working. The software has to sit beside that. It has to be readable by the people who will live with it. Automation stays inside a workflow someone can still describe.
Language models are used to write software, and sometimes to operate a narrow part of it. They are not treated as a substitute for the person who owns the process.
This website
tasunke.com is the public face of the practice. It describes the kind of work on offer and how to start a conversation. Client names, process designs, and project records stay in private correspondence.
Working with Nigel Wood
A first conversation is enough to tell whether there is a fit. Bring the workflow in ordinary language, the systems it touches in general terms, and what a useful change would look like for the people who run it. Sensitive material can wait until there is an agreed way to handle it.