The problem worth solving
The right starting point is not a feature list. It is a clear account of who does what, what information they need, where hand-offs break down and what a useful first release must handle.
What the work can include
How we approach it
We map the real workflow, agree the smallest useful scope, then build and review in stages. Access, hosting, data migration and ongoing support are discussed before implementation—not left as surprises.
Who should start a conversation?
Someone responsible for the process, system or operational outcome—ideally with a colleague who understands the day-to-day work. You do not need a finished specification. A clear description of what is happening now is enough to begin.

