Anything where the parts have started to outrun the plan. A product that has grown past the point one person can hold it in their head, a system that behaves differently once real users touch it, or an idea a group shares but cannot agree how to begin.

With a conversation and whatever you already have, drawings, spreadsheets, notes, a half-built prototype, the history of what you tried before. We map what exists and charter the issues. That part comes before anything gets built.

No. Much of the work is explaining a difficult thing plainly enough that the people who own the decision can make it. If you can describe the expected outcomes, that is enough to start.

I am one person, so work happens in sequence and I cannot always promise a start next week or to cover an emergency. Anything a licensed professional has to certify is outside what I can do alone, so building a rocketship will need others in the room. Where I am useful on those projects is getting the idea far enough that the certified party can price it and sign it off, because the specification and the boundaries will be clear.

An annual release cycle is the target. Each release is designed to showcase a working complex system rather than a simple accessory.